Opened 10 months ago
Last modified 10 months ago
#64441 new enhancement
Make Subdirectory networks compatible with custom wp-content directories
| Reported by: | oglekler | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Awaiting Review |
| Component: | Networks and Sites | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: | multisite |
Description
While having a custom wp-content directory and wanting to set up multisite in Network Setup, there is a warning that "Subdirectory networks may not be fully compatible with custom wp-content directories." It looks very inconvenient, because having WordPress and content in different places simplifies the deployment process. And if you already have content in a custom directory, you may want to go multisite any time, and then you have a problem.
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
@oglekler
Subdirectory multisite networks are currently not fully compatible with custom wp-content directories due to core assumptions tying content URLs to site paths. This limits modern deployment setups and discourages best practices such as separating application and content layers.