Background of the issue:
I am trying to update the WPML Multilingual CMS plugin to the latest version. After installing and activating the plugin, the version does not update. The dashboard still shows the old version (4.5.12) even though the newest available version is 4.8.5. No errors appear during installation. The update seems to complete, but the version number stays the same and the plugin behaves as if it never updated. Link to a page where the issue can be seen: hidden link
Symptoms:
The plugin remains on version 4.5.12 after installation and activation, despite expecting it to update to version 4.8.5.
Questions:
Why does the plugin version not update after installation?
How can I ensure the plugin updates to the latest version?
I have managed to update with clean installs.
But now, I am getting a repeated 404 error in the browser console coming from the WPML “Account / Installer” dashboard.
Error in console:
GET hidden link 404 (Not Found)
frame_ant.js:2 window.fetch
frame_ant.js:2 xf
frame_ant.js:2 kf
dashboard.js?ver=485900:2 value
...
admin.php?page=otgs-installer-support:2133
Problem:
WPML is trying to load a localization file for Slovenian (sl.json) that does not exist on your server, which results in a 404 on every admin page where the WPML Installer / Account dashboard runs.
What I need clarified:
Why is WPML requesting hidden link
when there is no Slovenian localization available?
Is this expected behavior or a missing file on the WPML side?
Can you provide the missing sl.json file or correct the request so the dashboard stops producing 404 errors?
This error occurs even when all WPML plugins are up to date.
Environment details:
WordPress version: 6.8.3
PHP version: 8.2
WPML Multilingual CMS: latest
WPML String Translation: latest
Browser: Chrome (also reproducible on others)
Please advise how to resolve this or if this is something that needs to be fixed on the WPML server side.
Thank you.
New threads created by Andrey and linked to this one are listed below:
I’m glad to hear that you were able to update the plugins. Since the new issue appears to be unrelated, I’ve created a separate support ticket to keep everything organized. I will continue assisting you here: