Beaver Builder translated saved items not showing up in BB frontend (S02)

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

Problem:

Beaver Builder - Saved Modules in other languages (not the default language) can not be saved after creation.

Solution:

This issue is fixed with the latest versions of Beaver Builder and WPML.

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.

This topic contains 39 replies, has 3 voices.

Last updated by Itamar 4 years, 5 months ago.

Assisted by: Itamar.

Author	Posts
May 20, 2020 at 4:28 pm #6179619
Itamar Supporter Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00)	Hi. Our third-tier supporter has debugged this issue and found out the cause of it. He explains it like so: There is a taxonomy term called "modules" in the taxonomy fl-builder-template-type. For some reason, that term is translated. This is why and because of problematic associations between term and post - the entries are not shown. This problem was spotted on the DB of the site. And it can also be fixed by proceeding with the following steps. 1. ** Important! Please make a full site backup (files and DB) before you proceed with those steps** 2. In the table, wp_term_relationships make sure that all terms assigned to term with id 1013 are assigned to term id 5. First you can get a list with this query: SELECT * FROM `wp_term_relationships` WHERE `term_taxonomy_id` = '1013' You should get 9 rows. Please see the attached screenshot select-1013.jpg. Then perform the following command: UPDATE `wp_term_relationships` SET `term_taxonomy_id` = '5' WHERE `term_taxonomy_id` = '1013'; Then those 9 rows will be changed. Please see the attached screenshot update-1013-to-5.jpg. 3. Then remove the entries in terms table: DELETE FROM `wp_terms` WHERE `term_id` = '1013'; 4. And lastly remove the entry in wp_icl_translations table for both terms: DELETE FROM `wp_icl_translations` WHERE `element_type` = 'tax_fl-builder-template-type'; ** Important! Please make a full site backup (files and DB) before you proceed with those steps** I've just tried this on the copy of your site and it fixed the problem. Please see the attached screenshot saved-modules-ok.jpg. Can you please try it on your site as well and tell me if it is ok? If you need help with this procedure, please let me know. WPML does not set the fl-builder-template-type taxonomy type to be translatable, it's not translatable by default. We suspect it was manually changed (probably accidentally) on your site. Nevertheless, the issue is being checked by our developers if anything can be done on our side to prevent such cases from happening in the past. I'll keep you updated on this when I have news from our developers. Regards, Itamar.
May 20, 2020 at 5:41 pm #6180123
danielaS-13	Hi, Same happening on one of my sites. Have you found a solution to this? I've translated the row with the Advanced Translation Editor, but it doesn't show up on the front end as a saved BB row. Have also tried all the troubleshooting tips you showed in a previous ticket. And I have created the row within the page, saved it, it shows up when I save it, but when I refresh it has disappeared. Any updates on this issue would be appreciated! Thanks, Daniela
May 20, 2020 at 8:07 pm #6181039
Itamar Supporter Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00)	Hi, Daniela. I'm not sure which troubleshooting tips you tried. Have you seen my reply from earlier today here? https://wpml.org/forums/topic/beaver-builder-translated-saved-items-not-showing-up-in-bb-frontend-s02/page/2/#post-6179619
May 21, 2020 at 6:43 pm #6189397
emmanuelS-7	Hi Itamar, Great, thanks for the in-depth troubleshooting! I successfully edited my database as recommended in your detailed instructions and, miracle, recovered the BB saved items of the second language in BB editing interface, hurray! Just a small detail i had to modify, in the last SQL command, at point 4, tax_fl-builder-template-type has to be surrounded by straight single quotes instead of tilted quotes. Otherwise, an error is returned: Unknown column… in 'where clause' This is the commands that works: DELETE FROM `wp_icl_translations` WHERE `element_type` = 'tax_fl-builder-template-type'; However, i applied this fix on a local copy of my site, just in case, now i have to do it on the live site… without having access to PHPMyAdmin, i have to find another way. Thanks a lot for your help! Emmanuel
May 21, 2020 at 7:35 pm #6189833
Itamar Supporter Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00)	Hi. Great! I'm glad that the fix worked for you. I'm sorry for the single quotes glitch. Thanks for pointing this out to me. I've fixed it in my reply. To get access to the DB of your site you can use the PHPMyAdmin plugin for WordPress. https://wordpress.org/plugins/wp-phpmyadmin-extension/ Or the Adminer script. hidden link The issue is now escalated to our developers. Best Regards, Itamar.
May 22, 2020 at 12:25 am #6190939
emmanuelS-7	Itamar, I finally found an access to PHP MyAdmin on the live site server, thanks for the info about the PHPMyAdmin WP plugin anyway, very helpful. So, i applied the DB modifications and the second language BB Saved items showed up in BB panel. At this point, the issue seemed to be fixed… unfortunately, i discovered other issues and restored the previous database of the live site to prevent side effects. 1 - In BB layout edit mode (second lang EN): when dropping saved modules in the layout, their content displayed doesn't reflect their real content, it seems to come from another saved module. To see and edit a saved modules content, click the wrench icon in BB panel, you should notice a difference. Maybe the DB modifications triggered a confusion in BB? 2 - In Admin > BB > Saved modules (main lang FR): edit an already translated module like Sidebar : Contact général by clicking the pen icon and you'll see that BB module's fields are now missing in WPML Translation Manager, so it's impossible to modify them. Best regards Emmanuel
May 22, 2020 at 1:12 am #6191135
emmanuelS-7	If useful, screenshots of my WPML settings for BB: 1 - Admin > WPML > Settings > Taxonomy Translation (fl-builder-template-category and fl-builder-template-type) 2 - Admin > Post Edit > Multilingual Content Configuration
May 22, 2020 at 5:24 am #6192457
Itamar Supporter Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00)	Hi and thanks for the extra details. fl-builder-template-type should not be set to translatable. Please set it to 'Don't translate'. Regards, Itamar.
May 22, 2020 at 9:22 am #6193683
emmanuelS-7	Hi Itamar, Yes, fl-builder-template-type is set as Not translatable as we can see on my first screenshot. It doesn't prevent the 2 new issues I described to occur. Please, would you try to push the investigations a little further on the test site you provided, by comparing a saved module content displayed when we drop it in the layout from BB panel in BB Edit mode, and its content once opened for editing in BB? This is my first point described above. Then my second point when trying to modify a FR saved module's EN translation with WPML Translation Manager (try an old module, for instance the one i pointed to above). You should see that BB fields are missing. Thanks Emmanuel
May 24, 2020 at 10:02 am #6203569
Itamar Supporter Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00)	Hi. 1. I can see the problem that you are talking about. Nevertheless, the 'Test 3 -EN' page is the translation of Test 3 (French page). If you will try to edit this page in the WordPress editor you'll see a notice about it. Please see the attached screenshot test. Therefore, you should only edit it with WPML's Translation Editor. Trying to edit it with the Beaver Builder editor can cause problems. It is important to keep following the translation procedure as specified in our documentation here. https://wpml.org/documentation/plugins-compatibility/beaver-builder/ 2. It seems that the 'Contact général' French module was not published or updated. After I had published it, everything works as expected. The text is showing for translation in WPML's Translation Editor. Please see the attached screenshot fr-module-ok.jpg. To make sure that everything is working correctly, I tested the Beaver Builder Saved Modules on a fresh WordPress installation. And I can see that everything is working as expected in regards to the Saved Modules. If you think that something is not working as expected, please try to replicate it on the test site I created. If you are able to replicate it there then explain the steps to replicate it. Please add some screenshots. You can access the test site here. hidden link Thanks, Itamar.
May 27, 2020 at 2:53 pm #6230483
emmanuelS-7	Hi Itamar, Thanks a lot for your details. I'm pretty busy right now and will get in depth as soon as possible, in the next days i hope. Emmanuel
May 28, 2020 at 10:48 pm #6244109
emmanuelS-7	Hi Itamar, Sorry for the delay, now i have a bit of time to go further in our investigations. 1 - I understand that you suggest me to only use WPML Translation manager to edit EN pages (second lang), am i correct? If so, i must remind you the goal of translating BB modules in the second language: some EN pages have a different structure and number of BB modules compared to their FR version (main lang). Hence they cannot be translated in the Translation manager and must be edited in BB, to add EN specific modules to the layout. That's where there's still a problem: I open an EN page in BB Edit mode, say test-3-en (hidden link; The EN translated modules show up fine in BB panel since you applied the DB fix (screenshot #1) But when i drop some of them in the layout, say Sidebar : Contact général EN, its content is not displayed in the layout (screenshot #2) Moreover, BB module editing panel detects it as a Heading module when it's actually a PowerPack Infobox module (screenshot #3) To see the module's actual content, open it in BB Edit mode by clicking the wrench icon in the saved modules list in BB panel when editing the page: you'll see its actual content and type are different. So i guess there's a problem in the DB linkage or something… 2 - Right, the FR module has to be modified and saved in its WP Edit page, then updating its EN translated version forces the fields to appear in WPML Translation manager, it works for me too (same old WPML trick to force things to get in order… a bit laborious though). Best regards Emmanuel
May 28, 2020 at 11:02 pm #6244187
emmanuelS-7	Itamar, I made another test by saving a FR new module and translating it in EN with WPML Translation manager (named Test module 1 FR / Test module 1 EN). This new module works as expected: when i drop it in an EN page layout, its content shows up fine and its type is properly detected by BB (screenshot 4). That's a good news for new saved modules, but it means that old saved modules still have a problem (linkage in the DB?). I hardly can consider rebuilding these old modules, many are global, all their occurrences in the site would disappear. Emmanuel
May 31, 2020 at 2:22 pm #6260483
Itamar Supporter Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00)	Hi. When I try to add an old saved module, it works for me. Please see the attached screenshots. Am I missing the point? Regards, Itamar.
May 31, 2020 at 4:45 pm #6261009
emmanuelS-7	Hi Itamar, Thanks for having tried. Some "old" saved modules work for me too, and some don't (probably the oldest). Could you please try with Sidebar : Contact général EN as mentioned in my post #6244109? https://wpml.org/forums/topic/beaver-builder-translated-saved-items-not-showing-up-in-bb-frontend-s02/page/2/#post-6244109 Regards Emmanuel