id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc
10814,Plugin GUIDs,mdawaffe,westi,"When a blog submits a list of plugins to the plugins update API, the API has no way of uniquely identifying the plugin; it's forced to do heuristics to make a best guess.

There are occasionally plugins that have the same name, for example, that make these heuristics difficult to perfect.

http://groups.google.com/group/wp-hackers/browse_thread/thread/69fa8f52249b13a0

Attached is a patch to get_plugin_data() that adds a meta datum to the plugin header: ""GUID"".

This GUID would just be the URL to the plugin's page on the WordPress.org Plugins Directory: e.g.

http://wordpress.org/extend/plugins/akismet/

I propose ""GUID"" because it's intentionally opaque; I don't think people will confuse it for anything they're supposed to do anything with (as opposed to ""Update URL"" or ""Update GUID"", which make it sound like I go there for updates or need it before updating).

I propose the URL because it gives us namespace::identifier for free and is understandable by humans and machines.

The intention is that these GUID lines would be automatically generated by the Plugins Directory to reduce plugin author error.",enhancement,closed,normal,,Plugins,2.8.4,normal,maybelater,has-patch,docwhat@…