Want to create your very own vBulletin powered page which includes the header, footer, and the user permissions system as well?
Well now you can
Want to know how it will look? Take a look at the attached screenshot below!
Now includes the Who's Online modification! Also, instructions included on how to create your own pages that are integrated with current vBulletin files!
I'm going to give you a generic page but you can easily modify the contents of the page by changing the template
So here we go
Instructions:
Create a new file, whatever you want to call it (let's say test.php).
Open up test.php and add the following (replace TEST with whatever template you want to show):
PHP Code:
<?php
// ####################### SET PHP ENVIRONMENT ########################### error_reporting(E_ALL & ~E_NOTICE);
// #################### DEFINE IMPORTANT CONSTANTS ####################### define('NO_REGISTER_GLOBALS', 1); define('THIS_SCRIPT', 'test'); // change this depending on your filename
// ################### PRE-CACHE TEMPLATES AND DATA ###################### // get special phrase groups $phrasegroups = array(
);
// get special data templates from the datastore $specialtemplates = array(
);
// pre-cache templates used by all actions $globaltemplates = array( 'TEST', );
// pre-cache templates used by specific actions $actiontemplates = array(
Be sure to change 'TEST' to the actual template name, and change 'test' to the filename. Also, change 'Test Page' to whatever you want to show in the navbar, such as 'Viewing Member Profile' (just an example).
Now create the template, called TEST with the following content:
Replace 'xxx' with whatever you want ?do= in the query string to be (for example, replace 'xxx' with 'showprofile' so then someone would type in example.php?do=showprofile to view this template.) Then of course, change TEMPLATE_XXX to your template name, it's that simple!
Is there a way to block custom pages like these from guests being able to view them unless they log in? with having the link to the pages in the navbar as well?
Is there a way to block custom pages like these from guests being able to view them unless they log in? with having the link to the pages in the navbar as well?
Just use an if condition in the template like this:
HTML Code:
<if condition="$show['member']">
ALL YOUR CONTENT HERE
<else /><tr><td><h2>You need to be registered or logged in to view this page</h2></td></tr></if>
It's not a good idea to do this on the template level. Just add this at the top of your custom code in the php file:
PHP Code:
if (!$vbulletin->userinfo['userid'])
{
print_no_permission();
exit();
}
Cellarius, why is it not a good idea to manage it at template level?, doing it with a template conditional means that it's easily manipulated later by admins...etc rather than having to access server files, unless i'm missing a security flaw or something?
First and foremost: Performance. Why run the whole file, go through the whole variable/template registering and rendering process etc. just to show nothing in the end?
Next, you break UI consistency by not using the usual way of handling such errors: You need to code your error message yourself instead of using the standard no permissions message, which is phrased and thus works with multi language environments.
Last, but not least: There is a standard procedure in vB to do this, and that's the way I did it. Just look at the original files. And if there is a standard way, it should be used.
Anyway, I really don't follow your argumentation - how often do your Admins need to change which usergroups get access to a custom page? This does not seem like a weekly operation to me, does it? This is a set it and forget it decision, is it not?
First and foremost: Performance. Why run the whole file, go through the whole variable/template registering and rendering process etc. just to show nothing in the end?
Next, you break UI consistency by not using the usual way of handling such errors: You need to code your error message yourself instead of using the standard no permissions message, which is phrased and thus works with multi language environments.
Last, but not least: There is a standard procedure in vB to do this, and that's the way I did it. Just look at the original files. And if there is a standard way, it should be used.
Anyway, I really don't follow your argumentation - how often do your Admins need to change which usergroups get access to a custom page? This does not seem like a weekly operation to me, does it? This is a set it and forget it decision, is it not?
Cellarius, don't get me wrong, i'm no coder by any means, it's just thats the way i have always (not too many times) done it. As for the whole admin's....etc changing things, i was purely talking from ease of operation for myself, i have used a similar conditional to allow certain usergroups to view some content, then when i have added usergroups it made it ease for me to find and change. I wasn't questioning your method & capability, just asking for information as to why, now that i know i would implement that, but it does make it difficult for adding or removing usergroups access.
--------------- Added [DATE]1274003452[/DATE] at [TIME]1274003452[/TIME] ---------------
Could it be incorporated in a pluggin where you can state which templates cannot be accessed?
Could you also tell me how to do this in a php statement?
<if condition="is_member_of($vbulletin->userinfo, array(1, 2, 3))">.
Cellarius, don't get me wrong, i'm no coder by any means, it's just thats the way i have always (not too many times) done it.
Of course you are free to do so if you prefer that method, I just don't think it should be recommended, as it just is not how it is done in vB and does have drawbacks.
Quote:
As for the whole admin's....etc changing things, i was purely talking from ease of operation for myself, i have used a similar conditional to allow certain usergroups to view some content, then when i have added usergroups it made it ease for me to find and change.
Then it would be still better to add an AdminCP setting where you can add/change those usergroups easily. You still would have to remember to do it, and a code fragment at the top of a php file seems not harder to find than a conditional in a template, IMHO.
Quote:
I wasn't questioning your method & capability,
I did not take it that way.
Quote:
just asking for information as to why, now that i know i would implement that, but it does make it difficult for adding or removing usergroups access.
As I said: Not really. Opening a php file and changing the code there is not really harder than editing a template. If you don't want to do that, set up an AdminCP setting for it. That would probably be the most comfortable way.
03-03-2004, 10:00 PM
05-14-2010, 01:53 PM
