I am trying to:fix the problem that translated part is totally crashing with error 500, hosting service support provided me with information that the problem originate from WPML plugin
This error happens every few days even though no changes were made to the site, when that happens translated site is downed, which is Polish versions, English original version still works fine--- Below is from my hosting Support:
Thank you for your patience. I can see that you have had a ticket with ID 4554936 related to this where our seniors have found that the issue is caused by the WPML plugin. I can suggest checking on this issue with the plugin support, or you can also check on this with your developer who will also be able to help configure the plugin correctly in order to avoid these database deadlock that is explained in the ticket
In order to fix the problem I am restoring backups until the next one crash
If this continue I will have to abandon WPML because this is impossible to operate that way, I am losing money and visitors while site is down, I currently have marketing campaigns going on.
Link to a page where the issue can be seen:interlinkjobs.com/pl
I expected to see: no crashes
Instead, I got:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at [no address given] to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
Thank you for contacting the support. And our apologies if WPML is causing the trouble.
However, before proceeding further, may I ask you to try the following?
IMPORTANT: Take full backup of your website and database beforehand. It is highly advised to try the following on a staging/dev site first, so your live website isn't compromised.
- Update WPML to the latest version.
- Enable debugging in your site. See https://wpml.org/documentation/support/debugging-wpml/ for details. So whenever you run into the problem, you'll be able to retrieve error information from /wp-content/debug.log file.
- Deactivate all plugins except WPML and its addons and check for the issue.
- Activate each plugin one-by-one, while keeping check on the issue after a plugin is activated. This way you'll be able to pinpoint a plugin having a conflict (or problem), if any.
- If the problem persists, repeat the above steps with a default theme of WordPress (i.e. 2021 or 2023).
Please let me know your findings, along with the error details and I'll try my best to help you further on the matter.
Thanks for reply, but I did not expect that kind of support from WPML, I think doing what you recommend is pretty logical and I can do it on my own without you telling me that, the problem with your approach is it would take weeks until right plugin is tracked down if this is a plugin issue, I have currently 56 active plugins, 6 of them are WPML, so if I am lucky and doing my own troubleshooting I can maybe find out in few weeks while I copy entire website and everyting to another location, otherwise I dont imagine doing it on live website. Is this your best approach and all you can do?? if thats the case it is hard for me to imagine that I am the only one who has such issue??????????
Since 500 error just points to a server error, while there can be "anything" causing this.
- Enabling debugging and checking error log, gives you detail on the error, so we can save time instead of hitting our heads here and there.
- Checking with WPML plugins only, rules out that if the problem is "really" coming from WPML. Since there are dozens of plugins active, you can't be sure.
--- If there's a conflict coming from another plugin or theme, you may need to check with their support. We can also check if we can provide a temporary workaround.
- We recommend taking backup and/or trying this on a dev site, because this may seriously impact the live site.
I hope this explains what's needed for debugging/investigating a problem.
I can enable debugging and check for the error details. But please be informed that due to a live site, we aren't allowed to perform any other debugging steps ourselves.
If you agree, I request temporary access (WP-Admin and FTP), preferably to a test site where the problem has been replicated.
Your next answer will be private, to share this information safely.
Also provide detailed steps to reproduce the issue and links to pages in admin and on frontend.
IMPORTANT: Please take a complete backup of the site to avoid data loss. I may need to activate/deactivate plugins also.