Forums / Setup & design / Url alias as permanent redirect, is there a setting ?

Url alias as permanent redirect, is there a setting ?

Author Message

Xavier Dutoit

Wednesday 14 November 2007 11:52:53 pm

Hello,

While updating a site to 3.10, I updated the url to the new pattern (Uppercase-and-dash), so it created an alias for the old one (uppercase_and_dash).

When I access the old url, I see the content, as before and I can also access it from the new url.

However, they are seen by the search engines and visitors as two different pages. No good.

Is there a way to have the alias behaving like an alias, and do a 301 permanent redirect to the new "official" url instead of displaying the content ?

Same question about /content/view/full/<nodeid>

X+

http://www.sydesy.com

Heath

Thursday 15 November 2007 1:01:04 am

This is an excellent point. As much as we all love the latest stable release 3.10.0 ...

It seems clear that the url translation systems were clearly affected/damaged/disabled with the multi-lingual url api changes introduced in kernel classes of the 3.10.0 release.

This is at least the second negative feature I've heard reported as a direct result.

Cheers,
Heath

Brookins Consulting | http://brookinsconsulting.com/
Certified | http://auth.ez.no/certification/verify/380350
Solutions | http://projects.ez.no/users/community/brookins_consulting
eZpedia community documentation project | http://ezpedia.org

Xavier Dutoit

Thursday 15 November 2007 3:48:18 am

Let me throw a new one:

How do you now do the link between one linguistic version and the other ?

It was already ugly/patchy before, now, I haven't heard it possible anymore

Ok, I'm going to update K redirect module, so at least I can do /redirect/full/<nodeid> that will do a proper 301, instead of the behaviour of content/view/full

;(

X+

http://www.sydesy.com

Matthew Carroll

Thursday 15 November 2007 4:07:21 pm

> How do you now do the link between one linguistic version and the other ?

I hit this issue after upgrading a few multilingual sites to 3.10. It looks like it will affect the ezwebin templates as well. Bug report:

http://issues.ez.no/11791

I worked around this by using $uri_string instead of $DesignKeys:used.url_alias for the language switcher. This is ugly, as it points to the system url on the other language siteaccess, rather than the translated url alias, but at least it works and goes to the correct page.

http://ez.no/developer/forum/setup_design/language_switcher_in_3_10

Matthew

http://carroll.org.uk