[wp-trac] [WordPress Trac] #32101: Ability to mark plugin as unmanaged
WordPress Trac
noreply at wordpress.org
Fri Apr 24 07:48:55 UTC 2015
#32101: Ability to mark plugin as unmanaged
-------------------------+-----------------------------
Reporter: damonganto | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Plugins | Version: 4.1.2
Severity: normal | Keywords:
Focuses: |
-------------------------+-----------------------------
We've had a rather unpleasent incident where we used a certain plugin name
for a private plugin, but then another plugin appeared under the same name
in the theme directory, marking our plugin for an update. Rest assured
''someone'' clicked on the update button, replacing our plugin with some
other.
Such conflicts may seem rare, but they do happen. Adding an optional,
defaults to false, `private` field to the theme header (like npm/Bower) to
disable update checking for such a plugin would be an easy fix.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/32101>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list