Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client needs to rebuild the permalinks after each plugin update to avoid a 500 error on their website.
Solution:
We recommend checking if the issue is related to the known problem described here: https://wpml.org/errata/htaccess-is-rewritten-with-language-folder/. If it is, the issue may not be directly caused by WPML but by another plugin that is not interacting correctly with WPML, leading to the htaccess file being incorrectly rewritten. Applying the fix provided in the link should resolve the issue.

If the solution provided is not relevant to your case, because it's outdated or simply doesn't apply to your situation, we encourage you to open a new support ticket. We also 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 further assistance is needed, please contact us in the WPML support forum.

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.

Tagged: 

This topic contains 1 reply, has 2 voices.

Last updated by Alejandro 1 year, 5 months ago.

Assisted by: Alejandro.

Author Posts
February 12, 2024 at 10:43 am #15292256

Bendimered Lotfi

Hi,

On my website boutiquehotstore.be I need to rebuild the permalinks after each plugin update. Otherwise I get a 500 error. This is annoying especially since the worpdress do some automatic update and thus I can't always re-save the permalinks quickly enough.

February 12, 2024 at 2:09 pm #15293505

Alejandro
WPML Supporter since 02/2018

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+02:00)

Hello!

Can you please check if your problem is this one: https://wpml.org/errata/htaccess-is-rewritten-with-language-folder/

If you apply the proposed fix there, then please know that this problem is not happening because of WPML itself but because another plugin is doing something that should not be doing or it's doing it in an improper way and as a result, the code gets localized by WPML and the problem appears.

Try it out and let me know how it goes.