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.
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
> 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.