#49976 closed defect (bug) (invalid)
Allow plugin author to select a reason when closing a plugin
| Reported by: | ttodua | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Plugins | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
When plugin developer closes the plugin, there needs to be some kind of dropdown, where he selects the REASON for closure. That is quite useful things to let the world know the reason. For example, possible dropdowns:
- Depreciated in favor of plugin X (X is input field for the plugin)
- WP core implemented the feature (or the Parent plugin, for which the current plugin comes as module, for example, "XYZ for Woocommerce" is depreciated, because Woocommerce implemented that feature)
- Lack of resource/ability to monitor/maintain it.
- Other reason.
Change History (2)
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Tickets for modifying the behavior of the WordPress.org site should be made on the Meta Trac: https://meta.trac.wordpress.org.