Amir Helzer

David Garcia Watkins

Pierre Sylvestre

<blockquote>
<h3>qTranslate X plugin was abandoned years ago, and we don’t actively maintain this migration plugin anymore.</h3>
</blockquote>
This plugin can either cleanup the qTranslate X meta-HTML tags from your site and leave just one ‘clean’ language, or migrate all languages to WPML’s format.
Very important: This plugin will modify the entire content of your database. You must backup your database before attempting to use it.
For complete documentation, please refer to the <a href="https://wpml.org/documentation/related-projects/qtranslate-importer/?utm_source=plugin&utm_medium=gui&utm_campaign=qtranslate" rel="nofollow ugc">qTranslate uninstall and WPML importer documentation</a>.
<h4>qTranslate X uninstall and cleanup mode</h4>
Must-read: All the issues mentioned in the reviews are solved. We are happy to announce the reintroduction of the clean-up mode with plugin version 2.0
This mode is intended if you just want to keep one language in your site and you want to clean up the language meta-tags that qTranslate added. For this mode, you don’t need WPML.
Instructions:
<ol>
<li>Save all qTranslate X settings</li>
<li>Go to the Plugins admin page and de-activate qTranslate X</li>
<li>Install & activate QT Importer</li>
<li>Go to Options -> QT Importer, select language to keep and click Start. </li>
</ol>
<h4>Migrate all languages from qTranslate X to WPML</h4>
In this mode, the QT import plugin will convert the language information from qTranslate’s language tags format to WPML’s post-per-language format. For this to work, you must have <a href="http://wpml.org" rel="nofollow ugc">WPML</a> active in the site (but not necessarily configured).
Instructions:
<ol>
<li>Save all qTranslate settings</li>
<li>Go to the Plugins admin page and de-activate qTranslate X</li>
<li>Have WPML activated, but not yet configured (just activated)</li>
<li>Install & activate QT Importer</li>
<li>Go to Options -> QT Importer and click Start</li>
<li>Add redirects from old URLs to new URLs</li>
</ol>
The import runs in small batches so it doesn’t have timeout issues with large databases. You can run it on sites of any size.
During the import process, the plugin generates a set of URL redirect rules. These rules tell visitors and search engines that the URLs in your site have changed (from qTranslate’s format to WPML’s format). When the import completes, you’ll be able to export these rules either as rewrite directives for your .htaccess file or as a PHP file to add to the theme.
You can skip the redirect rules, but then, incoming links to internal pages may lead to 404 pages.
The import tool converts posts, meta data and taxonomy. We tried to take every possible scenario in mind, but there’s no alternative to manual testing. Please consider spending time reviewing the final result and possible doing some last touch-ups before relaunching the site with WPML.

qTranslate X Cleanup and WPML Import

Migrating my QTranslate site to WPML worked flawlessly and saved me a lot of time.

A real time saver

Allows a complete uninstall and cleanup of qTranslate X meta-tags or importing translations into WPML

jmarceli

CMB2-qTranslate is WordPress plugin for CMB2 and qTranslate X integration. Adds language switch buttons above selected CMB2 fields to make content translatable. 
For updated docs please refer to the Github project page <a href="https://github.com/jmarceli/integration-cmb2-qtranslate" rel="nofollow ugc">https://github.com/jmarceli/integration-cmb2-qtranslate</a>.
Supported CMB2 field types:
<ul>
<li>input</li>
<li>textarea</li>
<li>wysiwyg</li>
<li>repeatable field groups</li>
</ul>
In order to make field translatable add <code>.cmb2-qtranslate</code> class to it. For non-WYSIWYG fields you may prefer to use <code>data-cmb2-qtranslate</code> which is also supported (since 0.0.3 version).
Usage example
WYSIWYG field:
<pre><code>> $field1 = $cmb_demo2->add_field( array(
> 'name' => __( 'SECOND Text', $this->plugin_slug ),
> 'desc' => __( 'field description (optional)', $this->plugin_slug ),
> 'id' => $prefix . $this->plugin_slug . '_second_text',
> 'class' => 'cmb2',
> 'type' => 'wysiwyg',
> 'options' => array(
> 'editor_class' => 'cmb2-qtranslate'
> )
> ) );
</code></pre>
Other fields:
<pre><code>> $field2 = $cmb_demo->add_field( array(
> 'name' => __( 'Text Small', $this->plugin_slug ),
> 'desc' => __( 'field description (optional)', $this->plugin_slug ),
> 'id' => $prefix . $this->plugin_slug . '_textsmall',
> 'class' => 'cmb2',
> 'type' => 'text',
> 'attributes' => array(
> 'class' => 'cmb2-qtranslate'
> )
> ) );

> // You may also use data-attributes instead of class to trigger qTranslate for the field
> // however it is not supported by WYSIWYG field (WordPress limitation)

> $field2 = $cmb_demo->add_field( array(
> 'name' => __( 'Text Small', $this->plugin_slug ),
> 'desc' => __( 'field description (optional)', $this->plugin_slug ),
> 'id' => $prefix . $this->plugin_slug . '_textsmall',
> 'class' => 'cmb2',
> 'type' => 'text',
> 'attributes' => array(
> 'data-cmb2-qtranslate' => true
> )
> ) );
</code></pre>
Detailed info about field creation could be found in CMB2 project documentation (https://github.com/WebDevStudios/CMB2/wiki).
Usage on custom Theme Options Page:
See https://github.com/qTranslate-Team/qtranslate-x/wiki/Custom-page-(plugin)-integration
You should define at least one form field in <code>$admin-config</code> array to trigger qTranslate LSB on your custom Theme Options Page. In other case you will end up with not working LSB. It happens because by default qTranslate is available only on specific pages: content pages, general options and maybe some others, but not your custom page (if you will create one).
Requirements/Dependencies
<ul>
<li>CMB2 (https://pl.wordpress.org/plugins/cmb2/)</li>
<li>qTranslateX (https://pl.wordpress.org/plugins/qtranslate-x/)</li>
</ul>
Links
<ul>
<li><a href="https://github.com/jmarceli/integration-cmb2-qtranslate" rel="nofollow ugc">Github project page</a></li>
</ul>

qTranslate X Cleanup and WPML Import vs Integration-CMB2-qTranslate