Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:
If you're experiencing a 500 error every time you update WPML plugins, despite increasing the memory limit and deactivating and reactivating plugins, follow these steps to diagnose the issue.
Solution:
We recommend enabling the WordPress debug log to capture more specific error messages. Here’s how you can do it:
1. Edit the

wp-config.php

file in your WordPress directory.
2. Insert the following lines:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

3. Try to reproduce the issue. After this, you should be able to find the debug log at: /wp-content/debug.log
4. Upload the content of this log to a site like pastebin.com and share the link with us for further analysis.
Relevant Documentation:
https://codex.wordpress.org/Debugging_in_WordPress

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we 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. If the problem persists, please open a new support ticket.

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.

Tagged: ,

This topic contains 3 replies, has 3 voices.

Last updated by Andrey 8 months ago.

Assisted by: Andrey.

Author Posts
November 1, 2024 at 10:11 am #16354573

sindreN-2

Background of the issue:
I am working on a site under development. Every time I update WPML plugins, I encounter 500 error. I have tried increasing the memory limit and deactivating and activating plugins to resolve the issue temporarily.

Symptoms:
I get a 500 error every time I update WPML plugins. This issue has been persistent for a long time. Not necessarily any plugin conflict, because a deactivation/activation fix the issue, I never have to delete any plugins.

Questions:
Can you please help me resolve the 500 error when updating WPML plugins?

November 1, 2024 at 10:35 am #16354657

Mihai Apetrei
WPML Supporter since 03/2018

Languages: English (English )

Timezone: Europe/Bucharest (GMT+03:00)

Hi there.

Before this ticket gets assigned to one of my colleagues, I will try to help.

That is a general error message, and we can't know what is causing the error until we don't dig a bit deeper.

Let us share the steps you can use to find out more about the actual error when you see a general error message like that one.

We can enable the WordPress debug log and recreate the issue to see if we get a longer, more specific error message.

This will allow us to see if any PHP errors are being produced.

To do that, we can edit the wp-config.php file inside our WordPress directory and insert the following lines:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Now, we can try to reproduce the issue once again.

We should now be able to locate the debug log in: /wp-content/debug.log

Paste the content (if any) on a site like pastebin.com and then share the link with us (the URL you are sharing will be visible only to you and us; it will be automatically hidden for anyone else).

Relevant Documentation:
https://codex.wordpress.org/Debugging_in_WordPress

Please let us know how things go.

Mihai Apetrei

November 1, 2024 at 12:55 pm #16354881

sindreN-2

Thank you 🙂

I've set it up and reproduced the issue.

Here is the debug log:
https://pastebin.com/75rvfaA5

November 1, 2024 at 4:41 pm #16355649

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

Thank you for your feedback.

I reviewed the debug.log file you shared and found no fatal errors. However, if you're encountering a 500 error, a fatal error should be recorded in the debug.log.

Could you please clear or delete the log, replicate the issue, and then check the log again for any errors?