Feature Request
-
This relates to manual redirects.
The Issue
When a manual redirect is set, many people might forget to add the trailing slash. This means the redirect fails when a referring link uses a trailing slash but the configured redirect does not; the same is true vice versa.
For example
example.com/apples is not the same as example.com/apples/Likewise
example.com/apples/ is not the same as example.com/applesWhen slug lacks a trailing slash the redirect only works when the link followed lacks the trailing slash.
When slug has a trailing slash the redirect only works when the link followed has the trailing slash.
When I set manual redirects I use the non trailing slash version of the redirected URL slug then add .? to the end of it (I know I could, probably should, use a a forward slash instead of a dot) and set the redirect as a regex.
Another option is to use two separate redirects: one with and one without the trailing slash.
The Request
Can you add a tick-box option to cover trailing slashes e.g. ‘This redirect should work whether there is or is not a trailing slash (yes/no)’ i.e /? or \/? (I’m not sure whether forward slashes need to be commented or not for 404 Solution).
Can you add a tick-box to cover the redirected slug and anything that might follow it e.g ‘This redirect should work for this slug and any extensions of this slug (yes/no)’ i.e .*? or .+? or \/?.*? etc.., whichever is less resource hungry.
I think this will be easier for people unfamiliar with regexes to understand.
Thank you for your great work on 404 Solution.
Lee
-
Hi Aaron,
I apologise for my late reply. I have been ill the past few weeks.
Just gotten around to testing this. For some strange reason the redirects no longer work at all.
I will see whether I can discover any faults. If i can I will let you know.
Edit:
It’s strange. I can only attest to what I know as of today, having not checked before today.
– Manual redirects created before today seem to work as expected.
– A manual redirect edited today does not work.
– Deleting the edited redirect and creating it afresh did not resolve the fault.
– Automatic redirects appear to work fine.
– I tested manual redirects with the option to create automatic redirects disabled.
– I purged all automatic redirects, ran maintenance and further optimized the database with WP Optimize. This did not solve the problem.
– I cleared the website cache, the CDN cache and the browser cache + restarted the browser and tried with a VPN. The new redirect still failed to work.
– htaccess does not include any redirects for this particular 404 Solution redirected page.
– The 404 Solution debug log is empty. It wasn’t until I cleared it 30 minutes ago. No new logs have been written to it.
– No errors related to this issue have been recorded by the server.
– No errors are being sent to me via Fatal Error Notify (a WordPress plugin that reports errors).
– WP Debug is not reporting any 404 Solution / redirect errors.I will check on this again in a couple of hours just in case there is another network cache set by the site’s host or my ISP. Will keep you informed.
–You would be surprised how some sites are set up. Generally, I agree with you. What if the page is put into draft, will that trigger 404 Solution when the page is requested?
Edit: I can answer that. Putting a post/page into draft triggers 404 Solution redirects for anonymous visitors but not for logged in users with permission to view or edit draft posts.
- The topic ‘Feature Request’ is closed to new replies.
