Hmm..
It IS supposed to be reset upon the version changing.
On Mon, 28 Apr 2008 15:17:13 +1000, DD32 <[EMAIL PROTECTED]> wrote:
I was just thinking clearing the update check on upgrade would be a good
way to do it, But That'd requre changing the version it checks on
everytime.
Alternativly, The update checker could expire the saved data is the
WordPress version changes too (Instead of just basing it on time as it
currently does)_
On Mon, 28 Apr 2008 15:15:06 +1000, Aaron D. Campbell <[EMAIL PROTECTED]>
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
<[EMAIL PROTECTED]> 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
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
