Support for a network with containing a spath?

Sounds like you need to check that mod_rewrite in Apache (or the equivalent in IIS, if that’s what you use) is running. Also check your .htaccess file and make sure the correct rules are in place.

Did you update your .htaccess correctly?

Also, was your choice of blah.local in your example pique or because you’re doing all this on a local PC?

Thanks for the replies.

I’m using apache. Blah.local was just an example, but I am testing this all out locally right now on my PC (with WAMP).

I did not update my .htaccess file, so perhaps that’s the issue. But I’m not sure how I should be updating it. I’m using the WP Multi Network plugin, so I have multiple networks and the other networks do not contain a path like this network does.

So now I’m thinking multiple networks cannot live together if they don’t have the same setup in terms of paths. So I’m testing with a separate, independent install. Can anyone walk me through the steps necessary to create a network which contains a path (blah.com/mypath) and can have blogs underneath it (blogs.com/mypath/my-blog-name)?

I’ve tried setting the $base in wp-config.php, editing the wp_site table so the site contains a path of /mypath, instead of just /. That will create blogs with the correct path (/mypath/my-blog-name) in wp_blogs. But I still get a page not found for these blogs.

I tried updating the .htaccess so that the RewriteBase is /mypath/, but that’s giving me a 500 internal server error.

I gotta be doing something wrong here, as I would have thought this would be pretty straight forward.

I don’t think MultiNetwork works with subfolders, actually… but WordPress MultiSite itself doesn’t work if the path isn’t the same as the actual location (i.e. you can’t run your blog out of domain.com/wordpress but have the URLs be just domain.com, like you can with SingleSite).

I’m thinking multiple networks cannot live together if they don’t have the same setup in terms of paths.

No, they don’t.

you’ve got multiple issues tho – the mod_rewrite in Apache, which has been a bear in WAMP but in XAAMP people have had an easier time.

And then having a different path for one network… which I don’t think can be done.

So this is what I’ve had to do. Someone please correct me if there is an easier way of accomplishing this.

I’ve got an independent install going now just for this single network. No multi network going on.

1) New WP 3.1.1 install with multisite enabled, but no multi network plugin. Installed into a directory named “mypath”, where my apache virtual host points to.
2) In wp-config.php I set:

$base = '/mypath/';
define( 'PATH_CURRENT_SITE', '/mypath/' );

3) Updated wp_site to change the path column from / to /mypath/.
4) In .htaccess, I set the RewriteBase to /mypath/. It seemed I had to install WP into a directory of this name as I mentioned in step 1.

This got almost everything to load correctly. However, on the networks blogs, they couldn’t load their stylesheets. They get a file not found when trying to source them in, so they loaded but without any styling. To solve that, I made an edit to the .htaccess replacing this line:
RewriteRule ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]
With this line:
RewriteRule ^([_0-9a-zA-Z-]+/)(wp-(content|admin|includes).*) $2 [L]

This now gives me a network at blah.com/mypath with blogs under it at blah.com/mypath/this-is-the-blog-name.

Slight correction in step 1 I mentioned above. My apache virtual host points to the directory above “mypath”, not directly to “mypath”. Which seemingly allows “mypath” to function as the rewritebase in the .htaccess as I mentioned in step 4 above already.

Yep, that works.