All Url Tracker entries with some sort of ASP.NET URL (extensionless and .aspx) in the DB are stored without the extension or trailing slash, because that's configurable and changable within umbraco.
The way it's shown in the UI is based on the configuration of umbraco, which are the following settings:

• The 'umbracoUseDirectoryUrls' appSetting in the web.config
• The 'addTrailingSlash' configuration in the config\umbracoSettings.config file

So in your case I guess 'umbracoUseDirectoryUrls' is set to true and 'addTrailingSlash' is also set to true?

If you add 'some-page.aspx' as old URL, the redirect should work for '/some-page.aspx', '/some-page/' and '/some-page'.
If it doesn't it's definitely a bug, could you check this?

Yes you are correct regarding the config settings - that makes sense and I am sure that will work, however, a friendly note regarding useability - I am porting an old style asp.net project to umbraco so my perception when I enter those URLs is to have it read exactly the same as the old website (similar to they way a php link would read). I get that it is using the umbraco settings and that would explain the "/" instead of a file extension, however to avoid user confusion, make a note about that in the tool tip, document it, or override the text field to insert a .aspx extension for the end user. Just a thought.

Thanks for getting back to me!

Jamie

Thanks for the feedback. Adding it to the tooltip is IMO not an option, because the UI will get cluttered and I'm trying to keep it as clean as possible.
I agree with you that this should be documented somewhere and I'll add this somewhere in the near future.

Ok, just put this site live now and this has revealed a bunch of bugs with this set up:

1) redirects are not working for manually entered redirects with old .aspx extension.

Created redirect for OLD URL: http://skican.com/Destinations.aspx?rid=1&did=1

Set to target and expected result: http://www.skican.com/destinations/western-canada/whistlerblackcomb/

Actual result in browser:http://skican.com/Destinations.aspx?rid=1&did=1 (note the extension .aspx which should not be there because the site is set up such that

• The 'umbracoUseDirectoryUrls' appSetting in the web.config
• The 'addTrailingSlash' configuration in the config\umbracoSettings.config file

2) Previously entered manual redirects are simply gone from the system. I manually set up 105 of them and now they are gone! 

3) Multiple host names set to one node - deleted my dev hostname and yet it still appears in the list of root node names in URL tracker

4) Search filters for Automatic mappings / custom regex etc not working at all. I am seeing "An ancestor was renamed" all over the place and this should be classified as automatic.

Please help. The site is live and all our redirects are not working!!!!!

Just published this site and am now having some serious bugs with this. I just wrote a post and it vapourized into the void so not sure if it will show up, hopefully this one will.

1) With old .aspx extensions, querystring is being ignored and browser will default to only first resolved mapping. Example:

Set up old mappings: 

Blog_Details.aspx?cid=1 ( which shows up in the interface as Blog_Details/?cid=1)  => new umbraco page

Blog_Details.aspx ?cid=4 ( which shows up in the interface as Blog_Details/?cid=4)  => some other new umbraco page.

When I go to any Url that uses this style of mapping, they ALL redirect to the first page. Try it your self here. Each page is supposed to redirect to a different blog entry...

http://www.skican.com/Blog_Details.aspx?cid=4 Should map to: http://www.skican.com/skican-blog/welcome-to-the-new-skican-blog/

http://www.skican.com/Blog_Details.aspx?cid=6 => http://www.skican.com/skican-blog/where-would-you-rather-be/

http://www.skican.com/Blog_Details.aspx?cid=7 = http://www.skican.com/skican-blog/like-a-phoenix-from-the-ashes/

Note that they ALL will redirect to: http://www.skican.com/skican-blog/welcome-to-the-new-skican-blog/ DESPITE entries being set up for each....

Please help as the site is live and it is affecting over 100 pages....

Can you please tell me how I can post to you details of the URL tracker bugs/issues when I can't post a LINK into this forum without it getting BLOCKED (insert IRONY here) ? I have spent the last hour trying to send you examples of some serious issues encountered with the above thread! Basically, query strings are not forwarding correctly to their associated mappings. My site has just gone live and there are over 100 redirects that are NOT functioning. They all have old ASPX extensions whereby one page uses a querystring to ID a given page. NONE of the redirects are working. They ALL point to only the first mapping that uses the file name. I wish I could give you more details. Please email me as I am DESPARATE to resolve this.

I've alerted an admin that your posts are blocked, but I did get the email notifications.
I'll get back to you when I hear from the admin.

Thanks - I think I have isolated the issues. It occurs when the following situations exist:

1) Old site. The script name is mypage.aspx with a querystring identifier to id a page view. On the new site, the SAME file name exists but with umbracoUseDirectoryUrls and addTrailingSlash turned on - so on the new site: /mypage/. In url tracker, each entry is set to the script name /mypage/ with a querystring determining a different mapping. In all these cases, the mapped URL in the browser will show as mypage.ASPX?id=1234 even though umbracoUseDirectoryUrls and addTrailingSlash aret turned on!

2) In a similar situation, where the script name is not the same as on the old site, all the query string mappings will only map to the first entry (id=1).

3) after removing a host name from he list of names assigned to a node, in my case the dev URL, the deleted url still shows up in the list of site names

If there is no querystring, mappings function as they should.

Thanks,

Jamie

Interesting findings, thanks!

I should also mention (because maybe it was not clear)  that in 1) above -  that the mappings are not working - it just goes to the identified script name (with an aspx extension), so mappings are not working at all with any querystring. Same for 2, no querystring mappings work as they all default to the first even querystring ID (note that this is duplicated accross browsers with clear caches so it is not a 301 browser cache issue).

Any suggestions? I have about 100 affected pages that I need to get mapped to the new nodes...

Thanks,

Jamie

Well, I can at least tell you that 1) will never work, because the UrlTracker is executed only if umbraco hasn't found a page to render.

Interesting, so if I have a page on my old site that is called /products.aspx?id=1234, on my new site I can't use /products/ ? I can see the programing logic, but seems there should be a special case there for porting old asp.net sites to Umbraco. Thanks, I will try changing the node name and see what happens. I suspect that I will run into situation 2) above next, but will keep you posted.

Thanks,

Jamie

So, I renamed the offending node and am now encountering 2) above. Every URL using the same format, will default to the first entry:

Example:

http://www.skican.com/Destinations.aspx?rid=1&did=1 Maps correctly as first entry

http://www.skican.com/Destinations.aspx?rid=1&did=2 Maps to above despite having separate mapping in URL tracker....

Any suggestions there? (Please)

Cheers,

Jamie

Hi Jamie.

How have you solved the issue please?

Thank you in advance.

Kind Regards.

Simon, the issue where the .aspx gets stripped out turned out to be umbraco behavior when you turn on directory urls. Even though the .aspx gets stripped out of the original URL field, umbraco still knows that it's there - so you don't need to worrry about it. So if you posted: http://www.mysite.com/test.aspx it is the same thing as http://www.mysite.com/test/. The trailing "/" being equal to ".aspx" What I am trying to say is that it will work. From a usability standpoint, I agree - the expected behaviour is to see the .aspx in the original URL field as indeed it is the original url.

Hope that helps,

Jamie

is working on a reply...