- How do I install michielkempen/nova-froala-field in a Laravel Nova project?
- Install it with composer require michielkempen/nova-froala-field, then reference the field class inside your Nova resource's fields method. Laravel's package auto-discovery should register the service provider; if your application disables discovery, register the provider manually in config/app.php. Run php artisan vendor:publish if the package exposes configuration or assets, and clear cached config and views afterwards so the new settings take effect.
- Does this Froala field support Laravel Nova 4 and Laravel 11?
- Verify this against the package's composer.json constraints before committing, because the 4.0.0 release notes are empty and the supported PHP, Laravel, and Nova matrix is not documented in the available material. A major version bump usually signals breaking changes and possibly a higher PHP floor, which can force a framework upgrade in the same window. Freeze to an explicit version constraint rather than a caret range until you have reviewed the diff and run your test suite.
- How do I configure the Froala toolbar options in this Nova field?
- Toolbar settings are usually set on the field instance or through the published config file, and they map onto Froala's toolbar button arrays. Run vendor:publish and inspect the resulting config file for the exact key names, since defaults can be renamed between major versions. Keep the toolbar definition in one place per field so upgrades produce a small, reviewable diff.
- How does image upload and image handling work with the Froala editor field?
- Froala can insert images by URL or upload them to an endpoint, and this field typically exposes options for the upload path and file manager behaviour. Whether uploads hit a package-provided route or your own controller depends on the configuration, so review the published config and any routes the package registers. Always validate mime types and size limits server-side regardless of editor settings, and confirm the filesystem disk and driver assumptions in your deploy environment.
- Is there an upgrade guide for version 4.0.0 and what changed from v3?
- As of the available material, 4.0.0 ships with no published changelog or upgrade guide, which is a hard blocker for an upgrade decision. The practical workaround is to diff the v3 and v4 tags directly and enumerate renamed config keys, removed methods, and changed signatures. Treat v4 as unreviewed until you have that diff plus a passing run of your own test suite in a scratch environment.
- Does this Nova field package ship migrations or its own database tables?
- A WYSIWYG field is normally stateless: it renders an editor over an existing column and stores HTML in your model attribute, so it should not need tables of its own. Confirm by checking the package for a migrations directory or publishable migration assets before you deploy. If migrations do exist, exercise them against a production-shaped dataset in staging, since DDL differences between MySQL and Postgres can bite.
- How do I test a Nova Froala field in my application's test suite?
- In Laravel feature tests you can assert the field renders within the resource and that HTML submitted through the resource is persisted on your model. Froala itself is JavaScript, so editor UI behaviour needs Dusk or another headless browser if you care about it; server-side tests should focus on validation and sanitization. Sanitize stored HTML on output, since the editor saves raw markup.
- What are the alternatives to this package for rich text editing in Laravel Nova?
- Options include Nova's built-in textarea and markdown fields, other Froala or TinyMCE Nova field packages, and headless editor integrations you wire up yourself. Weigh maintenance activity, Nova major version compatibility, and whether the package's image handling matches your storage setup. If long-term stability matters, favour a field with a visible CI matrix and recent releases.
- Is michielkempen/nova-froala-field actively maintained and does it have a security policy?
- Check the repository's release cadence, how quickly open issues get responses, and whether a security disclosure policy is published before adopting it. Maintainer concentration matters: a single-maintainer package needs a documented plan for a fork or replacement. Run composer why after install to audit the transitive dependency surface, since one abandoned sub-dependency is a long-tail liability.
- How do I publish and customise this package's config file in a Laravel app?
- Run php artisan vendor:publish and select the provider tag belonging to this package to copy its config and any assets into your application. Commit the published file so configuration drift appears in diffs when you upgrade. Remember to clear config and view caches in your deploy pipeline, and diff the published file against the version currently in your repo before merging an upgrade.