Database upgrade to 5.0

Good morning ????

That doesn’t sound good. As part of the WordPress 5.0 update, the database needs upgrading, and that component is failing. Who is your host? It sounds as if this could be an issue with your site resources – your database shouldn’t timeout during this process.

I got a dedicated server, so I can manually update database if someone write to me the code to launch..

WordPress 5.0 does not have an actual database upgrade.

That particular upgrade screen just checks to see if the Gutenberg plugin is activated, and then it deactivates it if it is. Nothing more.

The db_version setting in the database gets updated to 43764, and that’s pretty much that. End of upgrade.

So, because it is not actually “doing” anything, you should probably figure out why you are getting a timeout. There’s nothing in WordPress that would cause that timeout. So something else is wrong with your server.

Ok, but why am I redirect on this page:
https://www.criticamente.it/wp-admin/upgrade.php?_wp_http_referer=%2Fwp-admin%2Fedit.php

Portal seems regularly upgraded: all pages are reachable and are loading fast… but if i go in admin section, I am redirect there… is there a file to delete?

Same error as above. The site is working fine, but I cannot get into admin. Anytime I try, I’m told the database is already upgraded… and I’m bounced back to the front end. I tried flushing all caches on my host (cloudways.com) to no avail.

Same issue as Edward, above. Cannot get into the dash whatsoever. Flushed caches, cannot get inside to do any actual work at all.

Do you have any security plugins? Can you examine the server logs to see if something is failing?

Clicking that button should take less than a second. It’s not doing any real work, just quick check to deactivate the gutenberg plugin, and then it updates the database with a version number change. That’s it. Not an intensive process or anything.

So the only reason it could be failing would be if something you have outside WordPress is blocking the update button click.

Follow-up: I have Cloudways backup every 6 hours. I restored from that backup, and I’m back up. I’ll add that I had disabled the auto update, and thought I was only updating plugins from the dashboard “update” screen. I had only checked one plugin … but apparently if there is a wordpress update, it does that FIRST (Not what I expected would happen)

After the backup was restored, I updated all the plugins and themes that needed it, then created a staging clone of the site. On the staging site I installed the Classic editor and activated it, checked that all themes and plugins were updated, and then updated to v5.0. This time it worked, and I could still edit my pages. (I have another staging clone that, without the “classic editor” plugin, cannot use my Visual Composer/WP Bakery interface interface) I’m not doing any more today.

From what I understand, the 5.0 update doesn’t even do any database changes … there must be an easy fix for the looping problem, but I’m very grateful I decided to backout with my backup. I’m very lucky no new orders came in before the restore completed.

Otto: I have Wordfence, but when I got the update to work (on my staging site) I didn’t change anything there. Wordfence was not one of the plugins that needed an update.

There was no indication that the [continue] button was failing, but any attempt to go to any admin function ended up at that [continue] screen, then the continue button brought me back (still logged in with the admin bar at the top) to the site home page. There must be some “do once” variable that wasn’t being set. It should never show that screen twice, right?

It should show that screen until you click the button and have it do the update function. After that function has been run, the database version number gets updated, and then it won’t show you that screen anymore.

Same problem here after 5.0 upgrade: stuck at /wp-admin/upgrade.php?_wp_http_referer=%2Fwp-admin%2F

I was using the Wordfence plugin.

Please advise how to solve problem.

Actually, BOTH of my websites are affected by your upgrade bug. The 2nd website I do NOT use any firewall (no Wordfence on it).

So you guys have a major upgrade bug on your hands.

FYI, the host of both websites is 1&1 Ionos.

This doesn’t seem like a bug on our end. It seems like you have a cache interfering that is not letting the button click get to your server.

Clear your caches. All of them. This is standard advice after every upgrade.

ok.

Let’s think…. I have been using WP since 2007. Auto upgrade ever since it was available, and I had even set the flag to auto upgrade before it was a default feature.

Never an issue.

Never “cleared a cache”, nor ever HEARD that in order for AUTO UPGRADE to work that I was supposed to ~MANUALLY~ CLEAR A CACHE/s (!!, yeah, that’s logical….)

So now two of my websites have (at least) a partially failed auto-upgrade install to 5.0 that prevents logging into the dashboard. Other users are reporting the same problem.

But you think there is not a bug. Ok, whatever you say. I guess it is my (and other users) fault that the auto-upgrade failed, even though there is NOTHING NON-STANDARD AT ALL about either of my installations.

I suspect that a lot of low-traffic websites will not discover this bug for quite a while. Had I not tried to log-in to see “what’s up” I would not know (yet) that the upgrade is at least partially failed. The external websites are loading fine, so no obvious sign that anything is amiss.

@otto42,

Besides, I assume that you mean “clear cache” under the assumption that I use some type of WP Cache plugin. I DO NOT.

I have very few plugins, most are disabled when not in use. All I have are WP-DBManager and WP-Optimize and Disable Emojis. The first two are disabled when not in use. And one website has the Wordfence firewall. That’s it. No caches, no other plugins.

So your assumptions are wrong.