Actually, I don’t have any upper letters in my path. I wish it was that simple.
Error 403 We have temporarily disabled logins
*blink* can you flush the Varnish cache?
I turned off varnish and switched apache back to port 80
Could this be an issue?
The siteURL for root level blog is http://knoxblogs.com
while the “home” is http://www.knoxblogs.com/ (both are grayed out in the admin).
On the subfolder blogs, the siteURl and home url do not have the www. But they are not grayed and are in form fields i could change (it appears).
as far as i can remember (like way back wp 3.2) if you are on a multisite the Home Url and the Site Url should be the same otherwise you will have redirect loop problems. why not try to go to your Php admin and change the home and site url there. its normal to see the SiteURL and the HomeURL to be grayed out on the network dashboard
Thanks, I’ll give that a try. I’m thinking just change the HomeURL.
And thanks for Mike’s attention to this!
Suggestions all appreciated.
Woohoo! This issue is resolved.
Thanks very much for the suggestions.
I’m not sure why the “home” was different from the site URL.
Hi!
I need to say thank you, because I get same issue after 3.9 upgrade.
I need to change site and home URL are same.
But now I need to change my default site URL from http://www.domain.com to domain.com (without www). Before 3.9 update the http://www.domain.com works fine.
I try to change every URL options to http://www.domain.com, but this kills whole multisite. Do you have any idea, how can I restore previous URL (www.domain.com) works?
Kind regards,
Jozsef
In trying to solve my issue, I did read up some on changing the URL of a multisite blog and it sounds painful.
If you are just trying to get what you had, you might look at what the siteURL and Home values are.
My site URL remained correct after the upgrade, but the home URL went to www and that (apparently) hosed it. It only affected the top level blog (the one at the root level).
I don’t if that is the same malady that has befallen you?
In my case, the webserver virtual host is set to domain.com and a server alias is set to http://www.domain.com.
— jack lail
It’s not THAT horrible, to be honest.
1) Do a searialized search/replace of the DB, changing http://www.domain.com to http://domain.com – Use https://github.com/interconnectit/Search-Replace-DB for that
2) Edit wp_site and wp_blogs to use NON www
3) Edit wp-config.php to use non www
That’s actually it.
LOL, that’s good to hear. One of the WordPress help guides I saw advised if you’re not a developer to follow a 15-step process. Whoa!
Your suggestion has a lot fewer steps.
I had this same problem and fixed it by changing home in _options table to not include the www in the URL: http://domainname.com. This needs to match siteurl field as well. wp-config was already correct.
Seems to work fine now, thanks for pointing me in the right direction.
I had the same problem on one of my sites
http://www.healthfitnesscorner.com
but the other was fine like the above said once i listed it as http://healthfitnesscorner.com
to match it got fixed.
I made a trac ticket: https://core.trac.wordpress.org/ticket/27927
www shouldn’t be treated like a subdomain, it’s special, but that seems to be what’s going on. Well besides the usual people having both www and non-www in there. That was always going to be odd.
