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.
This topic contains 8 replies, has 3 voices.
Last updated by Nigel 1 year, 11 months ago.
Assisted by: Nigel.
Author | Posts |
---|---|
July 25, 2023 at 12:21 pm #14096271 | |
celineM-6 |
the issue is on staging environment of Sifawy Link to a page where the issue can be seen: hidden link I expected to see: the Arabic version of the website Instead, I got: HTTP Error 500 But when I set the Language URL format to "Language name added as a parameter" it works fine |
July 25, 2023 at 12:32 pm #14096371 | |
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. Usually, the 500 errors (Internal Server Errors) are related to the server configuration or server limitations being reached. You can check our documentation to see if you meet all the WPML minimum requirements here: https://wpml.org/home/minimum-requirements/ Also, please take a look here: You can also activate WordPress debug to find out more about what is actually happening when you receive that 500 error: I hope that you will find this information helpful. Please let us know how things go. Mihai Apetrei |
July 26, 2023 at 10:13 am #14102257 | |
celineM-6 |
Hi There, |
July 26, 2023 at 11:16 am #14102947 | |
Nigel WPML Supporter since 02/2016 Timezone: Europe/Madrid (GMT+02:00) |
Hello, let me take over here. When there is a 500 error it means that a fatal error occurred on the server. We need to see details of the error to try and understand why it happened. If you edited your wp-config.php file as described in https://wpml.org/documentation/support/debugging-wpml/ then when you try again to change to languages in directories and it creates a 500 error, you should be able to see details of the error in the file wp-content/debug.log. You can paste those details in your next reply, or you could share the debug.log file itself via dropbox or wetransfer or similar, just paste the link in here. |
July 26, 2023 at 11:23 am #14102963 | |
celineM-6 |
Here are the content of debug.log file |
July 26, 2023 at 1:41 pm #14104471 | |
Nigel WPML Supporter since 02/2016 Timezone: Europe/Madrid (GMT+02:00) |
Thank you for that. I can follow what causes the error in a narrow sense, but not in a broader sense of what prompts it to occur. Looking at your site debug info you shared, your WP Memory Limit appears too low—below the minimum requirements shared with you earlier. Did you raise the memory limit since submitting the debug info? See this link for how to increase the memory limit; I would recommend similar settings for the WP_MEMORY_LIMIT and WP_MAX_MEMORY_LIMIT constants as in the example below. |
July 31, 2023 at 8:46 am #14124873 | |
celineM-6 |
Hi Nigel, as I mentioned before that I checked the requirements before and the error still there including the memory limit |
July 31, 2023 at 11:14 am #14126281 | |
Nigel WPML Supporter since 02/2016 Timezone: Europe/Madrid (GMT+02:00) |
OK, thanks for confirming. (The debug info you submitted shows different values memory but that can sometimes be inaccurate.) To debug further I'll need to take a closer look at your site, if that's okay. As this is a staging site is it okay for me to run some tests, including deactivating and reactivating plugins and possibly install utility plugins to help diagnose the problem? If that proves inconclusive, I may need to copy your site to work on locally. Would that be okay? If so, please share credentials in the private reply I've set for you. You may want to create a temporary admin user for me that you can later delete, and be sure to have a backup. |
July 31, 2023 at 3:28 pm #14128567 | |
Nigel WPML Supporter since 02/2016 Timezone: Europe/Madrid (GMT+02:00) |
Thanks for that. I deactivated all other plugins, activated WPML, and switched the language setting to use directories, to have a starting point to check WPML in isolation. It appeared to be working fine, both on the back end and front end, no errors affecting the site. So I gradually reactivated all of the other plugins that I had deactivated, and in the end I was able to reactivate all of them, again without creating any errors. So now the site appears to be in the same state as when you shared it with me, without triggering the errors. I'm not sure what would have responsible, as I don't seem to be able to reproduce them. (The one thing I did see is that for some reason the wp-content/languages/wpml directory has had its permissions set to read-only, while it should be read-and-write. See the screenshot I took, using the Filester plugin to browse your files. That should be fixed, which you should be able to do using an FTP client, or you can ask your host to fix.) |