- How do I install filament-mail-editor in a Laravel Filament panel?
- Install the package with Composer, then publish the config using the mail-editor-config tag and the migrations using the mail-editor-migrations tag. Run your migrations and register the plugin in your Filament panel provider. The core laravel-mail-editor package is pulled in automatically as a transitive dependency, so the install surface is a single Composer requirement.
- Can I edit email templates without touching Blade files?
- Yes. The plugin adds a visual editor for HTML mail content plus template management for subject lines, bodies, and variables. Routine copy changes can be made directly from the Filament admin panel instead of editing Blade files and deploying code.
- Does Filament Mail Editor work with existing Laravel mailables and notifications?
- Yes. It is designed to work alongside standard Laravel mailables and notifications, letting teams update the subject and content tied to those messages from the admin panel. You keep your existing mailables while moving routine template editing into Filament.
- How do I upgrade from a pre-1.1.0 version of filament-mail-editor?
- Upgrades from any pre-1.1.0 install are not drop-in. Four breaking changes land together: namespace relocation across app code, a config file and key rename, route path and route-name changes, and an export format identifier change. Treat it as one coordinated migration, plan a namespace rewrite across app code and published config, and avoid a partial cutover between environments.
- Why do old email preview or countdown links return 404 after upgrading?
- Preview and countdown routes moved from /filament-mail-editor/* to /mail-editor/*. If those URLs were embedded in emails already dispatched to recipients, previously sent mail will 404 after deploy unless you add a redirect, alias, or documented rewrite rule. Check whether those routes appear in sent email before rolling out the upgrade.
- Can I add custom blocks to the mail template builder?
- Yes. The HasPropsSchema contract turns custom blocks into a supported extension point instead of requiring you to hack the form schema. That is useful for bespoke block types such as product grids, personalized content, or dynamic pricing tables. Check the documented backward-compatibility policy for the contract before relying on it heavily.
- Is version 1.1.0 of filament-mail-editor a breaking release?
- Technically yes. Namespace moves, config key renames, and route renames are breaking changes under SemVer and would normally warrant 2.0.0. Because they shipped as 1.1.0, a ^1.1 constraint can silently pull a breaking release, so pin an exact version and verify the constraint in your composer.json.
- How do I restrict who can access the mail editor in Filament?
- The plugin integrates with Filament panel authorization support, so access is controlled through Filament's standard authorization mechanisms rather than a separate permission system. Define the appropriate policies or gates in your panel and verify them in staging before giving editors access to production templates.
- Does the package support live preview and Blade variables?
- Yes. The plugin includes a visual editor for HTML mail content with live preview, and it supports Blade variables in templates. Note that smoke tests confirm the Filament pages render, not that preview rendering is faithful across every mail client, so check important templates in the clients your recipients actually use.
- Can I import and export mail templates between environments?
- Template export and import are supported, but compatibility is one-directional. Exports from filament-mail-editor still import into 1.1.0, while 1.1.0 exports will not import into older installs. Avoid running mixed versions across staging and production or sharing a template library between them, because that can produce asymmetric import failures.