Opened 15 years ago
Closed 15 years ago
#10974 closed defect (bug) (fixed)
Theme Editor broken
Reported by: | richardmtl | Owned by: | |
---|---|---|---|
Milestone: | 2.9 | Priority: | normal |
Severity: | major | Version: | 2.9 |
Component: | General | Keywords: | has-patch tested commit |
Focuses: | Cc: |
Description
Hi, this is my 1st bug report, please ask if you need more details.
I have a blog that I use only for testing new plugins and themes, so I decided to try out 2.9 to see what's new. I installed a nightly today, and when I go to the Theme Editor page, I get the error "Oops, no such file exists! Double check the name and try again, merci.". I did a quick search on this message and suspected that the qtranslate plugin was the problem, so I deactivated it, but I still get the same error message. I have many plugins (only some of which are currently active) and many themes installed in this blog, so I do not know where to start to try to debug. I even deactivated all and used Kubrik, but I still get the same error. Please give me some guidance as to how I can help debug this issue.
Attachments (2)
Change History (9)
#1
@
15 years ago
- Keywords needs-patch added; theme editor edit themes removed
- Milestone changed from Unassigned to 2.9
- Summary changed from Error editing Theme from Theme Editor to Theme Editor broken
- Version set to 2.9
@
15 years ago
Theme files are full paths now. Don't prefix WP_CONTENT_DIR to $file in get_real_file_to_edit.
#2
@
15 years ago
- Cc matt@… added
- Keywords has-patch tested added; needs-patch removed
get_real_file_to_edit is currently only used in theme-editor.php. If we were to start using this file for other items we could run into problems with this modification if $file is not a full file system path. Just something to keep in mind for the future. To be honest we could probably remove the use of this function all together since it is really doing nothing for us at this point, except passing back exactly what we give it.
Let me know what you think, I can easily create a new patch to not use get_real_file_to_edit.
Was able to reproduce this in trunk: selecting any file from the right produces the same error.
Might be related to #10467.