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

WordPress Trac noreply at wordpress.org
Fri Feb 12 05:58:39 UTC 2021


#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 afragen):

 Replying to [comment:88 lev0]:
 > Replying to [comment:86 afragen]:
 > > I’ve always thought something like this was plugin territory
 >
 > Thank you for illustrating this problem perfectly.
 [https://wordpress.org/plugins/skip-updates/ Your plugin isn't taken]. If
 your plugin doesn't protect itself, someone named "Skip Jones" could
 create it and have it do something else update-y. Maybe no name-based
 shenanigans are required and it could simply skip updates outside of
 business hours so that someone would be on the clock in case anything
 needs fixing. Now every plugin and theme that was protected by your plugin
 is trashed. Maybe your plugin does protect itself but someone disabled it,
 or it failed for some other reason, and both it and the other plugins get
 wiped out.

 I guess all I would need to protect myself and anyone else who wants to
 use this as a solution is to submit it to the plugin repository. 😉

 I’ll do that in the morning.

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


More information about the wp-trac mailing list