[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:  2nd-opinion  |
-------------------------+----------------------------

Comment (by jdgrimes):

 Replying to [comment:3 rmccue]:
 > +1, this needs a smarter mechanism IMO. In my code, I use an extra
 plugin header called `Plugin ID: xxx`, where `xxx` is the slug on the
 repository. We could add something like that, with a legacy fallback to
 the directory name (and eventually mark that as deprecated).

 Thinking along the lines of solving #13928 as well, what about adding two
 headers, something like `Update Service: xxx` and `Plugin ID: xxx`. So for
 plugins that should receive updates from wordpress.org, you might have:

 {{{
 Update Service: wordpress.org
 Plugin ID:      google-sitemap-generator
 }}}

 Then we would only check wp.org for updates if `wordpress.org` was the
 update service. (Of course, `wordpress.org` would be the default update
 service.) If you've modified the plugin and don't want to receive updates,
 you could change that to:

 {{{
 Update Service: none
 Plugin ID:      google-sitemap-generator
 }}}

 I'm thinking this could also be used by other plugin distributors or
 repositories:

 {{{
 Update Service: github
 Plugin ID:      JDGrimes/google-sitemap-generator
 }}}

 These could be condensed into a single header, like `Update URI`, but then
 we would have to parse the URI to see where it pointed to. I think two
 headers is cleaner and more extensible/fine grained.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/23318#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress blogging software