[Michael Morris]

Ran across the session logout bug mentioned in this thread. This is how I killed it - I'm not familiar enough with mediaWiki yet to fully weigh the ramifications of this stunt. Use with caution.

In file vbWiki.php find this line of code

PHP Code:

require_once( LUX_VB_DIR . "/vbWiki_Hooks.php" ); 


Insert after

PHP Code:

/** Patch - make sure $_SESSION is populated **/
if ((empty($_SESSION['wsUserID']) || empty($_SESSION['wsUserName']) || empty($_SESSION['wsToken'])) && !empty($_COOKIE['seebelow']))
{
    $_SESSION = array_merge( $_SESSION, $db->query_first("SELECT 
        user_id AS wsUserID,
        user_name AS wsUserName,
        user_token AS wsToken
        FROM mw__user
        WHERE user_name = '".addslashes($_COOKIE['seebelow'])."' LIMIT 1"));
} 


To get the above to work you must also change $_COOKIE['seebelow'] following the instructions below. For my board it was

$_COOKIE['enprod_mw__UserName']

This appears to be databasename + underscore + mediawiki prefix + "UserName".

You can discover what the field actually is by calling print_r($_COOKIE); exit; where this code mod occurs to find out what part of the cookie you need to reference to find the username for the wiki.

It is during the code that precedes that vbWiki populates the cookie but for some reason the $_SESSION is left empty - this is why the user is logged out when they go to the wiki and has to log in. Keep in mind that vbulletin doesn't use $_SESSION at all.

The hack above populates $_SESSION with the values necessary to authenticate mediaWiki. It is called after the bridge has already tested the cookie using vbulletin core - so it should be safe.

With the fix above I now have this module running on vBulletin 3.7.2 and MediaWiki 1.12.0