[wp-hackers] Re: wp-hackers Digest, Vol 18, Issue 81
Dave W
dabbaking at gmail.com
Sun Jul 30 12:18:24 GMT 2006
I think the whole max version should be wiped out. A plugin usually breaks
when the user isn't using a recent version that doesn't have feature that
the plugin uses. Most times I see a plugin that only works for 2.0 and it
doesn't work for 1.5. As long as the basic API for plugins doesn't change
much, it won't be necessary to have.
Maybe there should be some tests setup that determine if the plugin is
compatible (checking hooks, etc.) and then alert that user that the plugin
isn't compatible and disable it and tell them to get a more recent version
if it's available.
On 7/30/06, wp-hackers-request at lists.automattic.com <
wp-hackers-request at lists.automattic.com> wrote:
>
> Send wp-hackers mailing list submissions to
> wp-hackers at lists.automattic.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.automattic.com/mailman/listinfo/wp-hackers
> or, via email, send a message with subject or body 'help' to
> wp-hackers-request at lists.automattic.com
>
> You can reach the person managing the list at
> wp-hackers-owner at lists.automattic.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of wp-hackers digest..."
>
>
> Today's Topics:
>
> 1. Re: Plugin Management and Autoupdate System (Arne Brachhold)
> 2. RE: Plugin Management and Autoupdate System (Computer Guru)
> 3. RE: Plugin Management and Autoupdate System (Computer Guru)
> 4. RE: Plugin Management and Autoupdate System (Computer Guru)
> 5. Re: Plugin Management and Autoupdate System (Rob Miller)
> 6. RE: Plugin Management and Autoupdate System (Computer Guru)
> 7. Re: Plugin Management and Autoupdate System (Andy Staines)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 30 Jul 2006 02:32:07 +0200
> From: "Arne Brachhold" <himself at arnebrachhold.de>
> Subject: Re: [wp-hackers] Plugin Management and Autoupdate System
> To: wp-hackers at lists.automattic.com
> Message-ID:
> <cb1226600607291732m49fa5af2jf40c70d30893d338 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi,
>
> On 7/29/06, Computer Guru <computerguru at neosmart.net> wrote:
> > I'm done with a framework that checks for the updates.
> > Basically I'm going with an RDF RSS file that looks something like this:
>
> I've started an Auto-Update-Plugin half a year ago too but decided to
> stop it when I saw that there was already another one. My idea was
> similar to the concept from Computer Guru, but I extended the RSS feed
> with some special tags:
>
> <?xml version="1.0"?>
> <rss xmlns:wpu="http://wordpress.org/dev/wpu/1.0/" version="2.0">
> <channel>
> <title>Google Sitemap Generator</title>
> <link>http://bla.com/GoogleSitemapGenerator/</link>
> <description>This generator will create a Google compliant
> sitemap of your WordPress blog.</description>
> <language>en-us</language>
> <pubDate>Tue, 10 Jun 2003 04:00:00 GMT</pubDate>
> <lastBuildDate>Tue, 10 Jun 2003 09:41:01 GMT</lastBuildDate>
>
> <wpu:pluginLink>http://www.arnebrachhold.de/redir/sm-home/
> </wpu:pluginLink>
> <wpu:pluginName>GoogleSitemapGenerator</wpu:pluginName>
>
> <wpu:authorName>Arne Brachhold</wpu:authorName>
> <wpu:authorLink>http://www.arnebrachhold.de/</wpu:authorLink>
>
> <item>
> <title>Version 1.5</title>
> <link>bla.com/GoogleSitemapGenerator/1.5/</link>
> <description>Works with 2.0, but not 1.5</description>
> <pubDate>Tue, 03 Jun 2003 09:39:21 GMT</pubDate>
> <guid>http://bla.com/GoogleSitemapGenerator/1.5/</guid>
>
> <wpu:minWordPressVersion>2.0.2</wpu:minWordPressVersion>
> <wpu:maxWordPressVersion>2.5</wpu:maxWordPressVersion>
>
> <wpu:minPhpVersion>4.3.3</wpu:minPhpVersion>
> <wpu:maxPhpVersion>4.4.5</wpu:maxPhpVersion>
> <wpu:downloadLink>
> http://www.arnebrachhold.de/get/sitemap/sitemap-1.5.zip</wpu:downloadLink>
>
> <wpu:devStatus>beta</wpu:devStatus>
> </item>
> <item>
> <title>Version 1.0</title>
> <link>http://bla.com/GoogleSitemapGenerator/1.0/</link>
> <description>Initial release.</description>
> <pubDate>Tue, 01 Jun 2003 09:39:21 GMT</pubDate>
> <guid>http://bla.com/GoogleSitemapGenerator/1.0/</guid>
>
> <wpu:minWordPressVersion>1.5</wpu:minWordPressVersion>
> <wpu:maxWordPressVersion>1.5.2.2
> </wpu:maxWordPressVersion>
>
> <wpu:minPhpVersion>4.3.3</wpu:minPhpVersion>
> <wpu:maxPhpVersion>4.4.5RC2</wpu:maxPhpVersion>
> <wpu:downloadLink>
> http://www.arnebrachhold.de/get/sitemap/sitemap.1-0.zip</wpu:downloadLink>
>
> <wpu:devStatus>stable</wpu:devStatus>
> </item>
> </channel>
> </rss>
>
> The idea was to code an additional WordPress plugin which allows
> plugin developers to announce the new plugin versions directly via
> their blog feed. The plugin would add some fields to the post form
> (the values above) and the author could use
> http://www.theblog.com/category/pluginOne/feed as the update feed.
> So you don't need to manage several feeds / files for the same data.
> The feed would also support different WordPress and PHP versions so it
> could display a message to the user like "The best version of this
> plugin for your blog is 1.2, if you upgrade to WordPress 2.0.4 you
> could also use the brand-new-super-featured 1.5".
>
> --
> Arne Brachhold
> mail: himself at arnebrachhold.de
> web: http://www.arnebrachhold.de/
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 30 Jul 2006 09:36:13 +0300
> From: Computer Guru <computerguru at neosmart.net>
> Subject: RE: [wp-hackers] Plugin Management and Autoupdate System
> To: <wp-hackers at lists.automattic.com>
> Message-ID: <000001c6b3a2$761c5540$6254ffc0$@net>
> Content-Type: text/plain; charset="us-ascii"
>
> > What do you mean by auto-remove? Your not suggesting WordPress
> > automatticly disables plugins based on information from an external
> > source are you - that's a surefire way to break sites!
>
> I mean auto-uninstall routines - there will be activate plugin, deactivate
> plugin, and delete plugin.. the latter of which completely wipes all
> residues and deletes the files.
>
> I want to keep this simple, no multiple URI's the plugin file itself
> should
> contain the install and uninstall routines, not reference another external
> RDF which in turn calls upon another document with install/uninstall
> steps.
>
> About the different plugin versions: I think if you have a plugin for 1.5
> and 2.0 that are different, and are both still actively developed, the
> most
> logical thing is to have two separate RDFs for both - in essence making
> them
> separate plugins, that way the RDF only provides relevant info.
>
> I'm glad this has some support :-)
>
> An important question: does WP need a script that can _make_ these RDF
> files? I mean, is it in the role of WP, or should this be an external
> script?
>
> ATM I'm just going to focus on setting up this new API, making it work,
> and
> I guess we can go from there.
>
> Computer Guru
> NeoSmart Technologies
> http://neosmart.net/blog
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 30 Jul 2006 10:27:28 +0300
> From: Computer Guru <computerguru at neosmart.net>
> Subject: RE: [wp-hackers] Plugin Management and Autoupdate System
> To: <wp-hackers at lists.automattic.com>
> Message-ID: <000101c6b3a9$a0acc540$e2064fc0$@net>
> Content-Type: text/plain; charset="us-ascii"
>
> There _is_ one thing that puts us at a big disadvantage: in order to
> autoupdate, we'd have to assume that fopen and fwrite are available, at
> least I don't know of any other way to replace the old version of the
> plugin
> with a new one... and quite a few hosts block fopen and fwrite.
>
> Even worse, we're going to have a real headache with n00bs coming in with
> wrong permissions all over the place until some 'godsend' teaches them how
> to do chmod 777 * -R and makes an even bigger mess of things.
>
> Firefox can create and delete files on the fly, but this _is_ going to be
> hard.
>
> Does anyone have any ideas for how one would circumvent this? I don't
> think
> the standard WP "If this file were writable you could save this.." dialog
> is
> enough....
>
> For now that's what I'm going to go for, it'll attempt fwrite, if it can
> that's dandy, but if it can't we're going to have to spit the plugin file
> to
> the screen for the user to cut and paste on their own - ugh.
>
> Any suggestions?
>
> Computer Guru
> NeoSmart Technologies
> http://neosmart.net/blog/
>
>
>
> ------------------------------
>
> Message: 4
> Date: Sun, 30 Jul 2006 13:24:30 +0300
> From: Computer Guru <computerguru at neosmart.net>
> Subject: RE: [wp-hackers] Plugin Management and Autoupdate System
> To: <wp-hackers at lists.automattic.com>
> Message-ID: <000501c6b3c2$5a1b8c60$0e52a520$@net>
> Content-Type: text/plain; charset="us-ascii"
>
> > I've started an Auto-Update-Plugin half a year ago too but decided to
> > stop it when I saw that there was already another one. My idea was
> > similar to the concept from Computer Guru, but I extended the RSS feed
> > with some special tags:
>
> I love the tags. (OT: I love your Sitemap generator too - I always forget
> I
> have it, it's completely maintenance and trouble-free!)
>
> I'm trying to make the feed as efficient as possible, so I just have a
> channel author instead of an author for each version - there shouldn't be
> a
> need to repeat that tag for every item.
>
> It's prolly a good idea to include min/max WordPress versions, but
> _please_
> let's not have the maxversion defined by default - look at Firefox: for
> every new version all plugins need a rewrite. Maxversion should *only* be
> used when it has been 100% verified that the plugin is broken in a higher
> version - innocent until proven guilty.
>
>
> Computer Guru
> NeoSmart Technologies
> http://neosmart.net/blog/
>
>
> > -----Original Message-----
> > From: wp-hackers-bounces at lists.automattic.com [mailto:wp-hackers-
> > bounces at lists.automattic.com] On Behalf Of Arne Brachhold
> > Sent: Sunday, July 30, 2006 3:32 AM
> > To: wp-hackers at lists.automattic.com
> > Subject: Re: [wp-hackers] Plugin Management and Autoupdate System
> >
> > <?xml version="1.0"?>
> > <rss xmlns:wpu="http://wordpress.org/dev/wpu/1.0/" version="2.0">
> > <channel>
> > <title>Google Sitemap Generator</title>
> > <link>http://bla.com/GoogleSitemapGenerator/</link>
> > <description>This generator will create a Google compliant
> > sitemap of your WordPress blog.</description>
> > <language>en-us</language>
> > <pubDate>Tue, 10 Jun 2003 04:00:00 GMT</pubDate>
> > <lastBuildDate>Tue, 10 Jun 2003 09:41:01 GMT</lastBuildDate>
> >
> > <wpu:pluginLink>http://www.arnebrachhold.de/redir/sm-
> > home/</wpu:pluginLink>
> > <wpu:pluginName>GoogleSitemapGenerator</wpu:pluginName>
> >
> > <wpu:authorName>Arne Brachhold</wpu:authorName>
> > <wpu:authorLink>http://www.arnebrachhold.de/</wpu:authorLink>
> >
> > <item>
> > <title>Version 1.5</title>
> > <link>bla.com/GoogleSitemapGenerator/1.5/</link>
> > <description>Works with 2.0, but not 1.5</description>
> > <pubDate>Tue, 03 Jun 2003 09:39:21 GMT</pubDate>
> > <guid>http://bla.com/GoogleSitemapGenerator/1.5/</guid>
> >
> > <wpu:minWordPressVersion>2.0.2</wpu:minWordPressVersion>
> > <wpu:maxWordPressVersion>2.5</wpu:maxWordPressVersion>
> >
> > <wpu:minPhpVersion>4.3.3</wpu:minPhpVersion>
> > <wpu:maxPhpVersion>4.4.5</wpu:maxPhpVersion>
> >
> > <wpu:downloadLink>http://www.arnebrachhold.de/get/sitemap/sitemap-
> > 1.5.zip</wpu:downloadLink>
> >
> > <wpu:devStatus>beta</wpu:devStatus>
> > </item>
> > <item>
> > <title>Version 1.0</title>
> > <link>http://bla.com/GoogleSitemapGenerator/1.0/</link>
> > <description>Initial release.</description>
> > <pubDate>Tue, 01 Jun 2003 09:39:21 GMT</pubDate>
> > <guid>http://bla.com/GoogleSitemapGenerator/1.0/</guid>
> >
> > <wpu:minWordPressVersion>1.5</wpu:minWordPressVersion>
> > <wpu:maxWordPressVersion>1.5.2.2
> </wpu:maxWordPressVersion>
> >
> > <wpu:minPhpVersion>4.3.3</wpu:minPhpVersion>
> > <wpu:maxPhpVersion>4.4.5RC2</wpu:maxPhpVersion>
> >
> > <wpu:downloadLink>http://www.arnebrachhold.de/get/sitemap/sitemap.1-
> > 0.zip</wpu:downloadLink>
> >
> > <wpu:devStatus>stable</wpu:devStatus>
> > </item>
> > </channel>
> > </rss>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Sun, 30 Jul 2006 12:26:13 +0100
> From: Rob Miller <r at robm.me.uk>
> Subject: Re: [wp-hackers] Plugin Management and Autoupdate System
> To: wp-hackers at lists.automattic.com
> Message-ID: <44CC9755.5010909 at robm.me.uk>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Computer Guru wrote:
> > It's prolly a good idea to include min/max WordPress versions, but
> _please_
> > let's not have the maxversion defined by default - look at Firefox: for
> > every new version all plugins need a rewrite. Maxversion should *only*
> be
> > used when it has been 100% verified that the plugin is broken in a
> higher
> > version - innocent until proven guilty.
> >
> Why purposefully introduce stability issues? Assume plugins are broken
> until they are confirmed as working, at which point the max version
> number gets bumped.
>
> --
> Rob Miller
> http://robm.me.uk/ | http://kantian.co.uk/
>
>
>
> ------------------------------
>
> Message: 6
> Date: Sun, 30 Jul 2006 14:28:50 +0300
> From: Computer Guru <computerguru at neosmart.net>
> Subject: RE: [wp-hackers] Plugin Management and Autoupdate System
> To: <wp-hackers at lists.automattic.com>
> Message-ID: <000601c6b3cb$566fd360$034f7a20$@net>
> Content-Type: text/plain; charset="us-ascii"
>
> > Why purposefully introduce stability issues? Assume plugins are broken
> > until they are confirmed as working, at which point the max version
> > number gets bumped.
>
> Because that's what the FF devs assumed and now it's a big mess (yes, I do
> contribute code to the FF project too).
>
> Let me ask you this:
> ATM does WP check if the plugin is compatible? No.
> Has it been a catastrophe? No.
>
> 999 times out of 1000 a plugin won't break because of a new version. To
> assume it's broken means you're going to have a lot of people crying when
> that new version comes out... but none of that matters because:
>
> Plugin devs are lazy. Let's face it, we're not willing to maintain a
> plugin
> unless there is a serious bug or we have some tasty new features to add -
> but to have to update the plugin file with every new WP version is not
> nice.
>
> Computer Guru
> NeoSmart Technologies
> http://neosmart.net/blog/
>
>
>
>
> ------------------------------
>
> Message: 7
> Date: Sun, 30 Jul 2006 12:34:19 +0100
> From: Andy Staines <andy at yellowswordfish.com>
> Subject: Re: [wp-hackers] Plugin Management and Autoupdate System
> To: wp-hackers at lists.automattic.com
> Message-ID: <3680C64C-3D35-4747-94C6-3F955BAEDED9 at yellowswordfish.com>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> For what it's worth, I agree with Rob
> Lazy or not - surely it's a responsibility.
> Andy
>
> On 12:28 PM | Sun 30 Jul 06, at 12:28 PM | 30 Jul 06, Computer
> Guru wrote:
>
> >> Why purposefully introduce stability issues? Assume plugins are
> >> broken
> >> until they are confirmed as working, at which point the max version
> >> number gets bumped.
> >
> > Because that's what the FF devs assumed and now it's a big mess
> > (yes, I do
> > contribute code to the FF project too).
> >
> > Let me ask you this:
> > ATM does WP check if the plugin is compatible? No.
> > Has it been a catastrophe? No.
> >
> > 999 times out of 1000 a plugin won't break because of a new
> > version. To
> > assume it's broken means you're going to have a lot of people
> > crying when
> > that new version comes out... but none of that matters because:
> >
> > Plugin devs are lazy. Let's face it, we're not willing to maintain
> > a plugin
> > unless there is a serious bug or we have some tasty new features to
> > add -
> > but to have to update the plugin file with every new WP version is
> > not nice.
> >
> > Computer Guru
> > NeoSmart Technologies
> > http://neosmart.net/blog/
> >
> >
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
>
>
>
> ------------------------------
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>
>
> End of wp-hackers Digest, Vol 18, Issue 81
> ******************************************
>
--
Dave W
More information about the wp-hackers
mailing list