[Resolved] WPML Plugin is causing an error in Divi

Hello there,

While debugging this, I noticed that when we hit the save button an error shows up in the console saying that a request to '/wp-admin/admin-ajax.php' failed within Cloudfware.

As a test, can you please(at least temporarily) add the /wp-admin/ to the allowlist/bypass of the Cloudfare waf rules:

hidden link
hidden link

If the issue persists after this, in order for me to debug this properly, I'd like to request your consent for me to make a local copy of your site that I'll remove as soon as we finish debugging this.

This is necessary to avoid causing any side effects to the live site and to test hosting-related specific issues.

Thank you, please let us know.

Hello there,

I'm attaching the screenshot with the error I'm referring to.

I need to make a correction, firstly, while checking the network tab I misread an info in the header that made me believe that the error was coming from cloudfare.

Upon further review I can't make this association, although the error is there, it doesn't necessarily come from the CDN.

I tried making a copy of the site using Duplicator but it seems like it was banned by Kinsta, I also tried creating a staging site using cloudways but it failed.

Is it possible for you to create a package of the site and upload it to the server where I can download it?

Thank you, please let us know.

Hello there,

I've successfully imported your site locally for testing. Despite the large size of the site, which slowed down the import process, I didn't encounter any issues in my local copy with a 512MB memory limit.

Upon reviewing the error logs from the live site, I noticed the following entry repeating a bit:

[error] 84773#84773: *63857 FastCGI sent in stderr: "PHP message: PHP Warning:  Constant WP_DEBUG already defined in wp-config.php on line 123PHP message: PHP Warning:  Constant WP_DEBUG_LOG already defined in /wp-config.php on line 129PHP message: PHP Warning:  Constant WP_DEBUG_DISPLAY already defined in /wp-config.php on line 135PHP message: PHP Warning:  Constant SCRIPT_DEBUG already defined in wp-config.php on line 143PHP message: PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in wp-includes/class-wpdb.php on line 2320" while reading response header from upstream, client: 81.193.13.127, server: multisitech.kinsta.cloud, request: "POST /wp-admin/admin-ajax.php HTTP/2.0", upstream: "<em><u>hidden link</u></em>:", host: "lofthotel.ch:64165", referrer: "<em><u>hidden link</u></em>"

The critical part of this log is the PHP fatal error indicating that the current memory limit of 256MB is insufficient for handling the request:

PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes)

As your hosting support has pointed out, and as evidenced by these logs, a 256MB memory limit is not being enough here, especially for a WordPress multisite which tends to have higher memory requirements.

To resolve this issue, please request your hosting provider to increase the PHP memory limit. Once they have done this, you can further increase the WordPress memory limit by adding the following line to your wp-config.php file:

  define( 'WP_MEMORY_LIMIT', '512M' );

The wp-config.php file is located in the root directory of your WordPress installation, alongside your database configuration settings. You will need to access and edit this file via SFTP.

To confirm the current WordPress memory limit, you can check it under WPML -> Support in the Info section.

For more information on editing the wp-config.php file and adjusting memory limits, you can refer to this guide:

https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

Thank you!
Mateus

Hello there,

Thank you for sharing the results.

Regarding your question about the memory limits, from your debug info I got this:

PHP MemoryLimit	256M
WP Memory Limit	256M

The PHP Memory Limit, as set in the php.ini file or .htaccess, is a general limit for all PHP scripts running on your server. It's like a ceiling that no individual script can exceed.

On the other hand, the WP Memory Limit, which is set in the wp-config.php file, specifically governs how much memory can be consumed by WordPress scripts. While this limit can be set independently, it cannot exceed the overarching PHP Memory Limit.

Initially, I suggested adjusting the PHP Memory Limit because if it's set too low, simply increasing the WP Memory Limit wouldn't be effective. The PHP limit acts as a cap for the WP limit.

After confirming the PHP Memory Limit was sufficiently high, it became appropriate to adjust the WP Memory Limit in wp-config.php. This step was necessary because even with a high PHP limit, WordPress will only use the amount of memory specified in its own configuration.

In summary, both limits needed to be addressed: first ensuring the PHP Memory Limit was adequate, and then adjusting the WP Memory Limit to leverage the available resources.

I hope this clarifies the process for you. Please feel free to reach out if you have any more questions.

Best regards,
Mateus