plugin/theme update check fixes
|Reported by:||DD32||Owned by:|
I just noticed that the plugins update check was being run on every request to the plugins page, Because the list of plugins that were being sent to the API server was never fully complete, if a plugin was detected that had changed in position 5 (of say 30 plugins), only the first 5 plugins were being checked for an update. (Thats the changes to the location of the break in the loops, Might be an idea to apply that to the 2.7 branch as well?)
In adition, I've streamlined a bit more of the code, It now checks every hour if the user visits the admin page for themes or plugins, or updates every 12 hours otherwise. This wont be a problem for most situations, And helps users who are visiting the plugins page since they know theres an update thats just been released.
The patch also removes header fields which are taken care of by the HTTP API, as well as using the specific _post() or _get() functions instead of the generic _request() (Which defaults to _get())
Finally, The themes update check is run on the themes & update page loads to bring it into line with the plugins update check.
Change History (17)
- Milestone changed from 2.8 to 2.7.1
- Resolution fixed deleted
- Status changed from closed to reopened
- Milestone changed from 2.7.1 to 2.8
- Resolution set to fixed
- Status changed from reopened to closed