Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Tinymce Laravel Package

contao-components/tinymce

Integrates the TinyMCE rich text editor into Contao as a reusable component, giving backend and frontend forms a ready-to-use WYSIWYG with bundled editor assets and sensible configuration. Ideal for projects needing flexible, customizable content editing without manual TinyMCE setup.

View on GitHub
Deep Wiki
Context7

TinyMCE integration for Contao Open Source CMS

Frequently asked questions about Tinymce
Is contao-components/tinymce compatible with Laravel?
It is a Contao CMS integration and asset package, not a Laravel editor package. Composer may install it, but Laravel auto-discovery likely provides no service provider or Blade integration. Treat it as TinyMCE assets packaged for Contao, not a supported Laravel dependency.
How do I install contao-components/tinymce in a Laravel application?
You can run composer require contao-components/tinymce, but installation is not the same as integration. There is no Laravel config, asset publishing, or upload endpoint included. If you only need assets, copy or publish the bundled TinyMCE files into public/vendor/tinymce and initialize TinyMCE yourself.
Which TinyMCE version and plugins are bundled with contao-components/tinymce?
The package metadata and README excerpt do not state a version or plugin set. Inspect the vendor directory or repository to confirm the TinyMCE build, plugins, skins, and license files. This matters because TinyMCE versions and plugin licensing affect security and feature support.
Does contao-components/tinymce require a TinyMCE API key or Cloud account?
That depends on whether the bundled TinyMCE build is self-hosted GPL or wired for TinyMCE Cloud. The package description does not clarify licensing or API key requirements. Check the bundled license and initialization config, and confirm whether domain allowlisting or a Cloud key is needed.
Can I use contao-components/tinymce with Livewire, Inertia, Vue, or React?
The package does not provide Laravel or JavaScript framework integration, so you would wire TinyMCE manually. In Livewire, Inertia, Vue, or React you must reinitialize editors after DOM updates and tear them down to avoid duplicate instances. Own that glue code in your app rather than relying on Contao behavior.
What are the alternatives to contao-components/tinymce for Laravel?
Use the official TinyMCE npm package or CDN distribution and a Blade component or frontend wrapper, or evaluate a Laravel-native editor package. For simpler needs, consider alternatives such as Trix, CKEditor, or Quill with your own sanitization and upload endpoints. The right choice depends on required plugins, licensing, and accessibility needs.
How do I migrate TinyMCE configuration from Contao to Laravel?
Inventory the Contao editor config first: plugins, toolbar, content CSS, upload behavior, and HTML sanitization rules. Recreate those settings in Laravel using official TinyMCE assets, a Blade or JS component, and Laravel-native storage and upload endpoints. Do not depend on Contao constants, paths, or runtime services in the Laravel app.
Is contao-components/tinymce maintained and safe for production?
The assessment flags high technical risk: 0 stars, 0 dependents, and a score of 0 are strong signals against strategic reliance. It is unclear how quickly TinyMCE security releases are absorbed. For production Laravel apps, prefer the official TinyMCE distribution or a maintained Laravel integration and track security updates yourself.
Does contao-components/tinymce include a Laravel service provider, config, or Blade component?
No Laravel service provider, publishable config, Blade component, or upload endpoint is described. The package exists to deliver TinyMCE assets and Contao-specific wiring. Laravel auto-discovery likely provides nothing useful, so any integration would be glue code you own.
How should I handle uploads and HTML sanitization if I use this package's TinyMCE assets?
Treat the package only as an asset source and implement Laravel-native uploads with validation, authorization, and storage abstraction. Add HTML sanitization on input and output with a defined allowed tag and attribute list. Configure CSP, asset caching, and editor teardown for SPA or Livewire updates.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
jinas/dhivatar
store-doc/laravel-storage-driver
plus-it/laravel-translation-manager
diephp/perhaps
diephp/telegraph
osmaviation/spreadsheet
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console
pnscripts/filament-broadquill-lite
pnscripts/laravel-sentfold-lite
vleap/mx-sdk-laravel-internal
twidpay/utils
htetmyathlaing/scout-elasticsearch-driver
artisan-toolbox/front-awesome
ls/client-assistant
users-au/laravel-client
cgv/localized-resource