Opened 11 years ago
Last modified 6 years ago
#26895 new enhancement
Deprecate recently_edited option
Reported by: | yani.iliev | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | minor | Version: | 3.8 |
Component: | Options, Meta APIs | Keywords: | dev-feedback |
Focuses: | Cc: |
Description
recently_edited option is being set when a plugin or a theme file is edited by the builtin Editor.
A search, in the WordPress 3.8 source code, tells me that the option is never being read.
I suggest that we deprecate that option and replace it by an action where plugins can hook and get the value of the edited file.
Change History (5)
#3
@
9 years ago
At least fix the option so that the paths it contains are relative to the install folder rather than absolute for the local file system.
#4
@
9 years ago
@maximinime can you comment on the benefits there will be if this is changed from absolute? I was trying to figure out the pros/cons and I am thinking the main time this would change is if you switch hosting providers. In that case I was thinking it may be a good thing to know which file was changed(before or after).
I think keeping this is potentially useful information we may wish to use at a later point, and something that core probably could use, too.