Thanks for the reply, man. I kinda gave up on Wordpress as it just would not connect properly, however, I have had more success with mediawiki (of a sort), which leads me to...
Xeagle,

I've managed to get this connected to MediaWiki 1.20.6, however, I'm having some real difficulties understanding what each setting is supposed to do.

You've made something that looks awesome. The downside of that is that you now get a load of demanding people trying to use it! :D

I need help... but you guys seriously need some step-by-step documentation and definitions! So I figured I'd construct my question in a way that starts making that documentation for you... and you can fill in the blanks.

Things you need to clarify are in red.

Here is my current Vbulletin-MediaWiki set-up:

Step 1: vBulletin Installation

• Upload everything from the unzipped "upload" folder to the `/` root directory of forum (in my case "/vb")
• Log in to forum Admin Control Panel as administrator
• Navigate to 'Plugins & Products' section
• Expand section and click on the 'Manage Products' link
• Scroll down in the right-hand frame until you find 'Add/Import Product' link
• Click on the link and browse for vbsso.xml file
• Click on the import button

Step 2: MediaWiki Installation

• Download MediaWiki vBSSO.
• Unzip and upload everything to `/extensions/vbsso/` directory of your MediaWiki installation.
• Log in to MediaWiki as administrator.
• Open `LocalSettings.php` file in the root of MediaWiki installation and add:
  
  Code:

  ---

  require_once( “$IP/extensions/vbsso/vbsso.php” );

  ---

• Make sure that *.conf files are writable. (I see two such files: "platform.conf" and "vbsso.conf" - who should they be writable to? At the point of installation, chmod is set to 644. Is this enough?)

Step 3: MediaWiki Configuration

• Log into Administrator account on MediaWiki installation.
• Navigate to 'Special Pages'.
• At the bottom, under 'Other special pages', click 'vBSSO' and you will be taken to the 'Special:Vbssoconfig' page.
• Fill in the shared platform key to one of your choice (this will need to match what you put in vBulletin in the next step).
• Click Submit.
• Your completed form should now look like this:
  
  https://vborg.vbsupport.ru/external/2013/05/7.png

Step 4: vBulletin Configuration

• Log in to forum Admin Control Panel as administrator
• Navigate to the vBSSO section near the top of the left-hand frame
• Expand the section and click 'Connect a Platform'
• Insert the respective details from the wiki's 'Special:Vbssoconfig' page. Your completed form should look like this:
  
  https://vborg.vbsupport.ru/external/2013/05/8.png
  
  
• Click 'Connect'.
• After receiving confirmation, you should now have the following connection in green at the bottom of the page:
  
  https://vborg.vbsupport.ru/external/2013/05/9.png

At this point, any vBulletin account can successfully log into MediaWiki as a 'User'. However, I would like to restrict this to particular usergroups. In the example below, I go to 'Access Settings' and set the usergroup to 6 (vBulletin Admin usergroup number).

https://vborg.vbsupport.ru/external/2013/05/10.png

Despite this, it's still permitting access to other usergroups. 'Registered Users' (usergroup 2) are able to log into and edit the wiki.

Further questions that aren't clear to me:

• What do the 'Login Access Setting' do, and why are they arranged in a 2x2 checkbox formation? They don't seem to have an effect.
  
  
• If I were to remove the top-right checkbox (the only one I can toggle in the example above), what is supposed to be the effect?
  
  
• Also, what is the effect of the 'Connection Settings' and 'Master Platform'? On installation, I left it alone, but have since changed it to match the MediaWiki key, as shown below. Again, it has not made much difference.
  
  https://vborg.vbsupport.ru/external/2013/05/11.png
  
  
• Assuming the plugin does handle usergroups, how does the plugin handle a change of usergroup? So if I ban someone in vBulletin, is their access revoked in MediaWiki too?

tambo, great start for knowledge base! Unfortunately we admit there is a lack of useful documentation and the summer is a season when vBSSO is committed to change this to the better state.

