Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
Can someone explain to me in simple terms how the 301 Moved permanently handler is supposed to work?
I have read through the documentation her: http://ucomponents.codeplex.com/wikipage?title=SearchFor301MovedPermanently&referringTitle=Documentation but I must admit that I still don't get it.
I'm guessing, but if I read it correctly, then the page you want to redirect TO should have that property, and the value should be a string containging the old url that you want to redirect FROM. ?
Morten is right - the property should be a textstring wherein you put the URL (e.g.: /tutorials/muenchian) of a page that you're about to trash (or as it were on the previous version of the site, usually) - so that future requests for that URL gets a 301 Redirect with the location of the node containing the property...
Hi Morten and Chriztian
Ah yes, of course that makes perfect sense. However when I tried doing as described above yesterday I had no luck. But I'm about to give it a spin on a fresh demo-install once again to see if I can make it work.
I'll get back to you guys later.
As a follow up in Jans question, do the uComponents 301 permanently moved handler support other extensions than ".aspx" ? Such as ".html" and/or ".php" ? Asking because the all famous 301 URL Tracker package doesn't support it :-)
Thanks in advance.
@Chriztian and Morten - you guys were totally right :)
It also makes perfect sense that it is working this way. This handler is just ace!
However I think it should be explicitly stated that the datatype should be a "textstring" - must admit I missed the explanation about this working in the same way as the umbracoUrlAlias when I first came across the documentation and in a comment I saw a guy who had been using a content picker, which really does'nt make sense but created a bit confusion in my mind.
@Bo, support for other file extensions depends on your IIS set-up. Meaning that if those extensions are passed through to the ASP.NET pipeline; then Umbraco would pick them up and try to handle them.
Thanks to Morten & Chriztian for answering the original question #h5yr!
I can see this is and old topic, but I'm trying to do exactly this in Umbraco 6.1.6 and nothing happens.
As a test I have a page with url /products, I entered prdcts to the umbraco301MovedPermanently field of this page, but when I browse /prdcts I get my usual 404 page.
Just to be sure: You have uComponents installed in that site, right? (It's not totally obvious if you've searched for this functionality, especially because they've used the umbraco prefix for a custom property).
If you have indeed installed uComponents, I guess you should look into the order of the NotFound handlers in the web.config (I guess?).
uComponents is included in core in 6.1.6, I didn't install it specifically, but I do use other uComponents methods and they work. The property alias is "umbraco301MovedPermanently" and I added <notFound assembly="uComponents.Core" type="NotFoundHandlers.SearchFor301MovedPermanently" /> to 404handlers.config (first position).
<notFound assembly="uComponents.Core" type="NotFoundHandlers.SearchFor301MovedPermanently" />
Do I have to update web.config too?
Just want to add that I also have "umbracoUrlAlias" property and it works fine.
Of course this is included - my bad :-(
No need to tinker with the web.config I think, but then I don't really have any other ideas as to where it's going wrong...
Which version of IIS are you using? I know these 404-handler-thingy-majiggy things need IIS to be in "Integrated Mode" (whatever that is :-).
I'm using IIS 8.5 and the app pool is running in integrated mode.
Do you have any other 3rd party stuff installed like the SEO package from Richard Soteman or the Url tracker for instance? These might interfere with the handler perhaps.
Write your reply to:
Image will be uploaded when post is submitted