x theme wpml editor broken, Translation editor does not show original content

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

Problem:
The client is unable to see the original content in the left column of the translation editor, and the translated content is also missing after updating the homepage using Cornerstone.

Solution:
In this case the client confirmed that running all available updates on the site solved the issue. If this will not solve the issue in your case, please check if the issue is related to known problems with Cornerstone:

For issues with nesting one Cornerstone widget into another, refer to the WPML errata page.
For issues with translating Global Blocks in X Theme, refer to the WPML errata page.

If these resources do not resolve the issue, we recommend creating a staging site for further testing.

If this solution doesn't look relevant, please open a new support ticket.

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: Compatibility

This topic contains 1 reply, has 2 voices.

Last updated by Andreas W. 1 year, 6 months ago.

Assisted by: Andreas W..

Author	Posts
November 7, 2023 at 11:46 pm #14752217
ivoM-3	I am trying to: Translate my pages, while keeping the the Same Design Across All the Languages. As described in your official guide as described here, https://wpml.org/documentation/theme-compatibility/xtheme/#keeping-the-same-design-across-all-your-languages. I always did like that, and I already had several problems. You can see my previous tickets, the last one solved the problem. As the previous times, when I had the same problem, I updated my homepage using cornerstone, and when I go in my pages list, and I click on 'edit translation' for any page or language, I cannot see the original content anymore on the left column of the translator editor, and I also lost the translated content. So I am blocked and I cannot update the translated pages again. Last time we managed to make the original content appear again. Please note that it is important that I only see the text there and not the html code. so far I updated the wpml configuration file: hidden link. But that did not help. I tried to identify the strings but that did not help either. I also tried to localize the theme and plugins but that did not help either. Maybe it is important for you to know that I just activated a child theme, but that should not be the problem. Link to a page where the issue can be seen: My homepage hidden link in italian has a css style, if you switch languages, it is not reflected. However this problem is more in the translation editor. I cannot see any content of the page I expected to see: The original page contents and the translations in the translation editor. Instead, I got: Original page contents and translated content is gone, this applies to all my pages. For example if I try to edit the translation of my homepage I see what you can see in the attached image. Somehow the cornerstone page builder 9498 is empty. BUT, it is not empty if I go in string translation (see other image). Somehow the translation editor and the string editor desynchronized. I hope that we can find a solution without the need to rewrite all the translations again.
November 9, 2023 at 6:05 am #14762229
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Hello, Could this be related to this known issue when nesting one Cornerstone widget into another one? https://wpml.org/errata/x-theme-cornerstone-certain-widgets-are-untranslatable-using-advanced-translation-editor-ate/ Or could this maybe be related to this known issue when using Global Blocks in X Theme? https://wpml.org/errata/cornerstone-cant-translate-global-blocks/ If not, could you maybe create a staging site, so that we can run some tests? Best regards Andreas
November 9, 2023 at 7:08 pm #14770639
ivoM-3	Das problem hat sich seber gelöst mit letzes update. Komischweise the problem was solved automatically with the last update. So we can close this issue. Thank you Andreas