Opened 8 weeks ago
Last modified 8 weeks ago
#64441 new enhancement
Make Subdirectory networks compatible with custom wp-content directories
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Awaiting Review | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | Networks and Sites | Keywords: | |
| Focuses: | multisite | Cc: |
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.
@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.