sbouey

<p>The Falang for WPBakery plugin makes your WPBakery page translation simpler. You need to have your site working with the Falang system for translation.</p>
<p>You don’t have to duplicate the page anymore to translate it, just translate only what is necessary. It’s easier to maintain and all parameters are the same for all languages.</p>
<h4>Free vs Pro</h4>
<p>Free verion support vc_btn,vc_column,vc_message,vc_section,vc_tta_section</p>
<p>Pro version support</p>
<ul>
<li>
<p>WPBakery :<br />
vc_cta,vc_custom_heading, vc_hoverbox, vc_line_chart, vc_pie,vc_progress_bar, vc_raw_html, vc_round_chart, vc_single_image, vc_text_separator</p>
</li>
<li>
<p>martfury :<br />
banner_large, banner_medium, banner_small, counter, faqs, icon_box, icons_list, image_box, member</p>
</li>
<li>
<p>plethora<br />
button,counter,headinggroup,hoverbox,teaserbox….</p>
</li>
<li>
<p>Woodmart<br />
Text Block, Button, Section Title, Info Box, Promo banner, Responsive Text block, Testimonial</p>
</li>
<li>
<p>Ultimate<br />
Info Circle</p>
</li>
<li>Naapo<br />
Vertical Tab</li>
</ul>
<p>other elements on demand.</p>
<h4>Concept</h4>
<p>Translate static text ,url, textarea, from the main language to other languages.</p>
<p>WPBakery 7.0 and 6.7.0 don’t need anymore change to be working with Falang for WPBakery.</p>
<p>Witht the 6.6.0 version of WPBakery you have too add a Filter to allow the translation tab to be displayed.<br />
wp-content/plugins/js_composer/include/classes/core/class-wpb-map.php 925<br />
add this line :<br />
self::$sc[ $tag ] = apply_filters(‘vc_element_settings_filter’, self::$sc[ $tag ], $tag );</p>
<h3>Known issues</h3>
<p>Between the 1.5 and the previous version the datastorage for content html translation is changed.<br />
The front-end translation will work but when you edit an old widget with content , the translation is removed.</p>


Falang for WPBakery Lite

The Falang for WPBakery plugin makes your WPBakery page translation simpler.

<h4>Features</h4>
<ul>
<li>Imports languages and WPML options (when the same options exist in Falang).</li>
<li>Imports posts and terms languages as well as translations (including for custom post types and custom taxonomies).</li>
<li>Imports multilingual nav menus.</li>
<li>Imports strings translations (not yet).</li>
<li>Does not delete WPML data.</li>
</ul>
<h4>Important</h4>
<p>Although WPML data should not be corrupted, as Falang data are created without deleting anything, <strong>make a database backup before proceeding</strong>.</p>
<h4>How to proceed?</h4>
<ul>
<li>De-activate WPML</li>
<li>Activate <a href="https://wordpress.org/plugins/falang/" rel="ugc">Falang</a> and WPML to Falang. Do <strong>not</strong> create any language with Falang (they will be imported).</li>
<li>Go to Tools -> WPML Importer.</li>
<li>If all checks are passed, you can click on ‘Import Languages’.</li>
<li>If the WPML languages are imported, you can click on ‘Import’.</li>
<li>De-activate WPML to Falang (You can even delete it).</li>
<li>Setup a language switcher either as a widget or in nav menus.</li>
<li>Check that everything is OK.</li>
<li>If something went wrong and you want to revert to WPML, you can delete Falang using the red link in the Plugins table (If you want to delete all data created for Falang, you need to set the option in Falang > Settings;` <strong>before</strong> Delete Translations on uninstall) and then re-activate WPML.</li>
</ul>
<h4>Notes</h4>
<p>This plugin does not include error management. It has however been tested successfully to migrate a site with about 9,000 posts and media.<br />
It has been tested with WPML 4.5.5</p>
<h4>Credits</h4>


Falang WPML importer

Import multilingual data from WPML into Falang for Wordpress

Falang for WPBakery Lite vs Falang WPML importer