Weave Code
Filament Ban Manager Laravel Package
rectitude-open/filament-ban-manager
A Filament plugin for Laravel that adds user ban management to your admin panel. Review active and expired bans, ban or unban users, record reasons and expiration dates, and keep moderation actions organized in one Filament resource for faster admin workflows.
The Filament plugin for model & IP ban management
Frequently asked questions about Filament Ban Manager
- What is rectitude-open/filament-ban-manager used for?
- It is a Filament plugin for Laravel that adds model and IP ban management to an admin panel. Admins can review active and expired bans, ban or unban users, and record reasons and expiration dates in one Filament resource. It is intended for teams already using Filament, not for headless or non-Filament backends.
- How do I install filament-ban-manager in a Laravel Filament panel?
- Install it with Composer using rectitude-open/filament-ban-manager, then register BanManagerPlugin::make() on the relevant Filament panel. Publish config and translations as documented, and run package migrations if the package owns the bans table. Confirm PHP, Laravel, and Filament constraints before installing.
- Which Filament versions does filament-ban-manager support?
- The package is built as a Filament panel plugin and its Composer constraints target the Filament v3/v4 line. Always check the installed Filament major against the package's composer.json before upgrading. A Filament major release is the main compatibility trigger, so pin the package version rather than floating it.
- Does filament-ban-manager enforce bans at the Laravel auth level?
- The plugin provides ban management in the Filament admin UI; the assessment notes that ban enforcement is not clearly handled by the package itself. Your Laravel app should own authentication and any middleware or guard checks that block banned users. Treat the plugin as the moderation interface, not the enforcement layer.
- Can I use filament-ban-manager without Filament or in an API-only Laravel app?
- No, the ban logic is coupled to Filament's admin UI layer, so it adds little to headless or API-only backends. It is appropriate only when your application already runs a Filament panel. For non-Filament apps, implement ban state and enforcement directly in your Laravel models and middleware.
- How do I translate filament-ban-manager labels into my locale?
- Version 1.11.0 moved label strings into translation keys and expanded locale coverage. Publish the package translations with php artisan vendor:publish, then add or override locale files for your target languages. Smoke-test ban and unban flows and notification copy in each enabled locale.
- Is there a navigation badge for active bans in filament-ban-manager?
- Yes, v1.11.0 adds an opt-in navigation badge configuration option for ban-count visibility. It is optional and does not change existing behavior unless enabled. On large ban tables, confirm the badge does not introduce noisy queries before enabling it in production.
- Does upgrading filament-ban-manager from 1.10.x to 1.11.0 require migrations?
- No, v1.11.0 is described as an incremental, drop-in release with no mandatory migration or config-publish step. The changes are additive: translation string migration, expanded locales, and the navigation badge option. English defaults remain, so existing untranslated labels should continue to work.
- What are the maintenance risks of using filament-ban-manager?
- The main risks are dependency coupling to Filament major versions and the project's single-maintainer, small-audience status. Pin the package version and review each release diff before upgrading. Track Filament major releases as the primary upgrade trigger rather than the plugin's own semver.
- Does filament-ban-manager own the bans database table or expect my schema?
- The assessment flags this as something to confirm in the package README and migrations. Review whether the package publishes its own bans table or maps to an existing model before installing. If your app already has ban records, plan how the Filament resource will map to that schema.
Weaver
How can I help you explore Laravel packages today?