- Is presta/cms-ckeditor-bundle a Laravel package?
- No. It is a Symfony 2-era bundle built for PrestaCMS, a discontinued Symfony CMS distribution, and it has no Laravel service providers, facades, or package auto-discovery. Its integration points are Symfony-specific, including AppKernel registration, DI container configuration, Twig form themes, and Assetic asset publishing. For Laravel, treat it as a non-candidate dependency.
- Can I install presta/cms-ckeditor-bundle in a Laravel application?
- Not feasibly. Composer may resolve it only against pinned PHP 5.x/7.0-era and Symfony 2.x constraints, and it is incompatible with PHP 8.x and Laravel 8-11. Even if installed, there is no Laravel integration layer for routing, Blade, asset publishing, or media handling. Porting the useful ideas into Laravel is the practical path, not adding the package.
- What does PrestaCMSCKEditorBundle actually do?
- It wires the CKEditor WYSIWYG editor into PrestaCMS pages with configurable toolbars and editor options. It also integrates SonataMedia browsing for embedding media and a picker for linking to CMS pages. The value is the rich-text, media-embed, and internal-link workflow rather than any Laravel-specific capability.
- Which PHP and Laravel versions are compatible with presta/cms-ckeditor-bundle?
- It targets PHP 5.x/7.0-era runtimes and Symfony 2.x components, not Laravel. It has no declared support for Laravel 8, 9, 10, or 11, and it is not compatible with PHP 8.x. The bundled CKEditor version is also legacy and does not share configuration or plugin APIs with CKEditor 5.
- Is PrestaCMSCKEditorBundle maintained and safe for production?
- No. The last release was 2014-09-03, the repository is archived, and it has 0 dependents and 2 stars. It receives no security patching and pulls in obsolete SonataMedia/SonataAdmin and CKEditor 3/4 builds with unpatched CVEs, including XSS advisories. Using it in production, especially in a Laravel app, carries very high risk.
- How do I add CKEditor with media embedding and page links in Laravel?
- Use a maintained editor such as CKEditor 5 via a custom npm build, TinyMCE, or Tiptap in your Blade, Vue, or React front end. Store and serve assets with spatie/laravel-medialibrary or an equivalent Laravel media package. Build a link-picker endpoint that resolves Laravel named routes rather than Symfony CMF page IDs, and rewrite stored links on render or save.
- What are the best alternatives to presta/cms-ckeditor-bundle for Laravel?
- For the editor, choose CKEditor 5, TinyMCE, or Tiptap, each of which has maintained JavaScript packages and framework-agnostic integration. For media, use spatie/laravel-medialibrary, Laravel Media Library, or a custom upload endpoint backed by Laravel filesystem disks. For internal links, implement a route-aware picker using Laravel named routes instead of a Symfony page-ID picker.
- How do I migrate content from PrestaCMS CKEditor to a Laravel editor?
- Export page HTML and any referenced media from the PrestaCMS database and filesystem. Rewrite SonataMedia embed references and PrestaCMS page links to your Laravel media URLs and named routes, then re-import the HTML into the new editor's storage format. Plan for a validation pass because legacy CKEditor 3/4 markup may not map cleanly to CKEditor 5 or Tiptap schemas.
- How do I configure CKEditor toolbars and options in Laravel without this bundle?
- Configure the toolbar in the editor's JavaScript build or init options, not in a Symfony DI container. Pass a config object from Blade or your front-end component, and keep upload and link-picker endpoints as Laravel routes with authentication and validation. This keeps editor configuration versioned with your assets and avoids Assetic or Twig form themes.
- Does this bundle work with CKEditor 5 and modern Symfony or Laravel stacks?
- No. It bundles legacy CKEditor 3/4-era integration and relies on Assetic, AppKernel, and Resources/public conventions removed or deprecated in Symfony 4+. It does not support CKEditor 5 plugin APIs and has no Laravel stack support. Modern projects should use a current CKEditor 5 build and a native Laravel integration.