[wp-trac] [WordPress Trac] #32101: Ability to mark plugin as unmanaged

WordPress Trac noreply at wordpress.org
Thu Nov 26 00:27:59 UTC 2020


#32101: Ability to mark plugin as unmanaged
-------------------------------------+----------------------------
 Reporter:  damonganto               |       Owner:  DrewAPicture
     Type:  task (blessed)           |      Status:  assigned
 Priority:  normal                   |   Milestone:  WordPress.org
Component:  Plugins                  |     Version:  4.1.2
 Severity:  major                    |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+----------------------------

Comment (by lev0):

 The suggestion by [comment:13 jdgrimes] make a lot of sense:
 > A while ago I created a
 [https://github.com/WordPoints/wordpointsorg/tree/develop/src/admin/includes
 fork of the plugin update code] for a plugin. Instead of hard-coding the
 handling of requests based on a single remote URL and API, I abstracted
 the code in such a way that it is remote API agnostic. All that is needed
 to receive updates from a given URL is to set the `Channel` header like
 this: `Channel: wordpress.org`.

 It's concise, doesn't add extra descriptive terms that are already evident
 from context (e.g. `WordPress Repository:`), and makes it extensible for
 future update methods. It would immediately provide a patch path for this
 issue with a reserved word, e.g. `Channel: none`. If that's not
 descriptive enough `Update Channel:` could do. Omission of the header
 would obviously default to whatever WP.org wishes to reserve for itself,
 if not the quoted suggestion above.

 The downside of using terms like "Repo" or "Repository" in the header name
 is the implication of consistent, remote archives of code that can be
 utilised with read-only operations. Those terms are usually associated
 with package managers that have strict format and delivery standards, but
 it's not necessary to define how updates should be delivered.

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


More information about the wp-trac mailing list