Plugin Author
chsxf
(@chsxf)
The plugin disables itself to avoid breaking the post and page editor but the localization features are still functional.
The QT_*_SUPPORTED_WP_VERSION constants are a feature of the original qTranslate and we do not have any plan to remove it.
It’s a bad feature. Editing a page or post after the plugin has disabled itself can lead to a single post housing all of the content for whatever languages you previously had separated. Thanks though I’ll just keep editing the plugin file to change max supported version.
@jondewitt
If you are worried about WP auto updates you could always change
/wp-content/plugins/mqtranslate/mqtranslate.php
From:
— define(‘QT_MAX_SUPPORTED_WP_VERSION’, ‘3.9’);
To:
+++ define(‘QT_MAX_SUPPORTED_WP_VERSION’, get_bloginfo(‘version’));
Plugin Author
chsxf
(@chsxf)
We are looking to change our WordPress versions support.
In a future update, we will change QT_MIN|MAX_SUPPORT_WP_VERSION to QT_MIN|MAX_SUPPORT_WP_MAJOR_RELEASE
By supporting major releases, we will improve support between security patch releases of WordPress, which generally do not break the plugin.
Plugin Author
chsxf
(@chsxf)
The next release will introduce the feature I told about in my previous post.
Hi. I just updated to wp 3.9 and the plugin to its current latest version. It deactivated itself, giving me the “The mqTranslate Editor has disabled itself because it hasn’t been tested with your WordPress version yet.” message, event though both the wp and plugin versions are the latest. I tried by changing the QT_MAX_SUPPORTED_WP_VERSION parameter as explained above, but it is not working. Please, help.
Plugin Author
chsxf
(@chsxf)
New version 2.6.2.1 fixes the blocking bug introduced in 2.6.2. Very sorry for the inconvenience.
