Weave Code
Tinymce Bundle Laravel Package
gibilogic/tinymce-bundle
A Symfony bundle that integrates the TinyMCE rich text editor into your applications, providing configurable WYSIWYG editing for forms and content fields with minimal setup and easy customization.
Bundle for connecting TinyMCE (WYSIWYG editor) to your Symfony2 project
Frequently asked questions about Tinymce Bundle
- Is gibilogic/tinymce-bundle a Laravel package?
- No. It is a Symfony2 bundle that registers in AppKernel, configures through the DI container, and ships a form type plus a Twig extension. There is no Laravel service provider, facade, or publishable config file, so it is a non-candidate for a Laravel stack and should be removed from the evaluation set rather than ranked.
- How do I install gibilogic/tinymce-bundle?
- Install it with Composer using composer require gibilogic/tinymce-bundle, then register the bundle in AppKernel and set its options in your Symfony configuration. That flow assumes a Symfony 2.x application; there is no service provider or package auto-discovery for modern stacks. Budget a compatibility spike before committing to it.
- Does this bundle support Symfony 6, Symfony 7, or Symfony Flex?
- No. The bundle targets Symfony 2.x, which has been end-of-life for years, and its bundle registration, DI, and Twig conventions conflict with Flex, autowiring, and PHP 8 attributes. Bringing it forward is fork-and-upgrade work, not install-and-configure. Only consider it for a legacy Symfony 2.x app already in maintenance-only mode.
- Which Laravel versions does this package support?
- None. There is no Laravel integration surface here: no service provider, no facade, and no publishable config/tinymce.php. Vite, package discovery, and Blade have no overlap with Symfony bundle conventions. If your target stack is Laravel, assess the upstream TinyMCE npm package directly instead.
- How do I configure the TinyMCE toolbar, plugins, and editor height?
- The bundle exposes a configuration tree covering toolbar, plugins, theme, height, and content CSS, which is injected into the editor init config. Even if you do not adopt the bundle, that tree is a clean, already-scoped requirements spec you can lift into your own integration. Verify the exact keys against the bundle's config definition before copying.
- How do I render the editor in a Twig template or Symfony form?
- The bundle provides a Twig extension and a form-friendly setup for rendering the editor, with options for language and appearance. In a legacy Symfony 2.x app that is direct, but the surrounding platform is itself EOL, which is the larger strategic problem. The modern equivalent is a Twig form theme plus a Stimulus controller, which is sub-day effort.
- Does the bundle self-host TinyMCE assets or require a CDN or cloud API key?
- The overview describes asset management through Symfony's asset system, which points to locally served assets rather than TinyMCE Cloud. The pinned TinyMCE major is not stated in the overview and is likely years behind current releases, so confirm both before relying on it. If it turns out to need a cloud key or CDN, that changes your CSP and procurement story.
- Is gibilogic/tinymce-bundle safe and maintained enough for production?
- Treat it as high and asymmetric risk. Seven stars and zero dependents mean no downstream validation, no issue triage, and no security response, and a WYSIWYG editor sits directly on the content-authoring path. An outdated editor there is a live XSS vector, and inline init scripts add CSP friction. The upside is a thin convenience wrapper you can reproduce in under a day.
- Does the bundle handle HTML sanitization, file uploads, or content policy?
- Nothing in the described scope goes beyond wrapping the JavaScript editor and injecting init configuration; sanitization, upload wiring, and HTML policy are not part of the feature list. Treat all editor output as untrusted and route it through a server-side allowlist such as HTMLPurifier. If it really does nothing more than inject config, build-versus-buy is trivially build.
- What is the fastest migration path or Laravel alternative to this bundle?
- The realistic path is migration away from the pattern, not to this package. On Laravel, install TinyMCE from npm, register a small x-tinymce Blade component or a once-guarded script stack entry, and sanitize output server-side. On Symfony, use a Twig form theme plus a Stimulus controller. Both are sub-day work, and either way you keep version pinning and security patching under your control.
Weaver
How can I help you explore Laravel packages today?