- Does sirroland/ckeditor-bundle work with Laravel?
- No. This is a Symfony bundle built on the Symfony bundle system, a DI extension with a configuration tree, a CKEditorType form type and Twig form themes, none of which exist in Laravel. There is no service provider, Blade component or config bridge, so adopting it in a Laravel app means rewriting the only meaningful parts. For Laravel, integrate CKEditor 5 directly with npm or a CDN instead.
- How do I install and register sirroland/ckeditor-bundle?
- Run composer require sirroland/ckeditor-bundle, then register the bundle in AppKernel for Symfony 3.x or in config/bundles.php for Symfony 4.x. Define your ivory_ck_editor configuration in YAML or PHP, publish the packaged assets with assets:install, and confirm the Twig form themes are wired up. After that you can swap textarea fields for CKEditorType in your form classes.
- Which Symfony and PHP versions does this bundle support?
- It targets the Symfony 2.8 through 4.x era on PHP 7.x, matching its last release in January 2019. There is no Symfony 5, 6 or 7 compatibility and no PHP 8.2 or 8.3 support, so expect breakage in the form type and configuration tree on modern stacks. Treat it as viable only inside a legacy Symfony codebase you already own.
- Which CKEditor version does it bundle?
- It packages CKEditor 4, which reached end of life in mid-2023 and has a history of XSS advisories. CKEditor 5 is the current major and is not supported by this bundle. If your product requirement is CKEditor 5, this package is not a fit.
- How do I add a CKEditor field to a Symfony form?
- Add it like any other form field, for example add body as CKEditorType::class with a config array for per-field options. The bundle must be registered, its assets published and its Twig form theme available, otherwise the field renders as a plain textarea. Keep toolbar settings in the bundle configuration so individual forms stay short.
- How do I configure the toolbar and editor options?
- Toolbar and editor settings live in the ivory_ck_editor configuration section, where you define named configs and toolbars referenced by your form fields. You can override options per field through the config key passed to CKEditorType. Because this is a Symfony configuration tree, none of it transfers to a Laravel config file without a rewrite.
- Is sirroland/ckeditor-bundle still maintained?
- No. The last release was 2019-01-24, it has zero stars and zero dependents, and it is a low-visibility fork of the already-abandoned IvoryCKEditorBundle, formerly egeloen/ivory-ckeditor-bundle. There are no security backports and no upstream to merge fixes from. Note also that the Composer name and repository name differ, so run a provenance and typosquat review before it enters a lockfile.
- Is it safe to use in production?
- The biggest risk is shipping CKEditor 4, an end-of-life editor with a stored-XSS attack surface on any authoring or user-generated content field. If you adopt the fork you take on permanent security patch responsibility yourself. Sanitise editor HTML server-side with an allowlist such as HTMLPurifier regardless of which editor you choose.
- How do I test forms that use CKEditorType?
- CKEditorType extends a textarea, so Symfony form and functional tests submit plain HTML strings while the JavaScript editor never runs under PHPUnit. Assert on the submitted value and on your server-side sanitisation rather than on editor behaviour. Save browser-level checks for a small number of end-to-end tests.
- What should I use instead in a Laravel application?
- Skip this package and build the integration directly: install CKEditor 5 via npm or a CDN, add a Blade component with a named push for scripts, expose toolbar and upload settings from a config endpoint, and write a POST upload controller with MIME and size validation. That is roughly two to four developer days with no abandonware dependency. If you are on legacy Symfony, evaluate FOSCKEditorBundle or EasyAdmin's built-in editor before forking this one.