Make WordPress Core

Opened 11 months ago

Closed 8 months ago

#24368 closed feature request (maybelater)

Renaming feature for wp-includes

Reported by: JoeIzzard 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:


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)

patch.zip (136.6 KB) - added by JoeIzzard 11 months ago.
Zip folder containing all edited files for feature to function
24368.patch (67.6 KB) - added by JoeIzzard 11 months ago.
Patch file for this feature

Download all attachments as: .zip

Change History (5)

JoeIzzard11 months ago

Zip folder containing all edited files for feature to function

JoeIzzard11 months ago

Patch file for this feature

comment:1 JoeIzzard11 months ago

  • Keywords needs-testing added

comment:2 SergeyBiryukov11 months ago

Related/duplicate: #23249

comment:3 dd328 months 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.

Note: See TracTickets for help on using tickets.