Weave Code
Redactor Widget Laravel Package
friendsofvictoire/redactor-widget
A Laravel package that provides a Redactor rich-text editor widget for your admin forms, letting content editors write and format HTML with a familiar WYSIWYG interface.
Redactor Widget is a Laravel package that integrates the Imperavi Redactor WYSIWYG editor into your application as a reusable widget. It wraps the editor's initialization and asset loading in a simple, configurable component, so you can drop a rich text field into Blade views or forms without hand-writing JavaScript setup each time.
- Provides a ready-to-use Redactor editor widget for Laravel views
- Handles asset publishing and inclusion automatically
- Configurable editor options via a clean configuration file
- Works with Blade templates and standard form inputs
- Optional localization and toolbar customization
Frequently asked questions about Redactor Widget
- Is friendsofvictoire/redactor-widget compatible with Laravel?
- No. friendsofvictoire/redactor-widget is a Symfony/Victoire DCMS bundle, not a Laravel package; it does not provide Laravel service providers, facades, config publishing, or Blade integration. A Laravel app would need to adapt Symfony bundle conventions and legacy dependencies, which is usually more work than integrating a supported JavaScript editor directly. Treat it as a Victoire/Symfony-only artifact unless you have a specific legacy CMS requirement.
- How do I install friendsofvictoire/redactor-widget in a Laravel application?
- There is no Laravel installation path for this package. Composer may resolve it, but you will not get a Laravel service provider, publishable configuration, or Blade components, and its Symfony/Victoire assumptions will not match Laravel conventions. For Laravel, the practical approach is to install a maintained editor via your asset pipeline rather than adding this bundle.
- Which Laravel versions support friendsofvictoire/redactor-widget?
- None are supported in the Laravel sense. The package is a Symfony/Victoire widget with a last release in 2016 and no Laravel version constraints, service provider integration, or framework compatibility layer. Any use in Laravel would be unsupported and would require custom adaptation and testing.
- Can I use this Redactor widget with Blade templates and Eloquent models?
- Not natively. The package is built for Symfony/Victoire content editing and does not ship Blade directives, Eloquent integration, validation rules, or Laravel-friendly asset publishing. You could theoretically render an editor in Blade, but persistence, sanitization, and validation would be your own Laravel code, not something the package provides.
- Is friendsofvictoire/redactor-widget actively maintained?
- No. The last release was 2016-11-10, the project has very low adoption with 2 stars and 0 dependents, and there is no evidence of active maintenance. That means no security patch path and a high likelihood of abandoned dependencies or PHP/Symfony version conflicts. Retaining it requires a named internal owner for patching and asset updates.
- What are the best alternatives to this package for rich text editing in Laravel?
- Use a maintained JavaScript editor such as CKEditor, TinyMCE, or Tiptap and integrate it through Laravel's asset pipeline with your own validation, sanitization, and persistence. This avoids Symfony/Victoire coupling and gives you a supported upgrade path. The package assessment explicitly recommends replacing the widget for Laravel rather than migrating the bundle.
- What Redactor licensing or asset-delivery issues should I check before using this widget?
- Redactor is a commercial editor, so confirm that a valid license and a compliant asset-distribution path already exist for your deployment. The bundle's age also raises questions about which Redactor editor version it expects and whether assets are still available or blocked by modern pipelines. Do not adopt it without validating licensing and asset delivery in a disposable environment.
- How should I spike compatibility before adopting friendsofvictoire/redactor-widget?
- Inventory your existing Victoire and Redactor usage, then run a disposable Composer dependency-resolution spike against your target PHP, Symfony, and Victoire versions. Check autoloading, asset pipeline assumptions, and editor version compatibility before committing. If the spike fails, do not force it into Laravel; replace the editor component instead.
- Can I migrate from Victoire/Redactor to a Laravel content model?
- Yes, but migrate the content model, not the package. For a Laravel or modern PHP application, do not port the Symfony bundle; define how content is stored, sanitized, validated, and rendered, then replace the editor widget with a supported component. Plan content migration and acceptance tests before removing the old bundle.
- What production risks come with using an abandoned Symfony bundle in Laravel?
- Expect Composer conflicts, missing or blocked editor assets, license expiry, Symfony deprecation failures, and content-sanitization or XSS concerns. Because the package is effectively unmaintained, you also lose a security patch path and downstream validation. A technical lead should not approve it without a bounded legacy-use justification and a named maintainer.
Weaver
How can I help you explore Laravel packages today?