Problem: The client was experiencing issues with translating some backend blocks on their English version page.
Solution: We accessed the client's site and set the
kc_raw_content
field to be copied. We then updated the page in the default language and its translation. We asked the client to check if the translated team page was working correctly now.
We also informed the client that KingComposer is currently incompatible with WPML, which might cause issues when translating with the translation editor. We recommended using the manual translation approach and provided a link to the relevant documentation:
If the solution provided is not relevant due to being outdated or not applicable to your case, we suggest opening a new support ticket. 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 contact us in the WPML support forum.
Problem: The client was experiencing issues with Revolution Slider not working with KingComposer on the translation page. Solution: We also noted that KingComposer is not compatible with WPML and is outdated, recommending the use of the WordPress editor to translate the page instead. We provided a link to our documentation on using different translation editors for different pages: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/
Upon further investigation, since the issue could not be replicated on the sandbox site, we suggested a workaround by manually selecting the slider when editing the translation page using the WordPress editor. We provided an example of a test page where the slider was displayed correctly.
If the solution provided here is not relevant to your case, perhaps because it's outdated or simply not applicable, we encourage you to open a new support ticket. 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 need further assistance, please contact us through the WPML support forum: https://wpml.org/forums/forum/english-support/.
Problem: The client needed to manually translate content using a page builder that is not compatible with WPML. Solution: We recommend using the WPML manual translation method. Here are the steps: 1. Duplicate the page from the default language to another language. 2. Switch the language from the backend top bar area to the target language. 3. Go to the "Pages" main list. 4. Edit the duplicated page with your preferred builder and manually change the text or recreate it as needed. However, we cannot guarantee that this will work due to the lack of compatibility with WPML. We also suggest contacting the plugin authors and recommending them to join our Go Global program, where our Compatibility developers will assist in making their product fully compatible with WPML at no cost.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If so, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket.
