Problem: If you're working on a site using WPML to translate posts and pages built with WPBakery and find that all fields except buttons get translated, this summary is for you. Solution: We recommend making a full backup of your website first. Then, follow these steps: 1. Navigate to WPML > Settings > Custom XML Configuration tab. 2. Insert the following code:
3. Save the changes. 4. Make a small change to the original page containing the buttons. 5. Update the translation. This should enable the translation of the button elements. If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client was trying to translate a page from Swedish to English using automatic translation. After publishing, the page content still appeared in Swedish, the default language, despite the translation looking good in the preview. The client was using BeTheme.
Solution: We recommend the following steps to resolve the issue: 1. Navigate to WPML >> Support >> Troubleshooting page. 2. Click the following buttons: - Clear the cache in WPML - Synchronize posts taxonomies - Remove ghost entries from the translation tables - Synchronize local job ids with ATE jobs - Synchronize translators and translation managers with ATE - Assign translation status to duplicated content - Fix post type assignment for translations - Set language information 3. Edit the problematic page in BeBuilder, make a minor change (like adding a space at the end of a paragraph) to force the translation to reload, and then re-save the secondary language page.
Please check if the issue is resolved after following these steps.
Note that the solution provided might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket.
