#16200 closed defect (bug) (fixed)
Multisite can't find site /foo at /FOO (gives 404)
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 3.5 | Priority: | normal |
Severity: | normal | Version: | 3.1 |
Component: | Multisite | Keywords: | has-patch 3.5-early needs-unit-tests |
Focuses: | Cc: |
Description
Wordpress 3.0.4 and 3.1RC2 - multisite with subfolder installs.
Create a site at mysite.com/foo and a page on it at mysite.com/foo/about
Works as expected:
mysite.com/FOO/about goes to mysite.com/foo/about
mysite.com/foo loads foo's home page
Doesn't work as expected:
mysite.com/FOO loads foo's theme and gives a 404
So, it's only for the home page of a site on a multisite network that is addressed with a different capitalization scheme than the original. going to any subpages works fine.
Attachments (1)
Change History (11)
#2
@
14 years ago
- Keywords has-patch 3.2-early added
Requesting /ms-3.1-RC1/site1/:
[request] => [matched_rule] => [matched_query] =>
Requesting /ms-3.1-RC1/SITE1/:
[request] => ms-3.1-RC1/SITE1 [matched_rule] => (.+?)(/[0-9]+)?/?$ [matched_query] => pagename=ms-3.1-RC1%2FSITE1&page=
Case insensitivity only seems necessary for $req_uri
regarding this specific issue, but I've decided to add it for $pathinfo
and $self
as well for consistency.
#5
@
13 years ago
Apparently single site installations can also be affected. #17114 suggests doing a canonical redirect.
#6
@
13 years ago
- Keywords needs-testing dev-feedback 3.5-early added; 3.2-early removed
- Version changed from 3.1 to 3.4
Wondering if this could be part of 3.5. Patch has been here for a while. Issue is still present in 3.4. Thoughts?
#7
@
13 years ago
- Milestone changed from Future Release to 3.5
- Version changed from 3.4 to 3.1
Version number indicates when the bug was initially introduced/reported.
#8
@
13 years ago
- Component changed from General to Multisite
- Keywords needs-unit-tests added; needs-testing dev-feedback removed
Reproduced on trunk. Should fix this.