[wp-hackers] WordPress Plugin GUID

Peter Westwood peter.westwood at ftwr.co.uk
Fri Jun 5 06:23:06 GMT 2009

This sounds like a good idea.

Is it not something the extend plugin pacager could add to the readme  
as it packaged up the plugin for downloads that way each plugin gets  
the correct GUID for free.

Peter Westwood

On 5 Jun 2009, at 00:10, Lloyd Budd <lloydomattic at gmail.com> wrote:

>> 2009/6/4 Ozh <ozh at planetozh.com>:
>>> Yeah but... if two plugins have the same name, won't they be given  
>>> the
>>> same guids too by their respective authors?
> No method would be fool proof or sabotage proof. On the surface it
> would seem plugin name + [other detail] would be unique enough, but
> likely are surprisingly fragile.
> It really only matters for plugins in wordpress.org/extend/plugins/
> On Thu, Jun 4, 2009 at 3:55 PM, John Blackbourn
> <johnbillion+wp at gmail.com> wrote:
>> I think the point Lloyd is making is that the Extend URL is a GUID  
>> itself.
>> Couldn't the "Plugin URL" field just be used as the GUID? No need to
>> add another field to the readme.txt file then. Maybe use something
>> like the Author Name as a fallback if the Plugin URL isn't present?
> Many authors have a shared (landing) page for all of their plugins.
> The proposal is saying that wp.org URL for the plugin is explicitly
> part of the description for a plugin to get updates.
> Actually including it in plainer language might be a better idea,
> because would also encourage users from downloading (manually
> updating) directly from WordPress.org without disrupting the authors
> use of Plugin URI. Maybe something like "WordPress.org Page" Or is the
> developer info intrinsic to GUID better?
> Cheers,
> Lloyd
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list