AutoUpdate tool ruined or delusional?

I don’t want to rub salt into the wound (see SiteGround AutoUpdate tool ruined), but this post will be about the SiteGround AutoUpdate tool yet again. After deciding not to trust this tool anymore, I thought I was done with it (even though I could not opt-out). However, a little technical hitch brought me back to Site Tools > WordPress > Autoupdate. AutoUpdate, the last dance!

SiteGround logo with a referral link to their website
Referral Link

From an error…

First thing first, let me clear SiteGround tool of the aforementioned technical issue. The latter was most probably due to corrupted files in the browser cache or problems with expired/corrupted browser cookies1. In fact, the dysfunction occurred right after I updated WordPress manually.

Bad Request
Your browser sent a request that this server could not understand. Size of a request header field exceeds server limit

I could not access the Network Admin dashboard of my Multisite installation anymore (via the My Sites link); every time I had the above error message. To make a long story short, after trying the various fixes1 for a 400 Bad Request Error, I thought (erroneously2) that something went wrong during the manual update (see above) and I wanted to restore my WordPress installation to a previous version. Before to head toward the automatic daily backup option (not the SiteGround backup tool, obviously), I doubled check whether I could use the restore feature of the AutoUpdate tool or not.

Still believing erroneously that there was something wrong with my current version of WordPress (i.e. WordPress 5.7), I felt relieved to see that the tool was showing a nice and big UPDATE SCHEDULED. Surprisingly, the available WordPress version was not mentioned; granted, this was better than the previous “WordPress unknown now available” (see SiteGround New Client Area and Site Tools – part 10). In despair, I hit the UPDATE NOW button, well aware there was no new version anyway (other than WordPress 5.7 already installed)…

Unbelievably, the tool “updated” my installation back to the previous version (i.e. WordPress 5.6.2).

… to a diagnostic

Delusion3
An idiosyncratic belief or impression maintained despite being contradicted by reality or rational argument.
AutoUpdateWordPress

Status: UP TO DATE
Current version: WordPress 5.6.2

WordPress 5.7 is available! Please update now.

In reality, the current version was indeed WordPress 5.7 (since March 9, 2021). Accordingly, after the tool “updated” my installation based on its delusional belief, my WordPress was no more up-to-date!

I ended up doing the manual update toward WordPress 5.7 one more time (see SiteGround AutoUpdate tool ruined) and the tool put back the same delusional message!

UPDATE SCHEDULED


1 Matteo Duò (2019) How to Fix a 400 Bad Request Error [Causes and Fixes]. Kinsta. ^
2 Without feeling sorry for myself further, I have barely any “CogitActive” time since last summer (see 100th post – a bittersweet celebration!) and I am far to get back to normal. Given this situation, and the unavoidable exhaustion resulting from it, I forget to change the time range before to clear my browsing data (i.e. it was not long enough). An oversight that leads to the mishap reported in this post. ^
3 Delusion (2010) Oxford Dictionary of English – Third Edition. Oxford University Press. ^

What do you think?
  • Like 
  • Agree 
  • Disagree 
  • Thank you