[pmwiki-users] allowing existing vbulletin users to edit a pmwiki powered wiki

[Rodney Blackwell]

Hi there,

Thanks for the help so far! I think I have the vbulletin
authentication working (I'm not getting any errors when I load the
pages, but I can't be sure how to test it).

I can't seem to figure out how to "require" that writers/editors must
login (and match the mysql authentication).

So I think these might be my final questions :)

1) How to define the editors group array to set in /local/config.php
so that only logged in vbulletin  members can edit.

I've read the Passwords and AuthUser documentation at pmwiki:
http://www.pmwiki.org/wiki/PmWiki/AuthUser
http://www.pmwiki.org/wiki/PmWiki/Passwords

But I can't seem to figure out the right terminology for requiring
that writers/editors must login and be authenticated by the mysql
database.

I've added "mysql : required for AuthUserMysql" to my site/authuser
page, but that doesn't make it so that editors/writers of any page are
required to login.

2) How to make it so that only certain logged in members in only a
specific "usergroups" within vbulletin can edit.  The user table is
the same (user) and the field I'm trying to pull from is: usergroupid
(specifically usergroupid: 15)

According to this post, it seems like I should be able to set the
editors group as the usergroup's id number (15), but I don't see how I
tell config.php which usergroup is OK and where to find the usergroup
ids:
http://article.gmane.org/gmane.comp.web.wiki.pmwiki.user/21703/match=vbulletin

Thanks again for any help you can give. I thik I almost have this
licked. Once I do, I'll be sure to document my process and add it as a
cookbook recipe for others to use/modify.

Thanks,

Rodney


On 9/28/06, Crisses <crisses at kinhost.org> wrote:
>
>
>
> On Sep 28, 2006, at 10:13 PM, Rodney Blackwell wrote:
>
> On 9/28/06, Ben Wilson <dausha at gmail.com> wrote:
> I believe AuthUserDbase (or XesAuthUserDbase) will allow you to use
> the vBulletin board user table. I finally got AuthUserDbase to work
> (still need to publish the code), after allowing it to sit tantalizing
> for a few months. In the interim, Xes co-opted the code, fixed it and
> improved on it.