WordPress.org

Making WordPress.org

#1716 closed enhancement (invalid)

No Option to Close/Disable plugins

Reported by: Ipstenu Owned by:
Milestone: Priority: normal
Component: Plugin Directory Keywords:
Cc:

Description

Admins should be able to Close and Disable plugins

  • Closed - Plugin is not available for download, no one can see it, updates are not pushed.
  • Disabled - Plugin cannot be seen, but updates ARE pushed

Primarily we use Closed, however there are use-cases where we want disabled - like security where we need to retire a plugin and push an update at the same time.

Right now we only have 'Rejected' which is not usable, as that (should) free up a slug for someone else to submit with.

Attachments (1)

Screen Shot 2016-05-18 at 10.30.13 AM.png (24.8 KB) - added by Ipstenu 19 months ago.

Download all attachments as: .zip

Change History (5)

#1 @obenland
19 months ago

The Closed and Disabled statuses are only available if the plugin is Publish, Closed, or Disabled.

This ticket was mentioned in Slack in #meta by obenland. View the logs.


19 months ago

#3 @Ipstenu
19 months ago

Sneaky!

Okay that should work. I can think of a could WEIRD moments where we'd want to approve and then immediatly close a plugin, but that's no different than today.

#4 @Ipstenu
19 months ago

  • Milestone Plugin Directory v3 - M3 deleted
  • Resolution set to invalid
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.