DrCherry

That must be it.

Using: W3 Total Cache, Omniture – SiteCatalyst, JSON API, Google News Sitemap Feed With Multisite Support, and Embedly.

W3 Total Cache is a pain to re-enable for each blog. I’ll do some testing next week and try to figure out which two conflict.

What was strange is that some of the blogs wouldn’t allow the creation of new categories and others would. It may have been blogs we added after one of the conflicting plugins was added. I’ll try to be more scientific about tracking down which ones interact badly.

To add to the complication some are activated at the network level and others at the blog level.

Thanks, it appears to be the WordPress SEO by Yoast plugin with WP 3.2.1 network install.

I’ll keep testing to see if there are others.

I must say that losing core functionality because of a javascript conflict seems slightly more than trivial. I’ll report it to the plugin author.

I’ve got the same problem on a 3.2.1 networked/multi site install. I did some research on the forums and there’s probably four closed threads on this issue going back three years.

I would first test that address by removing wp from the directory and putting a simple html file out there.

Then I would test php by putting a simple php file out there with <?php phpinfo(); ?> in it to make sure php was working and to the version was correct.

I have a feeling that it’s a httpd server config issue.

The MU plugin is depreciated with the latest WP release. The additional db tables are created when blogs are created via the administration UI.

“My” method is following the instructions here precisely:

https://codex.www.ads-software.com/Create_A_Network

There should be no need to delete tables, or improvise steps.

The .htaccess file is not created automatically, you’ll have to create it yourself and chmod it to 644.

I resolved this issue myself. I was missing this directive in my wp-config.php

define('MULTISITE', true);

I guess it seemed superflous to have both of these directives:

define('WP_ALLOW_MULTISITE', true);
define('MULTISITE', true);

Yet both are obviously necessary. Thanks for all the help.

I’m also working on this process today and I don’t think the instructions call for “clearing out” the single blog install.

I’m working from this document:

https://codex.www.ads-software.com/Create_A_Network

The way I understand them, we’re supposed to install wp normally, then follow the instructions for enabling the Network functions. I don’t remember seeing anything there about clearing anything out.

I’m finding this link which sort of infers that it’s possible:

https://www.ads-software.com/support/topic/sub-directory-install-setting-up-a-base-directory-for-network-sites?replies=5

Yes, that was guide I used. I checked the requirements before I started.

Are you saying that I can’t install a networked installation in a subdirectory? If so, the documentation isn’t extremely clear on that point.

According to that document, these are the cases where it will not work:

“WordPress address (URL)” is different from “Site address (URL)”.

Does this preclude subdirectories?

If your existing WordPress installation has been set up for more than a month, due to issues with existing permalinks. (This problem will be fixed in a future version. See Switching between subdomains and subfolders for more information.)

this was not the case.