Restrict access to HTML pages using vBulletins login/password

[EddieVan]

Is there a way to restrict users to access one or more web pages on a web site such that users must be logged into vBulletin to do so? We are actually currently using 3.7 and would like to do the change in 3.7, but we will be moving to 3.8, so I'd like to know the answer for both!

I have checked vBulletin.org and noticed there are some "hacks" that do this for 3.6 and earlier.

Ed

[Lynne]

See either of these articles - How to create your own vBulletin-powered page! (uses vB templates) or [How-To] vBulletin API Basics: Creating Custom Pages & Misc. If you include global.php like those articles do, then you may do any sort of condition on the users id or group to restrict access.

[1Unreal]

You can password protect forums in vB by default. If you used that it would be much more streamlined and easier all round.

[Lynne]

I don't think he is asking about forums, though. I got the impression he was asking about custom pages.

[1Unreal]

Yes but restricting a forum would be easier than a custom page. You would probably have to create a plugin to password protect a custom page. I don't think you could do it with just conditionals.

[Lynne]

Originally Posted by 1Unreal

Yes but restricting a forum would be easier than a custom page. You would probably have to create a plugin to password protect a custom page. I don't think you could do it with just conditionals.

It's pretty easy actually:

PHP Code:

if (!isset($vbulletin->userinfo['userid']) OR $vbulletin->userinfo['userid'] == 0 OR !is_member_of($vbulletin->userinfo,x,y,z))
{
    print_no_permission();
} 


That keeps out all unregistered users and also all users that are not a member of x,y, or z.

[1Unreal]

Hm...Ok. You win.

[EddieVan]

Thanks Lynne.

You are correct. We are automatically generating HTML pages from corporate internal infomation that we would like to restrict access to. The people that we would like to be able to read the pages would be members of our forum, as we are pretty strict on whom those members are. Being able to further restrict based on groups is even better. I had reviewed a few threads here, and the ones I read seemed geared towards specific versions (3.5 and 3.6).

Two other issues we're keeping in mind are: ease to configure that access [after all, there may be many HTML pages, and the will likely be regenerated on a regular basis], and ease for patching vBullein [we'd like to stay current, and don't want to have to re-implement the mod each time].

Thanks again,

[Dismounted]

Originally Posted by EddieVan

ease to configure that access [after all, there may be many HTML pages, and the will likely be regenerated on a regular basis]

Create a separate PHP file with an array that indicates which groups get access. On your files, include that file and use this array for the is_member_of() function.

Originally Posted by EddieVan

ease for patching vBullein [we'd like to stay current, and don't want to have to re-implement the mod each time].

I can nearly guarantee you that is_member_of() will not break.