LS Cache conflict with 301 Redirects (by Web Factory)
-
I’ve just activated LS Cache and then edited one of my 301 redirects, to find that it stopped working and I got a “Page not found” error. (Existing redirects continued to work, it was only the one I edited that broke.) Deactivated LS Cache, re-saved the redirect and it was fine again. Reactived LS Cache and the redirect continued to work.
So I have a workaround, but I’m sure I shouldn’t need to deactivate LS Cache to be able to edit a 301 redirect successfully!
-
Apologies for the delay in replying; I’ve just found the notification in my spam folder.
I’m finding that, if LSCache is activated and I edit or add a 301 redirect in the 301 Redirects app, the redirection doesn’t work (even if I’ve edited one that was previously working).
If I deactivate LSCache and re-save the redirect (can’t remember whether I actually edited it again first) then it works fine, and it continues to work once LSCache is reactived.
- The topic ‘LS Cache conflict with 301 Redirects (by Web Factory)’ is closed to new replies.
