Translation saving issues

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

Problem:
The client was experiencing issues with saving and publishing content on their multilingual site, specifically with the Swedish pages and a custom US language setup. The root of the problem was identified as incorrect handling of the root page and server-level redirect rules affecting WordPress REST API requests.
Solution:
We recommended the client to check with their hosting provider to adjust the redirect rules that were converting POST requests into GET requests, which prevented content from being saved. Additionally, we advised setting up a new root page correctly by deleting the existing 'Global' page and creating a new one through WPML > Languages > Create a root page. For detailed guidance on setting up the root page, visit this documentation.

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 further assistance is needed, please open a new support ticket at 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: Exception

This topic contains 23 replies, has 0 voices.

Last updated by sarahI 4 months, 2 weeks ago.

Assisted by: Dražen.

Author	Posts
December 8, 2025 at 8:06 pm #17645298
sarahI	Hi Drazan Yes we set up a custom language for US, I'm not sure if you have access to previous tickets but we did get some advice of how to do this. This is the link to the older post / ticket hidden link We're not that far into any sort of translations so if we need to set up WPML again then thats not an issue We just need default language to be US (not English with UK flag) Andy
December 9, 2025 at 7:23 am #17645883
Dražen Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+02:00)	Hello Andy, Thank you for getting back to me — I understand the process now. I’ll share this with our second-tier team so they can continue investigating. We are still checking, because as you know, everything worked fine a few days ago, and now the same issue has appeared again. It also works correctly on our side and with a copy of your website, so it’s a bit difficult to understand why it only happens on your end. In any case, we’re looking into it further and I’ll update you soon. Regards, Drazen
December 10, 2025 at 7:20 am #17650173
Dražen Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+02:00)	Hello Andy, After investigating, we found that the issue on your server is caused by 301 redirects being applied to WordPress REST API requests. For example, a request like: hidden link is automatically redirected to, notice the last slash hidden link The problem is that the original request is a POST request (used to save page content), but the redirect changes it into a GET request. Because of this, the content cannot be saved. It appears that there are server-level rules enforcing trailing slashes, and these redirects are interfering with REST API calls. If you speak with your hosting provider, they should be able to identify and adjust the redirect rules causing this. You can see the behaviour yourself by opening the first URL in a browser — it automatically redirects. Any redirect will turn a PUT/POST request into a GET request, which is exactly what’s happening when trying to edit and save pages. Regards, Drazen
December 16, 2025 at 3:38 am #17666011
sarahI	Hi Drazen Thanks for the update, I'll take this up with Siteground to see what they think. I may need to check there is nothing on the live website that requires this. I will keep you posted Andy
December 16, 2025 at 7:40 am #17666293
Dražen Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+02:00)	Hello Andy, sure, sounds good. Thanks and kind regards, Drazen
December 16, 2025 at 10:18 am #17666987
sarahI	Hi Drazan I've checked the htaccess on the main site and we've got this in place # Force trailing slash <IfModule mod_rewrite.c> RewriteCond %{REQUEST_URI} /+[^\.]+$ RewriteCond %{REQUEST_URI} !^/wp-json RewriteRule ^(.+[^/])$ %{REQUEST_URI}/ [R=301,L] </IfModule> I'm just getting some advice on whether we can adjust this or have a separate htaccess to disable this on the sub folder. Thanks Andy
December 16, 2025 at 10:47 am #17667158
Dražen Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+02:00)	Hello Andy, I’m not certain whether this was added by your hosting provider or through another server-level configuration. As mentioned earlier, the best approach would be to check this further with your hosting support and clarify any questions with them, including the best way to disable the mentioned redirect on your staging site or live website. Suggesting any change in hosting / server configuration from our side when we are not sure how/why it was added would not be really safe or correct thing to do. Hope you understand. Regards, Dražen
December 16, 2025 at 9:42 pm #17669277
sarahI	Hi Drazan We've amended the htaccess rule in staging5 and also in the /global/ folder on the main folder. I 'think' this has sorted this issue, I can certainly save and publish now. If you wouldn't mind just double checking the staging5 to confirm all expected features are working as they should then hopefully we can finally close this one off. Thanks so much for your help Andy
December 17, 2025 at 7:29 am #17669765
Dražen Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+02:00)	Hello Andy, great, thanks for updating us. I have checked and tried few things / settings and it all looks good to me. I think we can close here. Kind regards and all the best! Drazen
December 17, 2025 at 9:23 pm #17672858
sarahI	Great, thanks for all your help. If we encounter any more issues we will let you know.