[Resolved] Internal server error pendant l'edition de projets

Hi there,

Even now I can not access the login page and it throws the Error 500 one.

Would you please contact the hosting service provider and ask what is the error under the hood?

Also for a starter I'd appreciate it if you could do the steps below:

The minimum requirement is 128M but I suggest that you increase it to 512M: https://wpml.org/home/minimum-requirements/

You can add this by adding the code below to "wp-config.php" file of your WordPress installation root folder:

/** Memory Limit */
define('WP_MEMORY_LIMIT', '512M');
define( 'WP_MAX_MEMORY_LIMIT', '512M' );

Please add the code above the line below:

/* That's all, stop editing! Happy blogging. */

Thanks.

Hi Romain,

The fact that the issue is happening even on the login screen shows that it might be possible that the issue is even not related to WPML.

The OVH could at least give the error behind the error 500 to know if it was a PHP error or not.

Anyways, I logged in to the website and did a few tests but the issue did not happen.

The best way to go forward is to determine if the issue even happens if you check it on another server.

I can try to copy your website to our server if you allow us (if the website is under 1 GB) and you can do some tests there.

There are two other tests that needs to be checked:

- IMPORTANT STEP! Create a backup of your website. Or better approach will be to test this on a copy/staging version of the website to avoid any disruption of a live website.
- Switch to the default theme such as "TwentyTwenty" by going to "WordPress Dashboard > Appearance > themes".
- Go to "WordPress Dashboard > Plugins" and deactivate all plugins except WPML and its add-ons.
- Check if you can still recreate the issue.

The test above isolates WPML to see if the issue is still there.

The other test is to have the vice versa, that is, deactivating all WPML plugins and having other plugins enabled. See if the same thing happens.

The nature of randomness of the error 500 and the fact that even the login screen sometimes throws the same error makes it necessary to do the tests above to narrow that the issue.

Thanks.