WebTemplates 3.5.x: VB Integrated CMS (Content Management System)

(This hack is for vb version 3.5.x AND 3.6.x. For vb 3.0.x and 2.x see my profile for relevant threads.)

(For vb 3.7 version, please go to this thread)

"WebTemplates" is a vBulletin integrated Content Management System which allows you to create vb integrated "HTML" pages in your vb admin cp very easily. The pages can inherit your vbulletin skin/style, can recognize logged-in user, can be applied permissions per user or usergroup basis, can keep visit logs, hit counts and do many more.






WEBTEMPLATES 3.5.x BASIC FEATURES:

• Very Easy Installation : Webtemplates can be installed to your board without modifying even a single vbulletin file. It is coded as an pluggin and supports phrase system for user interfaces.
• Apply VB Permissions: You can ban any webtemplate to any user or usergroups easily. So for instance you can design a webtemplate which only members can see while guests can not, or only user A can not see etc.
• Page Counter : Each webtemplate has a built-in counter and you can display page count to your visitors and you can edit it or turn it OFF/ON per webtemplate basis.
• Visitor Logging&Tracking : You can track certain users' (by usergroup or userid) webtemplate visits to see who visited a webtemplate and when. This is configurable per webtemplate basis.
• Site Contributers (Editor) Support : You can grant editing permissions for certain users or usergroups for your webtemplates individually and they will be able to update these webtemplates using their own editor interface. vB's WYSIWYG editor is supported in Editor interface.
• Page Browsers & Who is Online Display: Webtemplates can display who is browsing that webtemplate while visitor is reading them (like default forum browse display of vbulletin). Webtemplate visits can also be monitored in who is online page.
• Header/Footer Inclusion : Webtemplates can automatically use headers/footers (your default vb header/footer or custom ones)
• Help Documents : The script comes with an extensive help document.
• Admin Panel in Webtemplates : Your webtemplates can include an "admin panel" displayed to only admins and by using them you can access many details and stats of your page while you are browsing them.
• SEO friendly URLs: You can make webtemplate URLs seo friendly in vb settings (Requires apache server).
• XML Import/Export : XML Import/Export feature allows you to backup your webtemplates and use other hack users webtemplates in your board.

ADVANCED FEATURES FOR ADVANCED USERS:

• Webquery Feature : With advanced "webquery" feature you can create dynamic webtemplates which include database query results. For instance you can easily add "last 10 threads forum X", "most active users list" etc. to your webtemplates with default webqueries that comes with installation or you can create your custom webqueries with basic SQL knowledge.
• Multi Parsing : Webtemplates can parse PHP or HTML or TEXT (=smilie/img tags/bbcode parsing like vb posts). This means you can design a page just like vb posts (TEXT parsing), standart HTML (HTML parsing) or even in PHP (PHP parsing).
• PHPINCLUDE per webtemplate : Every webtemplate has its own "phpinclude" field which you can run PHP codes before loading the Webtemplate
• Theme Support : Webtemplates support "themes" which are parent webtemplates which include child webtemplates in them. For instance if you have 20 similiar pages which uses the same visual look, you can make a single theme for all of them, then just insert their content into this theme. If you change theme later, all 20 pages' visual will change automatically.
• Conditionals : Webtemplates supports VB3 template conditionals so you can design webtemplates which change their display under different conditions.
• Default variables : You can use/display certain variables in your webtemplates like username of the visitor, visitor email address, last visit time, page creation time, page last edit time, Last visitor name, last visit time etc.

