Translations

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.

Our wait time is higher than usual, please make sure you are meeting the minimum requirement - https://wpml.org/home/minimum-requirements before you report issues, and if you can take a look at current Known Issues - https://wpml.org/known-issues/. Thank you.

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

Supporter timezone: America/Los_Angeles (GMT-07:00)

Tagged: ATE

This topic contains 5 replies, has 1 voice.

Last updated by Bobby 1 day, 23 hours ago.

Assisted by: Bobby.

Author	Posts
March 28, 2025 at 12:22 pm #16872714
Romain	Background of the issue: I am trying to translate a string by going to WPML > Translations, clicking to translate on any page, and then clicking on a string to translate. The issue can be seen at this link: hidden link. Symptoms: I get a white screen when I click on a string to translate. Questions: Why do I get a white screen when trying to translate a string? How can I resolve the white screen issue in WPML translations?
March 28, 2025 at 6:50 pm #16874411
Mihai Apetrei Supporter Languages: English (English ) Timezone: Europe/Bucharest (GMT+03:00)	Hi there. Receiving a blank page usually means that there is a chance of a fatal error taking place or an existing incompatibility issue between WPML and (at least) one of the active plugins or the active theme. 1. Can you please enable the WordPress debug feature and recreate the issue to see if you are getting an actual error message instead of just the blank page? This will allow us to see if any PHP errors are being produced. More Info: https://codex.wordpress.org/Debugging_in_WordPress In order to do that, edit the wp-config.php file inside your WordPress directory and insert the following lines: define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', false ); define( 'WP_DEBUG_DISPLAY', true ); Now, please reproduce the issue once again. Now, if you see more information than just a blank screen, please share a screenshot with us so that we can see what error is causing that blank page to show up. 2. We can also test for a compatibility issue. Can you please let us know if this issue happens even when only the WPML plugins are active, and you are using a default WordPress theme? Please try the following steps so that we can test for a compatibility-related issue: - create a full website backup - disable all plugins except WPML and its add-ons - check if the issue is happening again  - if it's not, reactivate your plugins one by one, checking every time if the issue shows up again so that you can understand which plugin is causing that issue If the issue happens even with the non-WPML plugins disabled: - leave all the non-WPML plugins deactivated  - switch to a default theme like TwentySeventeen  - try to recreate the issue now If you have the chance, it would be best to do this in a staging (testing) environment. Please let us know how that goes and if following any of these steps solved your issue or brought any change. We will be waiting for your response. Mihai Apetrei
March 31, 2025 at 10:59 am #16878771
Romain	Hi, I activate the WP_DEBUG but I don't get any PHP error. THe only error I see is in the JS console: hook.js:608 SecurityError: Failed to read the 'cssRules' property from 'CSSStyleSheet': Cannot access rules at application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:91:12978 at Array.forEach (<anonymous>) at application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:91:12931 at application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:91:13172 at L (application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:91:14570) at r2 (application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:91:17301) at vn (application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:13:22992) at wu (application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:15:25090) at qr (application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:14:24725) at Wr (application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:14:24653) overrideMethod @ hook.js:608Comprendre cette erreur application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:13 Uncaught SecurityError: Failed to read the 'cssRules' property from 'CSSStyleSheet': Cannot access rules at application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:91:12978 at Array.forEach (<anonymous>) at application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:91:12931 at application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:91:13172 at L (application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:91:14570) at r2 (application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:91:17301) at vn (application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:13:22992) at wu (application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:15:25090) at qr (application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:14:24725) at Wr (application-b0679dcc577f8b664129266caeac87690d649b01d02015cb25a282d9aacb1da0.js:14:24653) I also tried deactivating all the plugins but WPML and it is still not working. Do you have any idea of what could cause this?
April 1, 2025 at 6:01 am #16881369
Bobby Supporter Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	Hi there, Did you recently migrate your site by any chance? Please go to WPML->Support->ATE error logs and share with me the top 5 errors logged there.
April 1, 2025 at 10:49 am #16882424
Romain	Hi, The WPML->Support->ATE error logs are empty but for whatever reason the plugin is now working fine 🙂
April 2, 2025 at 4:15 am #16885256
Bobby Supporter Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	That's great, please let me know if the issue returns otherwise the fact that the ATE error logs is empty is a good sign.