Download
2011-09-28, 10:48:49
Quote:One more suggestion, it's easy to implement.
It has to do with having all pages in default language displayed without the language prefix while translated versions of those pages do get the language prefix
Quote:$deflang = return_i18n_default_language();
if ($lang != $deflang) {
$plink = str_replace('%language%', $lang, $PERMALINK_ORIG);
} else {
$plink = str_replace('%language%/', '', $PERMALINK_ORIG);
}
I had a very similar problem with dizarter.
From the SEO point of view, must agree that default language index page should look like www.domain.com not www.domain.com/en/
I was upgrading a site from static to GetSimple powered and transposing the existing multilanguage ULRs to I18N plugin.
The site allready has PR2 on mainpage domain , and redirecting the frontpage http://www.pensiuneahanna.ro/ to http://www.pensiuneahanna.ro/ro/ (romanian as default language) was risky with google SR and PR.
I think that default language index page should be treated exactly like GetSimple does, it is left with no parameter.
The "auto" language based on user preferences and session vars, is NOT Seo friendly, unfortunately.
I had to hack getFancyLanguageUrl() function to make my ulr look like old urls. (witch I am not happy with)
And Last:
It is a god practice (a must SEO practice) that on multilanguage sites, to use multilanguage slug urls.
Using slug to identify coresponding pages, makes this imposible. It would be a chalange to find a solution to this.
I know this sounds somehow "demanding" but I have noticed that you are realy preoccupied with I18N system, and the plugin is realy so perfect, that it's a pity to neglect the fancy url / slugs.
Best regards
