[wp-testers] Keeping Up-to-date [s]

[Rob]

John Ha [c] wrote:
> Hi,
>  
> I've implemented a version checking hack for the next release of my 
> plugins (kca & kin). Here's how I've done it:
>  
> I have a file with just the following code:
>  
> echo preg_replace('/^[\s\S]*kin-(\d\.\d\.\d)[\s\S]*$/', '$1', 
> @file_get_contents('http://svn.wp-plugins.org/kin/tags/'));
>  
> What this code does is read the page 
> http://svn.wp-plugins.org/kin/tags/. This page contains the the 
> directory to latest version of my plugin Eg. kin-1.0.0. It then does a 
> regexp to extract the version number. Finally it echos the results.
>  
> The next part just involves using some ajax to get the results 
> from that file (this will overcome the security limitation of reading 
> a page from another domain using xmlhttp). Ajax is used for background 
> loading to reduce wait time for plugin load.
>  
> Finally it's just a case of comparing the results (in this case the 
> version number from svn repos) with the current user plugin version.
>  
> That's my solution to plugin version checking. Not the most graceful 
> method, but little code is involved, no need to update any version 
> files, no server, quite safe and it works for me.
>  
> John Ha

Please don't rely on allow_url_fopen being open, Wordpress includes 
Snoopy for a reason :)

-- 
Rob Miller
http://robm.me.uk/ | http://kantian.co.uk/