chsxf

We have resolved this issue and a fix will be available in the next plugin update.

In fact, I was wrong. We use some themes with front-page.php in them and we do not experience any specific problem.

However, we will release an update to the plugin resolving some URL and request related issues. It may correct your problem.

I’m surprised it was working with qTranslate as we did not find anything relevant with quicktags for this function.

However, we implemented the feature and it will be available in the next update of the plugin.

Hi,

I have to admit we never tried the plugin with front-page.php. We will investigate this and come back to you as soon as possible.

Regards

Hi leslierad,

We will investigate this issue as soon as possible.

You can switch back and forth at any time between the two of them. However, you need to ask mqTranslate to migrate your options from or to qTranslate in order to keep your original settings.

Hi, the QT_SUPPORTED_WP_VERSION is a legacy feature from qTranslate.
We tried to simplify this by using MIN and MAX defines in order to bring fixes and updates to several WordPress versions at the same time (and not only the currently supported version).

However, as qTranslate (and mqTranslate) does heavy transformations in the post editor, we cannot remove this efficiently. For an example, at this time, the plugin breaks the post editor completely for WordPress 3.9. We are working on an update for this, but it is better from our point of view to disable the plugin if the WordPress version is not supported.

We do not know how long this will be sustainable for us, but we try our best.

An update is now available.

I have to admit we have not tested mqTranslate against Qtranslate Slug. Are the plugin not compatible with each other?

As seen by email with the topic author, it seems we have a bug with the way we handle bloginfo('url'); result.
Try using esc_url( home_url( '/' ) ); instead.

A future will fix this issue.

Just call qtrans_generateLanguageSelectCode() in your template PHP file.

Take note than in Query mode, the right syntax is ?lang=es and NOT lang=?es

That’s what I explained in the first place in my previous post.
The URL must contain language information if you do intend to see your website in another language than the default one. Without language information, the default language is used.

If mqTranslate is configured in Pre-Path mode, you should use for example:
https://www.example.com/fr/

Or in Query mode:
https://www.example.com/?lang=fr

Hi,

The correct URL structure depends on mqTranslate settings (Pre-path or Query string mode).

However, you can use the mqTranslator widget to automatically build these links for you.
Or, if you do not use widgets, you can use the qtrans_generateLanguageSelectCode() function in your template.

We you select a specific language, its information is added to the URL. If you go to another URL which lacks this language information, the default language is used instead.

What you describe seems to be the correct behavior of the plugin.
If you go to your home page through a link in your template, maybe this link is not correctly generated.

We just published version 2.5.43 that should fix issues with Pre-Path mode.