We keep having issues with our site ciistaging.wpengine.com in relation to the plugin: We keep having 500 errors on the website that appear to be random throughout navigating the site both in the frontend and in the backend, and the error contains the same message
PHP Fatal error: Allowed memory size of XXXXX bytes exhausted" on different php files on the sitepress-multilingual-cms/ folder which is the plugin's main folder on the wp-content/plugins/ directory. Our site is currently on php 7.4, and we've already implemented the recommended configuration of WPEngine as described here: hidden link to increase the allowed memory, but the problem remains.
We've contacted support about the issue, and the support team told us the problem is with a memory leak issue within the plugin itself and that we should contact you for further assistance.
One more note, we deactivated the plugin the other day to test, and the 500 error went away. This confirms that the error is coming from the plugin.
Welcome to the WPML support forum. I will do my best to assist you in resolving the issue.
Please try the following troubleshooting steps after a full site backup {mandatory} and make sure the issue exists or not.
1) Go to WPML>>Support page, click on the Troubleshooting link (blue link in the middle of the page)
2) On the Troubleshooting page, please click on the following options of the *Clean up* section. Wait for confirmation of processing after each one.
- Clear the cache in WPML
- Remove ghost entries from the translation tables
- Fix element_type collation
- Set language information
- Fix WPML tables collation
- Assign translation status to duplicated content
- Fix terms count
- Fix post type assignment
- Cleanup and optimize string tables
If the problem remains, please share the WordPress debug.log (not WPML debug information) with us. So we can collect more details on this. Refer to the following links for instructions
To enable WordPress Debug log, open your wp-config.php file of the site root and look for define('WP_DEBUG', false);. Change it to:
// Enable WP_DEBUG mode
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
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
In this case, the errors will be saved to a debug.log log file inside the */wp-content/* directory. Please do the steps to reproduce the bug and check if you are getting any errors or warnings related to WPML in the log file.
If you can paste your debug.log to http://pastebin.com/index.php and provide me with that link, it would be great! (This is the cleanest way because sometimes the logs are long and create a complete mess of discussion.)
Thank you for the updates and for sharing the debug.log file. But the log does not show any warnings or errors related to WPML.
Therefore, to help us track this issue more effectively, we have a couple of requests:
1) Please fill in the private details fields (including FTP) after taking a full site backup. I would like to access your staging site’s admin area for further investigation. You can refer to the following resources for more information about our privacy and data handling policies:
2) Please provide the exact steps to reproduce the issue, so we can investigate it more efficiently.
Kindly note that our support is limited to this support forum. Therefore, there are limitations to assist with calls. Thank you for your understanding.
Thank you for the updates and for sharing the login details. However, I am encountering the following error when trying to log in to the site.
Error: The password you entered for the email address m***+***t@*****ge.com is incorrect. Lost your password?
Additionally, I am seeing the following warning when connecting via FTP. Please check.
Status: Waiting to retry...
Status: Connecting to c*****.****.****engine.com.com...
Response: fzSftp started, protocol_version=11
Command: open "****@*****engine.com" 22
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Thank you for the updates. I can now access the site backend and FTP as expected.
Are you using a custom theme? Which plugins are essential for the proper functioning of the theme?
When did you first notice this issue? Did it start occurring after upgrading to the latest versions?
Also, could you please update all plugins to their latest versions after taking a full site backup? Currently, more than 20 plugins need updates. We would like to confirm whether the issue persists with the latest versions installed.
