We have an old solution located at language area ID 1. This area ID cannot be deactivated, so we have to figure out something else.
The best solution would be to give the user a true HTTP Status code 301 and redirect them to the new design/language area but is that even possible?
Is there a "custom ASP" area in DynamicWeb where I could lay an old fashion asp script and by ID redirect pages? If so, this could be a solution.
Any other solution ideas are very welcome!
Developer forum
E-mail notifications
True HTTP Status 301 at AreaId 1
Posted on 21/10/2009 12:31:17
Replies
Nicolai Høeg Pedersen
Posted on 21/10/2009 12:42:24
Just add the domains to the domain list of the new area. Then Dynamicweb will load that area instead of the old.
Another solution is to create one page on AreaID=1 and create a shortcut to the first page of the new area. This will result in a 302.
In Dynamicweb 7, we changed all shortcut links on pages from 302 to 301. So if the solution has this update, it will receive a 301.
//NP
Another solution is to create one page on AreaID=1 and create a shortcut to the first page of the new area. This will result in a 302.
In Dynamicweb 7, we changed all shortcut links on pages from 302 to 301. So if the solution has this update, it will receive a 301.
//NP
Posted on 21/10/2009 12:53:05
>>Just add the domains to the domain list of the new area. Then Dynamicweb will load that area instead of the old.
The domains are only on the new language area, the old (area is 1) has no domain names on it.
>>Another solution is to create one page on AreaID=1 and create a shortcut to the first page of the new area. This will result in a 302.
Won't this simply result in a 404 (when the page cannot be found) instead of a 301?
>>In Dynamicweb 7, we changed all shortcut links on pages from 302 to 301. So if the solution has this update, it will receive a 301.
No such luck and a big job as I will have to map every single page.
//NP
The domains are only on the new language area, the old (area is 1) has no domain names on it.
>>Another solution is to create one page on AreaID=1 and create a shortcut to the first page of the new area. This will result in a 302.
Won't this simply result in a 404 (when the page cannot be found) instead of a 301?
>>In Dynamicweb 7, we changed all shortcut links on pages from 302 to 301. So if the solution has this update, it will receive a 301.
No such luck and a big job as I will have to map every single page.
//NP
Nicolai Høeg Pedersen
Posted on 21/10/2009 13:06:57
Now I'm a little confused...
Could you please e-mail me a link and maybe your number. Then I'll take a look and give you a call.
Could you please e-mail me a link and maybe your number. Then I'll take a look and give you a call.
Posted on 21/10/2009 13:43:13
Ok, this problem solved itself as our solution has been upgraded since I checked it last. So I'll forward the pages and keep the language layer active for now.
You must be logged in to post in the forum