we are experiencing an issue with WPML (ATE) in combination with Divi Builder:
Problem:
Pages created with Divi Builder lose some styles in translated versions created via ATE.
Affected styles include element-level settings such as background and font size.
Behavior:
In the default language, all styles display correctly.
After translating a page using ATE, some styles are missing and appear to fall back to Divi default styles.
If we open the translated page in Divi Builder and click "Save" (without making any changes), all styles are applied correctly.
However, when the original page is updated and the translation is refreshed via ATE, the issue reappears.
Important notes:
This happens consistently across multiple pages.
Divi Static CSS is disabled.
Expected behavior:
Styles defined in Divi Builder should be preserved correctly when using WPML ATE, without requiring a manual save in Divi Builder for each translated page.
Could you please advise:
Whether this is a known issue with Divi + ATE?
If there is a configuration or workaround to ensure styles persist correctly?
Whether specific custom fields (e.g. _et_pb_*) need to be configured differently in WPML?
At the moment, I’m unable to reproduce the issue in the staging environment (which is a copy of the live system).
I will continue investigating and report back once I identify the root cause. Currently, I suspect caching on the hosting environment as a possible factor.
Additionally, auto-translation is enabled on this site. Could this be related to a timing issue?
Specifically, if a user visits the translated page after the original content is updated but before the automatic translation process has fully completed, could this result in partially applied styles (e.g., incomplete or fallback CSS)?
Automatic translations should not cause this issue. Once all translations are completed, they will appear on the front end, so in-progress jobs shouldn’t lead to this behavior.
