- What is Filament Mails (vormkracht10/filament-mails) used for?
- Filament Mails is a Laravel package that brings email management into a Filament admin panel. It lets you browse and manage mailables, preview rendered emails, send test emails, and work with reusable templates and variables. The provided overview also describes inspecting sent messages, previewing HTML and attachments, resending mail, and debugging delivery issues from the dashboard.
- How do I install Filament Mails in a Laravel Filament app?
- Install it with Composer using composer require vormkracht10/filament-mails, then register the plugin or resources in your Filament panel as described in the repository README. The package exposes a native Filament UI with mail-related resources and pages such as ListMails. The provided context does not list exact publish, migration, or configuration steps, so confirm those in the README for your Filament version.
- Does Filament Mails work with Filament v5?
- Yes, for Filament v5 users the minimum safe version is v3.0.15. That release is a compatibility patch for Filament v5.7.0 and later and is intended to work across the filament/filament ^5.0 range. Earlier releases could fail during package discovery because of an unmountAction method signature mismatch.
- Which Laravel and PHP versions does Filament Mails support?
- The provided context does not specify exact Laravel and PHP version constraints. Check the package composer.json and README for the supported Laravel and PHP ranges, and confirm whether CI covers the full filament/filament ^5.0 range. For Filament compatibility, v3.0.15 is documented as the minimum safe version for Filament v5.7.0 and later.
- How do I preview and send test emails from the Filament dashboard?
- In the Filament dashboard, open the package's mail resource to preview a rendered mailable or template before sending. You can send test emails to verify content quickly without leaving the admin panel. Reusable templates and variables help you keep transactional messages consistent.
- Can I browse, search, and resend sent emails with Filament Mails?
- Yes. The package's Filament UI lets you browse, search, and inspect sent messages, preview the rendered HTML and attachments, resend mail, and debug delivery issues. It does not replace Laravel's mail transport; it gives you a backstage view of outgoing email inside Filament.
- Do I need to change application code to upgrade to v3.0.15?
- No. The v3.0.15 release note requires only a Composer update for the package, with no application code changes. Update in a branch, commit the updated lockfile, and deploy through your normal release process. Verify package discovery completes and smoke-test the ListMails page and action unmount or cancel flows.
- Why does Filament Mails fail during package discovery with an unmountAction signature error?
- The prior release caused a fatal error during package discovery because ListMails::unmountAction() had a narrower signature than Filament's widened bool|string|null $cancelParentActions = null parameter. Version 3.0.15 accepts the widest type and forwards only the arguments it receives. That restores compatibility across filament/filament ^5.0, including the new string-based named parent action path.
- How should I test the Filament Mails upgrade in CI or staging?
- Update in a branch and run CI against the Filament version you intend to use. Confirm package discovery completes without a fatal signature error, then smoke-test the ListMails page plus action unmount and cancel flows, including cancellation up to a named parent action. Add targeted smoke coverage for that string-based path if your app relies on it.
- Is Filament Mails safe for production and how do I roll back if something breaks?
- The change is a targeted compatibility patch with low maintenance impact and no meaningful runtime scaling effect, since it affects Filament page and action compatibility rather than mail throughput or storage. Residual risks include other overrides becoming incompatible with future Filament signature changes and regressions in action cancellation behavior. Detect issues through CI package discovery and targeted UI smoke tests, and roll back by reverting the lockfile if discovery or action behavior regresses.