- Can I use ezsystems/ezplatform-admin-ui directly in a Laravel project without Symfony?
- No, this package is a Symfony bundle for eZ Platform and isn’t natively compatible with Laravel. However, you can integrate it via API-driven approaches (REST/GraphQL), iframes, or micro-frontends. Laravel’s Eloquent and Symfony’s Doctrine require custom synchronization layers if shared data access is needed.
- What’s the easiest way to embed the eZ Admin UI in Laravel?
- The simplest method is to serve the eZ Admin UI as a sub-application under a Laravel route (e.g., `/admin`) using a reverse proxy like Nginx or Apache. Alternatively, embed it as an iframe or use Laravel’s middleware to proxy requests to the Symfony-based admin interface.
- How do I handle authentication between Laravel and eZ Platform?
- For shared authentication, use OAuth2, OpenID Connect, or a centralized identity provider like Keycloak. Alternatively, sync sessions via Redis or implement a custom auth bridge. Avoid mixing Laravel’s auth system with Symfony’s security component directly, as they’re incompatible.
- Does ezsystems/ezplatform-admin-ui support Laravel’s Eloquent ORM?
- No, this package relies on Doctrine ORM (Symfony’s default). To use it with Laravel, you’d need to build an API layer (GraphQL/REST) or create a custom abstraction layer to translate between Eloquent and Doctrine models, which adds complexity.
- What Laravel versions are compatible with this package?
- Laravel version compatibility isn’t direct, but integration is possible with Laravel 8.x–10.x via API contracts or proxy setups. The package itself targets Symfony 5.4+ and eZ Platform v2+, so ensure your Laravel app can communicate with Symfony’s ecosystem (e.g., via HTTP clients or microservices).
- Are there Laravel alternatives to eZ Platform’s admin features?
- Yes, for content management, consider Spatie’s Laravel Media Library or Nova for admin panels. For workflows, use Laravel’s built-in task scheduling or packages like Spatie’s Activity Log. However, eZ Platform offers enterprise-grade CMS features (e.g., content structure, multilingual support) that may lack direct Laravel equivalents.
- How do I handle routing conflicts between Laravel and Symfony?
- Delegate `/admin` routes to the eZ Admin UI via a reverse proxy (Nginx/Apache) or Laravel middleware that forwards requests to the Symfony application. Avoid overlapping routes in Laravel’s `routes/web.php` to prevent conflicts with Symfony’s kernel.
- Can I use Livewire or Inertia.js with ezsystems/ezplatform-admin-ui?
- Indirectly, yes. Expose eZ Platform’s backend via a GraphQL or REST API, then consume it in Livewire/Inertia.js components. The eZ Admin UI itself is Vue.js-based (Symfony UX), so hybrid setups would require careful UI isolation to avoid CSS/JS conflicts.
- What’s the licensing impact of using this package in Laravel?
- The package is dual-licensed under Ibexa BUL (requires an eZ Platform Enterprise subscription) **or** GPL-2.0. If you’re not using eZ Platform commercially, GPL-2.0 applies, but ensure your Laravel app’s license aligns. Commercial use without a subscription violates the BUL terms.
- How do I test the integration between Laravel and eZ Platform?
- Test API endpoints (GraphQL/REST) with Laravel’s HTTP tests or Postman. For UI integration, use Laravel Dusk or Selenium to verify iframe/embedded workflows. Mock Symfony services in Laravel tests if using a proxy layer. Focus on auth flows, data synchronization, and edge cases like concurrent edits.