- How do I install rias/statamic-redirect in a Statamic site?
- Install it with Composer and publish its configuration file; in the typical flat-file setup there is no database migration, so rollback is trivial. The package registers itself through Statamic's addon manifest, so the Control Panel UI and redirect middleware become available without touching your server config. Confirm your Statamic minor version and PHP constraint match the addon's composer.json before installing. After install, verify the middleware is actually in the request path before you rely on any redirect.
- Does rias/statamic-redirect work in a plain Laravel app without Statamic?
- No. This is a Statamic addon, not a standalone Laravel package, and its value depends entirely on the application already running Statamic on Laravel. For a Laravel-only application, use something like spatie/laravel-missing-page-redirector or a route-level redirect table instead. Installing it without Statamic adds an abstraction you cannot actually use.
- Which Statamic and Laravel versions does this redirect addon support?
- The evaluation indicates Statamic v3, v4 and v5 support on Laravel, but there is a metadata anomaly in the reported release date, so do not assume active maintenance. Check the composer.json constraints and the repository tags directly, and look for a CI matrix proving the supported combinations. Pin the version you validate and re-check after any upgrade of Statamic or PHP.
- How are redirects stored, and will thousands of rules slow down my site?
- In the typical flat-file variant, redirect definitions live in YAML or flat files and are parsed per request unless a cache or compiled index is in place. A few hundred rules are generally fine; thousands may show up as measurable latency because the middleware sits in the hot path of every request. Tens of thousands of rules are not viable without an index or exporting them to a CDN edge. Ask the maintainer whether a compiled cache exists before importing a large legacy rule set.
- Why are my redirects not working when Statamic static caching is enabled?
- Statamic's static cache can serve a page without invoking the redirect middleware, so a redirect added in the Control Panel may appear to have no effect. Purge or invalidate the static cache after saving a redirect and confirm the response with curl. Test with caching disabled first to isolate whether the problem is the rule or the cache layer.
- Does it support wildcards, query strings, and 301 vs 302 status codes?
- Wildcards for dynamic URLs and 301/302 rules are the documented core features. Support for 307/308, query-string preservation, trailing-slash normalization and case handling is not clearly documented in the available material, so verify each behavior you depend on with a test redirect. Do not assume query strings are carried over to the destination.
- How does rias/statamic-redirect handle redirect loops and chains?
- The available evaluation does not establish whether chains and loops are detected at save time, at request time, or not at all. A circular target or regex backtracking in the middleware can turn into a 500 for the whole site rather than a graceful fallback, which is the highest-severity failure mode here. Validate your rule set for loops before deployment and keep a kill switch, such as a config flag, so you can disable the middleware quickly.
- Is rias/statamic-redirect safe to use in production?
- It is a small, single-maintainer addon with low adoption, roughly 29 stars, no dependents and no third-party validation, so the bus factor is the main concern. The maintainer is well known in the Statamic community, which raises the quality prior, but that is not the same as a proven release history. Audit the code, pin the version, and confirm the license allows you to fork and own it if maintenance lapses.
- Are redirects scoped per site in a Statamic multisite install?
- This is not established in the available documentation and is one of the open questions to put to the maintainer. Whether redirects are global or scoped per site changes how you model legacy URL migrations across domains. Test with a staging multisite before importing rules.
- How should I migrate existing .htaccess or CDN redirects into this addon?
- Treat it as a consolidation project, not an install. Inventory every existing redirect source, including CDN edge rules, web-server config, legacy CMS tables and marketing spreadsheets, into one list with source, target, status code and owner, load that into the addon, then explicitly disable the superseded mechanisms in the same change window. Half-migrated redirect state with two systems active at once is the most common source of ordering bugs.