Regarding to your questions:
Q: Make sure that *.conf files are writable. (I see two such files: "platform.conf" and "vbsso.conf" - who should they be writable to? At the point of installation, chmod is set to 644. Is this enough?)

A: platform.conf and vbsso.conf. In most cases 644 is not enough, because the web application server should have a permission to update those files.

Q: Despite this, it's still permitting access to other usergroups. 'Registered Users' (usergroup 2) are able to log into and edit the wiki.

A: It shouldn't happen, we will check it.

Q: What do the 'Login Access Setting' do, and why are they arranged in a 2x2 checkbox formation? They don't seem to have an effect.

A: It's another type of configuration. For example if there are more than 2 platforms connected to vBulletin it makes sense to log user from WordPress and skip sign-in to MediaWIki for example and it's regulated by checkbox from left(source platform) to right(destination platform).

Q: Also, what is the effect of the 'Connection Settings' and 'Master Platform'? On installation, I left it alone, but have since changed it to match the MediaWiki key, as shown below. Again, it has not made much difference.

A: Connection Settings are used if you want to connect one vBulletin forum to another one and slave forum settings are configured at Connection Settings.

Q: Assuming the plugin does handle usergroups, how does the plugin handle a change of usergroup? So if I ban someone in vBulletin, is their access revoked in MediaWiki too?

A: Latest version of MediaWiki doesn't support usergroups. MediaWiki usergroups support is in progress.

We hope our answers bring more understanding to you.

I went to install this on a VB 4.2 install today and in doing the import, it returned these errors:

We have identified the potential buggy hooks / plugins conflicted with vBSSO. If you experience any issues with vBSSO, please resolve the conflicts before contacting the support team.
You need to replace highlighted code with this pattern:
require_once(DIR . '/path/to/plugin/file.php');

Title Hook Location Hook code
GlowHost - Spam-O-Matic: AKISMET SPAM filter newpost_process
require_once('includes/functions_ghsom.php');

GlowHost - Spam-O-Matic: Finish Registration register_addmember_complete
require_once('includes/functions_ghsom.php');
SOM_UpdateLog();
GlowHost - Spam-O-Matic: Registration Pre-Check register_addmember_process
require_once('includes/functions_ghsom.php');
SOM_Process();
GlowHost - Spam-O-Matic: First Post/Thread Control threadfpdata_presave
require_once('includes/functions_ghsom.php');

GlowHost - Spam-O-Matic: Replies Control postdata_presave
require_once('includes/functions_ghsom.php');

Form actions inlinemod_action_switch
require_once('includes/functions_ghsom.php');
SOM_cleanupProcess();

666 then?

Hmmm... so, as I understand it, only the array of vBulletin usergroups IDs defined in 'Access Settings' should be provided access to the default "Users" MediaWiki usergroup?

For your info, I'm running vB 4.2.1 and MW 1.20.6.

Do you require access to my test site to verify/compare?

Happy to do so, if needed.
Understood, thankyou.

Understood.

Being able to match specific vB usergroup IDs to specific MediWiki usergroup names (and have a change in the vBulletin usergroup effect a change in the MediWiki usergroup) would be pretty much awesome.

Chris, try please go over those hooks ("Plugins & Products" section) and replace the includes in require_once('lib') with the require_once(DIR . '/lib'); where "lib" is included script.

#1 Just ensure that your *.conf files are writable by application server, so, keep using extension connecting mediawiki to vBulletin.

#2 if 'Access Settings' is specified, yes, access only to those certain usergroups is allowed, otherwise for all.

If you have a more tech questions please don't hesitate to contact vBSSO support team. :)

xeagle-
Has your team been successful in making this modification work with "https" for a member that paid for it? I've been waiting for quite some time. Do I need to take the time to see if I can make the changes to the code myself?

I really like this plug-in but it will not work for me!

The latests version of vBSSO support https connection between vBulletin and WordPress. So, vBSSO readme.txt was updated for WordPress, please feel free to give it a try.

Were you able to replicate this, or do I need to work on my installation?

Cheers

The issue was replicated and fix would be actually a part of soonest vBSSO vBulletin update with features and improvements.