Re: MLP - The Multi-Lingual Publishing Pack

Hi again !…

every thing seems to work for now except some path related issue :
the site i’m working on has 2 languages : French and English.
Let’s say i’m accessing the site at a second level url (my-site.com/my-section) with non-french language set in my browser
I will see the right page (ie: english rendition) but the url is not set to my-site.com/en/my-section, it is still my-site.com/my-section.

And this error message show :Notice: Undefined index: l10n_request_uri in site_directory\textpattern\lib\txplib_misc.php(653) : eval()'d code on line 430
It’s on my development server with status set to debug.

I can understand that it may not be a problem from the plug-in point of view but how can i set a redirection with header 301 moved permanently for all previous French content to my-site.com/fr ?
Would it be possible to add an .htaccess rule for the whole site ?

Re: MLP - The Multi-Lingual Publishing Pack

planeth wrote:

Let’s say i’m accessing the site at a second level url (my-site.com/my-section) with non-french language set in my browser I will see the right page (ie: english rendition) but the url is not set to my-site.com/en/my-section, it is still my-site.com/my-section.

If you just type ‘my-site.com/my-section/’ in the URL bar, that is expected behaviour. As soon as you navigate using the MLP generated links, the language marker should appear in the URL again.

Re: MLP - The Multi-Lingual Publishing Pack

Hi Els,

If you just type ‘my-site.com/my-section/’ in the URL bar, that is expected behaviour. As soon as you navigate using the MLP generated links, the language marker should appear in the URL again.

I understand it is expected. My concern is about SEO, actually.
People (and robot) accessing this link will see different content depending of the browser default language. Which will lead to duplicate content in google “machinery”.
That’s why my question about setting a .htacces directive to redirect to the french url with a 301 header.

Re: MLP - The Multi-Lingual Publishing Pack

planeth wrote:

It’s on my development server

Are you sure the server configuration couldn’t be interpreted as a subdirectory? Have a look at this post. The only two references to this error I could find are about sites in subdirectories. MLP is known not to work in subdirectories, so if this is the cause, the only way to solve it is to change the setup. A subdomain would be fine.

That’s why my question about setting a .htacces directive to redirect to the french url with a 301 header.

I’m not so sure this is necessary, why would these URLs without language markers ever be requested? Unless they existed previously of course.

Re: MLP - The Multi-Lingual Publishing Pack

Unless they existed previously of course

Yes, in fact. I forgot i stated it in a previous post.
This is a site which has been online for a few years now and my client wants to go multi-languages.
So, yes url without language exist. And of course my client sure does not want to loose his positions in the google SERP

Are you sure the server configuration couldn’t be interpreted as a subdirectory?

Yes it could be. I’ve checked the post you linked but it does not make much sense for me.
I’m running my local server in a XAMPP stack and have set this site according to the wiki install guide, with a <VirtualHost> directive

This is the debug message when debug is set to 1 in _l10n_process_url ()

Re: MLP - The Multi-Lingual Publishing Pack

So, yes url without language exist. And of course my client sure does not want to loose his positions in the google SERP

In that case I understand :) If you don’t have too many sections you could do something like this for each section in .htaccess:

Redirect permanent /cuisine http://site.com/fr/cuisine

which will redirect not only /cuisine/ to /fr/cuisine/, but also all other pages in that section. So for instance /cuisine/article-title will go to /fr/cuisine/article-title.
I guess it’s possible to catch all URLs without language marker using regular expressions, but I’m not good at that ;) If you need help with it, you’d better start a new topic in the How do I forum (where it will attract more attention).

This is the debug message

I’m not technical enough to be able to tell you what the debug output means, but my guess is that the error will disappear once you have moved the site to its live location. If it’s working otherwise, I’d ignore it for now if I were you.

Re: MLP - The Multi-Lingual Publishing Pack

Hello (once) again,

this is a comment on what went wrong when going live with MLP.
On the production server, the setup wizard did not create tables for english – the site is french by default.
On admin side the 2 languages where updated.
I did an ugrade (shame on me, i wasn’t running Txp latest version) to no avail.

Finally, I manually edited the ‘al10n_l10n-languages’ entry in txp_prefs table, run once more cleanup/setup wizard and obtain all the right tables.
Is this a known issue of MLP setup wizard not setting the installed languages ?

Re: MLP - The Multi-Lingual Publishing Pack

Hi all,

Some years ago i made a tri-lingual site for a .nl based arts institution. As budgets are tight these days they want to skip one language. What would be the best MLP practice to do that?

Either remove all articles for that language in MLP and remove the MLP preference for that language, or only do the last. In that case all links are invisible but the articles stay in the database (maybe preserved for better times). Or do they mess up the article list when the MLP lang preference is removed?

I also have to update MLP and txp to 4.4.1. Remove lang before or after updating?