- Can I use fsi/ckeditor-bundle in a Laravel application?
- No. It is a Symfony bundle built on Symfony's DependencyInjection, Config, Form and Twig components, none of which map onto Laravel's stack. Composer resolution will either fail against Laravel 10/11 constraints or drag in Symfony 2.x/3.x-era dependencies that conflict with Illuminate. The native Laravel equivalent is a Blade component plus a config/ckeditor.php file and an upload endpoint.
- Is fsi/ckeditor-bundle still maintained?
- No. The last release was 2018-02-01, with no security response, no PHP 8 compatibility work and no framework constraint updates. It has 1 star and 0 dependents, so there is no community review or downstream testing to lean on. Adopting it makes you the sole maintainer of record.
- Does fsi/ckeditor-bundle support Laravel 10 or 11 and PHP 8.2?
- There is no Laravel support at any version because it is a Symfony bundle, and its Composer constraints predate Laravel 8+, PHP 8.x and modern Composer strictness. Treat it as incompatible until proven otherwise. Timebox a composer require spike against your real application skeleton and cut it off after an hour.
- What does fsi/ckeditor-bundle actually provide?
- It integrates the CKEditor WYSIWYG editor into Symfony applications through a CKEditorType form type, configurable toolbar and editor options in bundle configuration, asset handling for editor scripts, styles and plugins, and Twig helpers for rendering and initializing the editor. Under the hood it mostly translates configuration arrays into CKEditor constructor options and renders a textarea plus an init script. That is convenience glue, not capability.
- Which CKEditor version does fsi/ckeditor-bundle target?
- CKEditor 4, which is past end of life. Running an EOL editor in a content-authoring surface means accepting an unpatched rich-text and XSS attack surface. CKEditor 5 has a different API and content model, so configuration from this bundle does not transfer. If you need CKEditor 5, integrate the npm packages directly.
- How do I install and configure fsi/ckeditor-bundle in Symfony?
- On an era-appropriate Symfony application you would require fsi/ckeditor-bundle with Composer, register the bundle in your kernel or bundles.php, set toolbars and editor options in the bundle configuration, then use CKEditorType in your forms with the Twig helpers in your templates. This only applies to Symfony projects on compatible legacy versions. Do not attempt the same approach in Laravel: pulling Symfony Form and Twig in gives you two templating engines and a large conflict surface for no benefit.
- How do I add CKEditor to a Laravel app without this bundle?
- Install the @ckeditor/ckeditor5 npm packages or a prebuilt classic build through Vite, create a resources/views/components/editor.blade.php component that renders your textarea and initializes the editor, and add a config/ckeditor.php for toolbars and plugins. Wire a POST /uploads/editor endpoint that returns the url shape the editor expects for image uploads. That is roughly 50 to 150 lines of first-party code and one to three days of work including upload wiring.
- Is fsi/ckeditor-bundle safe to use in production?
- Not for a Laravel or modern PHP application. It has been unmaintained since 2018, has no security response process, and wraps an end-of-life CKEditor 4 build. With 1 star and 0 dependents there is no informal audit or downstream testing to rely on. MIT licensing is fine, but it is the only unambiguous positive attribute here.
- How much work is it to replicate the bundle natively?
- Realistically one to three days including upload endpoint wiring. The bundle's useful surface is config assembly into CKEditor constructor options, a rendered textarea and an init script, which in Laravel is a small Blade component and a configuration file. Building it yourself gives you code you can maintain and keeps you on a supported editor major version.
- How do I migrate a Symfony project away from fsi/ckeditor-bundle?
- If a legacy Symfony application already uses the bundle, leave it in place there and do not port it forward as the pattern. Evaluate any replacement on Symfony using Symfony's own version constraints. For Laravel, build the native Blade component, config file and upload endpoint instead of trying to bridge the bundle, and if CKEditor 4 must be retained for content fidelity, integrate the standalone CKEditor 4 distribution directly.