Critical Issue: White Screen of Death on translations after Divi 5 update

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.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
9:00 – 18:00	9:00 – 18:00	9:00 – 18:00	9:00 – 18:00	9:00 – 18:00	-	-
-	-	-	-	-	-	-

Supporter timezone: Asia/Yerevan (GMT+04:00)

Tagged: Compatibility

This topic contains 7 replies, has 1 voice.

Last updated by Christopher Amirian 1 day, 21 hours ago.

Assisted by: Christopher Amirian.

Author	Posts
November 15, 2025 at 8:05 pm #17581045
hubertS-9	Background of the issue: I am experiencing a critical issue on my website (hidden link) immediately after updating Divi 5 (Public Alpha) to the latest version. The source language (PL) seems to be working, but the translations render no HTML output. I suspect a conflict with the new Divi 5 storage architecture or rendering engine hooks. I have cleared all caches (server-side, CDN, and browser), but the issue persists. I can provide access credentials or debug logs if necessary. Link to a page where the issue can be seen: hidden link. Symptoms: All translated pages (EN version) are displaying a completely blank white screen (White Screen of Death). The broken page returns HTTP 200 OK but 0 bytes/empty body or fails silently. No content is rendered on translated pages. Questions: Could you please verify compatibility with the latest Divi 5 build? When might a compatibility patch be expected?
November 15, 2025 at 8:35 pm #17581054
hubertS-9	Hello, I would like to provide an update regarding the ticket above. The "White Screen of Death" (fatal error) seems to have resolved itself (possibly due to cache clearing or a minor subsequent update), but the site is still broken in a specific way. Current Symptoms: The translated page (hidden link) now loads, but it is not loading the correct Divi Theme Builder template. Instead, it displays a default, unstyled skeleton layout with no content inside. It appears that while the PHP crash is gone, WPML is struggling to retrieve/inject the correct Theme Builder layout and page content within the new Divi 5 architecture. Could you please investigate why the Theme Builder assignment is being ignored for the secondary language in this Divi 5 environment? Thank you.
November 16, 2025 at 9:18 am #17581322
Christopher Amirian WPML Supporter since 07/2020 Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00)	Hi, Welcome to WPML support. We will need you to refrain from installing the public beta version of Divi 5 at the moment, as the feature releases of Divi are ongoing at the moment. We are in contact with Elegant Themes to fix any issues that might happen with each release. We create a known issue entry, providing the current stage: https://wpml.org/errata/divi-5-wpml-compatibility-while-new-features-are-being-released/ So, for now, I have the suggestions below: 1. To make sure the normal workflow of your website is not hurt, roll back Divi to a stable, compatible version with WPML. 2. Install the latest version of Divi on the website below and try to replicate the Unstyled template layout issue: hidden link 3. Send the layouts to translation again: In a case that it might be just a need to refresh the translation and not a structural compatibility, test by going to WPML > Translation Management and send the layouts that you used for the homepage again for translation. Make sure they are translated from the WPML > Translations menu. Thanks.
November 16, 2025 at 12:38 pm #17581516
hubertS-9	Hi WPML Support, Thank you for the clarification and the errata link. However, rolling back to Divi 4 is extremely problematic for us at this stage, as the project is already heavily dependent on the Divi 5 environment. I also cannot invest time in replicating the entire layout in your sandbox environment just to confirm a known compatibility gap. My main question is: Do you have an Estimated Time of Arrival (ETA) for a patch that addresses the Theme Builder assignment issue in Divi 5? Are we talking about a matter of days/weeks, or is full compatibility blocked until the official "Stable" release of Divi 5 later this year? Knowing this timeline will help me decide whether I can wait for a patch or if I am forced to perform a complex downgrade. Best regards,
November 17, 2025 at 1:55 pm #17584382
Christopher Amirian WPML Supporter since 07/2020 Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00)	Hi, I checked, and we could not give any sort of ETA as Divi itself also rolls out the features gradually. But I am willing to check if this might be a setting issue or a translation issue maybe? What I need you to do is to create a copy or staging version of the website and I can login there. If needed we also can give you the means to copy your website to our server. So at least we will have a check with the website before asking you to a complete downgrade which you mentioned it will be costly for you. You can set the next reply as private to provide the login information of the website copy. Thanks.
November 18, 2025 at 8:39 pm #17589682
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+02:00)	Christopher is away today. I tried accessing your staging site, but after logging in I received the following message: There has been a critical error on this website. Please check your site admin email inbox for instructions. If you continue to have problems, please try the support forums. Could you please look into this? If you do not know what the issue is, you can activate WordPress debugging to see the actual error and its source. Here are the steps: 1. Enable WordPress debugging by editing your wp-config.php file. Add (or modify, if these lines already exist) the following lines before the comment /* That's all, stop editing! Happy publishing. */: define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', false ); 2. Replicate the error. 3. Check the debug.log file (located in the /wp-content/debug.log) Additionally, could you provide FTP access? I’ve set the following message to private, so you can safely share the details there.
November 19, 2025 at 2:10 pm #17592195
Christopher Amirian WPML Supporter since 07/2020 Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00)	Hi Hubert, Thank you for the login information. I tried to login both with the WP Staging page and the default WordPress login page but the user/pass are invalid. I used the previous private reply information as the new one contained only FTP login info. Would you please set the next reply as private and give us the correct login information and URL so I can check? Thanks.
November 20, 2025 at 12:30 pm #17595487
Christopher Amirian WPML Supporter since 07/2020 Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00)	Hi, Thank you very much. I checked the details. Even the manual translation method does not work there, unfortunately. There is nothing that I can suggest at the time being, except the fact that you downgrade from Divi 5. As soon as the official version of Divi 5 is released, please get back to u,s and we will follow up on the issue. Thanks.