The above entry was working fine in 2.x, after upgrading to 3.9 simply landed on 404 page.
If I go back to the url tracker entry and check Force Redirect, than it works.
I dont know if its ideal to do that, to set Force Redirect for all the links.
The same was the case for within umbraco redirects; ie. oldurl /somepage redirecturl: /some-other-page
It wasnt working, till i go back and manually edit the entry field Force Redirect to true.
Any particular reason why is this happening? I have hundreds of entries like that and need manual editing.
I am not sure about the consequences of Force Redirect.
It seems the log isn't complete, there should be more info about why the Url Tracker is not able to find a redirect. So that's the first thing I notice.
Force redirect simply means the redirect is executed before Umbraco gets a chance to find content, so it happens earlier in the pipeline.
Why the redirect is not working is impossible for me to tell with this amount of information, sorry.
i had to turn off the debugging as it was live and size became unmanageable.
From 2.x to 3.9, upgrade scenario with no domain change, what are the likely cause of redirects not working?
If they are edited and set to force redirect they work, but not without.
would appreciate if you can share your thoughts on the likely/potential cause.
I realized if I edit the very same entries (mentioned above) and check Force Redirect, than redirects are working.
As there are tons of them, is there a workaround? Can I safely go back to previous version of URL tracker after installing 3.9?
Or can i somehow set Force Redirect to checked by default?
Redirects not working after upgrade from 2.x to 3.9
Using 7.1.8, upgraded the package from 2.x (working fine but getting way too many db hits) to 3.9 with no upgrades to the umbraco.
The redirects like /pageabc to /someotherpage or /page123 to http://somewebsite/page123
stopped working.
Tried enabling debug mode, i observed following
URL Tracker entry for that url was recorded as following in URL tracker UI;
Old Url: download-ACMEbrochure
Old Url Querystring: [empty]
Redirect URL: http://someotherpage/acmebrochure
Redirect Type: Temporary (302)
Forward QueryString: Yes
Force Redirect : unchecked
The above entry was working fine in 2.x, after upgrading to 3.9 simply landed on 404 page.
If I go back to the url tracker entry and check Force Redirect, than it works.
I dont know if its ideal to do that, to set Force Redirect for all the links.
The same was the case for within umbraco redirects; ie. oldurl /somepage redirecturl: /some-other-page
It wasnt working, till i go back and manually edit the entry field Force Redirect to true.
Any particular reason why is this happening? I have hundreds of entries like that and need manual editing. I am not sure about the consequences of Force Redirect.
Would appreciate your advise.
Hi!
It seems the log isn't complete, there should be more info about why the Url Tracker is not able to find a redirect. So that's the first thing I notice.
Force redirect simply means the redirect is executed before Umbraco gets a chance to find content, so it happens earlier in the pipeline.
Why the redirect is not working is impossible for me to tell with this amount of information, sorry.
thank you for the swifth reply!
i had to turn off the debugging as it was live and size became unmanageable.
From 2.x to 3.9, upgrade scenario with no domain change, what are the likely cause of redirects not working? If they are edited and set to force redirect they work, but not without.
would appreciate if you can share your thoughts on the likely/potential cause.
I realized if I edit the very same entries (mentioned above) and check Force Redirect, than redirects are working.
As there are tons of them, is there a workaround? Can I safely go back to previous version of URL tracker after installing 3.9? Or can i somehow set Force Redirect to checked by default?
would greatly appreciate your advise
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.