Make WordPress Core

Opened 10 years ago

Closed 8 years ago

#27987 closed defect (bug) (invalid)

Multisite subdirectory getting 404

Reported by: beccawitz's profile beccawitz Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.9
Component: Networks and Sites Keywords: close
Focuses: multisite Cc:

Description

The site is using Multisite with subdirectories and lowercase path /he as the directory.
The main site is working fine, but when I go to the subdirectory's homepage, I get a 404 error.
The Dashboard url www.site.com/he/wp-admin works but I can't see the correct Dashboard - it shows me the main site's Dashboard instead.

I tried re-saving the permalinks but it didn't help.
The domain is with www
Using WordPress version 3.9

Thank you!

Change History (14)

#1 @SergeyBiryukov
10 years ago

  • Component changed from General to Networks and Sites

#2 @AnthonyJKenn
10 years ago

Sounds like the exact duplicate of #27866, except with lowercase rather than my mixed case directory pathnames.

Last edited 10 years ago by AnthonyJKenn (previous) (diff)

#3 @jeremyfelt
10 years ago

  • Keywords reporter-feedback added

Hi @beccawitz, thanks for the report.

A couple things that may help distinguish this from #27866 or #27927:

  • Is DOMAIN_CURRENT_SITE configured as site.com or www.site.com?
  • IS PATH_CURRENT_SITE configured as /?

Is this a fresh installation of WordPress 3.9 or an upgrade?

#4 @beccawitz
10 years ago

define('DOMAIN_CURRENT_SITE', 'www.site.com');
define('PATH_CURRENT_SITE', '/');
It was an upgrade.
Thank you.

#5 @jugoretz
10 years ago

Not sure if this helps or just makes things more confusing, but I am having (what looks like) the same problem. www.mysite.com/he redirects to main site, but mysite.com/he works fine (as it always has).

Mine is an upgrade, too, but this was originally (way back when) a multiuser install, upgraded consistently over time, so my wp-config does not even have DOMAIN_CURRENT_SITE or PATH_CURRENT_SITE

#6 @Ipstenu
10 years ago

jugoretz, see #27927 - I think the force non-www htaccess rule might help.

beccawitz - Can you look in your database under wp_site and wp_blogs. Does your domain have the www in there?

#7 @jugoretz
10 years ago

Thanks very much, Ipstenu. That seems to have done the trick for my problem.

#8 @beccawitz
10 years ago

@Ipstenu, in wp_blogs, the main domain has www but I see the subsite does not have www.
In wp_site, there is no www.

#9 follow-up: @Ipstenu
10 years ago

@beccawitz - the www usage should be consistent. I would make them all use www in your case since the wp-config has www.

#10 in reply to: ↑ 9 @beccawitz
10 years ago

@Ipstenu, yes it should - thank you for your help!

Replying to Ipstenu:

@beccawitz - the www usage should be consistent. I would make them all use www in your case since the wp-config has www.

#11 @bi0xid
10 years ago

Hello, @beccawitz.

I had the same problem installing with Nginx. With a basic Apache configuration it's working without a problem in a subdirectory.

#12 @chriscct7
8 years ago

  • Keywords needs-patch added; reporter-feedback removed

#13 @jeremyfelt
8 years ago

  • Keywords close added; needs-patch removed

I'm tempted to close this out as a misconfiguration issue. Can this be reproduced?

#14 @jeremyfelt
8 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

I'm going to close this out as a misconfiguration rather than an issue. Please reopen with steps to reproduce if it does seem like a core bug.

Note: See TracTickets for help on using tickets.