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

[WordPress Trac]

#32101: Ability to mark plugin as unmanaged
-------------------------------------+---------------------------
 Reporter:  damonganto               |       Owner:  DrewAPicture
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  4.4
Component:  Plugins                  |     Version:  4.1.2
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+---------------------------

Comment (by Otto42):

 @GaryJ: WordPress is not going to include any code to have updates come
 from another URL anytime soon, so having a header to specify a URL which
 isn't going to ever be used by core does not make any sense. If a plugin
 is going to update from a different endpoint, then it's going to need to
 include code for it to do so, and the URL can be contained in there.
 There's no benefit to having a URL in the header for an update check that
 will never be implemented.

 The purpose of a "Private" header is not only to prevent updates, but also
 to prevent any information such as the plugin header from being sent out
 as part of the update check process. Privacy in these headers is a concern
 that has been expressed by others, and while w.org does not store this
 plugin header information (because we ultimately don't really care about
 your plugin headers), not everybody believes me when I tell them that
 (because people are paranoid). Having a way for them to simply not send
 this info for plugins they don't want to send is a simple and easy fix to
 add right now.

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