[wp-hackers] WordPress Plugin GUID

[John Blackbourn]

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?

John

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?
>
> Or I totally misunderstood something :)
>
> On Fri, Jun 5, 2009 at 12:11 AM, Lloyd Budd<lloydomattic at gmail.com> wrote:
>> Hi,
>>
>> Was working with mdawaffe on a plugin collision scenario -- two
>> plugins with the same name. We came to the conclusion that a decent
>> solution would be to add GUID to the "readme standard"
>> http://wordpress.org/extend/plugins/about/readme.txt.
>>
>> Plugin GUID: (string)
>>
>> For plugins in the extend/plugins the string would be their
>> extend/plugin URL. Example: "Plugin GUID:
>> http://wordpress.org/extend/plugins/stats/"
>>
>> The Plugin GUID would get sent to the plugin directory when checking
>> for updates. If the GUID does not match any known plugin in the
>> directory, it would just skip that plugin during the update check. If
>> it matches, use that match. No longer do any heuristic matches between
>> titles, urls, etc.
>>
>> Any comments, questions, concerns?
>>
>> Thanks,
>> Lloyd
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
>
>
>
> --
> http://planetOzh.com ~ Blog and WordPress Stuff
> http://FrenchFragFactory.net ~ Daily Quake News
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>