This thread is resolved. Here is a description of the problem and solution.
Problem: You are experiencing an Internal 500 Error when navigating your site in a translated language with WPML Multilingual CMS and WPML String Translation plugins activated. Solution: The issue might be related to your server settings. We recommend creating a copy of your website on another server to test WPML. Additionally, contact your hosting support to explain the problem and check the server error logs. They should be able to assist you further.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 needed, please open a new support ticket at WPML support forum for further assistance.
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 trying to navigate my site in the translated site using the menus. The issue can be seen at hidden link.
Symptoms:
Whenever WPML Multilingual CMS and WPML String Translation plugins are active and I attempt to navigate the site in the translated language, I get an Internal 500 Error: "Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator at webmaster@pamci.info 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."
Questions:
How can I resolve the Internal 500 Error when using WPML plugins?
What steps should I take to troubleshoot the server error related to WPML?
After further investigating, the issue is very likely related to your server settings. To confirm that, you can create a copy of your website on another server and test WPML there.
Please reach out to your hosting support, explain to them the problem and check the server error logs. They'll probably be able to better help you. Let me know if you need anything else from our side after talking to them.
I have reached out to them and they confirm that the issue is not due to server settings:
"We have checked the log and there seem to be multiple errors with the WPML plugin activated on your site pamci.info, We have also fixed the permalink issues with the domain."
The relevant error messages in the error log are as follows:
[25-Oct-2024 11:07:23 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/pamciyrd/public_html/wp-content/plugins/mesmerize-companion/src/Companion.php:611) in /home/pamciyrd/public_html/wp-admin/admin-header.php on line 9
[25-Oct-2024 11:07:23 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/pamciyrd/public_html/wp-content/plugins/mesmerize-companion/src/Companion.php:611) in /home/pamciyrd/public_html/wp-includes/option.php on line 1692
[25-Oct-2024 11:07:23 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/pamciyrd/public_html/wp-content/plugins/mesmerize-companion/src/Companion.php:611) in /home/pamciyrd/public_html/wp-includes/option.php on line 1693
[25-Oct-2024 11:07:25 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/pamciyrd/public_html/wp-content/plugins/mesmerize-companion/src/Companion.php:611) in /home/pamciyrd/public_html/wp-admin/admin-header.php on line 9
[25-Oct-2024 11:07:25 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/pamciyrd/public_html/wp-content/plugins/mesmerize-companion/src/Companion.php:611) in /home/pamciyrd/public_html/wp-includes/option.php on line 1692
[25-Oct-2024 11:07:25 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/pamciyrd/public_html/wp-content/plugins/mesmerize-companion/src/Companion.php:611) in /home/pamciyrd/public_html/wp-includes/option.php on line 1693
[25-Oct-2024 11:07:26 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/pamciyrd/public_html/wp-content/plugins/mesmerize-companion/src/Companion.php:611) in /home/pamciyrd/public_html/wp-admin/admin-header.php on line 9
[25-Oct-2024 11:07:26 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/pamciyrd/public_html/wp-content/plugins/mesmerize-companion/src/Companion.php:611) in /home/pamciyrd/public_html/wp-includes/option.php on line 1692
[25-Oct-2024 11:07:26 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/pamciyrd/public_html/wp-content/plugins/mesmerize-companion/src/Companion.php:611) in /home/pamciyrd/public_html/wp-includes/option.php on line 1693
[25-Oct-2024 12:07:38 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/pamciyrd/public_html/wp-content/plugins/mesmerize-companion/src/Companion.php:611) in /home/pamciyrd/public_html/wp-admin/admin-header.php on line 9
[25-Oct-2024 12:24:45 UTC] PHP Warning: fopen(https://cdn.wpml.org/home/pamciyrd/public_html/pamciyrd_wp141.sql): Failed to open stream: Permission denied in /home/pamciyrd/public_html/wp-content/plugins/wp-staging/Framework/Filesystem/Filesystem.php on line 969
[25-Oct-2024 13:04:23 UTC] PHP Warning: fopen(https://cdn.wpml.org/home/pamciyrd/public_html/pamciyrd_wp141.sql): Failed to open stream: Permission denied in /home/pamciyrd/public_html/wp-content/plugins/wp-staging/Framework/Filesystem/Filesystem.php on line 969
[25-Oct-2024 13:15:06 UTC] PHP Warning: fopen(https://cdn.wpml.org/home/pamciyrd/public_html/pamciyrd_wp141.sql): Failed to open stream: Permission denied in /home/pamciyrd/public_html/wp-content/plugins/wp-staging/Framework/Filesystem/Filesystem.php on line 969
[25-Oct-2024 15:01:19 UTC] PHP Fatal error: Uncaught ArgumentCountError: Too few arguments to function WPML_User_Language::update_user_lang_from_login(), 1 passed in /home/pamciyrd/public_html/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/functions.php on line 17 and exactly 2 expected in /home/pamciyrd/public_html/wp-content/plugins/sitepress-multilingual-cms/classes/user-language/class-wpml-user-language.php:259
Stack trace:
#0 /home/pamciyrd/public_html/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/functions.php(17): WPML_User_Language->update_user_lang_from_login('admin')
#1 /home/pamciyrd/public_html/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/Either.php(207): WPML\FP\{closure}(Array)
#2 /home/pamciyrd/public_html/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/Either.php(257): WPML\FP\Right->map(Object(Closure))
#3 /home/pamciyrd/public_html/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/Promise.php(24): WPML\FP\Right->chain(Object(Closure))
#4 /home/pamciyrd/public_html/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wp/classes/Hooks.php(50): WPML\FP\Promise->resolve(Object(WPML\FP\Right))
#5 /home/pamciyrd/public_html/wp-includes/class-wp-hook.php(324): WPML\LIB\WP\Hooks::WPML\LIB\WP\{closure}('admin')
#6 /home/pamciyrd/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
#7 /home/pamciyrd/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#8 /home/pamciyrd/public_html/autologin-atzalqex.php(11): do_action('wp_login', 'admin')
#9 {main}
thrown in /home/pamciyrd/public_html/wp-content/plugins/sitepress-multilingual-cms/classes/user-language/class-wpml-user-language.php on line 259
[25-Oct-2024 16:12:05 UTC] WordPress database error Got error 'repetition-operator operand invalid' from regexp for query DELETE FROM wpmv_usermeta WHERE meta_key REGEXP '^duplicator_(?!pro_)' made by do_action('wp_ajax_delete-plugin'), WP_Hook->do_action, WP_Hook->apply_filters, wp_ajax_delete_plugin, delete_plugins, uninstall_plugin, include_once('/plugins/duplicator/uninstall.php'), DuplicatorLiteUninstall::uninstall, DuplicatorLiteUninstall::removeSettings, DuplicatorLiteUninstall::deleteUserMetaKeys
[25-Oct-2024 16:12:05 UTC] WordPress database error Got error 'repetition-operator operand invalid' from regexp for query SELECT `option_name` FROM `wpmv_options` WHERE `option_name` REGEXP '^duplicator_(?!pro_)' made by do_action('wp_ajax_delete-plugin'), WP_Hook->do_action, WP_Hook->apply_filters, wp_ajax_delete_plugin, delete_plugins, uninstall_plugin, include_once('/plugins/duplicator/uninstall.php'), DuplicatorLiteUninstall::uninstall, DuplicatorLiteUninstall::removeSettings, DuplicatorLiteUninstall::deleteOptions
[25-Oct-2024 16:12:05 UTC] WordPress database error Got error 'repetition-operator operand invalid' from regexp for query SELECT `option_name` FROM `wpmv_options` WHERE `option_name` REGEXP '^_transient_duplicator_(?!pro_)' made by do_action('wp_ajax_delete-plugin'), WP_Hook->do_action, WP_Hook->apply_filters, wp_ajax_delete_plugin, delete_plugins, uninstall_plugin, include_once('/plugins/duplicator/uninstall.php'), DuplicatorLiteUninstall::uninstall, DuplicatorLiteUninstall::removeSettings, DuplicatorLiteUninstall::deleteTransients
[25-Oct-2024 17:28:25 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/pamciyrd/public_html/wp-content/plugins/mesmerize-companion/src/Companion.php:611) in /home/pamciyrd/public_html/wp-admin/admin-header.php on line 9
[25-Oct-2024 17:29:19 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/pamciyrd/public_html/wp-content/plugins/mesmerize-companion/src/Companion.php:611) in /home/pamciyrd/public_html/wp-admin/admin-header.php on line 9
[25-Oct-2024 17:32:00 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/pamciyrd/public_html/wp-content/plugins/mesmerize-companion/src/Companion.php:611) in /home/pamciyrd/public_html/wp-admin/admin-header.php on line 9
[25-Oct-2024 17:36:03 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/pamciyrd/public_html/wp-content/plugins/mesmerize-companion/src/Companion.php:611) in /home/pamciyrd/public_html/wp-admin/admin-header.php on line 9
[25-Oct-2024 17:43:33 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/pamciyrd/public_html/wp-content/plugins/mesmerize-companion/src/Companion.php:611) in /home/pamciyrd/public_html/wp-admin/admin-header.php on line 9
[25-Oct-2024 17:44:24 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/pamciyrd/public_html/wp-content/plugins/mesmerize-companion/src/Companion.php:611) in /home/pamciyrd/public_html/wp-admin/admin-header.php on line 9
I will get on this right away: I feel I am having too many issues trying to make this plugin work with our chosen theme and maybe this is just not the translation plugin for us. We have multiple users using the site (who are not technosavvy) and we cannot afford to have it crashing everytime we click a link. At the same time I cannot not have a translator (so I can't disable the plugin now), because 99% of the users are a french speaking. I had a similar issue back in May and one of your technicians inserted some code into my theme and that solved the problem that time.
So I'm pretty sure the issue is not server rerlated, but we will give this one last try.
I have been trying to do this migration, without success. The error message I get. Maybe there's omething that I entered incorrectly? (see screenshots).
I was not sure what goes int the http Auth (your message didn't provide for this) and when I tried to access the support link you shared to try and get more info, I just constantly got the black "wheel" while it verified whether I was human or not (see screenshot). I have limited time to actually and the network where I am currently is kind of sketchy.
I gave you credentials to the site, can you initiate the transfer and I will look out for the email?
We have deactivated WPML and the site is working 100% and is Internal 500 Error free.
As I said, it's been a struggle with this translator (for our site) and unfortunately it seems last time your technicians did JUST ENOUGH to make it work for us until it's too late to get a refund! Anyway, we are clearly going to change our theme, because it seems that is where the clash is. The site seems to work fine with other themes.
So I think we are just going to have to work flat-out over the next few days to convert from Highlight theme to Mezmerize which is similar but does not seem to cause issues...
My challenge now is that when I create a staging site (to test the interaction between WPML and Mezmerize) the translator doesn't work because all the WPML translated pages point to pamci.info/fr and not to pamci.info/phoenix/fr is there a way to quickly address this?
New threads created by Lucas Vidal de Andrade and linked to this one are listed below:
About the migration. I already tried creating a copy with the All In One WP Migration plugin, as well as with the Duplicator plugin. I had server errors with both. Furthermore, with Cloudways, we are getting errors, and I'm unable to migrate your website.
Let me make sure I'm following you: does the Mesmerize theme work with WPML flawlessly? In other words, does the 500 error go away, when WPML is active along with the Mesmerize theme?
I'm asking that to check how I should proceed with support, as this issue might also be coming from conflicts.
Please also note that we have an extensive list of themes and plugins that were tested with WPML and work with no issues. The Mesmerize Theme is not in that list. If you're taking the time to address the issue, it's a good opportunity to pick a tool that's WPML compatible:
Hi, we need to do extensive testing to confirm that there are ZERO compatibility issues between WPML and Mesmerize, hence the need to address the staging issue... I will apply the suggested changes , so that we can start that process and confirm definitively.
Unfortunately, the purchase of one of your suggested themes (and the extensive testing for other compatibilities - we have quite a number of other plugins that NEED to work on the site) is not in the budget right now. Mesmerize is the closest approximation to the theme we are currently using (Highlight).
Perhaps we would have planned things different if we had known from the outset that decision regarding the site needs to be tailored to WPML and not the other way round.
So the best course of action is to limp along until next year April and plan our decision regarding our future translator around which one works best with our site, or plan the change of theme to one of your recommended ones then.
Thanks for sharing the details. To provide you with some context, WPML, like other translation plugins, is deeply rooted on the website, as many parts of plugins and themes must pass through WPML to be properly translated. That's why testing and verifying compatibility is so important to us and our users.
"So the best course of action is to limp along until next year April and plan our decision regarding our future translator around which one works best with our site, or plan the change of theme to one of your recommended ones then."
Should we keep troubleshooting the 500 error right now? It's not clear to me.
Changing the theme to Mesmerize didn't resolve the issue. We still received Internal 500 Errors (albeit less frequently). However, changing we realized that selecting the option "Language name added as a parameter (hidden link - French)" resolved the issue completely. We haven't had an Internal error for the last few days. While it is less "pretty", it seems that we are not going resolve the other issue, we'll take functioning over pretty.
chipegoH confirmed that the issue was resolved on 2024-11-01 14:40:22.
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.
