Is it possible to use the Url Tracker in a multilingual setup where each language is placed in a subdirectory, so not in separate (sub)domains? I regularly use the following setup:
--- Root (no hostname, culture Inherit) --- NL (no hostname, culture nl-NL) --- EN (no hostname, culture en-US)
Url Tracker doesn't support this setup, because I have to configure hostnames for the NL and EN nodes, e.g.:
NL: example.com/nl EN: example.com/en
But when I do this Url Tracker starts prepending language subdirectories to the Old URL property, .e.g when I create the following redirect:
LanguageRedirect (Doctype: LanguageRedirect): Culture Language: Inherit, no domain settings, redirects to /nl or /en based on cookie NL (Doctype: HomePage): Culture Language: nl-NL, no domain settings EN (Doctype: HomePage): Culture Language: en-US, no domain settings
Of course URL Tracker forces me to configure domain settings, so:
NL: example.com/nl EN: example.com/en
URL Tracker still saves Old URL as "nl/nl/url_to_redirect" instead of "nl/url_to_redirect" as described in my initial post.
According to @kipusoep 301 URL Tracker has not been tested (and most likely will not work) on a multilingual setup based on subdirectories instead of subdomains. He does plan to add support for this type of multilingual setup in the future.
Url Tracker in multilingual setup
Is it possible to use the Url Tracker in a multilingual setup where each language is placed in a subdirectory, so not in separate (sub)domains? I regularly use the following setup:
--- Root (no hostname, culture Inherit)
--- NL (no hostname, culture nl-NL)
--- EN (no hostname, culture en-US)
Url Tracker doesn't support this setup, because I have to configure hostnames for the NL and EN nodes, e.g.:
NL: example.com/nl
EN: example.com/en
But when I do this Url Tracker starts prepending language subdirectories to the Old URL property, .e.g when I create the following redirect:
Root node: NL (example.com/nl)
Old URL: url_to_redirect
Redirect node: <selected node to redirect to>
Redirect type: Permanent (301)
Forward querystring: Yes
Url Tracker saves this as:
Old URL: nl/nl/url_to_redirect
Any suggestions?
I've made some changes to our default multilingual setup, but unfortunately we're still having issues with 301 URL Tracker.
Web.config: umbracoHideTopLevelNodeFromPath="false"
LanguageRedirect (Doctype: LanguageRedirect): Culture Language: Inherit, no domain settings, redirects to /nl or /en based on cookie
NL (Doctype: HomePage): Culture Language: nl-NL, no domain settings
EN (Doctype: HomePage): Culture Language: en-US, no domain settings
Of course URL Tracker forces me to configure domain settings, so:
NL: example.com/nl
EN: example.com/en
URL Tracker still saves Old URL as "nl/nl/url_to_redirect" instead of "nl/url_to_redirect" as described in my initial post.
Any help would be appreciated.
Hello,
I've got exactly the same problem.
http://screencast.com/t/7PnRaOPhHk0Q
When renaming a page, the languages node gets added twice.
E.g.
en/my-page => rename to => en/my-great-page
Redirect = en/en/my-page => en/my-great-page
Lau
According to @kipusoep 301 URL Tracker has not been tested (and most likely will not work) on a multilingual setup based on subdirectories instead of subdomains. He does plan to add support for this type of multilingual setup in the future.
Wondering if this was fixed in later version of URL Tracker. I have a multi-region, multi language site with similar setup with URL Tracker 3.0.
Yes, AFAIK this issue has been fixed in later versions.
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.