[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:  accepted
 Priority:  normal                   |   Milestone:  4.4
Component:  Plugins                  |     Version:  4.1.2
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+---------------------------

Comment (by DrewAPicture):

 Replying to [comment:30 jorbin]:
 > Thinking about this a little more, I think some UI to ensure users know
 that a plugin is unmanaged is going to be needed.

 I disagree with needing a UI element. I think users are more jarred by
 having their third-party plugins overwritten with one from the repo when
 they click update.

 > Users expect plugins to receive updates. And they expect the plugin
 screens to be where they find out about upgrades.  They should know that a
 plugin they are using isn't upgradable in the normal tradditional sense.

 The onus is on third-party developers to provide an update mechanism for
 their plugins whether users expect them or not, and that isn't really
 relevant here, in my opinion. This solves a very specific and longstanding
 problem. We aren't changing the expectation of using the plugins screens
 for updates. We're proposing to not overwrite one plugin with another one
 just because there's a matching slug for a plugin the repo.

 > When this goes in, we should create a meta ticket to have the plugin
 repo block any attempts at adding this header.  Ideally, via a pre-commit
 SVN hook so it can never ever be added.

 Noted.

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