[wp-hackers] Bundled Plug-ins

Eric Mann eric at eamann.com
Sun Oct 3 15:10:06 UTC 2010

+1 on updating the external plugin automatically ... the only issue here is
when (for one reason or another) the blog can't use the auto upgrade
feature.  I have yet to get this to work on a PHP4-powered site.  And some
server setups require you to enter your FTP information each time anything
is downloaded.  A transparent update wouldn't work there.

What about "including" Akismet the same way the blog importers are
"included?"  They aren't bundled functionality, but are still called out
explicitly with a relatively painless download/activation link.

-----Original Message-----
From: wp-hackers-bounces at lists.automattic.com
[mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of Peter Westwood
Sent: Sunday, October 03, 2010 1:40 AM
To: wp-hackers at lists.automattic.com
Subject: Re: [wp-hackers] Bundled Plug-ins

On 3 Oct 2010, at 05:17, Andrew Nacin wrote:

> 1. Akismet is free for personal use.
> 2. Regarding hiding the update nags for deactivated plugins: I've
> this before, but the explanation I received was enough to cause me to flip
> my opinion completely. Some people will deactivate a plugin (or switch
> from a theme, I guess) specifically because they are waiting for an
> I see no reason to offer an option in core to hide such nags. We want
> to stay current.
> 3. I really do like the idea of latest.zip being re-bundled whenever a new
> version of Akismet or Twenty Ten is released. Feasible as Akismet is an
> external, but not feasible for Twenty Ten as it is not. OTOH, tags should
> atomic, so I'm not really sure about whether it makes sense. I'll mention
> to some of the other core devs.
> 4. Akismet is a plugin, and that is why it is on plugins Trac/SVN instead
> core Trac/SVN. It is bundled, I grant you, because spam is a huge issue
> Akismet solved a very important need when it was introduced. Having it on
> its own repository allows for its own release cycle. Twenty Ten is
> on themes SVN because it can have its own release cycle. (We'll likely be
> releasing a new version soon that fixes some image styling issues, and
> around an IE9 bug.)

If we were to rebuild the zip everytime a new version of akismet / twentyten
was released then we would have to release a new version of WordPress
everytime that happens

That just links them together in such a way that is not productive.

The best solution here IMHO would be for the "5 Minute install" to detect
that the upgrades are needed at install time and to do the upgrades as part
of the install transparently

This is the best solution - we don't have to keep rebuilding the zips, the
users gets the latest version at install, the user doesn't get annoyed by
upgrades straight after install.

If anyone would care to patch this it would be really great :-)

Peter Westwood
http://blog.ftwr.co.uk | http://westi.wordpress.com
C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5

wp-hackers mailing list
wp-hackers at lists.automattic.com

More information about the wp-hackers mailing list