This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing persistent 500 errors linked to WPML on their staging site, despite extensive troubleshooting including deactivating less essential plugins, reverting to older WPML versions, and consulting forum topics. The errors persist even after enabling WordPress debugging and updating plugins.
Solution: We recommended the following steps to further diagnose and potentially resolve the issue: 1. Enable WordPress debugging to capture specific error messages. This involves adding specific lines of code to the
wp-config.php
file to log errors without displaying them on the site. 2. Reproduce the error to trigger and log specific error messages, then share these messages for further analysis. 3. Ensure all WPML components are updated to the latest versions after ensuring a complete backup of the site and database. 4. If the issue persists, we advised checking the PHP memory limit and using WPML’s troubleshooting tools.
If these steps do not resolve the issue or if the solution becomes outdated, we recommend opening a new support ticket. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at https://wpml.org/forums/.
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.
Background of the issue:
I am experiencing constant 500 errors linked to WPML. It's been a week, and these errors occur randomly but consistently. I had to deactivate the main plugin from the live website. The issue is also present on the sandbox site where the plugin is active: hidden link. I have tried reinstalling wp-admin and wp-includes, isolated the bug to the WPML main plugin, deactivated some less essential plugins, and reverted to an older version 4.7.6, including WooCommerce Multilingual and String. I also referred to this forum topic: https://wpml.org/forums/topic/php-fatal-error-in-sitepress-multilingual-cms-classes-wp-core-hooks-post-class-wpml-remove-pages-not/.
Symptoms:
I am encountering constant 500 errors on my website. I expected to see no 500 errors, but they persist.
Questions:
How can I resolve the constant 500 errors linked to WPML?
Is there a specific configuration or update needed to prevent these errors?
Hello,
My name is Carlos, and I will continue working on this ticket
I kindly ask you to follow these steps to get more information about the cause of the error:
- Go to the wp-content folder -> debug.log file -> Rename the debug.log file to debug-old.file -> Save the changes
- Make sure the debug mode is active as described by the AI chat or as described in this guide: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/
- Reproduce the 500 error
- Check the new debug.log file that was automatically created and share the last fatal error message in it
This information will help us identify the cause of the issue.
Note: Please let me know if you need assistance following the steps described.
Sure, I have set your next message private so you can securely share the information.
Also, please share the access credentials to the site in the next message and confirm you have created a full site backup that you can restore if necessary. This will allow me to double-check the configuration and try to reproduce the issue.
I was double-checking the description of the issue, and you mentioned that the issue also persists in the staging site; however, the staging site you mentioned is different from the staging site you shared. I have tried to reproduce the issue, but everything is working correctly on the site you shared.
Can you describe step-by-step how to reproduce the 500 error?
Sorry, yes i had to create another staging site since and the way to replicate is annoying but you have to navigate between that pages until it does it. The bug seems to be a memory leak.
I was gonna replicate it for you but it seems you have deactivated wpml, so it won't do the bug !
I am not saying the source is 100% wpml necessarily, might be a conflict, but I can tell you for sure it wont happen if wpml is deactivated.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Madrid (GMT+01:00)
Hi there!
This is Paola and I will continue with the ticket as Carlos is off.
To find out the details of the error you are getting, could you do the following?
- Access the wp-config.php file (located in the WordPress root).
- Insert these lines just before /* That's all, stop editing! Happy blogging. */
Do you know what is a memory leak? It is only produced after many clicks. It would happen after a few hours on the main site, when people brought in trafic. I had replicated it after 15 minutes when someone of your support first replied to me.
Now that the staging site has no trafic and it's been a while since I reported it, we need to go back throught the process by clicking on things for at least 15 minutes, it's really time demanding and wish it would be taken care of rapidly when I manage to spend that much time on it.
Sorry but its the busiest time of year. I can try replicating again tonite, will get back to you
