Weave Code
Filament Tinyeditor 6 Laravel Package
rectitude-open/filament-tinyeditor-6
Adds the TinyMCE rich text editor to Filament forms as a ready-to-use WYSIWYG field. Configure toolbars, plugins, menus, and file uploads to give your admin panel a full-featured content editing experience with minimal setup and sensible defaults.
A TinyMCE v6 integration for Filament Forms
Frequently asked questions about Filament Tinyeditor 6
- What is rectitude-open/filament-tinyeditor-6 and what does it do?
- It is a Composer package that adds a TinyMCE 6 rich text editor as a form field in Filament. It wraps the editor in a Filament form component so you can configure toolbars, plugins, menus, and uploads with sensible defaults. Install it with Composer and register the plugin in your Filament panel provider to use it in resources.
- How do I install filament-tinyeditor-6 in a Laravel Filament app?
- Install the package with Composer, then register its service provider or plugin in your Filament panel provider. After that, publish the assets to public/ following standard Filament conventions so the bundled editor files are served. You can then use the TinyEditor field in any Filament form or resource.
- Which Filament and Laravel versions does filament-tinyeditor-6 support?
- The package is built for Laravel applications using Filament Forms, and the release notes do not signal a PHP or Laravel constraint change between v6.3.2 and v6.4.0. You should confirm compatibility against your project's Filament major version before upgrading. The vendored TinyMCE version is the main compatibility variable if you have custom skins or plugins.
- How do I configure TinyMCE toolbars, plugins, and menus in Filament?
- The field exposes TinyMCE configuration options such as toolbar buttons, plugins, and menu entries directly from your Filament form schema. You pass those options on the field instance so each editor can have a different setup. Defaults are included, so you only need to override what your content workflow requires.
- Does filament-tinyeditor-6 support image and file uploads?
- Yes, the package supports configuring file uploads as part of the TinyMCE field setup. Upload handling still needs a backend endpoint or Filament upload configuration that matches your storage and validation rules. Review the upload path before enabling it in production, especially for public-facing admin panels.
- Is the bundled TinyMCE license a problem for commercial Laravel apps?
- Version 6.4.0 moves to locally bundled TinyMCE assets, which means the package redistributes TinyMCE source rather than only consuming a CDN or npm artifact. TinyMCE's GPL and commercial licensing distinction can therefore apply to products that ship this package. Legal review is warranted before rollout, and you should confirm the license terms of the vendored build with the maintainer.
- How do I upgrade from v6.3.2 to v6.4.0 without breaking the editor?
- Upgrade in a staging branch and re-publish the vendor assets if your project caches or commits published files. Smoke-test existing editor fields and any custom TinyMCE init overrides after the upgrade. Then opt into the paste-from-word plugin field by field rather than enabling it everywhere at once.
- What does the paste-from-word plugin change about saved HTML?
- The paste-from-word plugin is a drop-in TinyMCE plugin that helps preserve formatting when content is pasted from Microsoft Word. It can introduce extra markup, inline styles, or base64 images, so your sanitization policy on save should be re-validated. Test the emitted HTML on representative documents before rolling it out to all content types.
- Will locally bundled TinyMCE assets break my Content Security Policy?
- Because v6.4.0 serves TinyMCE assets locally instead of from a CDN, you may need to add or adjust script-src and style-src entries in your CSP. Check the published asset paths in public/ and confirm they are allowed by your policy. Re-test editor rendering after any CSP or asset-publishing change.
- Who is responsible for TinyMCE security updates when using this package?
- By vendoring TinyMCE, the package maintainers now own CVE tracking and version bumps for the editor, so consumers depend on their release cadence. Your team should add a recurring check that the vendored TinyMCE is current and monitor upstream TinyMCE advisories. If the package lags, that becomes a security regression for your application.
Weaver
How can I help you explore Laravel packages today?