Why do you need to customize the way it is actually doing it for certain situations, maybe there is a better way to achieve what you want, or a package that suits your needs for doing redirects.
Looking forward to hear from you, perhaps I can help you.
Well the solution we have is pretty specific but I'll try to explain here.
We have a MainSite node (domain: www.mainsite.com) that has child nodes under it. At the same level of this MainSite node we have what we call a SubSite (domain: www.mainsite.com/subsite) node that has it's own child nodes. Now when a user enters a MainSite child node and if a user goes to SubSite node the normal Umbraco flow works perfectly.
The requirement we have however complicates because whenever you try to reach a SubSite url that only exists on the MainSite this should be working.
Example: www.mainSite.com/page1 exists under the MainSite node but not under SubSite node, still you can reach it with www.mainSite.com/subSite/page1 and see the same contents with small changes like SubSite name instead of MainSite name on the header
My problem now is when the guys on the MainSite use umbracoRedirect on www.mainSite.com/page1 to go for www.mainSite.com/page2, because that will cause www.mainSite.com/subSite/page1 to be redirected to www.mainSite.com/page2.
Attach to the umbracoRedirect
I need to get into the umbracoRedirect flow because I need to customize the way it is actually doing it for certain situations.
Is there any way of doing it?
Hi Diogo,
Why do you need to customize the way it is actually doing it for certain situations, maybe there is a better way to achieve what you want, or a package that suits your needs for doing redirects.
Looking forward to hear from you, perhaps I can help you.
/Dennis
Hi Dennis,
Well the solution we have is pretty specific but I'll try to explain here.
We have a MainSite node (domain: www.mainsite.com) that has child nodes under it. At the same level of this MainSite node we have what we call a SubSite (domain: www.mainsite.com/subsite) node that has it's own child nodes. Now when a user enters a MainSite child node and if a user goes to SubSite node the normal Umbraco flow works perfectly. The requirement we have however complicates because whenever you try to reach a SubSite url that only exists on the MainSite this should be working.
Example: www.mainSite.com/page1 exists under the MainSite node but not under SubSite node, still you can reach it with www.mainSite.com/subSite/page1 and see the same contents with small changes like SubSite name instead of MainSite name on the header
My problem now is when the guys on the MainSite use umbracoRedirect on www.mainSite.com/page1 to go for www.mainSite.com/page2, because that will cause www.mainSite.com/subSite/page1 to be redirected to www.mainSite.com/page2.
I know it's a nasty challenge..
Not sure if this blog is what you're looking for, but maybe it can give you some ideas: http://24days.in/umbraco/2014/urlprovider-and-contentfinder/
Jeroen
Thanks Jeroen that is the type of thing I was looking for! tried to give you a high five but for some reason it doesn't stick after I refresh
You need 70 karma for a high five I think, but you could mark my post as the answer.
Jeroen
is working on a reply...