[pmwiki-users] vBulletin 3.5 user system integration

Tim Ahrentlov ta at ateist.org
Fri Jan 20 12:46:40 CST 2006


Hi Patrick,

Thanks for your quick reply. It sounds very promising. Please allow me to
follow up with a couple of questions to your suggestions.

A:    $DefaultPasswords['edit'] = (<person_is_logged_in>) ? '' : '*';

Q: 	What other $DefaultPasswords are there?

---

A: 	$Author = <VB_username>;

Q1:	Will this make the system stop asking for an author name or will it
merely pre-fill it with the VB Username as a default?  

Q2:	What about the link to the VB users profile page? Can I do the
following: $Author=<a
href="http://www.vbulletin.com/forum/member.php?u=1">Administrator</a> and
expect pmwiki to show both name and link?

---

A: if (<user_is_admin>) $DefaultPasswords['admin'] = '';

Q: Will pmwiki still prompt for password for vb users not recognized as
privileged?


Regards
Tim

-----Original Message-----
From: Patrick R. Michaud [mailto:pmichaud at pobox.com] 
Sent: 20. januar 2006 16:41
To: Tim Ahrentlov
Cc: pmwiki-users at pmichaud.com
Subject: Re: [pmwiki-users] vBulletin 3.5 user system integration

On Fri, Jan 20, 2006 at 03:56:06PM +0100, Tim Ahrentlov wrote:
> I'm about to launch a site featuring both vBulletin 3.53 and PMWIKI. The
> community however, has decided that we don't want double user
administration
> and since VB has waaaay the upper hand in this regard I've prepared a
little
> VB script that will do the following:
> ...

Sounds like a terrific idea.   Fortunately, PmWiki makes it
extremely easy to do what you want to do through local
customizations (in the local/config.php file).  In fact, each
one of them is a single line of code in the local/config.php file.

For each one, replace the <...> with whatever variable or code
you want to have that holds the appropriate value.

> 1. Only allow the editing of pages if the person logged-in in VB and
> privileged/trusted. I can use the IP blocking script as a basis for this,
so
> that's ok.

    $DefaultPasswords['edit'] = (<person_is_logged_in>) ? '' : '*';

> A. A username/user-page-link variable that could be set in the config file
> that - once set - override any built in requests for usernames. And of
> course sets the link.

    $Author = <VB_username>;

> B. An IsPrivileged variable that can be set in the config file if the user
> browsing is deemed privileged on an admin level and there's no need to
deny
> him any requests from now on:)

    if (<user_is_admin>) $DefaultPasswords['admin'] = '';

> C. Have a discuss variable that can be set to an URL, and that once set,
> will show up with the "View", "Edit", "History", etc. links on each page.

Just edit the Site.PageActions page on the site and add any additional
urls there.

> Is there anything like the A-C in place for me to tag into already? 

Yes, see above!  :-) :-)

> Then
> can anyone kindly give me some hints as to where this should be
implemented
> and with the least number of lines (perhaps some cookbook recipe that I
> missed) so that the multiple upgrades don't become a pain? :) 

Note that each of the above belong in your local/config.php file;
and don't require modifying any PmWiki scripts.  So, upgrading
shouldn't be a pain at all.  

> Needless to say, to tag into the VB user base could really put pmwiki on
the
> map. 

Gee, I thought PmWiki was already "on the map", or at least on
*a* map.  :-) :-)

Let me know how it works out.

Pm






More information about the pmwiki-users mailing list