Internal server error - htaccess wrong after saving menu in other language - WPML

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 2 replies, has 1 voice.

Last updated by ericH-23 1 month, 1 week ago.

Author	Posts
February 21, 2025 at 6:35 pm #16734963
ericH-23	Background of the issue: I am working on a site under development and trying to save the menu in a second language. I have added code in my functions.php as per the documentation: https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/#how-can-i-identify-the-plugin-causing-this-and-fix-the-issue. Symptoms: I encounter an internal server error after saving the menu in another language. The language redirects from WPML with the login translation are incorrectly changed in the htaccess file. Questions: Why does saving the menu in a second language cause an internal server error? How can I fix the htaccess file being wrongly changed by WPML?
February 23, 2025 at 3:08 pm #16738110
Christopher Amirian Supporter Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00)	Hi, Welcome to WPML support. I am going to answer his question before the ticket is assigned to one of my colleagues. Could you please follow the steps below to check if the same thing happens on a minimal installation? If no, then follow the steps to identify which plugin or theme causes the problem. - 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. - If not, re-activate your plugins one by one and check the issue each time to find out the plugin that causes the problem.
February 26, 2025 at 1:13 pm #16751090
ericH-23	Hi, Thanks, at the moment this behavior is gone, hopefully it was same cache problem. If this will be occure again, I make a new ticket. Thanks, kind regards Eric