[wp-trac] [WordPress Trac] #23318: Plugins Admin Showing Details for Wrong Plugin

[WordPress Trac]

#23318: Plugins Admin Showing Details for Wrong Plugin
-------------------------+----------------------------
 Reporter:  miqrogroove  |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  WordPress.org
Component:  Plugins      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+----------------------------

Comment (by DavidAnderson):

 Both of dd32's suggestions are mathematically redundant... a name-space
 identifier plus a slug already constitutes a GUID.

 1) w.org/hello-dolly
 The slug is already known, and hence redundant. The "host" part of the URL
 is being used as a name-space/ownership identifier - same as the existing
 suggestion.

 The only new thing is a convention that the identifier be a valid domain
 name, to prevent clashes. But since this convention can't be enforced upon
 3rd-party plugins, and presumably won't be part of the code (WHOIS lookups
 on the domain ownership?!?) it does not add anything. (Sensible 3rd
 parties would do something to make sure their identifier was unique
 anyway).

 2) Pretty much the same then goes for https://wordpress.org/plugins/hello-
 dolly/ - this does not encode any different information from w.org/hello-
 dolly, except that it's a plugin, and that it's also a valid URL - but,
 both these bits of information are already known from other sources, hence
 redundant.

 My conclusions:

 * It doesn't matter what we call it; it functions as a name-space
 identifier
 * It's best not to include redundant information that can already be added
 if doing things like constructing URLs
 * Since it's essentially a name-space or vendor identifier, we may as well
 call it that, instead of my earlier suggestion of "Upgrade Service", which
 suggests a more restricted use.

 e.g. "Vendor: wordpress.org" (for repo plugins - and the assumed legacy
 value if not present), or "Vendor: example.com" by convention for 3rd
 parties - but nothing enforces this, so if someone has a reason to not be
 tied to a domain name, they can use "Vendor: MyBigFatSecretMegaCorp"

--
Ticket URL: <https://core.trac.wordpress.org/ticket/23318#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform