Manual redirects not working with root set to /

Question

Manual redirects not working with root set to /

jonathanS8080 opened this issue 10 years ago · 32 comments

Hi,
We have installed the URL Tracker onto our Umbraco 7.2 and it doesnt seem to redirect.
We set up an old url, for example /blog/ and set the new url to a node id in the site, for arguments sake, 1074. When we test the old url it takes us to a 404 error page. We have also tried manually entering the RedirectURL and still it takes us to the 404 page.
We have added the settings in the Webconfig as described in the Projects page.
Each url redirect entry appears in the icUrlTracker database table.
We did notice that if you delete a url rewrite it doesnt remove it from the database. One test we did it actually added the entry in again after we deleted it.
Any ideas on what we need to do - does it use a config file (apart from the webconfig)?

Thanks in advance,
Jon

Answer 1 · 2015-02-10T16:03:03.000Z

What version of the Url Tracker?
Do you have any hostnames configured in umbraco? Which?

Answer 2 · 2015-02-10T16:07:58.000Z

Hi,
It is package version 3.4.
How would you find which Hostnames you have set up in Umbraco?

Thanks
Jon

Answer 3 · 2015-02-10T16:09:07.000Z

Hi,
If you are referring to Hostnames in the Admin section then we haven't set any up,

Jon

Answer 4 · 2015-02-10T16:10:17.000Z

Yes I mean this:

Answer 5 · 2015-02-10T16:11:31.000Z

Hi,
Thanks for that - no we haven't set any up,

Jon

Answer 6 · 2015-02-11T11:57:17.000Z

Hi, any updates to your thoughts? Jon

Answer 7 · 2015-02-11T12:46:07.000Z

No not yet. Maybe you can provide some screenshots of the Url Tracker UI to see what kind or redirects you've created?

Answer 8 · 2015-02-11T16:06:55.000Z

Hi, the only one I have done is OldUrl: /blog/
New Url: /newsblog/

Answer 9 · 2015-02-13T15:17:19.000Z

I've been able to reproduce. It's a bug introduced by #40 I think.
Let me check with Sandro about this, I'll get back to you soon.

Answer 10 · 2015-02-18T11:02:55.000Z

Any news on this issue?

Answer 11 · 2015-02-18T11:09:34.000Z

No, if there was I would have said so, right?

Answer 12 · 2015-02-19T14:23:33.000Z

Using 3.3 here and I have no hostname in Umbraco set. It works just fine for me.

@jonathan, perhaps you could uninstall and go back a version for now?

Answer 13 · 2015-02-19T14:32:27.000Z

Yes I can confirm this bug was introduced in v3.4 because of #40

Answer 14 · 2015-02-19T20:28:26.000Z

I am having the same issue after upgrading my site to 7.2.1 and installing the UrlTracker version 3.4. All of my previous 301 redirects now throw a 404. Is there a way to roll back to version 3.3?

Answer 15 · 2015-02-19T20:51:36.000Z

Sure, but I'll fix it tomorrow ok?

Answer 16 · 2015-02-19T21:35:32.000Z

Sounds great. Thanks.

Answer 17 · 2015-02-20T09:53:07.000Z

This is fixed in v3.5, which I'll release in a few.

Answer 18 · 2015-02-20T14:23:57.000Z

My redirects are still not working after upgrading. Are there any additional steps besides uninstalling 3.4 and upgrading to 3.5 for UrlTracker to work?

Answer 19 · 2015-02-20T14:55:08.000Z

No that should be it. Could you post the entire SQL row of the redirect you mentioned?

Answer 20 · 2015-02-20T15:51:31.000Z

These are the contents of a row:

Id=1474965
OldUrl=recipe-category/30-minutes-or-less-recipes
OldUrlQueryString=NULL
OldRegex=NULL
RedirectRootNodeId=1055
RedirectNodeId=NULL
RedirectUrl=recipes
RedirectHttpCode=301
RedirectPassThroughQueryString=1
Notes=Fixing Legacy 404
Is404=0
Referrer=NULL
Inserted=2015-01-21 19:25:42.397
ForceRedirect=1

Also, if I click Advanced view in any redirect setup in UrlTracker, I get this error: Sys.WebForms.PageRequestManagerServerErrorException: Sys.WebForms.PageRequestManagerServerErrorException: 'ddlRootNode' has a SelectedValue which is invalid because it does not exist in the list of items. Parameter name: value

Answer 21 · 2015-02-20T15:52:03.000Z

Is there a node with id 1055?

Answer 22 · 2015-02-20T15:57:22.000Z

Yes, but it's a different page than the redirect url is supposed to go to.

Answer 23 · 2015-02-20T16:13:05.000Z

I know, but it's the redirect ROOT node id, not the redirect id.
Could you create a screenshot of the umbraco tree and highlight the redirect id node and the redirect root id node?

Answer 24 · 2015-02-20T16:20:36.000Z

justinbhayes commented 10 years ago

Answer 25 · 2015-02-23T16:06:38.000Z

Did I answer your question correctly? Redirects are still not working for me.

Answer 26 · 2015-02-24T08:29:50.000Z

Yes you did.

Answer 27 · 2015-03-02T18:49:50.000Z

I had the same issue Sorry for not reading this thread earlier I went from 3.4 to 3.5 using umbraco 7.0 and all of my redirects quit working. All I get now are 404 errors as well.

Answer 28 · 2015-03-12T22:59:30.000Z

Hi there, I had to downgrade version from 3.5 to 3.3 for manual redirects to work again. The issue on this version is that old urls with extension .html for example don't work. No error page, the page just goes blank.

Answer 29 · 2015-03-13T08:52:59.000Z

Thanks @gnokto, I hope I can look into this today.

Answer 30 · 2015-03-13T14:26:52.000Z

I am unable to reproduce this :-(
Could you tell me what the output of the logs is when you enable it and request an 'Old URL'?

Instructions to enable logging:

Add an appSetting to your web.config: <add key="urlTracker:enableLogging" value="true"/>
In 'config\log4net.config', change the root logger priority to 'Debug' instead of 'Info': <priority value="Debug"/>

The lines I'm interested in contain "InfoCaster.Umbraco.UrlTracker.Helpers.LoggingHelper".

Answer 31 · 2015-05-13T17:26:10.000Z

I'm having the same issue.

Umbraco 7.2.5
UrlTracker 3.7

Used to work great (on other sites), now its just doing nothing.

Answer 32 · 2015-05-15T07:50:10.000Z

@mschraeder Please look at the comment I left above yours. To fix this I need more information.