ianbeyer

It looks like something in 3.9 broke the www. redirects, I’m having all kinds of trouble with my site as well, sites that used to respond to https://www.foo.com the same way they did to foo.com are now responding correctly on foo.com and sending them to the root network/site when going to https://www.foo.com

Any idea how to get the Genesis header image to work with this plugin? The header process doesn’t seem to play nice with the normal header process.

I must not have been looking at the right ones – virtually all the ones I found said “compatible up to 2.something or 3.2.1” or returned “broken” when selecting 3.3 as a version.

I have 8 different domains (and several subdomains of those) pointed at this particular wordpress instance, all of them get different sites. Where WP falls short with networks is the 1:1 ratio between domain names and blogs. I want a many:1 ratio on SOME of the blogs, not all. This is not a case of having multiple domain names funneling into a single blog. Some blogs have a single domain name associated with them, others have more than one.

This used to be solved by using a domain mapping plugin with wordpress MU. As of V3, most of those domain mapping plugins became obsolete due to the merge of MU into the core code. The few that remained going concerns pretty much stopped working after the subsequent point releases.

While that’s a nice tutorial on DNS 101, it’s largely irrelevant to the question. The domains are already pointing to the correct place. What I’m trying to do is have wordpress handle the aliasing – This is not especially difficult with .htaccess rewrites, but since WP is heavily invested in rewrites, it seems silly that it can’t add the requisite redirects internally when creating a network. This should be as simple as adding one or more alias fields in the network setup.

As of now, I can do a redirect manually by pointing those domains to their own hosting directory and putting a 301 redirect in that directory’s .htaccess, but it’s an ugly hack and a pain to manage effectively.

OK, it turns out that there’s a minor bug – You can’t log in to the newly created sites unless you specify a path when you create them, even if it’s “/”. Leaving that blank is not a valid option.

As such, that field should be mandatory or default to “/”.

OK, still having problems after installing the multi-network plugin.

I’m unable to add users to a site (and apparently the admin user is not added by default). Also, when I create a site, I don’t have a dropdown asking me which network to create the site in.

OK, now my head is spinning. ??

It certainly explains why I can’t migrate my other MU install over to 3.0, though.

I thought the whole point of integrating MU into the codebase was so you didn’t have to use plugins for multisite.

I’ve had very bad luck with PJW MIME config, every time I’ve installed it, it’s filled my wp_options table with tens of thousands of duplicate entries, rendering it unusable.

When I try uploading an FLV, it gets to the end and then I get an “HTTP Error” after it tries crunching it.