ricomtl

nope – I just uninstalled the plugin

Ok, it does work if I enable “Hide URL language information for default language”. My url can be accessed either with the /fr or without and existing links in Google are still working, and so is my custom login page with iTheme Security.

Thanks ??

@gunu

Does this mean that all my existing articles and site content under /fr indexed in Google will no longer be accessible and will have to be re-indexed?

Thks – I read the article and I am somewhat confused! ??

My default language is FR, and I always had the option set to redirect the user to either /fr or/en based on their browser language. That is the setting I had with qTranslate & mqTranslate for the past couple of years. I’ve always been able to use it along iTheme Security’s Hide Login page feature.

As soon as I re-activate mqTranslate, I can regain access to my login screen and I see the plugin doesn’t force a language.

I’ll continue using mqTranslate for now unless you know if there’s a feature I must enable/disable within qTranslate-X.

Thanks!

You are right, I should have a copy/test site to play around with. I was testing this on my live site behind a “Maintenance/Under construction” splash page. I have no problem testing – I always like being part of the early adopters!

I checked my Apache error log and there is nothing in reference to this…

I’ll keep an eye on new versions! ?? Cheers and thanks for the support!

@john Clause

Thanks for this new version. I backed up my site (thanks God!) and installed 3.2. At least, this time I got past the installation. I did not get the previous error msg: Failed to load resource: the server responded with a status of 500 (Internal Server Error). That’s the good news!

I noticed that my page editor had grouped both FR/EN content in the same window with the usual tags [:fr] content [:en] content. I did not have the option to toggle between each language as per your schreenshots.

However, as soon as qTranslate-X was activated, I got this message:

Qtranslate Slug:

This plugin requires at least WordPress 3.3 and either qTranslate-X (2.9 or newer), or mqTranslate (2.6.2.4 or newer), or qTranslate (2.5.8 or newer).

I am running qTranslate Slug (latest 1.1.13) which claims to be compatible with qTranslate-X.

Now the bad news is that – all previous slugs for all my pages got deleted and were swapped out with generic slugs, making all my indexed pages lead to 404.

I restored my entire site and now everything is back as it was…!

I agree with tfagen – qTranslateX fails as soon as I load and my site no longer works (I also have Visual Composer). I’d be ready to support mqTranslate financially as I know it’s stable and solid. ??

@john Clause thanks. Do you mean the error log part of the plugin or Firebug?

Updated to latest 3.1 version, followed the tutorial to migrate from mqTranslate and same behavior as with previous version.

When I have have the compatibility box checked off – my site does not even load in any language. Firebug error console shows: Failed to load resource: the server responded with a status of 500 (Internal Server Error).

If I disable Compatibility box, only my nav bar loads, but cannot click on any link. Console still shows: Failed to load resource: the server responded with a status of 500 (Internal Server Error).

Thank you for the tremendous undertaking… mqTranslate was perfect, and the transition from qTranslate to mqTranslate was flawless in my case. It just worked out of the box!

I tried qTranslate-X yesterday following the tutotorial and my entire size became unresponsive, no page loading, etc. Bummer. I like being part of the early adopters but I guess I’ll continue to monitor the support forums and see how it evolves.

Great job and thanks again!

Will do… the error console is blank, it’s strange. Perhaps it’s a plugin conflict, but I have over 51 plugins active! ??

Thks.

Followed all steps – imported mqtranslate settings, checked off “Advanced settings” – “Compatibility Functions”.

I clear the site’s cache and then, my site won’t load. Completely blank…

Quite odd. I moved from qTranslate to mQtranslate without any issue last year.

This has been reported several times and although I have provided author with screenshots + steps to reproduce, no solution or workaround have been provided.

Yup – that is my site! I use qTranslate slug so that I can use different slugs for each language for each post, page, tag, category.

I will continue using the manual https://www.xml-sitemaps.com/ and submit via Google Webmaster. So far, that’s the only method I found that captures everything correctly without duplicate or odd entries.

I will still use WordPress SEO and disable sitemap.

Thanks for all your precious help!

// edit – I figured out what you meant. ?? I modified the code in class-sitemap.xml according to the language of my site. Now my question is – is it normal that all permalinks (page/post/tag) appears 10 times each in the sitemap?
————————-
Thanks again leslierad – I just got some time to tackle this and I uploaded the revised plugin as per your download link and modified my functions.php. All works on that end. Thank you.

I’m not as a clear on the last post you wrote re: sitemap.xml (although I have a current workaround to submit my sitemap manually) I could be interested in getting it to work out of the box with WordPress SEO.

What exactly do I need to update in the class-sitemaps.xml … I keep re-reading your post and I just don’t get it! ??

Thanks a bunch again.