MediWiki Integration

[leitel]

Thank you so much for sharing this. I will look it over. I saw that stub class and wondered if it could be used. At this point, I am in the analyzing mode. Input from others like yourself will produce the maximum results. Of course, whatever I/we come up with will be shared.

Thanks!

[ndahiya]

Hi

A couple of small doubts... Does the user have to register for Media Wiki ? I already have a user DB, and getting the ones who want to register again might be cumbersome... If yes, is there some way to "transfer" the userDB?

Just thinking aloud:

IS this a valid (though less elegant) solution: on the edit page of the wiki, check to see if the user is logged onto vbulletin (using the cookie). if not, bump them to the login page... ???

Originally Posted by Kai Backman

MediaWiki has a facility for creating Authentication plugins that let you do the integration pretty easily. They were non-documented when I started with the hack, but once you find the correct template everything was smooth sailing. There are a few comments about the code

- People still need to log on to MediaWiki once, after that they are cookied.
- MediaWiki has a smaller namespace for usernames than vBulletin, on a large board you might have clashes. I'm assuming it's not a security problem, but it might be an inconvenience.
- You need to clean up the user properties pages of things like changing names and stuff (they aren't automatically dropped).
- The Wiki will create only those users who actually log on
- The $usergroupid clauses determine who can create an account, you need to change these clauses to suit your own board.

Have fun!

[leitel]

That is exactly what I am going to do. I have it already working with our OSCommerce site. If there is a cookie, they don't even know that they have been automatically logged into vB. The Wiki is a bit more tricky. Please see article where I have outlined some details.

[Kai Backman]

They don't need to register, MediaWiki creates an account automatically for them the first time they log in. However, the AuthPlugin still requires MediaWiki to have separate user information, even if it's just the name. The comments give more information on how it works.

[leitel]

You're right. What happens in the scenario I mentioned previously is when a user goes to the wiki, it will check vB to see if there is a cookie. If not, they will be taken to vB to login or create an account. The process of creating an account ALSO creates an account in the wiki for them. There a number of preferences, etc that are best maintained in the wiki.

There is still a need to maintain 'connections' to vB and back. For example, see this page as an example to link to vB profile from the wiki.

Hopefully, we will begin coding this next week.

[Mek]

Hi folks, I just tired out Kai Backman's integration authplugin; I was wondering if there is a way to make registering a user on the wiki create a coresponding vbulletin account. Or would I simply turn off the new user creation to force registration on the vbulletin end?

[Viktor Kraft]

Originally Posted by Mek

Hi folks, I just tired out Kai Backman's integration authplugin; I was wondering if there is a way to make registering a user on the wiki create a coresponding vbulletin account. Or would I simply turn off the new user creation to force registration on the vbulletin end?

At least, you can do the second one easily

On your LocalSettings.php find

PHP Code:

require_once( "includes/DefaultSettings.php" ); 


Add below

PHP Code:

# Only sysops can register new users
$wgWhitelistAccount = array ( "sysop" => 1, "developer" => 1 ); 


[Burgy]

Allthough the user integration through MW Authplugin and automatic acount creation in MW if not existant seems to be the most professional solution. There is a miner drowback of how to handle change of preferences and logout situations.

some thoughts about unsolved problems

1. Preferences such as email do exist and are stored twice the vB and MW and should be changed in vB by user and then be updated in MW automaticly
2. Logout should be made global which means that logout manualy in either vB or MW should log out both automaticly to be secure
3. or even better the login in MW should just use the db of vB but not the login procedure then there could serveral MW installations eg german and english been run together useing the centralised vB User Data

The above thougts are not critic but merely helpless nonprogrammer effort to contribute on the grounds of checking possible cases.

shortes way by logic with smalles chance of interference
I do hope that in the end there can be achived a working bridge that does as little as possible except checking user data in the vB Database and producing doubles in MW in order to make things independent. The Preferences which exist twise should be changed in vB because of code copyright bull++++ and then updated in MW automaticaly where only Preferences should be changeble which are nonexistant in vB.


I hope my thoughts might trigger some genius programmers efforts to solve the problem with minimum effort.

Sincerely yours
Burgy Zapp with greatings from Hagenheim

[ndahiya]

hi

i get the following error

Fatal error: Call to a member function on a non-object in /home/jatland/public_html/wiki/includes/SpecialUserlogin.php on line 314

maybe it is coz of the version i am using ? (1.5RC4).. Would really appreciate help on this.. TIA.



also,

Originally Posted by Burgy

some thoughts about unsolved problems

1. Preferences such as email do exist and are stored twice the vB and MW and should be changed in vB by user and then be updated in MW automaticly
2. Logout should be made global which means that logout manualy in either vB or MW should log out both automaticly to be secure
3. or even better the login in MW should just use the db of vB but not the login procedure then there could serveral MW installations eg german and english been run together useing the centralised vB User Data

this would be excellent to have... anyone made any progress on this ?

[Yorixz]

I'm wondering; does anyone have this running with vB3.5 and secondly; is it possible to run MediaWiki on windows?