- How do I install the Laravel rich text editor in a new project?
- Run composer require arm092/laravel-rich-text-editor, then run php artisan rich-text-editor:publish to copy the configuration and prebuilt assets. After that, use the Blade component in your form, for example x-rich-text-editor with a name and value. The package supports Laravel 10 through 13 and PHP 8.1 or newer.
- Does arm092/laravel-rich-text-editor work with Livewire 3 and Livewire 4?
- Yes, Livewire binding is supported when you use Livewire 3 or 4. Bind the editor with wire:model, such as wire:model="form.content", and the component synchronizes through a native textarea. It uses wire:ignore to isolate the editor-managed DOM, and default, .live, .blur, and .change model modifiers pass through unchanged.
- How should I store and render sanitized HTML from the editor in Laravel?
- Cast the model attribute with the package's RichTextCast cast so the submitted HTML is handled safely when persisted. On Laravel 10, put the same cast in the model's protected $casts property. Render saved content with the x-rich-text-content component, passing the content value, rather than echoing raw HTML.
- What Laravel and PHP versions does this package support?
- The README lists PHP 8.1 or newer and Laravel 10, 11, 12, or 13. Livewire 3 or 4 is required only when you need Livewire binding. It also expects a modern evergreen browser for the editor UI.
- How do I upgrade to v1.3.11 when I have customized toolbar profiles?
- Update the Composer constraint to ^1.3.11, republish the assets with the force flag if appropriate, and clear config and view caches. Do not blind-overwrite a customized published profile; diff the package's default profile against yours and manually merge copyStyle and pasteStyle into the toolbar arrays. If you miss the profile merge, the new toolbar buttons will simply be absent rather than causing an error.
- Will pasted Word lists and text sizes be sanitized correctly after the v1.3.11 update?
- v1.3.11 normalizes Word bullet and numbered paragraphs into semantic ul, ol, and li elements on the client side, and it preserves configured text sizes when parsing and applying format painter styles. If your app uses a server-side sanitizer allowlist, confirm that it includes ul, ol, li, and any inline styles you intend to keep. If those elements are stripped, content will degrade silently to flat paragraphs, so test a Word paste through the full save and render path.
- Can I use the editor without Blade or Livewire using plain JavaScript?
- Yes, the package ships standalone browser assets. Load /vendor/rich-text-editor/rich-text-editor.js for basic code view or rich-text-editor-with-code.js for enhanced code view, then call RichTextEditor.create on a target element. The standalone API exposes create, scan, destroy, getHTML, setHTML, focus, setReadOnly, and instance destroy.
- Why are the Copy style and Paste style buttons missing after upgrading?
- The new Copy style and Paste style toolbar entries come from the profile configuration. If you republished assets but kept an older customized profile, the editor will load without those buttons and no error will be raised. Diff your published profile against the package default and merge copyStyle and pasteStyle into the standard toolbar and any custom profiles.
- Does v1.3.11 require a database migration or change the stored HTML format?
- No database migration is required for v1.3.11, and the release notes describe no changes to models, storage, or serialization. Existing content remains valid, but after the update you may temporarily render a mix of older flat paragraph lists and new semantic ul/ol lists. Verify that your content CSS handles list spacing and nesting before rolling out to authors.
- Is there a helper for merging package config changes, or do I merge profiles manually?
- The provided technical notes do not describe a config-merge or validation helper, so treat profile updates as a manual config diff and merge task. Republish assets, compare the package's default profile with your published profile, and hand-merge new toolbar entries rather than overwriting customizations. A half-day developer task plus a short QA pass is a reasonable estimate for customized installs.