Sample WebTemplates from Sites using this hack:
(Some 3.5 and some are 3.0 versions but WebTemplate look and feel didn't change much so both will give you the idea)
http://www.leatherneck.com/forums/view_aboutus.htm
http://www.hystersisters.com/vb2/view_funding.htm
http://www.theadminzone.com/forums/view.php?pg=aboutus
http://www.hystersisters.com/vb2/view_guidelines.htm
http://www.hystersisters.com/vb2/view_books.htm
http://www3.fertilethoughts.com/foru...hp?pg=acronyms
http://www.makeuptalk.com/forums/vie...alk-newsletter
http://www.bklab.com (entire site is designed with Webtemplates only!)

3.5 version Admin CP screenshot attached to this post. 3.0.x screenshots (here and here) also still applies for this version.

If you use the hack, clicking here will make sure you'll know about updates&bug fixes. It will also help me understand how many people is using the hack so please click the install button if you use it. Thank you..

Note in 6.August. 2006 : I've tested Webtemplates with vbulletin 3.6.0 gold version and they are compatible. So this hack released here is both for vb 3.5.x AND 3.6.x

Note for vb 3.7.x : (29.July.2008): For vb 3.7.x, I released a new version here:
https://vborg.vbsupport.ru/showthread.php?t=186644


Version Updates:
16.Dec.2005 - > Version 3.5.01
* Hack released.
16.Dec.2005 - > Version 3.5.02
* A webquery bug fix for boards which use table_prefix. To upgrade just overwrite hack .php files.
17.Dec.2005 - > Version 3.5.03
* A minor bug in WOL page fixed. To upgrade overwrite hack .php files + reinstall product XML
17.Dec.2005 - > Version 3.5.04
* A bug fix for edit webtemplate page not remembering webtemplate's showbrowsers setting.To upgrade overwrite hack .php files
16.Jan.2006 - > Version 3.5.05
* A bug fix for boards which has too many usergroups. To upgrade overwrite hack .php files + uninstall product, then reinstall (your existing webtemplates will be intact)
20.Aug.2006 - > Version 3.6.00
* A bug fix that can cause a MYSQL warning in a few servers in WT admin cp. A minor and unusual problem that happens in certain servers and you don't need to upgrade if you don't see such a message. To upgrade overwrite /includes/wt_include.php and /admincp/wt_wt.php files.
1.Oct.2006 - > Version 3.6.01
* A minor bug fix for showing user avatar and ipaddress in webtemplates. To upgrade overwrite /includes/wt_include.php and view.php files.
2.May.2007 - > Version 3.6.02
* IMPORTANT SECURITY UPDATE! A security problem has been fixed in this version. To upgrade overwrite /includes/wt_include.php and view.php files which is attached to this post.
21.June.2008 - > Version 3.6.03
* Two minor bugs (1 & 2) fixed.
29.July.2008 - > Version 3.7.00
* A new version for vbulletin 3.7.x is released in a seperate thread here:
https://vborg.vbsupport.ru/showthread.php?t=186644

[dcpaq2xx]

Group,

The htaccess file that is in the forum folder...

I dont see anything in the installation instructions indicating to do anything with it or what it is for.

Is this file suppose to be placed anywhere, and if so what is it for or do?

Thanks

Doug

[Logician]

Originally Posted by dcpaq2

The htaccess file that is in the forum folder...

I dont see anything in the installation instructions indicating to do anything with it or what it is for.

Is this file suppose to be placed anywhere, and if so what is it for or do?

Details in User Manual, section IV : How to Enable Search Engine Friendly WebTemplate URLs

[EasyTarget]

hi Logician, I'm using the latest version of this but I seem to still have permission errors for users with quite a few usergroups.

I have the main user group set to yes and the various other groups set to no, and they get a no permission error.

[Logician]

Originally Posted by EasyTarget

hi Logician, I'm using the latest version of this but I seem to still have permission errors for users with quite a few usergroups.

I have the main user group set to yes and the various other groups set to no, and they get a no permission error.

Sorry but this is not a bug, this is how the permission system works. More info:
https://vborg.vbsupport.ru/showpost....&postcount=118

[bang]

Logician, do you have any plans to add nested categories functionality to this great hack? It would be totally awesome for those that use vBSEO and want to build their site completely around vBulletin, and yet have it SEO'd.

For example, If I could have a site.com/view.php?cat=tutorials&subcat=php&pg=seo, using vBSEO I could turn this into site.com/page/tutorials/php/seo
and so on. plus cateries would make it a lot easier to sort information when there are a lot of pages that need to be created.

[EasyTarget]

Originally Posted by Logician

Sorry but this is not a bug, this is how the permission system works. More info:
https://vborg.vbsupport.ru/showpost....&postcount=118

well according to that post that's the situation with secondary groups, but this is with a primary group.

I have no problems with the permissions on other parts of vb, its just in the pages created with webtemplates.

[Logician]

Originally Posted by EasyTarget

well according to that post that's the situation with secondary groups, but this is with a primary group.

I have no problems with the permissions on other parts of vb, its just in the pages created with webtemplates.

Actually it does not matter whether it is a primary group or secondary. The important point in the hack's permission structure is that, if you check a usergroup as "banned usergroup" for a webtemplate, the user who in any way related to this usergroup (as a member of secondary of primary usergroup) will be denied access.

[Logician]

Originally Posted by bang

Logician, do you have any plans to add nested categories functionality to this great hack? It would be totally awesome for those that use vBSEO and want to build their site completely around vBulletin, and yet have it SEO'd.

For example, If I could have a site.com/view.php?cat=tutorials&subcat=php&pg=seo, using vBSEO I could turn this into site.com/page/tutorials/php/seo
and so on. plus cateries would make it a lot easier to sort information when there are a lot of pages that need to be created.

I'm sorry but I don't have more time to commit for improving this hack. Any hackers who like to improve it has my blessing though.

[EasyTarget]

Originally Posted by Logician

Actually it does not matter whether it is a primary group or secondary. The important point in the hack's permission structure is that, if you check a usergroup as "banned usergroup" for a webtemplate, the user who in any way related to this usergroup (as a member of secondary of primary usergroup) will be denied access.

is there any solution to this besides not using secondary usergroups?

my situation..
its a gaming forum with different teams. The team captain has access to stuff that the rest of his team doesn't. The team captain is a member of the team captain group and his team group. Because this hack handles permissions differently than the forum the team captain can't access the team captain page because he's a member of the team group.

There's also an administration page for admins. Some admins are also team members. The admins can't access their pages because they are also in the team group which can't have access to the administration pages.

[WAR]

Originally Posted by EasyTarget

is there any solution to this besides not using secondary usergroups?

my situation..
its a gaming forum with different teams. The team captain has access to stuff that the rest of his team doesn't. The team captain is a member of the team captain group and his team group. Because this hack handles permissions differently than the forum the team captain can't access the team captain page because he's a member of the team group.

There's also an administration page for admins. Some admins are also team members. The admins can't access their pages because they are also in the team group which can't have access to the administration pages.

That was the same problem that I ran into. It's just a different mindset for how you are using vbulletin's permission system compared to how Logician apparently uses it (both being perfectly valid methods)

Here is one fix:

WARNING: The following changes will completely reverse the way that Logician has set up the permissions for this Hack. DO NOT USE this unless you completely understand what it is for!!!

function WT_UsergroupPermission($userinfo, $return10 = 1, $usergroupname = '')
{
	global $WT;  

	$permitted = 0;

	$WT['banusergroups'] = trim($WT['banusergroups']);

	if ($WT['banusergroups'])
	{
		$WT_banusergroups = explode(" ", $WT['banusergroups']);
		
		if (WTis_member_of($userinfo, $WT_banusergroups)) 
		{
			$permitted = 1;
		} 
		else 
		{
			$permitted = 0;
		}
		
		if ($userinfo[userid] > 0 AND in_array('('.$userinfo[userid].')', $WT_banusergroups)) 
		{
			$permitted = 1;
		}
	}


	
	if ($WT['draft'] == 1 AND !WTis_member_of($userinfo, array("6"))) //draft webtemplate
	{
		$permitted = 0;
	}

	if ($return10) //return 1 or 0
	{
		return $permitted;
	}
    else //return usergroup name with color (permitten green, banned red)
	{
		if ($permitted) 
		{
			return '<font color="#006600">'.$usergroupname.'</font>';
		}
		else 
		{
			return '<font color="#C40000">'.$usergroupname.'</font>';
		}
	}

}

EasyTarget, if you replace the default "function WT_UsergroupPermission" code found in wt_include.php with the above version, it will switch the way webtemplates permissions work from being an "opt-out" system to being an "opt-in" system. What that means is that the section marked
"Disallowed Usergroups
Mark usergroups who can NOT display this page"

Should now be treated as if it said
"Allowed Usergroups
Mark usergroups who CAN display this page"

and the "Disallowed Usernames" section should be treated as if it read:
"Allowed Usernames
Enter usernames who CAN display this page even if their usergroup is disallowed."

The above text will NOT ACTUALLY CHANGE unless you go in and edit it (I haven't bothered yet so I am not sure where it is), but you need to realize that by applying the above code you have completely changed how webtemplates processes usergroup permissions.

Logician is in no way responsible for the above change, and I am officially recommending that you do not apply this change unless you completely understand exactly what it does and are willing to accept complete responsibility for anything it or you may mess up in the process. (the code does work though, I have it running on two different live sites)