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

Sun Jan 22 18:26:09 GMT 2006

Agreed. I think your approach is actually superior... for those using  
the SVN. :)

On Jan 22, 2006, at 1:20 PM, John Ha [c] wrote:

> Yes, I thought about making a separate text file or setting up a  
> server, but I'm pretty lazy and forgetful. That's why I opted for  
> reading the svn directory, since I will have the latest version  
> there anyway. This way I don't have to worry about updating the  
> version number in one extra file. Version check is pretty much  
> automatic as long as I use the svn. I also like to keep my plugins  
> as self contained / self-reliant as possible. This technique allows  
> for that.
>
> John Ha
> ----- Original Message -----
> From: Chris Meller
> To: wp-testers at lists.automattic.com
> Sent: Monday, 23 January 2006 4:55 AM
> Subject: Re: [wp-testers] Keeping Up-to-date
>
> That's what my Plugin Update Server plugin does. Instead of using a  
> hard-coded text file, it simply stores everything as a Wordpress  
> option, allowing you to manage everything from your Admin pages.
>
> In a great moment of irony, I realized a day or two later that I'd  
> implemented pretty much exactly the same thing K2 used... Mine's  
> just cooler. ;)
>
> The idea could, of course, be expanded to offer a public service.  
> If someone wanted to take the initiative to keep track of the  
> latest versions of plugins, I have no doubt a comprehensive list  
> would be quite welcome.
>
> --
> Chris Meller
> chris at doesnthaveone.com
>
>
> On Jan 22, 2006, at 12:48 PM, ch0de wrote:
>
>> Pretty nice buddy. But what I was thinking was something that k2  
>> had implented but I think It’s broken. The plugin author would  
>> create a .txt file on their website (Ex: http://somewebsite.com/sk- 
>> version.txt) and It would have a number in their like 1.0 for the  
>> version. In the plugin, in the “version:” field in the beginning  
>> of the plugin, the plugin that checks for updates will see if the  
>> “version:” field matches the .txt file version and If it does, it  
>> will echo “$PLUGIN_Name is up to date” or else “$PLUGIN_Name is  
>> currently out-dated. Please upgrade to $PLUGIN_UPDATED_VERSION”. J
>>
>>
>> -ch0de
>>
>>
>> From: wp-testers-bounces at lists.automattic.com [mailto:wp-testers- 
>> bounces at lists.automattic.com] On Behalf Of John Ha [c]
>> Sent: Sunday, January 22, 2006 12:44 PM
>> To: wp-testers at lists.automattic.com
>> Subject: Re: [wp-testers] Keeping Up-to-date [s]
>>
>>
>> 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
>>
>> ----- Original Message -----
>>
>> From: Podz
>>
>> To: wp-testers at lists.automattic.com
>>
>> Sent: Sunday, 22 January 2006 11:26 PM
>>
>> Subject: Re: [wp-testers] Keeping Up-to-date
>>
>>
>> Roy Schestowitz wrote:
>> > __/ On Sun 22 Jan 2006 11:22:06 GMT, [Sean Hayford O'Leary]  
>> wrote : \___
>> >
>>
>> <<snip>>
>>
>> > Sean makes a valid point.
>>
>> I totally agree, I just don't see how it can be done and certainly  
>> not
>> unless the core has the code added.
>>
>> P.
>> _______________________________________________
>> wp-testers mailing list
>> wp-testers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-testers
>>
>> [ SECURITY NOTICE ]
>>
>> To: wp-testers at lists.automattic.com.
>> For your security, khanh at netspace.net.au
>> digitally signed this message on 22 January 2006 at 17:44:19 UTC.
>> Verify this digital signature at http://www.ciphire.com/verify.
>>
>> [ CIPHIRE DIGITAL SIGNATURE ]
>>
>>
>> _______________________________________________
>> wp-testers mailing list
>> wp-testers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-testers
>
>
>
> _______________________________________________
> wp-testers mailing list
> wp-testers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-testers
> [ SECURITY NOTICE ]
> To: wp-testers at lists.automattic.com.
> For your security, khanh at netspace.net.au
> digitally signed this message on 22 January 2006 at 18:20:10 UTC.
> Verify this digital signature at http://www.ciphire.com/verify.
> [ CIPHIRE DIGITAL SIGNATURE ]
> _______________________________________________
> wp-testers mailing list
> wp-testers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-testers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://comox.textdrive.com/pipermail/wp-testers/attachments/20060122/b1ae7b6d/attachment-0001.htm