[Solved] Database Upgrade Required – a detailed view!
It’s getting frustrated 🙁 After the WordPress upgrade I’m not able to login. It’s redirecting me while trying to login.
It seems something wrong happened with my last WP upgrade.
Database Update Required WordPress has been updated! Before we send you on your way, we have to update your database to the newest version. The update process may take a little while, so please be patient. Update WordPress Database
Yes, of-course there will be an option to upgrade database. I clicked on it and that shows a success message:
Update Complete Your WordPress database has been successfully updated! Continue
Oops.. That’s not helped yet!
It can occurs due to many reasons. Here we goes with some explanations.
It’s not a big deal. You can safely do the changes without the afraid of data loss. It’s a table related problem. In wordpress database, there is table named “WP_Options” which includes some general information related to the blog which appears in the setting tab of admin. We have to check the following things to troubleshoot this.
1, This might be due to the siteURL mistake in WP_Options table.
Site URL in WP_Options table must be populated to the home page of the website.
You can check this from the PhpMyAdmin.
Log into panel >> Click on PhpMyAdmin >> Select the database from left side >> Click on the table "WP_Options" >> Check the siteURL option.
2, Next is important, check the DB version in version.php file. The DB version should be match with the WordPress version installed.
This can also be done from the PhpMyAdmin “WP_Options” table.
Also, you can change this from backend. The “version.php” file is located under:
/** * The WordPress version string * * @global string $wp_version */ $wp_version = '4.2.2'; /** * Holds the WordPress DB revision, increments when changes are made to the WordPress DB schema. * * @global int $wp_db_version */ $wp_db_version = 31535;
The database and db version table:
You can check the updated details from here >> WordPress version and its db version <<
If none of the above helped, please restore the DB from its previous backup.
That’s it, let me know your suggestions on it.