Developed by: new qTranslate community, from qTranslate-X by John Clause and qTranslate by Qian Qin
Contributors: herrvigg, johnclause, chineseleper, Vavooon, grafcom
Tags: multilingual, language, admin, tinymce, bilingual, widget, switcher, i18n, l10n, multilanguage, translation
Requires at least: 5.0
Tested up to: 6.2.2
Requires PHP: 7.1
Stable tag: N/A
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html
Adds user-friendly multilingual content support, stored in single post.
The qTranslate-XT plugin is an eXTended version of qTranslate-X that we are reviving with a new community, since the original plugin is abandoned by its author. Our first goal is to maintain the essential features of this plugin with the last Wordpress and PHP updates. The migration to Gutenberg will be a critical milestone for the survival of this plugin. We are currently building a new organization to give qTranslate a new life. Let's try together, anyone is welcome to participate!
GitHub repository of the new repo: https://github.com/qtranslate/qtranslate-xt.git.
Since the -XT version is not officially available at Wordpress.org the initial installation must be done manually. You require the permissions to access the plugins
folder of your Wordpress installation. Contact your system administrator if needed.
git clone
the repo.plugins
folder and rename it to qtranslate-xt
./wp-admin/plugins.php
).If you didn't already have qTranslate-X, proceed with the initial setup of qTranslate-XT:
Check the FAQ for further instructions.
The previous qTranslate-Team was only one person. We tried to contact the author many times but we got no answer since 2016. Our goal is to build up a real team and make this plugin available again for the whole community. We can't update the official plugin yet. It is still not clear either if we should go on with the qTranslate name, but for now we should focus on new releases. The -XT version can be seen for the least as a "bridge" project.
Yes and it's very easy! Currently you can have both qTranslate-X and qTranslate-XT installed in the plugins folder for experimentations, but you should have at most one active at any time: BOTH -X AND -XT SHARE THE SAME OPTIONS! So if you change some options and switch between the plugins, the last changes will remain for the other. The plugin can actually re-adapt its configuration after a switch, in the general case you have nothing to do. If you have some incompatible options you should see some warnings. Note that even if you uninstall either -X or -XT, the options are not erased!
Disclaimer: be sure to backup your database regularly.
It is partially supported, with some limitations. Read carefully our Gutenberg FAQ before use.
WooCommerce, ACF, Slugs and other plugins are now supported as built-in modules. Developers able to test properly are much welcome! Please send PR for bug fixes. See the complete list of available modules in our repo.
Some major plugins are now supported with the built-in modules. Some plugins are also supported with built-in i18n configurations. For other plugins you need to provide custom integration through i18n configuration (json) and/or code (PHP/JS). A major refactoring is needed to make this easier.
Check our Wiki pages:
Since the -XT version is not available at wordpress.org, we recommend you to install GitHub Updater. This is is an awesome tool to update plugins from a git repo (with many other features). It checks regularly the last release available in github (from the git tags
) and compares it to your current version (defined in the header of qtranslate.php
). If a new release is available an update link will appear as for a regular plugin from Wordpress. The check is performed even if the plugin is deactivated.
Alternatively you can delete the current folder and repeat the installation from the last archive. Make sure to deactivate the previous version and then activate the new one, otherwise you will miss the execution of activation hooks and some options may become misconfigured.
Note for developers:
git clone
. If you want to use a cloned version in production you should not update through GHU, use git pull
instead.See Github releases.
See original plugin.
See CHANGELOG.md for the full history.
The previous issues have been duplicated to our new git repository. Please check the git issues before creating new ones.
The legacy issues should also be reviewed before starting using the plugin.