After the “update failed” I tried to inspect what happens in “network”. The system continue to try the “autosave” operation. The result is:
URL: https://www.mulinomontalbano.it/wp-json/wp/v2/pages/1446/autosaves?_locale=user
Stato: —
Sorgente: —
Richiesta
Accept: application/json, */*;q=0.1
Content-Type: application/json
Origin: http://www.mulinomontalbano.it
Referer: http://www.mulinomontalbano.it/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_1) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.0.1 Safari/605.1.15
X-WP-Nonce: 7ef641e640
Risposta
Nessun header di risposta
Parametri string di query
_locale: user
Dati richiesta
Tipo MIME: application/json
Dati richiesta:
Please, the REST API check. It’s really simple, it’s green or red on Health Check’s primary tab.
We need that answer, otherwise I wouldn’t keep repeating it.
I’m getting on a plane now, I’ll check back later, unless someone else does.
REST API availability The REST API is available.
This is the inspection of the error:
Riepilogo
URL: https://www.mulinomontalbano.it/wp-json/wp/v2/pages/1446/autosaves?_locale=user
Stato: —
Sorgente: —
Richiesta
Accept: application/json, */*;q=0.1
Content-Type: application/json
Origin: http://www.mulinomontalbano.it
Referer: http://www.mulinomontalbano.it/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_1) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.0.1 Safari/605.1.15
X-WP-Nonce: 7ef641e640
Risposta
Nessun header di risposta
Parametri string di query
_locale: user
Dati richiesta
Tipo MIME: application/json
Dati richiesta:
And it continue to try to update and continue to return “update failed”. Could be this one?
Risposta (answer)
Nessun header di risposta (no header answer)
OK, something is filtering away headers, it is possible that it is your webserver, custom htaccess entries, a proxy, a plugin or a CDN, there are many potential layers here unfortunately. so you’ll have to test them one by one.
The first thing I would do is reach out to your host and check what they are doing in regards to clearing headers and similar (it’s a common procedure for cache engines, but should not be used in this scenario for example).
Yes ok. But the problem started few days ago. In the moment I updated wordpress to the new release. Before everything was OK. So, the problem is inside the new release. How many of wordpress site are going in trouble with this problem? We can check all the providers but the problem must be solved inside the release. You know what’s the first provider answer? It is not our problem. We are doing nothing.
It’s not good that they replied like that, at all. Without being able to get a proper response it is really hard to find the source of this. The new editing experience does rely on APIs inside of WordPress which we have not used before, which is why you did not experience this before.
I’m checking with the provider. Could be that the same could be also for other wordpress services.
Understood.I’m waiting for the provider answer. It’s femmes to me that it could be tomorrow.
Dears, I’m looking what’s happening but the problem seems to be because the difference between wordpress url (HTTP) and site url (HTTPS). At the moment both are in SSL and the problem seems to be recovered. This difference was irrelevant in previous releases of the product and everything was ok.
Thank you for your cooperation and suggests.
Regards
