I manually pushed them to work - so in short the solutions is not working.
In short when I create a new page automatic translation doesnt do translation for affected langauges, I have to do them manually each time - which is not a good solution and stops us from working normally.
Secondary, when I update the page it pushes the update to all translated content not the affected langagues.
So its just not working at the moment.
When can I expect a resolution?
So we restored couple of databases and files for last couple of months and unfortunately the same problem persists. So it is clearly problem on your end.
I attach the the screenshot from before the update of the WPML as well as core WORDPRESS.
This happened around the end of last week. This proofs that probiem is certainly on your end (databases has been restored to the state from 2 weeks ago, when everything worked well and we get the same problem).
I demand to have it fixed, I have a team of people on hold due to this issue and, we cannot work, we canot restore so we are stuck due to evidently your problem.
You are more then welcome to any changes on the server I have provided you access with. I have full backups and can restore to current point at any time.
Probably the size of the site created the issue for migration, I used your database and files and replicated them on my local site and I can set up the mapping without any issues. So it looks like some site-specific issues which is showing the messages.
As mentioned earlier, can you move the site URL to public which doesn't need host file and contact your server once to see if there is any cache and ask them to disable every cache thing?
Please explain, I do have a production server that get the same message (different server).
I have a vanilla debian severs. The same issue occurs on the live (non /etc/hosts).
Just to clarify - there were no changes made to our end (in production we didnt touch the website for over 1.5 month) and at the end of next week all versions of the server, prod and dev started to show the error [possibly at the same time].
There were no changes to the firewall, webserver, website, server, no upgrades of the code nor the server. One of the restored servers has been restored in the different provider (most of the servers are on vultr but the restored one is on linode).
I don't see any logical reason why that should happened on our end. I tried to disable firewall, memceched, php caching, disabled all the plugins and everything is the same.
Seems this error showed up on all server not on a single one it seems like its the communication with wpml.
This seems to be stuck on your end - possibly changes the codebase or some blockage from our servers to wmpl's.
We will try to change the websever (we use openlitespeed) to nginx and apache and see what happens. Will keep you posted.
