Database Update Required after upgrading to 4.2.2

Hello, Tanya, & welcome to the WordPress support forum.

Firstly, because you gave the url to your site, it really helped in quickly pointing out a few possible problem areas.

The first thing that jumps out at me is that you’ve got some sort of custom login going on. So, whereas I could not log in by means of the wp-admin path, if I knew the credentials, it looks as though I’d be able to do so using https://netballscoop.com/wp-login.php

Please rename your theme folder, & please rename the plugins folder to disable plugins until we get this sorted. Renaming the theme folder will break the front end of your site–be advised & forewarned.

Now please try logging in using wp-login.php & change the theme to a default WordPress theme such as 2015. Next, please exit & try logging in using wp-admin & click the ‘Update Database’ link. Please let us know how that goes.

Lastly, if that didn’t work, then we may need to explore server error logs &/or do a database export/repair. It therefore might help, in terms of giving specific instructions, if we knew who you’re hosting with.

Please keep in touch.

Hi Jackie, thanks for your assistance.

Yes, I am using Restrict Content Pro as a custom login.

I renamed my theme folder and plugins folder, then logged in using https://netballscoop.com/wp-login.php. I hit the “Update Database” link, but once gain I received an internal server error.

My website is hosted with Media Temple.

Tanya, do you have SSH access w/Media Temple? If not, I’d suggest you contact them & ask them do export it using sql commands as opposed to PHPMyAdmin. PHPMyadmin’s cool, but it can have trouble w/large databases.

Hi Jackie,

Yes, I’m pretty sure I have SSH access. However, they will not do the import for me as it “isn’t within the scope” of their support.

What is your hosting package, Tanya? It looks like SSH only comes w/certain packages. I’d really like to make very certain we have a complete & valid backup of the database before proceeding w/anything. Since it appears PHPMyAdmin is choking on it, then our next option is SSH, but we need to be very sure it comes w/your package. For example, I personally do web hosting. SSH is not enabled by default, because, frankly, there are a lot of folks who wouldn’t know what to do w/a command prompt if it walked up, said “hi”, & shook their hand. That’s understandable, but because it can be so powerful, it is disabled by default. Clients have to ask to have it enabled.

So–could you just please ease my mind & let me know for sure we have this at our disposal? Otherwise, it’s time to consider plan C–& I’m not entirely sure I like plan C.

I’m got Dedicated Virtual Server Level 1.

I’m emailing a support request just to make double sure I have access to SSH.

Ok, I have a reply:

Thank you for contacting (mt) Media Temple!

By default, you should have SSH access via your root user unless you disabled it.

Well, then I’m going to assume you didn’t disable it, understanding full well the proviso of what happens when you assume. Gulp!

So here’s what let’s do.

If you use windows, you’re going to need to downoad an ssh client. There are quite a few–I happen to like Putty, which is available at:
https://www.chiark.greenend.org.uk/~sgtatham/putty/
in either an instaler or portable distribution. Conversely, you can use Google or Media Temple’s knowledgebase for other recommendations.

If you use a Mac, you can actually use the provided terminal program.

When you open your SSH client, you’ll need to provide it w/the hostname (likely your domain name), your username, & your password. These are probably the same as your CPanel credentials.

Once you’ve successfully SSH’d into your server, please go to the directory where you want your database to be dumped. The command is cd/dirname. Or you can juststay in the default folder.

To dump the database, the command is:
mysqldump –username yourdatabaseusername –password yourdatabasepassword databasename > dbfilename.sql
(any name after the > sign is fine). Databasename is the name of your WordPress database, & you can find it in your wp-config.php file if you don’t recall it.

Once the database has been backed up, then might I suggest that you log into your CPanel, go to SQL Databases, choose your WordPress database, & then choose to check it. If there appears to be a problem following the check, then choose the ‘Repair’ instead of the ‘Check Database’ option.

Let us know how that goes, won’t you, Tanya?

@tanya I think this could help to you:

How to stop – Database Update Required – loop

Is an error in the core, so you have to update a file to fix it.

@gabrielperezs my client also uses (mt) Media Temple as their host and so I’m in the same situation as Tanya with this error. Thank you for the explanation of the loop being a bug in the update code itself.

I’m not a programmer by any means, just trying to help resolve this issue on the website I help with. My question is where inside my website’s folders do I put the file you provided in the link?

By the way, the front end of the website is working just fine. https://momitforward.com/

amesDHC, welcome to the WordPress support forums. Actually, the powers that be request you start your own topic, per forum guidelines at https://codex.www.ads-software.com/Forum_Welcome#Welcome_to_the_WordPress_Support_Forum

Having said that, though, I should’ve posted how I resolved this for the benefit both of those in the support forum who may encounter this in the future, as well as for those, like yourself, who are searching for just such information.

If this does not help, however, or if you don’t know how to perform the steps outlined here, then please do as the forum guidelines request & start your own topic.

Thank you.

The problem was that there was an incompatibility between the database version & the version listed in wp-includes/version.php.

The first thing to do is to go into PHPMyAdmin or use the command line to obtain the database version the WordPress install is currently using. The next step, once that’s done, is to edit wp-includes/version.php, specifically:
$wp_db_version = 123456;

Obviously, that last number is a placeholder representing the version number. Simply substitute the version number of the file for the one which you obtained from the database, save it, & you should be good to go.

Again, please start your own topic if anything needs additional clarification.

Thank you and my apologies.

perdi tudinho! tks por nada!