Opened 15 years ago
Closed 14 years ago
#12716 closed enhancement (duplicate)
Incorrect theme editor behaviour with child themes
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 2.9 |
Component: | Themes | Keywords: | needs-patch |
Focuses: | Cc: |
Description
I have created a child theme of 2010 and noticed that the theme editor is not working correctly with child themes.
I am currently able to edit ALL files in the active theme, including the ones stored in the parent theme.
There is no easy way to tell which files are in the child theme and which are in the parent (without looking in the URL)
To be honest I would still perhaps like the ability to edit these files, but it MUST be very obvious that you are doing so, as I do not wish to edit the parent by accident as I want to be able to updated them via SVN.
Idealy if you try to edit a file in the parent theme, WordPress should give you the option to copy the file to the Child theme folder and then you can edit it there, as that would obviously your intention in doing the edit in the first place.
Change History (5)
#2
@
15 years ago
- Milestone changed from Unassigned to 3.0
Regarding the last paragraph, FWIW, this has been suggested as part of a theme editor overhaul.
#3
@
15 years ago
- Keywords needs-patch added; theme editor removed
- Milestone changed from 3.0 to 3.1
- Priority changed from high to normal
- Severity changed from major to normal
- Type changed from defect (bug) to enhancement
- Version set to 2.9
In my opinion, this is a enhancement over what we currently have in the file editors. I agree that separation would be great, but without a patch, I'm punting this to 3.1 when we'll have some work done related to parent/child themes and theme editors.
Related feature #12717