Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter jeffstaf

    (@jeffstaf)

    That is a normal part of upgrading WordPress

    Wait… our host provider reverted our site to a point prior to the upgrade… so I’m having trouble understanding why we’re dealing with upgrade issues when our site was rolled back to a point before the upgrade even came into play.

    It’s likely that your WordPress files are still the current version of WordPress, and are identifying correctly that your database reflects an older version of WordPress.

    Again, how could the WordPress files be the current version of WP if our site was reverted to a point before upgrading WP occurred?

    Thread Starter jeffstaf

    (@jeffstaf)

    Thanks for the feedback, James.

    So the “Database Update Required” page is not in error and we actually really do need to just update our database? And the conflicting version values in db_version and wp_db_version are indicative of this?

    Though why are we being prompted to update the database when our host provider reverted our site to a point where we weren’t being prompted to do so?

    I’m really concerned since I’ve read of other people reverting their site after a failed upgrade, being prompted to update their database and, after clicking the update button, having the front end of their site end up being totally scrambled or just go completely blank.

    We absolutely can’t afford another site outage as we’re in the middle of our biggest fundraising drive of the year… but we desperately need to get back in and update our site’s content.

Viewing 2 replies - 1 through 2 (of 2 total)