Weave Code
Content Browser Ibexa Laravel Package
netgen/content-browser-ibexa
Netgen Content Browser Ibexa integrates the Netgen Content Browser with Ibexa, providing a fast, flexible interface for browsing, searching, and selecting content from your Ibexa repository. It connects the browser’s UI to Ibexa’s content model, making content discovery and reuse easier for editors...
Netgen Content Browser & Ibexa DXP integration
Frequently asked questions about Content Browser Ibexa
- Is netgen/content-browser-ibexa a Laravel package?
- No. It is a Symfony/Ibexa bundle that connects the Netgen Content Browser backend to Ibexa's content, location, and search services. There is no Laravel service provider, Eloquent integration, or Blade UI. In a Laravel estate, treat it as an editorial-side Ibexa tool consumed headlessly, not as an application dependency.
- How do I install netgen/content-browser-ibexa?
- Install it with Composer in an Ibexa project, register the bundle after IbexaBundle and NetgenContentBrowserBundle, and configure the Content Browser adapter to use the Ibexa backend. Because version compatibility is not clearly documented, pin your Ibexa, Symfony, and PHP versions and validate in a sandbox first. Confirm bundle registration order and configuration against a real Ibexa installation rather than relying only on the README.
- Which Ibexa DXP versions and PHP/Symfony combinations are supported?
- The available context does not establish a published, tested compatibility matrix. Ibexa has moved through multiple Symfony and PHP release lines, and this shim has no visible dependents that would prove coverage. Verify the supported Ibexa DXP, PHP, and Symfony combinations with a timeboxed spike on a pinned sandbox before committing to it.
- Can I use netgen/content-browser-ibexa directly in a Laravel application?
- Not directly. The package depends on Ibexa's content repository model and Symfony bundle integration, so porting it into Laravel is not the intended path. The realistic pattern is a separate Ibexa deployment with this package installed CMS-side, consumed by the Laravel application through a headless or API integration.
- How does it connect the Content Browser to Ibexa content and locations?
- It acts as a pluggable Ibexa content provider for the Netgen Content Browser, bridging the browser's item provider API to Ibexa's ContentService, LocationService, and SearchService. That lets editors browse and search content items and locations, then resolve selected items for use in fields and editors. The value is the editorial find-and-reuse workflow, not framework-level functionality.
- Does it respect Ibexa permissions, languages, and multisite semantics?
- This needs explicit confirmation in your environment. A security-adjacent risk is whether the browser honors Ibexa's content-level access control instead of querying with elevated privileges. Test real content types, locations, languages, siteaccesses, and restricted editor accounts; a permission bypass here should be treated as a finding, not a minor bug.
- What license does netgen/content-browser-ibexa use, and is GPL-2.0 a problem?
- The context identifies GPL-2.0 as a material licensing risk. Copyleft obligations can attach if the combined work is distributed, which may be disqualifying for a proprietary DXP product without legal sign-off or alternative commercial terms. Have Legal review the distribution model and ask whether a commercial license is available before adoption.
- Is netgen/content-browser-ibexa actively maintained and safe for production?
- Adoption signals are weak: zero stars, zero dependents, and no observable community or patch flow. The package is also subordinate to both Ibexa's release line and the upstream Netgen Content Browser lifecycle, so every meaningful change becomes a three-way compatibility exercise. Treat vendor or internal ownership as the support path and pilot it before relying on it in production.
- What are the alternatives to using this Ibexa content browser adapter?
- First evaluate Ibexa's native browsing and search tooling to determine whether the gap is editor ergonomics or a genuine capability void. Alternatives include building a custom content-finder integration, using a supported commercial arrangement with Netgen, or keeping Ibexa as a headless CMS and building the editorial workflow around that boundary. Do not choose the package before confirming it solves a real editorial gap.
- How should I test netgen/content-browser-ibexa before adopting it?
- Run a timeboxed spike on a pinned Ibexa sandbox, not a README review. Validate bundle registration, adapter configuration, browse and search behavior, item resolution, permissions, multilingual content, and multisite siteaccess handling with realistic editor accounts. Also confirm what upstream Content Browser maintenance looks like and whether this repository is a generated read-only split, because fixes may belong upstream.
Weaver
How can I help you explore Laravel packages today?