Weave Code
Redirect Bundle Laravel Package
opifer/redirect-bundle
Opifer RedirectBundle is a Symfony package for creating and managing URL redirects. It lets applications map old paths to new destinations, handle redirect responses, and avoid broken links when content moves. Useful for SEO-friendly URL changes and legacy route support.
[READ-ONLY] Subtree split of the Opifer Redirect Bundle
Frequently asked questions about Redirect Bundle
- Is opifer/redirect-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. It depends on Symfony's bundle system, dependency injection container, event dispatcher, and Doctrine ORM. Its redirect handling is built around Symfony's routing and kernel events.
- Can I install opifer/redirect-bundle in a Laravel application?
- No, not without a rewrite. Laravel uses service providers and middleware rather than Symfony bundles, so the package's registration and request-listener model does not map onto Laravel. For a Laravel app, implement redirects with a database table plus middleware or a Laravel-native package.
- Does opifer/redirect-bundle support Laravel 10 or Laravel 11?
- There is no Laravel version support because the package is a Symfony bundle. It does not ship a Laravel service provider or middleware. Do not expect it to work on Laravel 10, Laravel 11, or any Laravel release.
- How do I install and enable opifer/redirect-bundle in Symfony?
- Install it with Composer and register the bundle in your Symfony kernel, following the bundle's documented registration. You will also need Doctrine set up for the redirect entity's table. Because the project is tied to the Opifer CMS stack, verify that any admin UI you expect is actually present in the split repository before relying on it.
- Which Symfony and PHP versions does opifer/redirect-bundle support?
- Release 0.1.4 provides no evidence of modern Symfony or PHP support. The bundle originates from the Symfony 2-era Opifer CMS distribution, and a matcher swap is not a compatibility upgrade. Treat it as legacy-only and confirm compatibility against your exact Symfony and PHP versions before attempting an install.
- What changed in opifer/redirect-bundle 0.1.4?
- Version 0.1.4 replaces the bundle's own RedirectableUrlMatcher with Symfony's core UrlMatcher. That is a behavior-contract change in a patch release: redirect resolution may move out of, or be reordered within, the routing layer. Test for silent 404 regressions and check whether redirects now depend on listener priority relative to the router.
- Does opifer/redirect-bundle include the admin UI for managing redirects?
- The admin interface belongs to the broader Opifer CMS stack, and this repository is a subtree split of that monorepo. The split may not contain the full UI, so check exactly what is shipped. If the UI is not included, your operational model becomes direct database authoring or a custom admin screen.
- Is opifer/redirect-bundle still maintained?
- Effectively no. It has no security patching, no PHP 8 compatibility work, no dependency upgrades, and no stated support commitment. It was previously described as a read-only subtree split, and a single 0.1.4 tag does not establish a release cadence. Adoption signal is minimal, so there is little community to surface defects or absorb risk.
- What are the alternatives to opifer/redirect-bundle for Laravel apps?
- Use a Laravel-native approach: a redirects table with source path, target, and status code, served by middleware that runs before routing. You can also use a maintained Laravel redirect package, but evaluate its maintenance and Laravel version support. The feature is small enough that a custom middleware implementation is often the lowest-risk choice.
- What should I test before relying on opifer/redirect-bundle in production?
- Test exact-match versus regex behavior, 301/302/307 status codes, query-string preservation, case sensitivity, trailing-slash normalization, and hit counting. Confirm whether redirects resolve inside the URL matcher or in the kernel listener and how that interacts with router priority. Also verify where redirect rules are authored and how a fork would be owned, since the real project is the parent monorepo.
Weaver
How can I help you explore Laravel packages today?