Troubleshooting

A redirect doesn't fire

Check the following in order:

• Is the redirect set to Active? Only active redirects are considered (Manage redirects).
• Does the source path match exactly the requested path? Matching happens without wildcards — even a missing leading / or a differing trailing slash (/page vs. /page/) will prevent a match.
• Does the requested path include a query string (?…)? That is ignored during matching and should not be included in the source path.
• Test in a private browser window or clear your browser cache — 301 redirects in particular are cached aggressively by browsers.

Infinite loop, or the redirect does nothing

If the target URL is identical to the source path, the redirect intentionally does not fire — this is a built-in safeguard against infinite loops. Check the target URL in the edit form and correct it.

A 404 error doesn't show up in the log

• Is the Log 404 errors setting enabled? Nothing is captured while it's disabled.
• Does the path fall under one of the excluded prefixes (/api, /admin, /store-api, /_, /bundles, /theme, /media, /thumbnail)? These are never logged.
• Was it a main request? Ajax or background requests that result in a 404 are not captured, only full page loads.

Can't create a duplicate source path

The source path is unique per redirect (a UNIQUE constraint in the database). Don't create a second redirect for the same source path — instead, edit the existing redirect under Manage redirects.

Tables remain after uninstalling

When you uninstall the plugin, the futi_redirect and futi_redirect_404_log tables are not removed automatically. Your redirects and your 404 log are therefore preserved if you reinstall the plugin later. If you want to remove the tables deliberately, you'll need to do so manually in the database.

---

Still stuck? Write to us at support@fulltime-ecommerce.de.