[wp-trac] [WordPress Trac] #32101: Ability to mark plugin as unmanaged
WordPress Trac
noreply at wordpress.org
Thu Apr 30 16:10:40 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: normal | Resolution:
Keywords: has-patch needs-testing | Focuses:
-------------------------------------+----------------------------
Changes (by apedog):
* severity: major => normal
Comment:
First off I'd like to admin an embarrassing fact..
The plugin slug conflict did ''NOT'' cause the deletion of my plugin on
auto-update.
My plugin was configured to update from github - and wp core respected
that.
What happened was that I had accidentally moved the plugin inside another
plugin's directory. (I believe wp also looks one directory down the
hierarchy - so it was still available on the Plugins page as it always had
been). My plugin was deleted when its "parent" plugin had auto-updated.
So that's that. I'm sorry if I sent anyone chasing down this wrong rabbit
hole.
As it stands, the plugin retains its association with the github
repository/version so long as its activated. On deactivation it reverts to
being erroneously associated with the plugin of the same name on
WordPress.org and displays the notice suggesting an upgrade. ie. to be
replaced by the wp.org plugin (which is at a higher version).
> IF we were to add that, I would want an SVN commit blocker on anyone
trying to upload something to .org with that header as anything but
WordPress, in order to prevent them from accidentally breaking their
plugins the other way. Or just block that header entirely.
That sounds very reasonable.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/32101#comment:67>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list