Weave Code
At a glance
Frequently asked questions about Content Forms
- Can I use ibexa/content-forms directly in a Laravel project without Ibexa DXP?
- No, this package requires Ibexa DXP as a hard dependency. It’s designed for Ibexa-based systems and won’t work standalone in Laravel. For Laravel-only projects, consider alternatives like Laravel Collective or Symfony Form standalone.
- How do I install ibexa/content-forms in a Laravel project?
- You can’t install it directly via Composer without Ibexa DXP. First install Ibexa DXP following their [official guide](https://doc.ibexa.co/en/latest/install/), then add `ibexa/content-forms` as a dependency. Laravel projects must isolate Ibexa dependencies in a microservice or API layer.
- Will this package work with Laravel 10+?
- No, this package is not natively compatible with Laravel. It relies on Symfony’s kernel and event system, which Laravel doesn’t use out of the box. You’d need to bridge Symfony components (like `symfony/form`) or use Ibexa via REST/GraphQL.
- How do I handle Ibexa’s Content/User objects in Laravel?
- Ibexa’s Content and User objects are incompatible with Eloquent. You’ll need to build custom adapters or use Ibexa’s repository pattern via API calls. For example, fetch data via Ibexa’s GraphQL API and map it to Laravel models manually.
- Are there breaking changes in v5.0.9 that affect Laravel integration?
- No, the switch from PHPUnit assertions to Webmozart assertions in v5.0.9 is internal to the test suite and doesn’t impact runtime. Just ensure your Laravel project requires `webmozart/assert:^1.11` to avoid conflicts.
- Can I use Ibexa-specific form types (like ezimage) in Laravel?
- No, Ibexa-specific form types (e.g., `ezimage`) aren’t compatible with Laravel’s Symfony Form integration. You’ll need to create custom Laravel form components or replace them with native Laravel alternatives like file upload handlers.
- What’s the best way to integrate Ibexa forms with Laravel in production?
- Use a hybrid architecture: host Ibexa DXP as a microservice and consume its forms via REST or GraphQL. This decouples Laravel from Ibexa’s dependencies while allowing form data synchronization. Avoid direct kernel integration.
- Do I need to rewrite existing Laravel form logic if migrating to Ibexa?
- Yes, Ibexa’s form system is fundamentally different. Start by auditing your forms, then either rebuild them in Laravel using Symfony Form standalone or expose Ibexa forms via API and adapt responses to Laravel’s validation system.
- Are there Laravel-specific documentation or tutorials for this package?
- No, the package is Ibexa-centric with no Laravel-specific guides. You’ll need to rely on Ibexa’s [official docs](https://doc.ibexa.co/) and community resources for Symfony-Laravel bridging techniques, like using `symfony/form` as a standalone component.
- What alternatives exist for form integration in Laravel if Ibexa isn’t required?
- For pure Laravel projects, consider `laravelcollective/html` (legacy) or `symfony/form` standalone for advanced forms. For CMS-like features, explore Laravel Nova, Filament, or Spatie’s Laravel packages, which are natively compatible without Ibexa dependencies.
Weaver
How can I help you explore Laravel packages today?