Michael

mdawaffe,

Because Jetpack was not yet appearing in the automatic updater (early adopter, I guess), I downloaded it from Jetpack.me. Then I manually replaced the “jetpack” folder in /wp-content/plugins.

I already had Jetpack 1.1.3 installed and Network Activated. Three test sites were not connected to Jetpack on WordPress.com and still had the “Learn More” banner message.

For the broken sites with the Debug message, the Sharing link is gone from the Admin → Settings menu, and the Configure button is gone from the Sharing feature’s box (for the working sites, the Sharing settings appeared as expected).

If I try to trick it by going to the “options-general.php?page=sharing” link manually for one of the three test sites, I get the message, “You do not have sufficient permissions to access this page.”

One more thing, on the Jetpack admin page for the problem sites, the Debug bar has the following notice:

NOTICE: wp-content/plugins/jetpack/jetpack.php:1807 - Undefined offset: 1

This notice does not appear on the Jetpack admin page for the sites where Jetpack is working correctly.

Just as a follow up, with the current version of the plugin, 1.5, the following:
@media (max-width: 800px) { }
would become:
@media max-width 800px { }
and

background: #222;
background: -moz-linear-gradient(#252525, #0a0a0a);
background: -o-linear-gradient(#252525, #0a0a0a);
background: -webkit-gradient(linear, 0% 0%, 0% 100%, from(#252525), to(#0a0a0a));
background: -webkit-linear-gradient(#252525, #0a0a0a);

would become:
background:0;

Thank you for pinpointing the line I would need to change, Ov3rfly.

I will wait a few days to see if there is any response from the plugin author. Then I will probably see if I can write a mini plugin to remove the “wp_login_failed” filter and add a function with the patched value.

Thanks for the quick follow-up.
I would be glad to test anything that you can come up with.

We did confirm that the wpCAS-w-LDAP plugin works as intended with the default, single-site setup of WordPress. However, as soon as WordPress 3.2 is configured to use Multisite, the designated user roles are reset upon login to whatever role is supplied by the ‘userrole’ variable.

I can confirm that activating the All in One Video Pack plugin in multisite (subdirectories), either activated on an individual multisite blog or as a network activation, causes the Network Admin page to become a blank page.

Giving the local settings.php file an absolute path in all_in_one_video_pack.php did allow me to access the Network Admin page, but then I got the error “The plugin generated 31313 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.”

Uninstalling for now.

So on my test installation, I discovered that AVH First Defense Against Spam breaks multisite on WordPress 3.1

The key difference from petervanderdoes is that my sites are set up as subdirectories, so https://www.mainsite.tld/newsite

When I create a new site when AVH FDAS is installed, the link to its site-specific Dashboard in the network admin Sites listing is: https://www.mainsite.tld/wp-admin instead of https://www.mainsite.tld/newsite/wp-admin

Also, I get the “Error establishing a database connection” error when trying to directly access https://www.mainsite.tld/newsite/
The site-specific Visit link from the network admin Sites listing is https://www.mainsite.tld/wp-admin/network/sites.php

If I disable AVH FDAS, then create a site in my network, and re-enable AVH FDAS, things seem to work fine. I would suspect that this plug-in only interferes with the site creation process.