Weave Code
Laravel Ckeditor Laravel Package
unisharp/laravel-ckeditor
Integrates CKEditor into Laravel with simple configuration, Blade helpers, asset publishing, and file upload support. Add a full-featured WYSIWYG editor to your forms quickly, with customizable toolbar and upload handling out of the box.
JavaScript WYSIWYG web text editor (for laravel).
Frequently asked questions about Laravel Ckeditor
- How do I install unisharp/laravel-ckeditor in a Laravel app?
- Install it with Composer using composer require unisharp/laravel-ckeditor. Laravel's package auto-discovery registers the service provider, so no manual entry in config/app.php is usually needed on supported versions. After that, publish the bundled CKEditor assets to your public directory with vendor:publish, then drop the @ckeditor('editor_id') directive under a textarea in your Blade form.
- Which Laravel and PHP versions does laravel-ckeditor support?
- This package originated in the Laravel 5.x/6.x era, so its Composer constraints may not declare support for Laravel 10, 11, or PHP 8.3. Check the requires block in the package's composer.json before adopting it, and test installation on a dev branch. The vendored CKEditor JavaScript is framework-agnostic, so most incompatibilities show up as service provider or asset-publishing problems rather than editor runtime errors.
- How do I publish the CKEditor assets and config file?
- Run php artisan vendor:publish and select the UniSharp CKEditor provider, or use the specific tag documented in the package readme. This copies the CKEditor 4 build into public/vendor/ckeditor and places a config file in your config directory. Commit or deploy those published assets, since the editor will not load without them being publicly reachable.
- How do I customize the CKEditor toolbar and height with the @ckeditor directive?
- The directive accepts options that map onto CKEditor configuration such as toolbar groups, height, and allowedContent. You can pass these inline to the directive or set global defaults in the published config file. Because the wrapper is a thin binding over CKEditor 4, any option supported by the editor's config API is generally usable.
- Can I use multiple CKEditor instances on the same Blade page?
- Yes. Call the directive once per textarea, giving each one a unique element id, for example @ckeditor('body') and @ckeditor('summary'). Each call initializes a separate editor instance with its own configuration. Avoid duplicate ids, since CKEditor resolves editors by the underlying textarea id.
- Is CKEditor 4.7.2 safe to use in production?
- CKEditor 4 is end-of-life, and this package vendors the 2018-era 4.7.2 build, which predates later XSS and security fixes shipped in 4.16.1, 4.21.0, and 4.25.0-lts. For internal, low-trust authoring screens the risk may be acceptable, but for user-facing or regulated deployments it is a security-review blocker without a compensating control. If you adopt it, plan either a maintained CKEditor 4 LTS asset override or a migration to CKEditor 5, TinyMCE, or TipTap.
- How do I add file or image upload support to laravel-ckeditor?
- The wrapper does not ship a file browser or upload connector, so you have to build one. Create your own Laravel route that accepts the upload, validates and stores the file, and returns the response format CKEditor expects, then point config.filebrowserUploadUrl (or the image upload URL) at it. Lock that route down with auth and MIME/size validation, because it is a public upload endpoint.
- Does unisharp/laravel-ckeditor work with Vite or Laravel Mix?
- No, not in the bundler sense. The package copies a static CKEditor 4 build into public/vendor, so Vite and Mix never compile, tree-shake, or version-hash it. It will not conflict with your build pipeline, but you also get no nonce-aware CSP handling or dependency updates through npm. For SPA or Inertia front ends, install CKEditor as an npm dependency instead.
- How do I set editor options like allowedContent or a custom config file?
- Pass options through the Blade directive, or edit the published config file to set defaults used by every instance. For advanced cases you can point CKEditor at its own config.js with a customConfig setting and define allowedContent, extraPlugins, and toolbar rules there. Confirm the wrapper is not overriding your config keys before debugging deeper.
- What are the alternatives to unisharp/laravel-ckeditor for a maintained WYSIWYG editor?
- For a supported CKEditor 4 line, vendor a maintained 4.x LTS build yourself rather than relying on this frozen package. For a forward path, consider CKEditor 5, TinyMCE, or TipTap installed through npm and wired into your Blade or Inertia front end. All three receive active security updates, which the vendored 4.7.2 build here does not.
Weaver
How can I help you explore Laravel packages today?