chsxf

I’ve replied directly to your email.

Thank you for your report.
New version 0.5.2 fixes this issue.

I just pushed a new version (2.10.1) which allows to dismiss the message. This is cookie-based, so you will have to do it on every browser you use, but you can get rid of the message anyway.

I’ve replied to you here:
https://www.ads-software.com/support/topic/deprecation-of-mqtranslate?replies=13#post-6615785

First of all, thank you everybody for those very kind words. It’s important for me to know all of this was not for nothing.

I want to clarify something which seems to be very unclear. mqTranslate is now deprecated. It does not mean it won’t work anymore on your websites. It would have been marked obsolete in that case. mqTranslate will continue to work with WP 4.2 (so at least until the release of WP 4.3 planned in August and maybe even after that if the update needed to maintain it is not too heavy).

Unfortunately, maintaining the plugin and providing support is not possible for me anymore. And, sooner or later, mqTranslate will die.

Long story short. Two and a half years ago, I ran into the same problem as you with the original qTranslate: long delays between updates, inconsistencies with WordPress, etc. So, I decided to modify the plugin we used internally in my company and it finally became mqTranslate.

However, releasing mqTranslate on the plugin repository was maybe not my best shot ever. Despite my strong will to do it properly, I never managed to free enough spare time to handle all the support requests. From my perspective, mqTranslate would require at least a half-time developer to be correctly maintained and users to get the support they deserve. But as everyone else, I have to generate income to pay the bills, and working half-time on a non-profit open source plugin is not a good way to generate that amount of income. Donations are not sufficient as it would require gathering at least US$1500.00 per month (I live in France). I could have proposed paid customer support but it leverages many more problems I do not want to take care of (such as contractual, legal, etc.).

So, when John came and proposed his new fork, qTranslate X, based itself on zTranslate, we enter in a discussion on how we could work together. Unfortunately, I discovered a very different approach in how to complete a potential merge. And, in great part by my fault, we did not success to agree on a common way to do it. I decided on my own to deprecate the plugin to inform users of the existence of a much brighter future for them in the hands of John, who can devote much more time than I will ever be able and provides a very good support.

Concerning Visual Composer, I’m pretty sure to have read in an email that John is looking for a complete support of this plugin by qTranslate X. Give him the time to implement it (as well as for other plugins). I am very confident qTranslate X will be a great place to be for qTranslate users. In the meantime, you can stick with mqTranslate.

@tfagen and @ricomtl: Please do not take offense for what I will say, because there isn’t any in the following. A donation link has been available for the past year on the www.ads-software.com plugin repository’s page. A very few users have used it (and I thank them very much for that once again). It is interesting to note that now the deprecation of the plugin is threatening your businesses, you may consider paying to maintain it. The even interesting aspect of it is that if the plugin hadn’t been free in the beginning no one would have use it. When I deprecated the plugin, I removed the donation link as it was disrespectul to continue to accept donations for a dead plugin.

It seems that if you disable “Hide URL language information for default language.” in Settings > Languages > Advanced Settings, things are greatly improved.

At this time, the import settings function is not working. A fix has been submitted to John but it is not yet in the current released version of the plugin.

@justina.hudenko: I think your problem is related to the fact that the current version does not import correctly the setting from mqTranslate.

You have two options:

1. Revert back to mqTranslate until a fixed version of qTranslate-X is released
2. Copy all your settings from mqTranslate to qTranslate-X by hand and try. If it does not work yet, fallback to the first solution.

To anyone encountering problems with qTranslate-X, I suggest you send your support requests to the qTranslate-X team and, until a proper fix is released, revert back to mqTranslate.

As I said earlier, the plugin won’t be developed anymore (understand by that no bugfix or new feature will be added). But the plugin is still running if everything is ok for you. It should be ok until the release of WP 4.3 (planned in August 2015).

Two options:
– Switch and try with another qTranslate compatible plugin such as qTranslate-X
– Contact your hosting provider and explain the issue, eventually linking to this topic

@extremecarver: There is no “membership” feature in mqTranslate. In fact, what John is talking about is an admin panel feature that allows admins to set only a specific subset of languages available to some editors or contributors. It prevents some users to modify parts of the text in languages they do not master.

Yes, it is working with mqTranslate.

Potentially more information here. As stated, the bug is on the web server and not directly on PHP or WordPress or mqTranslate.

https://www.ads-software.com/support/topic/404-error-when-posting-adding-pages-with-mqtranslate-activated?replies=28

Try disabling Black Studio TinyMCE Widget. I suppose the problem comes from here.
You can also try qTranslate-X, which is another fork of qTranslate less prone to TinyMCE conflicts.

As I stated previously (and this confirms that), the error is thrown at a server level, not at WordPress code level. I’m not an Apache expert but I am pretty sure this must be fixed in the server configuration directly.