funkjedi

<p>This plugin provides qTranslate-X compatible ACF4 and ACF5PRO field types for Text, Text Area, WYSIWYG, Image and File. When adding a field to a field group these new field types will be listed under the qTranslate category in the Field Type dropdown.</p>
<h4>Field Types</h4>
<ul>
<li>qTranslate Text (type text, api returns text)</li>
<li>qTranslate Text Area (type text, api returns text)</li>
<li>qTranslate WYSIWYG (a wordpress wysiwyg editor, api returns html)</li>
<li>qTranslate Image (upload an image, api returns the url)</li>
<li>qTranslate File (upload a file, api returns the url)</li>
<li>qTranslate URL (type text, api returns text)</li>
</ul>
<p>The standard Text, Text Area and WYSIWYG field types can also be enabled for translation.</p>
<h4>Bug Submission</h4>
<p>https://github.com/funkjedi/acf-qtranslate/issues/</p>


ACF qTranslate

Provides qTranslate compatible ACF field types for Text, Text Area, WYSIWYG, Image and File.

Luka Petrovic

<p>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.</p>


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.

ACF qTranslate vs Fix for Yoast SEO and qTranslate/qTranslateX