Weave Code
Filament Redirects Laravel Package
cube-agency/filament-redirects
A Filament plugin for managing URL redirects directly from your admin panel. Create and edit redirects, set status codes, and keep old links working after URL changes—ideal for Laravel apps using Filament that need simple, SEO-friendly redirect management without touching code.
Redirect management
Frequently asked questions about Filament Redirects
- What is cube-agency/filament-redirects used for?
- It is a Filament plugin for managing URL redirects directly from your Laravel admin panel. You can create and edit redirects, set status codes, and keep old links working after URL changes. It is aimed at Filament-based applications that want simple, SEO-friendly redirect management without editing code.
- How do I install cube-agency/filament-redirects with Composer?
- Install it with composer require cube-agency/filament-redirects, then follow the repository README to register the plugin in your Filament panel and publish any config or assets you need. Pick the package major that matches your stack, because v3 targets Filament 5 and Laravel 13 while v2 targets Filament 4 and Laravel 12. Confirm the exact registration and publish commands in the repo documentation.
- Which Laravel and Filament versions does filament-redirects support?
- Version 3.0.0 is a compatibility-line release that adds support for Filament 5 and Laravel 13. For Laravel 12 and Filament 4 applications, the v2 line is the practical choice. Check the Composer constraints in the repository to confirm minimum PHP and exact framework versions.
- Can I set HTTP status codes such as 301 and 302 on redirects?
- Yes, the plugin lets you create and edit redirects and set their status codes from the admin panel. That covers common SEO cases such as permanent 301 moves after a URL change. Check the UI or README for the exact status-code options exposed.
- Will filament-redirects v3.0.0 break my existing redirects or config?
- v3.0.0 is a major bump aligned to Filament 5 and Laravel 13, and the release notes do not include a detailed breaking-change list. Expect possible namespace, config key, or published asset and migration changes, so re-publish and diff those files against your local overrides. Test the upgrade on a branch before applying it to production.
- How do I upgrade from filament-redirects v2 to v3?
- Treat this as a platform upgrade rather than a simple package bump. First confirm your app is ready for Laravel 13 and Filament 5, validate the Filament 4 to 5 upgrade with the package still on v2 or temporarily excluded, then upgrade the package to v3 and diff published config and assets. Avoid combining the Laravel, Filament, and package upgrades in a single branch.
- Does filament-redirects work with Laravel 12 or only Laravel 13?
- The v3 line targets Laravel 13 and Filament 5. If you are on Laravel 12 with Filament 4, use the v2 line instead, since v3 is not installable in practice on that stack. Before committing long term, confirm whether v2 still receives bug and security fixes.
- Does filament-redirects have a test suite covering the Filament integration?
- The release notes do not detail test coverage, so verify this in the repository before adopting. Look for tests that exercise the Filament panel, resource, and table integration rather than only isolated redirect logic. If coverage is thin, add your own smoke tests for redirect creation, status codes, and resolution behavior.
- Is filament-redirects safe to use in production?
- The blast radius is generally limited to admin and back-office surfaces rather than customer-facing request paths, which lowers severity if an upgrade runs long. The main risk is version coupling to Filament and Laravel majors. Pin versions, track the Filament major in your dependency planning, and test upgrades on a branch before production.
- What are alternatives to filament-redirects for Laravel redirects?
- Alternatives include general Laravel redirect packages such as spatie/laravel-redirects and other Filament plugins that expose redirect management in the admin panel. Choose based on whether you want deep Filament integration or a framework-agnostic redirect layer. If your application is already Filament-centric, this package's thin integration surface is the main draw.
Weaver
How can I help you explore Laravel packages today?