Weave Code
Filament Error Pages Laravel Package
cmsmaxinc/filament-error-pages
Filament Error Pages replaces Laravel’s default error screens with branded, Filament-styled pages for your admin panel. Customize 404, 403, 500 and other error views to match your app, with simple configuration and a consistent user experience.
This plugin provides a more user-friendly error page for Filament panels when an error occurs. Outside the Filament panel, the default Laravel error page will be displayed.
Frequently asked questions about Filament Error Pages
- How do I install filament-error-pages in a Laravel Filament app?
- Install the package with Composer using cmsmaxinc/filament-error-pages, then register the plugin in your Filament panel provider. You can optionally publish the config and error views to customize them for your application. After registration, Filament panel errors will use the package's styled error pages instead of Laravel's default screens.
- Does filament-error-pages support Filament v3?
- The package is designed for Filament panels and the v2.1 release is a minor update focused on tenant resolution for error pages. Check the package's Composer constraints and README for the exact Filament and Laravel versions supported before upgrading. It is safest to verify compatibility in a staging environment with your current Filament version.
- Can I customize the 404, 403, and 500 error pages?
- Yes, the package is built around customizable Filament-styled error views, including common status codes such as 404, 403, and 500. You can publish the views and configuration, then adjust branding, messaging, and layout to match your admin panel. This gives you a consistent user experience instead of exposing Laravel's default error screen inside Filament.
- Does it replace error pages outside the Filament panel?
- No, the plugin only provides user-friendly error pages inside Filament panels. Outside the Filament panel, Laravel's default error page will still be displayed. If you need branded errors for public routes as well, you should customize Laravel's standard error views separately.
- Does filament-error-pages support multi-tenant Filament panels?
- Yes, v2.1 adds support for slug and subdomain tenant resolution on error pages, which is useful for multi-tenant Filament applications. This lets error pages respect tenant context when rendering inside the panel. You should still test both slug and subdomain tenant setups in staging before relying on it in production.
- What happens if a tenant cannot be resolved on an error page?
- Unresolved tenant handling depends on your configuration and the package's fallback behavior, so you should explicitly test invalid or missing tenants. Make sure the error page fails safely, such as falling back to a generic page rather than throwing another exception. Avoid tenant resolution logic that performs fragile database calls during error rendering.
- Is there a performance penalty for rendering these Filament error pages?
- Error pages are rendered on demand and are typically lightweight, so the overhead should be negligible in normal use. Tenant resolution during error rendering adds some work, but it is not a hot path compared with regular application requests. The bigger concern is avoiding database or resolver calls that may fail while handling an error.
- Can error page rendering cause recursive error loops in production?
- There is a non-trivial risk if an exception occurs while rendering the error page, such as during tenant resolution or view rendering. Misconfigured tenant resolution could also leak tenant context or trigger cascading failures. Use safe fallbacks, monitor error page rendering, and test failure scenarios before rolling out to production.
- How should I test Filament error pages before deploying?
- Install and enable the package in a staging environment with representative tenant setups. Trigger 404, 403, and 500 errors for both slug and subdomain tenants inside the Filament panel, then validate fallback behavior for invalid or missing tenants. Also confirm that non-Filament routes still use Laravel's default error pages.
- Is filament-error-pages actively maintained and what are the alternatives?
- It is a community package with a recent contributor and active pull request activity, and v2.1 is a focused feature addition for tenancy support. Alternatives include Laravel's default error views, custom Filament error pages built in your application, or other Filament error page packages. Plan for periodic dependency updates and watch for breaking changes in future major versions.
Weaver
How can I help you explore Laravel packages today?