Making WordPress.org

#7087 closed enhancement (fixed)

Automatically move 'disabled' plugins to 'closed' after 12 months.

Reported by: ipstenu's profile Ipstenu Owned by: dd32's profile dd32
Milestone: Priority: normal
Component: Plugin Directory Keywords:
Cc:

Description

Right now, disabled is a nice alternative to closed, and allows developers to push updates (security, etc) while not permitting new installs.

The problem is ... plugins just live like that.

I propose that, 12 months after a plugin is set disabled, it is automatically moved to closed. After all, there's really no reason to be perma-disabled, is there? And we can always edit if needed.

Change History (1)

#1 @dd32
11 months ago

  • Owner set to dd32
  • Resolution set to fixed
  • Status changed from new to closed

In 12681:

Plugin Directory: Automatically move plugins from a Disabled state to a Closed state after 12 months.

Fixes #7087.

Note: See TracTickets for help on using tickets.