[wp-hackers] Richer metadata for plugin versions
highfive at jesserfriedman.com
Wed Jul 11 19:37:56 UTC 2012
I would love to see plugin id's assigned by the extend API. Then each
plugin could have a unique identifier.
With a unique identifier and appended version number themes could
potentially request the use of specific plugins. Then once installed
initiate (with the admins permission of course) an install of those plugins.
This could lead to ways to tracking plugins more easily and open a door of
On Wed, Jul 11, 2012 at 3:31 PM, Kevinjohn Gallagher <
kevinjohngallagher at hotmail.com> wrote:
> "Update. Immediately. Always."
> Thats just kind of unrealistic in the real word brother.
> I mean, it's not about plug-ins that ship with bugs, its that some
> plug-ins add random UI changes, move from being accessible ro inaccessible,
> or add in "news" meta boxes on the dashboard.
> Take the latest Yoast's WP SEO. Brilliant plugin. Moving form 1.1.8 to
> 1.2.1 added 4 new columns of crap in the default post, that make it
> unreadable - especially if using a fairly standard for non-geeks 1024
> In a world where you're dealing with Governments, Education or Charity
> bodies - you can't go trusting plug-ins (or WP .0 releases) to not screw
> you over. And many of our "non-geeky" clients/users have learnt that.
> > From: otto at ottodestruct.com
> > Date: Wed, 11 Jul 2012 08:26:16 -0500
> > To: wp-hackers at lists.automattic.com
> > Subject: Re: [wp-hackers] Richer metadata for plugin versions
> > On Wed, Jul 11, 2012 at 1:57 AM, David Anderson <david at wordshell.net>
> > > One challenge when maintaining a lot of websites is, to know which
> > > need to be updated immediately (e.g. a zero-day security hole), and
> > > not (perhaps on your client's website it is better to wait a week -
> > > plugin authors upload code with fatal errors in, or they add new bugs
> > > fix them 2 hours later, etc.).
> > You should update any and all plugins immediately when there is an
> > update available, period.
> > If the plugin author has a habit of introducing new versions with
> > bugs, then you should stop using that plugin and find a different one
> > instead.
> > I do not see it as a good idea to introduce anything which even
> > remotely suggests that it is okay to not update. It is not okay.
> > Update. Immediately. Always.
> > -Otto
> > _______________________________________________
> > 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
508-507-9673 | jesserfriedman at gmail.com
http://jesserfriedman.com | @professor <http://twitter.com/professor>
More information about the wp-hackers