Luka Petrovic

When using qTranslete or qTranslateX with Yoast SEO plugim it outputs all languanges in title. This plugin fix this. Only current languange will be outputed. It runs filter that wraps $title into __() and fixes Yoast SEO plugin that outputs all languanges at once in Title. I acctualy sugested to Joost to do this in his plugin (adding only 4 chars to file “class-frontend.php” at specific line), but he replied: “I won?t support qTranslate, sorry. It abuses the translation API in ways that breaks other stuff.” Since it does not break stuff i made this extreemly simple plugin.

Fix for Yoast SEO and qTranslate/qTranslateX

When using qTranslete with Yoast SEO plugin it outputs all languanges in title and meta description. This plugin fix this.

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>

Fix for Yoast SEO and qTranslate/qTranslateX vs Integration-CMB2-qTranslate