[wp-trac] Re: [WordPress Trac] #1476: WordPress Update Notification

[WordPress Trac]

#1476: WordPress Update Notification
----------------------------+-----------------------------------------------
 Reporter:  mdawaffe        |        Owner:  rob1n   
     Type:  enhancement     |       Status:  assigned
 Priority:  normal          |    Milestone:  2.3     
Component:  Administration  |      Version:  2.1     
 Severity:  normal          |   Resolution:          
 Keywords:  update upgrade  |  
----------------------------+-----------------------------------------------
Comment (by westi):

 Replying to [comment:17 rob1n]:
 > A "script."
 >
 >  * WP: Load Dashboard, makes AJAX call to rpc.wordpress.org (or
 whatever). Could be run through another local PHP file to cache it in the
 DB, but I don't think it's needed. The request has GET or POST variables
 (probably GET) such as current, which has the current version.
 >


 I think AJAX to local php file is better to allow check to be cached as we
 don't want every WordPress install hitting rpc.wordpress.org for every
 dashboard load.


 >  * RPC: Compare $_GET['current'] with the current version, most likely
 using PHP's version_compare() (if we do the RPC in PHP). If it's fine,
 then return an XML response with <status>0</status> or something. If it's
 not up to date, then <status>1</status> <latest>2.3.1</latest>
 <type>critical/major/minor</type>.
 >


 RPC should just be flat text files if possible spread the computational
 load of all the many remote requests onto the server making the request so
 as to not overload rpc.wordpress.org with too much work.

 Using a REST api such as : http://rpc.wordpress.org/update/1.0/wordpress-
 version to make the request which can then return some data:
  1. latest relevant version number for this branch (2.0 or 2.2)
  1. update type.
  1. link to blog posting.


 >  * WP: Use JS magic to parse the XML response (I know this is doable
 somehow). Based on what's returned, show an i18ned message in the
 Dashboard alerting the user to such, and provide a download link to
 http://wp.org/latest.tar.gz and http://wp.org/latest.zip
 >


 Parse the response in PHP and cache it so that you only check every 15
 mins at most.


 Some other comments:

  1. Consider making this update info available on more than just the
 dashboard - some  people will not necessarily visit the dashboard very
 often - if they did they would already see the blog posts!
  1. This feature must be auto disabled for private blogs to enforce their
 privacy.
  1. We need to consider which users should trigger the check and get it
 displayed to them.
  1. Provide a hook that is fired when a new message is detected to allow
 plugins to do things at this time.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/1476#comment:20>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software