It looks like WPML does not support BeTheme

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is unable to translate content created with BeBuilder on their BeTheme-based website using WPML. Despite setting BeBuilder data storage to Serialized | Readable format and updating all pages, WPML does not recognize the BeBuilder elements for translation.

Solution:
We recommend performing a full site backup before proceeding with any changes. After securing your backup, please follow the workaround provided in the WPML errata page for issues with BeTheme and BeBuilder content not being available in the translation editor. You can find the detailed instructions here:
https://wpml.org/errata/betheme-bebuilder-content-not-available-in-translation-editor/

May you need to make the mfn-page-objects field also as translatable.

Please note that this solution might be outdated or not applicable to your case. If after checking the errata and ensuring you have the latest versions of themes and plugins the issue persists, we encourage you to open a new support ticket. We also highly recommend visiting the WPML known issues page to verify if there's a permanent fix for your version. If further assistance is needed, please contact us in the WPML support forum.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: Known issue

This topic contains 4 replies, has 2 voices.

Last updated by Bigul 8 months, 3 weeks ago.

Assisted by: Bigul.

Author	Posts
February 23, 2024 at 2:26 pm #15338261
dariod-33	I recommended and purchased WPML for our company's site because it was explicitly stated that it supports BeTheme. Our site is based on BeTheme and completely built by BeBuilder. It is mostly finished and now we need to translate it from English to Italian and Spanish languages. We do not use Automatic Translation, since we want to translate with care and manually every single string. However it does not work. If I go to translation Manager, I can translate only the page title, non the content developed by Be Builder. PLEASE NOTE that in BeBuilder Advanced settings I set BeBuilder data storage as Serialized \| Readable format, and updated already all pages. Therefore WPML should be able to see all BeBuilder elements strings. But it does not. THIS IS A SEVERE PROBLEM. I have to publish the multi-language version of site by end of February. PLEASE, HELP!
February 23, 2024 at 3:01 pm #15338389
Bigul Supporter Languages: English (English ) Timezone: Europe/Vienna (GMT+01:00)	Hello, Welcome to the WPML support forum. I will do my best to help you resolve the issue. It looks like this bug is related to the following known issue. Please try the workaround suggested in the errata after a full site backup and let us know your feedback. https://wpml.org/errata/betheme-bebuilder-content-not-available-in-translation-editor/ -- Thanks! Bigul
February 23, 2024 at 4:01 pm #15338657
dariod-33	Well, i did as suggested, that is, I added mfn-page-items as translatable field, but nothing changed. The only translatable field in the Advanced (or even Classical) WPML Editor, is the page title. All the other texts werenot visible. So I inspected the MySQL database and found out that you have to make translatable also the custom field mfn-page-objects. You should update that piece of information.
February 23, 2024 at 5:11 pm #15338855
dariod-33	Good support, but wrong answer. You need to make translatable mfn-page-objects too. Please, update you info. Thank you for support.
February 23, 2024 at 5:13 pm #15338860
Bigul Supporter Languages: English (English ) Timezone: Europe/Vienna (GMT+01:00)	Hello, Thank you for the feedback. I will update our team about this. Please feel free to ping us if you need any further assistance with WPML. We are happy to help always. -- Thanks! Bigul