Quote:
Originally Posted by xeagle
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.
|
666 then?
Quote:
Originally Posted by xeagle
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.
|
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.
Quote:
Originally Posted by xeagle
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).
|
Understood, thankyou.
Quote:
Originally Posted by xeagle
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.
|
Understood.
Quote:
Originally Posted by xeagle
A: Latest version of MediaWiki doesn't support usergroups. MediaWiki usergroups support is in progress.
|
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.