When I use the InfiniteWP management software to update WP, the update fails with "Localization mismatch" on 9 out of 16 websites that use WPML. It doesn't happen on sites without WPML and doesn't happen when I update directly in the WP dashboard.
I also had this back in 2019 and that somehow was resolved. The issue came back with the update to WP 6.3 running the latest WPML version. Then I updated them from the WP dashboard but when I update to 6.3.1. it happens again.
I had a closer look at the WP language and the WPML configuration to see if I could find a pattern in the sites that did / did not result in the error. I did notice one thing, but changing that did not fix the problem (see attachment).
Do you have any idea what the cause could be, and if not, suggestions on what I can do to try and further investigate?
PS, the selected site is just one of the sites with the issue. See attachment for a complete overview.
I would be glad to help and advise further, but to be honest, I am not aware of this plugin nor what might be causing it. As the error says, I would suggest trying what you have already tried, matching the locale of your default language with the locale of the WP instance, in this case, en_US.
The best I can advise is to contact InfiniteWP and check with them what the error message represents, and what is causing it. Or what might be wrong with the language locale that is causing it to fail to update?
They are also free to contact us via the GoGlobal program and we would be glad to help.
Let me know how it goes and if there is anything else I can do to help.
What I tried had worked after all. I think there may have been some caching involved when it didn't work at first.
This is what I had
- In WP settings it said English US, which is the default language after installing WP.
- In the WPML language settings the default local for English was en_US.
- But in the wp_content\language folder, I only had en_GB translation files.
So I figured that according to the settings, WP was using US English, but somehow for translations and the update it used GB English causing a clash.
So in WPML I changed the default local for English to en_GB.
Then I cleared all caches, including the one from InfiniteWP.
And then the update succeeded.
I think there is still something strange though.
If the default language in WPML is set to Dutch, why does it not show Dutch as the default site language in the WPML settings?
it is correct, the one from WP Settings > Site Language shows the language set for your user from the user profile, which you can change from the Edit profile page.
That's not true. The language in my user profile has noting to do with it and it even is a different one. See attached.
My point is that the site language in WP should be the same as the default language in WPML. The whole issue in this ticket is caused by these two being different.
So if you change the default language is WPML, it should change the site language in the WP settings accordingly.
That is how it works now, I am sharing a video of this from the test site:
- hidden link
If it doesn't work for you like, it could be that something else is altering it. If you think this should have different behavior and be the same as WPML > Default language, I can further escalate to the 2nd tier to check and advise.
Yes please escalate, because that absolutely doesn't make any sense at all.
The WP settings language is the default SITE language for everything on the front end and there is onlye one such setting.
The WP user settings are for everything on the backend, depending on the language in which each user prefers to work with WP. There could be 5 different users in WP all having a different language. So that clashes with the single wp site language setting.
There is a single WPML default site language and a single WP defailt site language and they should be mapped to each other. User languages shouldn't have anything to do with that at all.
I am in the Netherlands, so default WP Site language is always Dutch. However, I prefer to work with WP in US English, because the standard language of themes and plugins is usually English, to get support you need their English terminology and they are often automatically (and badly) translated to Dutch.
So, I work in English, but the default site language has to stay in Dutch, it should never change to my user language.
New threads created by Dražen and linked to this one are listed below:
