Weave Code
Ibexa RichText Extension, including the RichText FieldType.
Frequently asked questions about Fieldtype Richtext
- Can I use ibexa/fieldtype-richtext directly in a Laravel project without Ibexa DXP?
- No, this package is not standalone. It requires Ibexa DXP (formerly eZ Platform) installed as a dependency. Laravel lacks native support for Ibexa’s fieldtype system, so direct integration would need custom middleware or API bridges.
- What Laravel versions does this package support?
- This package does not natively support Laravel. It’s designed for Ibexa DXP, which is built on Symfony. Laravel compatibility would require a custom integration layer, likely targeting Laravel 8+ due to Symfony’s modern dependencies.
- How does Ibexa’s XML-based richtext storage conflict with Laravel’s database?
- Ibexa stores richtext in XML format (e.g., `ezcontentobject_attribute` tables), while Laravel uses relational databases like MySQL. Direct integration would require schema mapping or a separate Ibexa instance to avoid conflicts.
- Are there Laravel-native alternatives to Ibexa’s richtext fieldtype?
- Yes. For Laravel, consider TinyMCE/CKEditor (via `beberlei/doctrineextensions` or `laravel-editor`), Markdown (e.g., `spatie/laravel-markdown`), or packages like `spatie/laravel-medialibrary` for media-rich content.
- How do I test Ibexa’s richtext fieldtype in a Laravel environment?
- Testing requires a hybrid setup: Deploy Ibexa DXP alongside Laravel, then use Laravel’s HTTP clients (e.g., Guzzle) to interact with Ibexa’s API. Mock Ibexa’s XML responses in unit tests or use Docker for isolated environments.
- What’s the best way to migrate existing Ibexa content to Laravel?
- Audit your Ibexa XML schema first, then map content types to Laravel Eloquent models. Use a script to parse Ibexa’s XML and insert data into Laravel tables, or expose Ibexa via GraphQL/REST and fetch content dynamically.
- Does this package work with Laravel’s Eloquent ORM?
- No. Ibexa’s fieldtype system is incompatible with Eloquent. You’d need custom accessors/mutators or a bridge package to translate Ibexa’s XML-based fields into Eloquent attributes.
- What are the licensing risks of using Ibexa’s GPL-licensed code in Laravel?
- Ibexa’s package is dual-licensed (GPLv2 + proprietary Ibexa BUL). If you use GPL-licensed components, your project must comply with GPL terms. For commercial use, a valid Ibexa DXP subscription is required.
- Can I use Ibexa’s richtext editor (CKEditor/TinyMCE) without the full DXP?
- Yes. Strip Ibexa’s dependencies and use the editor standalone via CDN or npm. Laravel packages like `laravel-editor` or `unisharp/laravel-ckeditor` offer similar functionality without Ibexa’s overhead.
- How do I handle multilingual content with Ibexa’s richtext in Laravel?
- Ibexa excels at multilingual support, but integrating it with Laravel requires API calls or a custom bridge. For pure Laravel, use packages like `spatie/laravel-translatable` or `laravel-localization` for multilingual fields.
Weaver
How can I help you explore Laravel packages today?