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.

Neat! Thanks for the reply! Look forward to the next update.

hello,

i would like to use your single sign on system to have vb users post comments on wp articles. but i do want to keep my wp users (editors / my staff) to create the content.
a couple of weeks/months ago you told me this is on your list - are there any news about it?

also, does your plugin work with the WP Plugin "WP Super Cache" ? Right now I am using the lampwrights plugin for the needs described above, but WP Super Cache doesnt work with it, so I would be happy if vbSSO would solve the problem - would be happy to buy the pro version if it does its job.

Having trouble with "forum/vbsso/profile.php?do=dst" which gives the user a 404 on registration. If I disable vBSSO in vB, it works lite i should.

Hi rmd1,

Answering your first question - yes, it's possible. The recent release of vBSSO vBulletin and vBSSO WordPress supports usergroups <> roles synchronization. To accomplish this, you should create the required roles in WordPress grant them the necessary permissions, configure usergroups in vBulletin, open vBSSO WordPress Settings and connect those roles to the certain vBulletin usergroups. This would connect your users to the certain WordPess roles.

Regarding to the SuperCache, we recommend you to contact vBSSO support team - http://vbsso.com/request-new-feature/ and they would help you to figure out.

It looks like the vBulletin option "Always use Forum URL as Base Path" is turned off. It has to be enabled.

No, thats not it. I do have that option enabled.

Oh, I'm on Nginx if that makes any differens?

It shouldn't make any difference generally. Could you please contact support team http://vbsso.com/report-an-issue/ describing the steps you use to reproduce your case on your website.

Thanks for the reply!!! Trying the new version out ASAP. If it works, I go Pro and spend some money on you guys :)

Any news on an update to the mediawiki version to support synchronous usergroups?

Earlier on August vBSSO expects to deliver the updated extension.

While trying to install VBSSO, why am I getting the error as attached?

I notice with two vBulletin forums one is master and one slave. Is there a way to simply share the two? I was hoping this could be used to link two forums users back and forth via username and e-mail.

The error message clearly states that PHP ZIP extension is missing on hosting where your forum is running. Please ask your hosting facility to install PHP zip extension.

vBSSO doesn't support two ways sync between connected platforms yet. vBulletin is always maser system so far and all the connected platforms are slave ones.

Since my hosting guys installed PHP zip extension, I haven't been able to access AdminCp. Gives a 404 Not Found error. Please advise.

While the forum pages (front-end) seems to be working fine. May be because the Forum page URLs are re-written to be HTML and retrieved as HTML pages (not PHP).

Yes, that might be a reason, we recommend you to review your .htaccess file to identify potential rewrite rules that might break it. Additionally you are free to contact vBSSO support http://vbsso.com/request-new-feature/ sent your .htaccess to let them review and asisst you. Thank you.

I'm having a problem with access rights in the Mediawiki extension.
Trying to limit read access of the wiki to forum members only, I set
in the Mediawiki config.
This however seems to lock out VBSSO completely, the single sign on no longer works.

Whitelisting Special:UserLogin doesn't do a difference either.

The api.php documentation mentions the vbsso plugin requires read rights. How do I assign these?

Hi xeagle ,

are you sure that vbsso is fully compatible with Tapatalk? When I activate vbsso product on vbulletin ( 4.1.11 ) , some tapatalk features doesn't work . In the Tapatalk site, on my control panel I get this:

Obviously the tapatalk API key is inserted correctly into Vbulletin settings --> Tapatalk settings.

Disabling vbsso , everything come to works normally and the error message disappear.

I think there's some issue with tapatalk API key.

Could you check it please?

Never mind, using your latest plugin version , it works. Sorry ;-)

This I great news, xeagle. Look forward to it.

Is there a way to prevent banned users from posting ?

I want to do premium subscriptions on my forum which changes a users usergroup. This seems to work fine in VB but it doesn't change the usergroup in VBSSO for wordpress. This is not allowing me to make it so my users will not see ads on my wordpress site.

My question is how to I make it so it pulls the usergroup from the vb side to do the check as VBSSO only seems to update the usergroup the first time they register/login to WP.

That's not happening, I can see the password change fields when I click edit users or profile in worspress (VB 4.2.1 + WP 3.6)

What exactly is not happening for you? Didn't you turn on the option in wordpress called "Show vBulletin Author Profile" ?

For Joomla any time soon?

As you said in your post that VBSSO actually hides the password change fields in the wordpress so the user can't change the password to avoid any vbulletin > WP sync conflict right? but I just installed the VBSSO on WP 3.6 and I can see the password change fields in Wordpress i-e I can change my password in wordpress..isn't it messed up the VBSSO since it do only one way sync (from vbulletin to wordpress)

bump, any update? regarding the above mentioned issue? what will happen if I change the password from the WP admin panel?

With vBSSO our users cannot reset their vBulletin passwords. They get a mail with a link for resetting the password and when they click it, they only get the following message:
We're using vB 4.1.11 with vBSSO 1.4.12 and Wordpress 3.5.2.

For some reason, when trying to link the databases, I'm thrown an HTTP 417 error code with it claiming that it's "Unable to verify platform."

I'm trying to use MediaWiki 1.20.6. Do I need to go all the way back down to 1.20 specifically?

Are there any news regarding this issue? Some of our users cannot login because of this.