Opened 14 years ago
Closed 9 years ago
#16400 closed enhancement (wontfix)
Add hook to delete_plugins() on successful delete
Reported by: | scottconnerly | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.0.4 |
Component: | Filesystem API | Keywords: | has-patch |
Focuses: | Cc: |
Description (last modified by )
Add an action or filter to the end of /wp-admin/includes/plugin.php delete_plugins()'s processing when the write is successful.
The use case is for managing a Wordpress install on an SVN-controlled server. Whenever the CMS changes a file's contents (particularly in the wp-content folder) I need to be able to trigger an svn commit.
See also Ticket #16399
Attachments (1)
Change History (7)
#2
in reply to:
↑ description
@
14 years ago
- Cc mikeschinkel@… added
#3
@
14 years ago
- Cc trac@… added
- Keywords has-patch added
ticket.16400.diff adds a new 'deleted_plugin' action hook into delete_plugins() passing the plugin file as the first parameter.
#4
@
11 years ago
- Component changed from Plugins to Filesystem
- Keywords 2nd-opinion dev-feedback added; subversion has-patch removed
Related: #16399, #16398, #16396, #16401
All the above referenced tickets are requesting an enhancement to add a hook whenever a file write is done. There has been no discussion on this in 3 years. If this is something that is not going to be considered or the use case is not broad enough can we go ahead and close these tickets? My thoughts are if your managing an install with version control it is better to disable filesystem writes.
If we are going to consider this then maybe a standard file write action could fire that passes the file name.
Replying to scottconnerly:
+1