Skip Navigation

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.

This topic contains 3 replies, has 0 voices.

Last updated by christosG-8 19 hours, 57 minutes ago.

Assisted by: Osama Mersal.

Author Posts
January 20, 2025 at 12:12 pm #16613128

christosG-8

Background of the issue:
I am trying to upgrade the WPML String Translation from version 3.2.7 to 3.2.18. Two weeks ago, I was informed by support that the Elements Pack Pro plugin was incompatible with WPML, so I removed it. Today, I attempted to install version 3.2.18 again.

Symptoms:
After installing the new version, I encountered a white page error on my website, causing the site to go down.

Questions:
Why does the site go down with a white page after updating WPML String Translation?
Is there another compatibility issue causing this problem?

January 20, 2025 at 3:17 pm #16614323

Osama Mersal
Supporter

Languages: English (English ) Arabic (العربية )

Timezone: Africa/Cairo (GMT+02:00)

Hi,

Thanks for contacting WPML forums support. I'll be glad to help you today.

1) Could you please check if the issue persists in a minimal environment by following these steps?

1- Deactivate all the plugins except WPML CMS.
2- Switch to a WordPress default theme like Twenty Twenty-one.
3- Update String Translation
4- Activate String Translation

If the issue is gone, activate them one by one to see which one is causing an interaction issue.

❌ Please backup your database before performing the above test ❌

If the issue happens while only WPML CMS and String Translation are activated, please provide the WordPress debug.log; this will allow us to see if any PHP errors are being produced. More Info: https://wordpress.org/support/article/debugging-in-wordpress/

To enable it, open your wp-config.php file and look for the following line:

define('WP_DEBUG', false);

And change it to:

define('WP_DEBUG', true);
// Enable Debug logging to the /wp-content/debug.log file
define('WP_DEBUG_LOG', true);
// Disable display of errors and warnings, which is recommended on a live site.
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors',0);

Then, try to reproduce the issue and check if any errors were saved to the debug.log log file inside the /wp-content/ directory.

It would be great if you could paste your debug.log to https://pastebin.com/ and provide me with that link!

2) Could you please share your Debug information with me?
You can read a detailed explanation about it here. (http://wpml.org/faq/provide-debug-information-faster-support)
The debug info will give me a lot of information about how your site is configured.

Best regards,
Osama

January 23, 2025 at 9:21 am #16626333

christosG-8

Hello,
I found out that the problem occurs when I have the plugin Anywhere Elementor Pro activated. Unfortunately my site depends heavily on this plugin, so I cannot uninstall it b4 working a couple of 100 hours on the site replacing all its widgets.|
Most of my translating is done, so I think I will stick to the version I have for now...

Thanks

January 23, 2025 at 9:45 am #16626718

Osama Mersal
Supporter

Languages: English (English ) Arabic (العربية )

Timezone: Africa/Cairo (GMT+02:00)

Hi,

Thanks for your update. Please log in to this hidden link">sandbox site and install the "" plugin.

After that, please let me know if the issue is reproducible there.

Best regards,
Osama

January 23, 2025 at 3:42 pm #16628993

christosG-8

Hello!!!!

Thanks for your help!
B4 installing the AEPro plugin I found out that the plugin I was using was not updated (WordPress did not inform me of the updates). After I updated AEPro to the latest version and WPML string translation, the problem is gone!!!!