I got this [http://slamlander.caselle-vpn.net/?p=21] :
Warning: Cannot modify header information – headers already sent by (output started at C:InetpubVwebSlamlanderwikiextensionsAuthPress.php:352) in C:InetpubVwebSlamlanderwikiincludesWebResponse.php on line 11
What I did:
On current install on integrated WP and BBP, added a “wiki/” directory and unpacked mediawiki 1.10.1 there, ran the install, and used the same DB. The wiki, at this time works stand-alone. What’s happening here is a version incompatibility issue, methinks, betwixt Authpress and MediaWiki. There are some code structure changes from 1.9.x to 1.10.1 but I don’t know what they were.
I do know one thing, no one has submitted this to the MediaWiki team, why not? I should have been able to download it from there and I could even get help from them, if it were submitted.
Jaithan, I wouldn’t be using WPMU. Rather, I’d be using current WP, 2.3.1 and wait for the WPMU to get upgraded, sorry.
The reasons are that we cannot rely on WPMU to remain stable, since they have to bring that up to 2.3.1 standards. I would suspect that it would be easier to add MU features to 2.3.1 than to bring WPMU up to snuff. For one thing, they went to a role-based authentication/security model, which also makes it much easier to integrate with MediaWiki, BTW.
So, if I get this right;
1) Install WordPress (current version, 2.3.1)
2) Install and integrate BBpress (current version)
3) Install MediaWiki (current version, 1.10.x)
Making sure that they all use the same data container and not to let MediaWiki set any prefixes.
Okay, that should integrate the Auth stuff and some judicious use of DB triggers (using MySQL5) might actually take care of most of the fleas. However, to be real Enterprise 2.0 here, the themes have to integrate aas well. Also, has anyone got WordPress to authenticate against an Active Directory Domain, like they have for MediaWiki?.
