Weave Code
Redactor Bundle Laravel Package
kraksoft/redactor-bundle
Symfony bundle for integrating the Imperavi Redactor WYSIWYG editor, with configuration and form support for adding rich-text editing fields to your application.
Redactor WYSIWYG editor to your Symfony2 project
Frequently asked questions about Redactor Bundle
- Can I install kraksoft/redactor-bundle in a Laravel app with Composer?
- No. It is a Symfony2 bundle and relies on Symfony's Bundle, Kernel, and DI-Extension system, which Laravel does not have. Composer may resolve it only if your platform allows the legacy Symfony ~2.x and PHP 5.x constraints, and even then there is no way to register or boot the bundle in a Laravel application. Laravel consumes individual Symfony components, not bundles.
- Does kraksoft/redactor-bundle support Laravel 9, 10, or 11?
- No. The package targets Symfony2-era APIs and expects PHP 5.x with symfony/symfony ~2.x, which hard-conflicts with Laravel 9, 10, and 11 on PHP 8.x. Symfony 2 reached end of life in 2018, so there is no compatible upgrade path inside this package. Any Laravel integration would require a fork or a new internal package, not a composer require.
- What Symfony and PHP versions does kraksoft/redactor-bundle require?
- It is a Symfony2 bundle, so expect constraints around symfony/symfony ~2.x and PHP 5.x in its composer.json. That places it roughly in the 2013–2014 era, before Symfony 3 and long before Symfony 4+ and PHP 8. Modern Symfony 6/7 applications cannot use it without a port.
- Is the Imperavi Redactor editor included with kraksoft/redactor-bundle?
- No. Redactor is a commercially licensed editor from Imperavi, and this bundle only provides the Symfony glue: a bundle class, a DI extension with a config tree, asset publishing, and a Twig form type and theme. You still need a valid Imperavi license and the actual Redactor JS/CSS distribution. Licensing is a procurement task separate from the Composer package.
- Is kraksoft/redactor-bundle still maintained?
- Effectively no. It has around 3 stars, 0 dependents, a composite score near 0.015, and no user base to surface regressions. It is best treated as a 2013–2014 artifact and reference documentation rather than a maintained dependency, because every defect you hit will be one you discover and fix yourself.
- How is kraksoft/redactor-bundle configured for toolbars, plugins, and uploads?
- It exposes a centralized YAML configuration tree through a Symfony DI extension, covering toolbars, plugins, language, asset loading for stylesheets, scripts, and locales, plus configurable upload handlers. That configuration only applies inside a Symfony application, and there is no Laravel config publishing, env integration, or config-cache equivalent. If you port the idea, translate the YAML into a config/redactor.php file in your own package.
- What Laravel alternatives should I use instead of kraksoft/redactor-bundle?
- If you just need a rich-text field, use a maintained Laravel-friendly editor package or a simple Blade component wrapping a modern editor such as Tiptap, TinyMCE, CKEditor, or Quill. If Redactor specifically is required by product, vendor the licensed Redactor distribution into resources/js/vendor and load it through Vite. Either way, do not depend on a Symfony2 bundle from a Laravel app.
- Does kraksoft/redactor-bundle handle HTML sanitization or XSS prevention?
- No. The bundle does nothing about sanitization, XSS, or upload validation, so those are your responsibility regardless of which editor you use. In Laravel, that means server-side HTML sanitization and authenticated, policy-protected upload endpoints. Budget for that work separately from the editor integration.
- Can I use kraksoft/redactor-bundle with Vite and a modern Laravel front end?
- Not directly. The bundle assumes Symfony asset publishing via assets:install into web/ and is built around jQuery-era assumptions that clash with Vite, Tailwind, and Livewire front ends. If you must use Redactor assets, load them through Vite from resources/js/vendor rather than via the bundle. Also check whether your CSP forbids inline scripts or unsafe-eval, which older editors often require.
- Should I fork kraksoft/redactor-bundle to port it to Laravel, and how would I test the port?
- Treat it as reference documentation only. Read the config tree and form-type wiring to see which Redactor options and defaults matter, then build a small internal Laravel package: a service provider, a publishable config file, a Blade component, an authenticated upload controller, and a sanitization rule. That is a few days of work and a new package, not an integration of this one. Test the component rendering, config publishing, upload authorization, and sanitization with PHPUnit or Pest, and add a browser test that the editor mounts under your CSP.
Weaver
How can I help you explore Laravel packages today?