Dies ist das technische Support-Forum für WPML – das mehrsprachige WordPress-Plugin.
Mitlesen können alle, doch nur WPML-Kunden können hier Fragen veröffentlichen. Das WPML-Team antwortet im Forum an 6 Tagen pro Woche, 22 Stunden am Tag.
I've tried migrating from Divi 4 to Divi 5. The migrator caused my page to be white at every sub-page including home. Contacted the Divi support about this and got this response yesterday:
"Sorry for the trouble! It seems the issue is caused by WPML. When WPML is active, the content isn't migrated correctly.
I disabled WPML and ran the migration, which worked correctly. Can you take a look and see if all pages migrated correctly? I re-enabled WPML and also checked some of the pages on both the original language and english and it seemed to work correctly."
Please check this asap! Otherwise I would need to cancel my subscription and switch to a different translation editor. My website really relies on this. Since Divi 5 will be release in about a week, there normally should be no more errors with plugins like yours. The Beta phase is running for about 1 1/2 year now. Enough time to test.
If you need access to my staging, please let me know.
Thank you for sharing the results. I tested the migration on fresh website using WPML 4.9, and had no issues. This indicates that the issue you're having is specific to your website, and we'd like to investigate it.
Please provide me with access to your staging website, prior to the migration. We'll create a copy of it, to test and investigate the migration process.
The required fields can be found below the comments section. The information you enter is private, i.e. only you and I can see it and have access to it.
I may need to replicate your website locally. To do this, I need to temporarily install a plugin called "Duplicator" or "All in One WP Migration" on your website. This will allow me to create a copy of your website and content. Once the issue is resolved, I will delete the local website. Let me know if this works for you.
IMPORTANT
Please make a backup copy of the site files and database before giving us access.
- If you do not see the wp-admin/FTP fields, this means your post and site login details are being made PUBLIC. DO NOT post your website details if you do not see the required wp-admin/FTP fields. If you do not, ask me to enable the private box. The private box looks like this:
Thanks for sharing. I was able to recreate the issue on a local copy of your website. After better understanding it, I could also reproduce it on a fresh install. Our compatibility team and devs are well aware of it and working on a solution.
Again, thanks for bringing that to our attention. I'll keep you updated.
that was fast! I was expecting an answer within the next days. Can you maybe explain the issue to me? I'm also a plugin dev and I'm interested in the cause.
When you migrate from Divi 4 → Divi 5, Divi runs a conversion step that updates each post (basically a wp_update_post() call) and swaps the old Divi 4 storage/markup into Divi 5’s format. During this process, there’s a moment where the content is in a “half-converted / temporary” state.
Divi also sets a post meta flag called _et_pb_use_divi_5 to indicate “this post is now using Divi 5”.
WPML Page Builders has a “Gutenberg cleanup” routine. Its job is: if content looks like block-editor markup (or mixed markup), we normalize/clean it so translation handling stays consistent.
The problem is: during the migration, before Divi sets _et_pb_use_divi_5, the page content can look like something WPML should clean up. So WPML runs its cleanup right while Divi is trying to convert.
That cleanup ended up removing the Divi widget markup from the original (default-language) post content, so the backend and frontend showed an empty page. The translated page often still looked fine because its content is stored/handled differently (ATE + translation packages), so it wasn’t hit the same way.
That’s the core cause: a timing/condition bug — WPML cleaning content while Divi was in the middle of rewriting it.
We are alredy working to fix this, but meanwhile we only have the provided workaround. I hope this answers your question!
