Quote:
1) It has to be real integration; not a bridge, and more than just simple user authentication.
|
Real integration will never happen given the differences between the two codes bases. What you're looking for is a better bridge. :)
Quote:
2) The wiki uses the vBulletin user database, and ranks and permissions system. It's not something where vBulletin login information is copied to the wiki database, and users may have to log into both, or automatic side-by-side logins. Rather, it should be like the Drupal and Photopost integration, where it's completely seamless from the user's standpoint.
|
Keeping the usernames in the mediawiki DB just makes it easier to do this without breaking something, it also insures you can upgrade to a stand a lone mediawiki installation in the future (you never know..). The log-in issue can be solved by setting a cookie for mediawiki when someone logs into vBulletin, you can do the same on the media wiki end (setting the vB cookies) so no matter where the log-in they are logged into both systems.
For ranks/permissions you can place some new things in the usergroup manager, and pick up on them during the log-in to mediawiki. Based on the information in the user's vBulletin permissions you can assign them the proper permissions in mediawiki. Just make sure this is done on every log-in attempt so both scripts stay in sync with each other.
Quote:
3) Existing users won't have to change their names. Some bridges and integration hacks require that vBulletin users change their names to remove spaces and other characters that would be invalid in the wiki's namespace.
|
Mediawiki's namespace is odd... You can do this by not coding in any checks to your log-in class, and hacking a few mediawiki files to remove the default checks for this (if you don't do this mediawiki will refuse the name upon log-in). This will break other things however, namely userpages on the wiki.
Quote:
4) The wiki isn't an old-school system that still uses CamelCase, where visible links within an article can't have any spaces (WikkiTikkiTavi, ErfurtWiki, PhpWiki, others). I want to link to articles about urban planning and form-based codes, not UrbanPlanning or FormBasedCodes.
|
Again possible by hacking out some internal checking.
Quote:
5) The wiki won't break when vBulletin is upgraded. The wiki should be easly updated, too.
|
When you get into hacking mediawiki this will be tough. Although as long as you're willing to keep up with your changes, it shouldn't be a problem. vBulletin should not be an issue at all as long as you use the plug-in system for any changes you need to make.
Quote:
6) No vBulletin code is altered.
|
Again, if you use the plug-in system you can get around this. :)
Hope that helps. |
More Information