Search In
Learn from 350 other Umbracians at the annual Umbraco Conference - CodeGarden '13. More than twenty high quality sessions, open spaces, hackathons and social events you'll remember. Not to be missed! Less than 25 tickets left - get yours now!
umbraco 4.0.2.1
I am trying to use umbracoUrlAlias to support old urls. I added umbracoUrlAlias to my document type. Then, I added the old url (no leading slash or trailing .aspx) to the content. The path in the umbracoUrlAlias returns a 404.
I have already verified that this exists int he 404.config- <add key="umbracoUseDirectoryUrls" value="true" />
What else am I missing?
It may be a dumb question, but do the standard URL's still work with the page? Do they work extension-less?
Tommy,
I have a simple user control that redirects a set of URLs to new paths that works with 404 pages.
Email me at casey at best case tech dot com, and I will share the package with you.
The standard URLs do work. It appears that the "magic" umbraco UmbracoUrlAlias property is not catching. I have an HttpModule that we built that will handle a large number of redirects and uses a central data source to do so. I was hoping to use the umbraco built in support though.
Casey - I'll email you if we need to go that route.
i am refering to www.mayflymedia.co.uk/.../alternate-page-name-in-umbraco-using-umbracourlalias
But umbracourlalias is not working . Please advice how can i remove "aspx" from url to make it user friendly ?
Thanks,
Shruti
Im having the same problem in Umbraco v 4.7.2 (Assembly version: 1.0.4500.21031).All the other default/hidden/internal properties work.
My implementation has worked before on other versions, following Warrens how-to @ our.umbraco.org/.../umbracourlalias
Is it a bug in the later versions?Any takers?
Turns out that there is more of a unexpected behaviour.
If i use the property in a subpage to a root-node (as in handeled by host name) it does work.But not if it is used on the root.
Example:
http://umbraco.codeplex.com/workitem/30851
Umbraco uses the UrlRewriting.net library and you can add your own rules to the UrlRewriting.config. I had the same issue and that's what I did to solve it for the time being.