[wp-testers] WordPress 2.5.1 is available! Please update now message returns after upgrade

[Alexander Beutl]

try the option with the name "update_core" (can not test this now - but
would be my best bet)

2008/4/28 headsetoptions.org <headsetop at yahoo.com>:

> I understand that, I am trying to figure what in this table was causing
> the version update from going through?
>
> Alexander Beutl <xel at netgra.de> wrote: >
> > I did manage to fix it by dropping the wp_options table in the database
> > and recreating one with the new install.
> > Not sure if that is the right way to do it but it did the job.
>
>
> Since the options table is used for storing many sorts of things (like
> Pluginsettings, maybe templatesettings and stuff) I wouldn't recommend
> this
> strategy in most cases and for most users.
>
> 2008/4/28 headsetoptions.org :
>
> >
> > These sites were originally updated on the 25th, the day 2.5.1 was
> > released.
> > I did manage to fix it by dropping the wp_options table in the database
> > and recreating one with the new install.
> > Not sure if that is the right way to do it but it did the job.
> >
> > Sunny
> >
> > DD32 wrote:
> > > The update check service is only run ~3 times a day.
> > > So if you upgrade, it'll still remember the old alert after the
> > > upgrade, and will continue showing it until it checks the update
> >  check
> > > service again.
> >
> >
> > "Aaron D. Campbell"  wrote: Is there a reason this
> > process isn't run on upgrade? (Isn't there a
> > database upgrade between 2.5 and 2.5.1? If so, couldn't we run the
> > update check service then?  It wouldn't always fix the issue, but
> > sometimes it would.)
> >
> > DD32 wrote:
> > > The update check service is only run ~3 times a day.
> > > So if you upgrade, it'll still remember the old alert after the
> > > upgrade, and will continue showing it until it checks the update check
> > > service again.
> > >
> > > On Mon, 28 Apr 2008 13:10:05 +1000, headsetoptions.org
> > >  wrote:
> > >
> > >> One of my clients site was upgraded to WP 2.5.1 from 2.5, however,
> > >> the message in dashboard reappears once the upgrade is done. We used
> > >> FTP initially to replace the WP files, then a plugin (WAUP), neither
> > >> worked. Is it a bug or is there something fundamentally wrong with
> > >> the way we are handling the upgrade. The FTP method worked when I
> > >> upgraded my personal site.
> > >>
> > >> Sunny
> > _______________________________________________
> > wp-testers mailing list
> > wp-testers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-testers
> >
> >
> >
> > http://www.headsetoptions.org
> > http://www.mandarinmusing.com
> >
> > ---------------------------------
> > Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try
> it
> > now.
> > _______________________________________________
> > wp-testers mailing list
> > wp-testers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-testers
> >
> _______________________________________________
> wp-testers mailing list
> wp-testers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-testers
>
>
>
> http://www.headsetoptions.org
> http://www.mandarinmusing.com
>
> ---------------------------------
> Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try it
> now.
> _______________________________________________
> wp-testers mailing list
> wp-testers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-testers
>