Weave Code
Tinymce Bundle Laravel Package
short-edition/tinymce-bundle
TinyMCE bundle for Laravel from short-edition: quickly add the TinyMCE rich text editor to your PHP app with packaged assets, config publishing, and Blade integration for fast, framework-friendly WYSIWYG editing.
This Bundle integrates TinyMCE WYSIWYG editor into a Symfony2 project.
Frequently asked questions about Tinymce Bundle
- Can I use short-edition/tinymce-bundle in a Laravel application?
- No. Despite the Composer name, this is a Symfony2 bundle: it expects AppKernel bundle registration, the Symfony dependency-injection container, Twig 1.x helpers and a PHP 5.x-era runtime, none of which exist in Laravel. Laravel has no bundle system, so there is no service provider, facade or config publish flow to hook into. The only portable part is the idea of emitting a tinymce.init script next to a textarea, which is roughly 20 to 150 lines of glue you can write yourself.
- Does this package support Laravel 10, Laravel 11 and PHP 8.2?
- It does not. The bundle targets Symfony 2.x, Twig 1.x and PHP 5.3+, and Symfony 2.8 reached end of life in November 2018. Modern Laravel releases require PHP 8.1 or newer and pull Symfony 6 or 7 components, so Composer will refuse to resolve both in one dependency tree. Expect hard conflicts on php, symfony/framework-bundle and twig/twig.
- How do you install and configure this TinyMCE bundle?
- In its intended Symfony2 context you add the bundle to AppKernel, merge its configuration for toolbars, plugins and content styles, and render editors through the provided Twig helper while assets load via your asset manager. There is no equivalent Laravel installation path: no artisan vendor:publish, no config file under config/, no Blade helper. If you inherit a legacy Symfony2 app, follow the bundle README there rather than trying to port it.
- Is there a Laravel service provider, facade or Blade directive in this package?
- No. The package predates the patterns Laravel developers expect and ships only Symfony bundle classes and Twig extensions. You will not find a ServiceProvider, a Facade, a Blade component or a @tinymce directive. Any Laravel integration would mean writing all of that yourself, at which point using TinyMCE directly is simpler and better supported.
- What is the best Laravel alternative to this bundle for a TinyMCE editor?
- Install tinymce from npm or pin a specific version from a CDN, then add a textarea to your Blade form and call tinymce.init from a script pushed into your layout. That gives you the same WYSIWYG result with a supported upstream package and no dead framework in the dependency tree. Worth benchmarking first: TipTap, Lexical, CKEditor 5, Quill and Markdown-first editors, compared on license, output content model, sanitization story and front-end framework support.
- Is short-edition/tinymce-bundle still maintained and safe for production?
- The health signals say no: zero stars, zero dependents, a single-organization release history and an end-of-life platform underneath. There is no visible release cadence, issue triage or CVE monitoring. Because the editor sits on a security-sensitive form surface, treating it as unmaintained glue code rather than an infrastructure dependency is the safe assumption.
- How long does it take to add TinyMCE to a Laravel Blade form yourself?
- Roughly one day, including testing. Install tinymce with npm, import it in your Vite entry point, render a plain textarea in Blade and initialize the editor inside a @push('scripts') block. Toolbar and plugin maps move into a small config array or a dedicated JS module, which is effectively all the bundle's configuration sugar gives you.
- Does this bundle sanitize TinyMCE output to prevent XSS?
- No. The bundle handles asset registration and editor rendering; it does not sanitize submitted HTML, and TinyMCE itself does not guarantee clean markup on the server side. You must validate and sanitize on the server before storage or display, for example with HTML Purifier or a similar allowlist-based filter. Assume output is untrusted input, because users can post directly to your endpoint without ever loading the editor.
- What TinyMCE license do I need for a commercial Laravel application?
- TinyMCE version 6 and later is available under GPLv2 or a commercial license, so a closed-source product needs the commercial option. That is a procurement and legal decision independent of any bundle, and a legacy bundle may pin or assume an older TinyMCE release, which splits the licensing question from the version you actually ship. Confirm the license before you pick a version or an integration path.
- Can the bundle render multiple editors, custom toolbars and localized skins per page?
- Yes, within Symfony2: it supports reusable presets, several independent editor instances on one page, configurable toolbars, plugins, content styles, localization and custom skins. In Laravel the same features come straight from TinyMCE through multiple init calls with distinct selectors and per-instance options. Those capabilities belong to the upstream editor, not to this bundle, so nothing is lost by dropping it.
Weaver
How can I help you explore Laravel packages today?