#24368 closed feature request (maybelater)
Renaming feature for wp-includes
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | 3.5.1 |
| Component: | Filesystem API | Keywords: | has-patch dev-feedback 2nd-opinion needs-testing |
| Focuses: | Cc: |
Description
Currently it is possible to rename wp-content to anything you want. WordPress has a definition built in for wp-includes, that is WPINC, however, this definition isn't used in about 15 - 16 core files preventing it from being changed (For example, some CSS doesn't load for the admin bar). I have added the files that I have changed to allow this to work, to work add a definition for WPINC to wp-config with the name of your wp-includes folder without and slashes. Without the definition it just uses the standard wp-includes.
Attachments (2)
Change History (7)
#3
@
11 years ago
- Milestone Awaiting Review deleted
- Resolution set to maybelater
- Status changed from new to closed
WordPress doesn't really support changing the location of core files, even with the constant available, it's not designed to be overridden.
I'm closing this as maybe later since there is currently no immediate planned support for this. Another core dev can re-open in the future if we decide to go down this path.
Zip folder containing all edited files for feature to function