Problem: If you're experiencing issues with auto translation not working for Saved Rows in Beaver Builder when using WPML, it might be due to a compatibility issue. The content of Saved Rows does not appear in the Advanced Translation Editor, preventing automatic translation. Solution: We recommend the following steps to address this issue: 1. Enable Beaver Builder Template Translation: - Go to WPML → Settings. - Open Post Types Translation. - Find “Templates (fl-builder-template)”. - Change it from Not Translatable → Translatable – only show translated items. - Click Save. 2. Send Templates and Pages for Translation: - Go to WPML → Translation Dashboard. - You will now see a new section for Beaver Builder Templates. - Select the Beaver Builder template (the saved row) and the page that uses this saved row. - Scroll down and send for translation. 3. Complete the Translation: - If you use Automatic Translation, WPML will translate it. - If translating manually: - Go to WPML → Translations. - Open the job and finish the translation. 4. IMPORTANT Manual Step (Required Every Time You Use a Saved Row): A. Open the Translated Page in Beaver Builder: - Go to Pages and open the page that contains the saved row. - Click the three dots (top right) and disable Fullscreen Mode so you can see the top admin bar. - Use the language switcher to switch to the translated language (e.g., Spanish). - Click Edit Anyway. - Launch Beaver Builder in the translated version of the page. B. Re-select the Translated Saved Row: - Click the module/element where you insert the saved row. - Click Edit. - The saved row is not selected by default. - Manually select the translated version of the row. - Save and publish the translated page.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are using WPML with Beaver Builder and have set up separate domains for different languages. However, when you switch languages in the WP Admin panel, the 'wp-wpml_current_language' cookie does not update correctly. It shows 'en' instead of 'ja', and when switching from the English domain to the Japanese domain, two cookies with values 'en' and 'ja' appear. Solution: We have identified that this issue might be related to custom code that alters WPML's default behavior. We recommend checking any custom code that might interfere with WPML's handling of cookies. Additionally, we suggest using WPML Hooks as a possible workaround for managing cookies across different domains. You can find more information on WPML Hooks here: WPML Hooks Reference. If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at WPML Support Forum.
Problem: The client reported receiving a notification from WPML indicating a change in the site's domain address, even though no changes were made. The message suggested that the site had moved from 'https://www.xyz.com' to 'https://xyz.co.kr', a domain the client does not recognize or use. Solution: 1. We suggested that the false message might be due to WPML detecting the site on a different domain. For more details, see the documentation on using WPML on two domains. 2. To address this issue: - Navigate to WPML → Support and click on the Troubleshooting link. - On the WPML Troubleshooting page, click the button labeled 'Force-enable WPML’s Advanced Translation Editor'. 3. If the issue relates to using an existing WPML site key for a different URL, which is not supported, the client may need to re-register the keys. Instructions for this can be found at removing development site notice after moving to production.
If these steps do not resolve the issue or if the solution seems irrelevant due to being outdated or not applicable to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
