Weave Code
Ezplatform Richtext Laravel Package
ezsystems/ezplatform-richtext
eZ Platform RichText adds RichText field support to eZ Platform, handling storage and rendering of rich content with XML-based markup, transformations, and editor integration. Use it to manage formatted text, embeds, and structured content in your CMS.
eZ Platform Rich Text Field Type Bundle
Frequently asked questions about Ezplatform Richtext
- Can I use ezsystems/ezplatform-richtext directly in a Laravel project without eZ Platform?
- No, this package is tightly coupled with eZ Platform’s architecture (Symfony-based CMS). For Laravel, you’d need to abstract dependencies like the Symfony DI container, database schema (ezrichtext table), and asset handling. Consider Laravel-specific alternatives like `laravel-editor` or `beyondcode/laravel-ckeditor` unless you’re migrating from eZ Platform.
- What Laravel versions and PHP versions does ezplatform-richtext support?
- This package is designed for eZ Platform (Symfony 5.x/6.x) and PHP 7.4–8.1. Laravel compatibility isn’t natively supported, but you could test it with PHP 8.2+ by patching deprecated functions (e.g., `create_function`). For Laravel 9/10, expect higher effort due to Symfony dependency mismatches.
- How do I store rich text content in Laravel’s database instead of eZ Platform’s ezrichtext table?
- You’d need to migrate the XML-based storage logic to Laravel’s schema (e.g., JSON or text columns) and rewrite the field type handlers. The package uses eZ’s repository pattern, which conflicts with Laravel’s Eloquent. A custom abstraction layer or middleware would bridge the gap, but this adds significant complexity.
- Does ezplatform-richtext support CKEditor or TinyMCE out of the box in Laravel?
- Yes, but only if integrated into eZ Platform’s Symfony stack. For Laravel, you’d replace eZ’s editor integration with Laravel packages like `unisharp/laravel-ckeditor` or `beyondcode/laravel-ckeditor`. The underlying XML storage and transformations would still require adaptation.
- What are the licensing implications of using ezplatform-richtext in a Laravel project?
- The package is dual-licensed under **Ibexa BUL (proprietary, requires Ibexa DXP subscription)** and **GPLv2 (open source, copyleft)**. If you’re not using Ibexa DXP, GPLv2 applies, meaning your project must also be open-source. For commercial Laravel projects, this may not be viable unless you negotiate a separate license.
- How do I handle asset embedding (images, links) in rich text for Laravel?
- eZ Platform uses its own asset service, which won’t work in Laravel. Replace it with Laravel’s storage system (e.g., `spatie/laravel-medialibrary`) or a custom solution. You’d need to rewrite URL generation (e.g., `asset()` helper) and asset upload logic to match Laravel’s file structure.
- Are there performance concerns with ezplatform-richtext in Laravel?
- Potential issues include: 1) XML storage vs. Laravel’s optimized database columns, 2) Symfony’s DI container overhead, and 3) asset handling if you don’t replace eZ’s system. Benchmark with your expected load—eZ Platform is optimized for content-heavy CMS, while Laravel may need caching (e.g., Redis) for rich text rendering.
- What’s the best alternative to ezplatform-richtext for Laravel if I need WYSIWYG editing?
- For Laravel, consider: 1) **beyondcode/laravel-ckeditor** (CKEditor integration), 2) **laravel-editor** (TinyMCE), or 3) **spatie/laravel-medialibrary** for asset handling. If you need structured HTML storage, use Laravel’s `html` column type or JSON with validation. These avoid Symfony dependencies entirely.
- How do I configure ezplatform-richtext for a Symfony 6 project instead of Laravel?
- For Symfony 6, follow eZ Platform’s installation docs: require `ezsystems/ezplatform-richtext`, configure the `ezrichtext` field type in your content types, and integrate CKEditor/TinyMCE via Symfony’s form themes. No major changes are needed—it’s designed for Symfony. Laravel would require a custom bridge layer.
- Is ezplatform-richtext actively maintained, and what are the risks of using it in production?
- The last release was in August 2024, and eZ Platform (now Ibexa DXP) is actively maintained. Risks include: 1) Symfony 5.x dependencies may conflict with newer Laravel/Symfony versions, 2) GPLv2 licensing restrictions for closed-source projects, and 3) monolithic design making extraction difficult. Test thoroughly in staging before production.
Weaver
How can I help you explore Laravel packages today?