As for WP_ALLOW_MULTISITE, the support team at HostGator did some tinkering with it. that line currently reads:
define( ‘MULTISITE’, true ); //hg commented this, to be replaced by next line:
//define( ‘WP_ALLOW_MULTISITE’, true );
Toggling the commented lines to:
//define( ‘MULTISITE’, true ); //hg commented this, to be replaced by next line:
define( ‘WP_ALLOW_MULTISITE’, true );
Oh my LORD. Will you please tell HG support that those two lines do *two different things*? You need both of them. One of them very specifically tells wordpress that multisite is in use.
What happens when you go to http://www.abetterworldbydesign.com/wp-admin/network/ ?
And yes. it’s something specific to your install that is borking. JUST to get that out there, in case support needs to know. 😛
Thread Starter
mrengy
(@mrengy)
Don’t get me started on HG support. I’ve given up hope on them long ago.
http://www.abetterworldbydesign.com/wp-admin/network/
redirects to
http://wp-admin/network/
any uppercase letters in the domain name anywhere?
Thread Starter
mrengy
(@mrengy)
Nope. At least not in the database tables I checked in this post. I also did a quick scan through the database for any other fields in the database that contained the domain and didn’t find any.
Thread Starter
mrengy
(@mrengy)
Sounds as though it might be related to http://core.trac.wordpress.org/ticket/17168
However, I’m not sure how to proceed.
That was more related to people who get redirected to the NON www version of their url. yours is being removed entirely. :-/
Thread Starter
mrengy
(@mrengy)
Another HostGator support rep (who seems to be quite a bit more competent) has picked up the ticket. Here’s the info he provided:
“In the file: wp-includes/link-template.php on about line 2168 there is the definition for the function named ‘network_site_url’, which is essentially where the invalid URL gets generated. In that function, there is a line:
$url = $scheme . ‘://’ . $current_site->domain . $current_site->path;
This is where the glitch occurs, as the variable $current_site is completely empty.”
Does that help?
Marginally. 🙂 Now we have to determine why, on your site, $current_site is empty.
Thread Starter
mrengy
(@mrengy)
Eureka.
I had written a function in my theme’s functions.php to store the current version of the site I was working on “production”, “stage”, “dev”, or “local”. Not knowing that WordPress core used the variable “$current_site”, I named my custom variable “$current_site”, and it was overwriting the value that should have been there.
I did this as a workaround because the Simple Fields plugin, while awesome, doesn’t support displaying images by title – it requires calling their IDs (which vary from production to stage to dev to local) to display. I wrote a post on the plugin forum about this.
Changing the “$current_site” variable in my theme to “$site_version” resolved the issue.
Thread Starter
mrengy
(@mrengy)
Couldn’t have done it without all of your help. Many thanks!
