Weave Code
Ckeditor Widget Laravel Package
friendsofvictoire/ckeditor-widget
Integrates a reusable CKEditor widget into your PHP application, letting you embed and manage rich-text editor components with minimal setup. Simple configuration, flexible integration, and a clean way to add custom widgets to CKEditor-powered forms and content fields.
At a glance
Frequently asked questions about Ckeditor Widget
- Is friendsofvictoire/ckeditor-widget a Laravel package?
- No. It is a Symfony bundle built for Victoire DCMS, a Symfony-based CMS, and registers a CKEditor-backed widget type inside Victoire's widget system. Laravel has no Symfony bundle concept, compiler passes, or tagged-service widget registry, so this package does not integrate natively with Laravel.
- Can I install friendsofvictoire/ckeditor-widget in a Laravel app with Composer?
- Composer may install the package, but that does not make it usable in Laravel. There is no Laravel service provider, Blade component, config publishing, or Vite asset wiring. Using it would require embedding a Symfony kernel or porting the widget registration and asset handling, which is not reasonable for a single editor widget.
- What Laravel versions does this CKEditor widget support?
- None. The package targets Symfony and Victoire, not Laravel, so there is no Laravel version support matrix. Any Laravel compatibility claim must be treated as unproven until you inspect and port the source.
- How do I install it for Symfony Victoire?
- Install it via Composer as friendsofvictoire/ckeditor-widget, register the bundle in the Symfony kernel, and wire it into Victoire's widget system. Pin the tag and vendor the lockfile, and verify the declared PHP, Symfony, and Victoire constraints first. It is only a clean fit for an existing Symfony plus Victoire application.
- Which Symfony, PHP, and Victoire versions are supported?
- The evaluation found no visible versioned support matrix, so verify composer.json and the current tag before committing. The surrounding Victoire ecosystem is described as dormant, and Symfony major versions are past end of life. Do not assume current Symfony or PHP support without source-level confirmation.
- Does it use CKEditor 4 or CKEditor 5?
- It is built around CKEditor 4 configuration for the widget edit form. CKEditor 4 reached end of life in mid-2023 and only receives extended security coverage under a paid LTS agreement. For new Laravel work, use a maintained CKEditor 5 build or another supported editor.
- Is CKEditor 4 safe to ship in production?
- CKEditor 4 is end of life, so shipping it carries known XSS and security exposure unless you have a paid LTS arrangement. This package also shows no security policy or CI signal. Treat the editor line and the bundle as separate risks, and require server-side sanitization on the save path.
- How would I integrate this widget into Laravel?
- Do not port the bundle directly. Extract the widget's editing UX contract and serialization format, then rebuild them as a thin Laravel package: a service provider for routes and config, a Blade component for the editor shell, a Vite entry with a maintained CKEditor build, and server-side HTML sanitization. That keeps Laravel on a supported editor line and a supported framework.
- Does the package include tests, CI, or a security policy?
- The assessment reports no visible CI signal, no security policy, and no versioned support matrix. It has 0 stars and 0 dependents, so there are no downstream consumers to surface regressions. Read the source carefully and vendor the lockfile if you must use it.
- What should I use instead for rich-text editing in Laravel?
- Build or choose a native Laravel solution rather than porting this Symfony bundle. A practical path is a service provider, Blade component, Vite entry with a maintained CKEditor 5, TipTap, or Quill build, and server-side HTML sanitization with HTML Purifier or equivalent. That gives you Laravel-native configuration, asset handling, and a supported editor line.
Weaver
How can I help you explore Laravel packages today?