We have in the last year or so done a great deal of CMS migration projects. Many clients use moving to Umbraco to restructure their web presence. That includes splitting up their content to different domains (often due to i18n) or merging content from different domains. Anyway, sometimes we get a request for handling this scenario:
When both support.example.com and www.example.com is sites in the same Umbraco installation, then the customers can't understand that the above can’t be done. I know that handling this scenario in 301 Url Tracker is not trivial, as the user interface somehow needs to support adding the domain name to the mapping.
So if you ever get bored, then you have something to work on.
Just for completeness (and reference to others) we currently handle the above scenarios with a custom 404 handler.
Your requesting a feature which most of the users don't need and it even requires a UI change for something trivial as this. The problems you describe can easily be fixed with IIS UrlRewite module, UrlRewriting.NET or like you did with the 404handlers. It's just too custom.
I follow you on the second issue regarding cross site redirects. Kind of specific, yes :-)
But I could see an implementation of the first suggestion that would be relatively unobtrusive. Something along the lines of using the nodeId of the top level node as part of the unique identifier of a mapping.
But of course, I understand and respect that you don't believe that such a functionality it is inside the scope of the package.
It sounds useful to have these redirections. When do we have to expect the updated version? I see that you're not going to implement the second Emil's option but I admit is a very common scenario for new sites built in umbraco.
Well, the news is that I'm planning on rewriting the 301 URL Tracker based on umbraco v6. This will break backward-compatibility, which means this feature won't make it into the current 301 URL Tracker for V4.
More multi-site support - duplicate oldUrls on different sites & cross site redirects
We use your package a lot, and on some of our larger installations we experience some limitations when we have multiple sites and languages.
1) Duplicate old urls on different sites
One example is when we have multiple sites for a multilingual support. At the moment we can't create the following using 301 Url Tracker:
www.example.dk/support.htm -> www.example.dk/support
www.example.se/support.htm -> www.example.dk/support
2) Cross site redirects
We have in the last year or so done a great deal of CMS migration projects. Many clients use moving to Umbraco to restructure their web presence. That includes splitting up their content to different domains (often due to i18n) or merging content from different domains. Anyway, sometimes we get a request for handling this scenario:
support.example.com/contact -> www.example.com/contact-support
When both support.example.com and www.example.com is sites in the same Umbraco installation, then the customers can't understand that the above can’t be done. I know that handling this scenario in 301 Url Tracker is not trivial, as the user interface somehow needs to support adding the domain name to the mapping.
So if you ever get bored, then you have something to work on.
Just for completeness (and reference to others) we currently handle the above scenarios with a custom 404 handler.
I'm sorry, but I will not implement this.
Your requesting a feature which most of the users don't need and it even requires a UI change for something trivial as this. The problems you describe can easily be fixed with IIS UrlRewite module, UrlRewriting.NET or like you did with the 404handlers. It's just too custom.
I hope you understand.
Hi
Thanks for you quick response!
I follow you on the second issue regarding cross site redirects. Kind of specific, yes :-)
But I could see an implementation of the first suggestion that would be relatively unobtrusive. Something along the lines of using the nodeId of the top level node as part of the unique identifier of a mapping.
But of course, I understand and respect that you don't believe that such a functionality it is inside the scope of the package.
Best regards
Emil
Hi Emil,
I have to alter my opinion about your first remark; I've ran into the same problem :P
I'm going to work on the 301 URL Tracker soon and I'll include your first request.
Greets.
Hi Stefan
That sounds great. Respect for admitting your "mistakes" ;-)
I look forward to further developments of the 301 URL Tracker. Thanks!
Best regards
Emil
Any news on that Stefan?
It sounds useful to have these redirections. When do we have to expect the updated version?
I see that you're not going to implement the second Emil's option but I admit is a very common scenario for new sites built in umbraco.
Cheers, Giorgos
The first feature is something we can really use at the moment and probably in the future. Any indication when this will be implemented?
Best regards,
Harm-Jan
Hey,
Any news about this feature ?
+1 For Me
Thanks.
Well, the news is that I'm planning on rewriting the 301 URL Tracker based on umbraco v6.
This will break backward-compatibility, which means this feature won't make it into the current 301 URL Tracker for V4.
I'm working on a new version which supports v4 & v6 and it supports domains really well :-) So stay tuned!
What is the status of this update?
If it was finished you'd have known...
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.