[wp-trac] [WordPress Trac] #16156: update-core is oblivious to api.wp.org being unreachable
WordPress Trac
wp-trac at lists.automattic.com
Mon Apr 4 06:19:38 UTC 2011
#16156: update-core is oblivious to api.wp.org being unreachable
-------------------------------------------------+-------------------------
Reporter: nacin | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Future
Component: Upgrade/Install | Release
Severity: normal | Version:
Keywords: has-patch needs-testing dev- | Resolution:
feedback 3.2-early |
-------------------------------------------------+-------------------------
Comment (by solarissmoke):
> I had independently started on this, and changed it based on a
"last_successful" field instead, and displaying a message if the last
successful update check was >24hrs ago.
This sounds like a good idea.
> Perhaps we need some goals here on what the user should be shown when an
update fails to decide which line of attack is used here?
Currently, there is no way to force an update check - you have to wait
till the `update_core` transient expires (or delete it manually). And
anyway, the transient doesn't store the last successful check, so it could
have been ages and you wouldn't know. The "Last checked on... " message
just prints the current time and is totally misleading.
I propose something like this for `update-core.php`:
- Display the last successful check time (by implementing a
`last_successful` value).
- If the last check offered no updates, present the option for the admin
to check again now (possibly with some restriction on doing this too
frequently)
- If they choose to check again now, and the check fails, then we tell
them it failed and why (and offer to try again). Otherwise we update the
results accordingly.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/16156#comment:15>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list