- What is devonab/filament-easy-footer used for?
- It is a Filament plugin that adds a customizable footer to Laravel Filament admin panels. You can configure footer position, custom text, a logo with a link, and optional GitHub version, installed version, and load time displays. It works at the presentation layer and adds no database migrations, queues, or persistent storage.
- How do I install filament-easy-footer in a Laravel Filament app?
- Install it with Composer, then add EasyFooterPlugin::make() to your Filament panel provider's plugin array. You can optionally publish the config and views to customize behavior. If you use the package's Tailwind styles, you must also add the required vendor @source entry to a custom Filament theme and compile the assets.
- Which Filament versions does filament-easy-footer support?
- Package v1 supports Filament v3, while package v2 supports Filament v4 and v5. For new Filament v4 or v5 projects, require devonab/filament-easy-footer:^2.0. Always verify the PHP and Laravel constraints in your application's Composer lock before upgrading.
- Why is my Filament EasyFooter styling missing or unstyled?
- The package's Tailwind classes are not automatically included in Filament's compiled CSS. You need a custom Filament theme that adds an @source entry for the package's vendor views, then rebuild the frontend assets. Without that step, Tailwind may purge the footer styles and the footer will look broken or plain.
- How do I customize the footer text, logo, and link in Filament?
- Configure the plugin in your panel provider using the available footer options for sentence text, logo, link, and position. The sentence option accepts an HtmlString with a whitelist of allowed tags, so only use trusted content. Publish the config if you prefer file-based defaults, and verify the rendered output in a preview panel.
- Can I hide the Filament footer on login or specific pages?
- Yes, the plugin provides footer enable controls and page-hiding options so you can suppress the footer on auth pages or selected panels. Test the behavior on login, registration, and password reset pages before release. You can also disable the plugin entirely as a simple rollback path.
- How does the GitHub version display work and do I need a token?
- The optional GitHub version display makes external API calls and can use a token, with caching that defaults to a 3600-second TTL. You must account for rate limits, private repository permissions, token rotation, and network failure paths. The GitHub display is not required, so leave it disabled if you do not have an owner for the token.
- Why does the installed version not show in production?
- Composer installed-version detection can fail in deployments that are not VCS checkouts, such as some artifact or container builds. Verify how your deployment records package metadata and test the footer in a production-like environment. If detection is unreliable, use custom footer text or the GitHub version display instead.
- Is filament-easy-footer safe for production?
- It is a low-risk presentation plugin with a small blast radius, but it is not widely proven: the repository has around 39 stars and zero dependents and is effectively single-maintainer. Pin a specific released version, review any external links or GitHub token usage, and test upgrades alongside Filament major versions. You can roll back by disabling the plugin or the footerEnabled() option.
- What are alternatives to filament-easy-footer and how should I maintain it?
- Alternatives include a custom Blade footer or your own Filament render hook, which avoids a third-party dependency but requires more code. If you adopt the package, assign an internal owner to track Filament majors, package releases, configuration, and token rotation. Because it is MIT licensed and small, a fork or local patch is feasible if the maintainer becomes inactive, but there is no evident commercial SLA.