Title: Polylang multilingual plugin incompatibility
Last modified: August 21, 2016

---

# Polylang multilingual plugin incompatibility

 *  Resolved [EsaI](https://wordpress.org/support/users/esai/)
 * (@esai)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/polylang-multilingual-plugin-incompatibility/)
 * Hi Greg,
    I asked about multilingual support for Vantage theme. Thanks for the
   support, theme works like a charm with Polylang.
 * The issue what I faced is actually with Page Builder. When creating a page in
   English with Page Builder the content is replicated also to the other languages.
   In practice if I add a widget to English page it will appear also on the page
   of other language. This happens with any content created with Page Builder.
 * Page Builder rocks and I really hope this issue can be resolved easily.
 * Cheers,
    Esa
 * [http://wordpress.org/plugins/siteorigin-panels/](http://wordpress.org/plugins/siteorigin-panels/)

Viewing 10 replies - 1 through 10 (of 10 total)

 *  [Solinx](https://wordpress.org/support/users/solinx/)
 * (@solinx)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/polylang-multilingual-plugin-incompatibility/#post-4225293)
 * Hi Esal,
 * We ran into exactly the same problem today. Fortunately there is a fix. The PageBuilder
   stores its information in custom fields, so the easy solution is to go to the
   polylang settings panel and turn off synchronization for custom fields.
 * If you have other custom fields attached to your posts you will need to do some
   more work, to manually sync those fields you added yourself. This requires hooking
   in on filters from polylang.
 * Alternatively you may be able to explicitly prevent the page_builder custom field(
   s) from being synchronized. We’re probably going to give that a try later today.
 * Regards,
    Wouter van Dam
 *  Thread Starter [EsaI](https://wordpress.org/support/users/esai/)
 * (@esai)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/polylang-multilingual-plugin-incompatibility/#post-4225299)
 * Thanks Wouter!
    I disabled the sync for custom fields and it did the trick. I
   am truly grateful for your help as this has spared me from huge frustration =)
 *  Plugin Author [Greg – SiteOrigin](https://wordpress.org/support/users/gpriday/)
 * (@gpriday)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/polylang-multilingual-plugin-incompatibility/#post-4225339)
 * Thanks for helping out Wouter. I’ll make note of this in the Page Builder docs.
   I’m not nearly as familiar with multilingual plugins as I should be.
 *  [Solinx](https://wordpress.org/support/users/solinx/)
 * (@solinx)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/polylang-multilingual-plugin-incompatibility/#post-4225345)
 * You’re welcome.
 * Here is the code we’re using now to specifically filter out the meta field for
   the page builder.
 *     ```
       /**
       	 * Filter the meta values that are synced between translated posts
       	 *
       	 * @since	18 Oct 2013
       	 * @version	1.0
       	 * @param	$metas 	an array of post metas
       	 * @param	$sync 	false when copying metas to a new translation, true when synchronizing translations
       	 * @return	Filtered array of post metas
       	 */
       	public function filter_copied_post_metas($metas, $sync)
       	{
       		if ($sync) {
       			if(($key = array_search('panels_data', $metas)) !== false) {
       			    unset($metas[$key]);
       			}
       		}
   
       		return $metas;
       	}
       add_filter('pll_the_languages', 'filter_the_languages', 10, 2)
       ```
   
 *  [kiksgreggel](https://wordpress.org/support/users/kiksgreggel/)
 * (@kiksgreggel)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/polylang-multilingual-plugin-incompatibility/#post-4225378)
 * Thanks for this solution, I had the same problem.
 *  [maplewang](https://wordpress.org/support/users/maplewang/)
 * (@maplewang)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/polylang-multilingual-plugin-incompatibility/#post-4225390)
 * Can It work with QTranslate then?
 *  [d4m0n](https://wordpress.org/support/users/d4m0n/)
 * (@d4m0n)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/polylang-multilingual-plugin-incompatibility/#post-4225392)
 * [@solinx](https://wordpress.org/support/users/solinx/)
 * I have the same problem.
 * Could you tell me where (in detail) I can paste this code?
 *  [Solinx](https://wordpress.org/support/users/solinx/)
 * (@solinx)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/polylang-multilingual-plugin-incompatibility/#post-4225393)
 * You could put the code at the bottom of the functions.php file of your theme.
 * Be sure to remove “public” from “public function …”, unless you know what PHP
   Classes are and will place the code within a class.
 * [@maplewang](https://wordpress.org/support/users/maplewang/):
    No, this is specifically
   for the polylang plugin.
 *  [florian_r](https://wordpress.org/support/users/florian_r/)
 * (@florian_r)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/polylang-multilingual-plugin-incompatibility/#post-4225394)
 * Hi Folks,
 * I’m having a similar issue and surely I’m just overlooking something:
    Running
   Vantage and Polylang works really good. I get both pages and posts translated
   as well as the respective menüs. Switching between languages works already.
 * However **what does not work is translating widgets** and, even more severe, **
   the custom vantage homepage** (i.e. the initial page being loaded). They stay
   the same even so I have changed between languages in the top panel of the wordpress
   admin interface. It seems impossible right now to save two language versions 
   of the custom homepage and of typical widgets like “pages” which I use for navigation
   the page footer.
 * I also unchecked all custom field sync as explained above. The code snipplet 
   provided seems to refer to posts only – this however is not my problem.
 * Any help is greatly appreaciated since I have to be live with the english site
   in a few days.
 * Thanks a lot in advance!
 * Best
    Florian
 *  [platschi](https://wordpress.org/support/users/platschi/)
 * (@platschi)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/polylang-multilingual-plugin-incompatibility/#post-4225397)
 * [@florian](https://wordpress.org/support/users/florian/) any succes with it? 
   I’m experiencing exactly the same problem.
 * Any solution would be awesome!

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘Polylang multilingual plugin incompatibility’ is closed to new replies.

 * ![](https://ps.w.org/siteorigin-panels/assets/icon.svg?rev=2556869)
 * [Page Builder by SiteOrigin](https://wordpress.org/plugins/siteorigin-panels/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/siteorigin-panels/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/siteorigin-panels/)
 * [Active Topics](https://wordpress.org/support/plugin/siteorigin-panels/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/siteorigin-panels/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/siteorigin-panels/reviews/)

 * 10 replies
 * 8 participants
 * Last reply from: [platschi](https://wordpress.org/support/users/platschi/)
 * Last activity: [11 years, 11 months ago](https://wordpress.org/support/topic/polylang-multilingual-plugin-incompatibility/#post-4225397)
 * Status: resolved