Database Upgrade Required: Not Working (WP 2.9)

When trying to access the wp-admin i get redirected to the ‘Database Upgrade Required’ page. After clicking the button i get ‘Upgrade Complete’ and then it just loops back to the ‘Database Upgrade Required’ page.

So i cant access to wp-admin area.

i tried this
https://www.clickonf5.org/wordpress/solution-database-upgrade-required/2247

and i repeared all tables but still not loading admin area.

Evidently some of you have many, many options, which is very unusual. The query that deletes duplicates during upgrade choked on so many options. miqrogroove came up with a better query in this ticket. If you haven’t yet worked around the problem, try the latest 2.9.1 build and let us know if that helps. If you already worked around the problem, you can install the new build, set your db_version option to 11556 (using the methods linked to earlier in this thread), and upgrade again. You will probably get some warnings about duplicate indexes or the like, but the upgrade should run to completion just fine. The good news is that if you had enough duplicate options to break the original query, your blog will likely run a bit faster once it is freed of the burden of those dupes.

Hi Ryan,

Looking good.

I first installed the WordPress Beta Tester Plug-in: https://www.ads-software.com/extend/plugins/wordpress-beta-tester/

I then set /wp-admin/tools.php?page=wp_beta_tester to “Point release nightlies”.

I then ran https://www.war59312.com/wp-admin/update-core.php and upgraded to 2.9.1 beta 1.

I then changed the Option_Value for the Option_Name db_version back to ‘11548’ instead of ‘12329’ via myphpadmin.

Lastly I ran /wp-admin/upgrade.php and it successfully upgraded my blog. ??

So indeed, looks like the change worked. ??

Thanks,

Will

PS: Now if only https://www.war59312.com/wp-admin/update-core.php would stop saying “new version of WordPress available for upgrade” when 2.9.1 beta 1 is already installed.

> stop saying “new version of WordPress available

There’s a plugin for that too ^_^

Once you’re on the beta track the upgrade notice will always show because there are new versions available multiple times a day as changes are committed. Once you upgrade to the final version of 2.9.1 when it becomes available, the notice will disappear.

I thought the trunk track only pushed nightlies, not every single commit.

Hello To All,
As I’ve voiced it, WordPress is at times, ‘change for the sake of change’. Numerous feature are being tucked in, with not enough testing before release. When does WordPress, once again become a stable version for more then a few weeks! Used version 2.3.3, and most of it’s convinces were taken out. So I held off as long as I could. Did post my battles with prior upgrading.
In that some newer themes were wanted by me, with great trepidations, did again upgrade to ver 2.9.
This time all went well.
Ah though, accessing my multi-blog sites for posting is still a clumbsy awkward process. Don’t misunderstand me here, WordPress is a fantastic free platform, but sheesh, how I long for the ver 2.3.3 layout, and dashboard.
The new theme, Atahualpa is the reason why I finally upgraded. Much to still learn with this new theme and the recent WP upgrade.
I venture to say, I will eventually get used to how the crowded the new version is, and quite dreaming how accessable version 2.3.3 was.

https://thetalker.org/

Ryan, indeed that makes since but the instance you upgrade it still says there is a new version, even when there is not. Of course not, because you just installed the latest.

So perhaps do a real check?

miqrogroove, indeed been using https://lud.icro.us/disable-wordpress-core-update/ since October 1st, 2007 . Notice the first comment, that is me. he-he

And on a related note (I guess), that when using a .maintenance it displays “An automated WordPress update has failed to complete – please attempt the update again now.”

Would be nice if that could be fixed. ??

I don’t think .maintenance is intended to be used by webmasters. It’s an internal flag. A proper maintenance mode needs to override .htaccess in most situations.

Well I was using https://www.ads-software.com/extend/plugins/maintenance-mode/ but it now causes massive CPU and RAM usage.