- How do I install filament-newsletter in a Laravel app?
- Install it with Composer using jeffersongoncalves/filament-newsletter and register the package's Filament plugin provider in your panel. The package is a thin Filament panel plugin over jeffersongoncalves/laravel-newsletter, so it does not require bespoke infrastructure. Check the resolved laravel-newsletter constraint before committing, because 1.1.0 bumped it to ^2.0.
- Which Laravel and Filament versions does filament-newsletter support?
- The package is built for Laravel applications with a Filament admin panel, but the exact version constraints are defined in its composer.json. The technical notes warn that laravel-newsletter 2.x may raise its own PHP or Laravel floor, so verify the composer require block before upgrading. Do not assume 1.1.0 is a translations-only change without checking platform requirements.
- What is the difference between filament-newsletter and laravel-newsletter?
- filament-newsletter is the Filament admin UI layer, providing resources and pages for subscribers, mailing lists, and campaigns. laravel-newsletter is the underlying domain library that handles newsletter behavior such as sending and tracking. Keeping domain logic out of the panel layer is the intended architecture, so evaluate upgrades to each package separately.
- Why did filament-newsletter 1.1.0 upgrade laravel-newsletter to ^2.0?
- Release 1.1.0 included a Dependabot group pull request that bumped the required jeffersongoncalves/laravel-newsletter from ^1.0 to ^2.0. That is a caret-major bump on the domain library, so it can affect sending behavior, config keys, queue and job contracts, and database schema expectations. Treat it as a real upgrade path rather than a routine dependency update.
- Can I install filament-newsletter 1.1.0 while keeping laravel-newsletter ^1.0?
- That depends on whether the ^2.0 constraint in filament-newsletter 1.1.0 is hard in Composer. The recommended approach is to try pinning laravel-newsletter to ^1.0 and adopting 1.1.0 for translations only if the constraint allows it. If it does not, evaluate 2.x independently in a branch before flipping the constraint.
- Does filament-newsletter handle double opt-in emails and open and click tracking?
- The package is described as composing, scheduling, and sending double opt-in email newsletters with open and click tracking. The Filament plugin itself supplies admin UI over the laravel-newsletter domain library, so confirm which behavior is implemented by the domain package versus rendered by the plugin. This matters when scoping translation-quality and subscriber-facing email risk.
- Does filament-newsletter support RTL languages such as Arabic and Farsi?
- Version 1.1.0 added 17 locales, including ar and fa, which are RTL languages. Filament handles RTL reasonably, but custom views and emails around the plugin are unlikely to have been RTL-tested. Enabling these locales is a UI QA commitment rather than a free win.
- Is filament-newsletter production ready and well maintained?
- The package is a straightforward Composer package registered through a Filament plugin provider, but it has single-maintainer concentration. Author, release management, CI standardization, and funding changes are all handled by one individual, with the sole external contribution being translations. Bus-factor and long-term support are standing risks to weigh before relying on it in production.
- How should I test filament-newsletter before sending a real campaign?
- Exercise your actual send path in a branch or staging environment, including queued jobs and mailable signatures, because laravel-newsletter 2.x may change contracts. Diff published config and assets and check for schema migrations before promoting the change. Also verify locale directory naming, especially zh_CN, resolves instead of silently falling back to English.
- What are the alternatives to filament-newsletter for Laravel newsletters?
- The technical notes do not name specific alternatives, so compare other Filament newsletter plugins or build admin screens directly on laravel-newsletter. Because filament-newsletter is a thin UI wrapper, the main alternative is using the domain library with your own Filament resources. Evaluate alternatives on the same criteria: dependency constraints, maintainer risk, and subscriber-facing email behavior.