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

[Logician]

Originally Posted by toucan42

I did a search for "count" and "iterate" on this mod and found nothing (can't handle going through 50 pages of posts) so I will ask my question:

I want to create a page that displays the results of a query in three columns. This means I need code within the query that iterates the records and keeps count - when it reaches three it will end a table row then start a new row.

how can i add code for a multiline recordset such that I can keep a counter as the records are returned?

I wouldn't think it is possible.

[toucan42]

Yeah that's what I am encountering though I may have a method that uses CSS instead of tables for the layout.

Thank you for this awesome hack - this is going to enable so many things for my site.

[tunamix]

Great job with this mod.
Thank you!

[da prez]

does anyone have some created web queries they wouldn't mind sharing ?

thanks

[RollaJedi]

i solved my problems and just want to say thank you to Logician for this great mod!

[toucan42]

I have a question - I am running a web query against a custom table for which many columns are NULL allowed. When I am looping the recordset in the WebQuery it seems that as soon as I encounter a NULL it stops processing that record.

Say my query is:

SELECT field1,field2,field3 FROM sometable WHERE condition = somecondition

in the WebQuery Query Result Row I am assigning the values of fields 1,2 and 3 to a string to be output to the screen:

var someString = '$WQfield[field1]' + ' some words ' + '$WQfield[field2]' + ' more words ' + '$WQfield[field3]'

If field2 is NULL - a valid data condition - field3 never shows up

Not sure if you have a tip on how to preserve NULL but also how to handle it within the WebQuery Query Result Row window?

[toucan42]

Originally Posted by leitel

I am trying to format the output so that ONLY IF there is a 'dept', it will print out.
I tried putting code in the query output area as well as at the main page template.

$WQfield[name]<br/>
<if condition="$WQfield['dept']">
     $WQfield[dept]<br/>
</if>

Thanks!

This question earlier may apply - how can you test the condition of the return set for a field?

[kollam003]

Installed and works like a charm , you have very well explained for even a newbie would do it professionally .

Kudos

Clicks Install

[Wolfhawk]

Awesome product ya created! Thanks a Million! Setup was extremely simple, Your "tutorial" and User Manual is very understandable and easy to follow...Man, the possibilities!

::: Running off to format some templates---Not forgetting to click the Install button and ratings on my way out :::

Great Job Logician! Keep up the good work!

[TigerWare]

Originally Posted by da prez

does anyone have some created web queries they wouldn't mind sharing ?

thanks

Maybe there should be a repository somewhere?

Here is one that I have implemented which appears at the bottom of an article page written in LWT. The idea is to provide readers with snippets of comments made about the page they have just read, plus a visible link to a specific thread in the forum to read fully or add comments of their own. It displays a collapsable table containing the last 3 comments to the specific thread specified in the query. Text from each post is truncated at 500 characters. If there are no replies to the specified threadid, then the table content reverts to a generic "Be the first to add a comment" style.

Query name: $WQ_comments_sometitle
Advanced Query?: Yes
Description: Displays information about comments for this page.

Query: (Required ThreadID is hard-coded in the WHERE clause)

select thr.threadid AS threadid, pst.title AS title, thr.firstpostid AS firstpostid, thr.replycount AS replycount, thr.views AS views, pst.postid AS postid, usr.username AS username, pst.dateline AS dateline, pst.userid AS userid, LEFT(pst.pagetext, 500) AS pagetext FROM thread AS thr LEFT JOIN post AS pst ON(thr.threadid = pst.threadid) LEFT JOIN user AS usr ON(usr.userid = pst.userid) WHERE thr.threadid = 0000 AND pst.postid <> thr.firstpostid  ORDER BY pst.postid DESC LIMIT 3

Query PHPInclude Code (Before): (Required ThreadID is hard-coded in the WHERE clause)

PHP Code:

$queryfirstpostid = $db->query_first("SELECT firstpostid FROM " . TABLE_PREFIX . "thread AS thread WHERE threadid = 0000");
$firstpostid = $queryfirstpostid[firstpostid]; 


The above PHPInclude provides the WebQuery with a variable [$firstpostid], which contains the first post id of the required thread. This variable is consumed in the 'Query No Results Row' which forms part of the link to the thread reply editor screen. (Many thanks to Logican for input on this).

Result Prefix Code:

<div style="padding-bottom:15px">
  <table align="center" border="0" cellpadding="6" cellspacing="1" class="tborder" width="75%">
    <thead>
      <tr><td class="tcat"><a href="#top" onclick="return toggle_collapse('mysite_comments_module')" style="float:right"><img alt="" border="0" id="collapseimg_mysite_comments_module" src="images/buttons/collapse_tcat.gif" /></a>
      <span class="smallfont"><strong>&raquo; Discussion &amp; Comments...</strong></span></td></tr>
    </thead>
    <tbody id="collapseobj_mysite_comments_module" style="">

Query Result Row:

<tr><td><span class="smallfont">&nbsp;</span></td></tr>
      <tr>
        <td class="thead"><a href="showthread.php?t=$WQfield[threadid]" title="[click here to view other comments]" target="_blank">$WQfield[title]</a></td>
      </tr>
      <tr>
        <td class="alt2">
          <div class="smallfont"><strong>Posted By</strong>:&nbsp;<span style="cursor:pointer" onclick="window.open('member.php?u=$WQfield[userid]')">$WQfield[username]</span></div>
          <div class="smallfont"><strong>Posted On</strong>:&nbsp;$WQfield[dateline]</div>
          <br/>
          <table align="center" border="0" cellpadding="6" cellspacing="1" class="tborder" width="95%">
            <tr>
              <td class="alt1">
                $WQfield[pagetext]<span class="smallfont"><a href="showthread.php?p=$WQfield[postid]#post$WQfield[postid]" title="[click here to read more]" target="_blank">...</a></span>
              </td>
            </tr>
          </table>
          <br/>
        </td>
      </tr>
      <tr class="thead"><td><span class="smallfont">Views ($WQfield[views]) - Comments ($WQfield[replycount]) - <a href="showthread.php?t=$WQfield[threadid]" title="[click here to view other comments]" target="_blank">View</a> or <a href="newreply.php?do=newreply&noquote=1&p=$WQfield[firstpostid]" target="_blank" title="[click here to add your comment now]">Add</a> Comments</span></td></tr>

Result Affix Code:

</tbody>
  </table>
</div>

Query No Result Row:

<tr><td class="alt2"><span class="smallfont">Be the first to <a href="newreply.php?do=newreply&noquote=1&p=$firstpostid" target="_blank" title="[click here to add your comment now]">Add</a> a comment.</span></td></tr>

BB Code Parsed Field Names: pagetext (can be omitted if your template is 'text parsed')
Date Parsed Field Names: dateline

[Note: If your template is 'text parsed' please ensure that the HTML shown above contains NO line breaks. This would be interpreted and a hard break added to each line with a <br/> HTML code. This will make the formatting look very strange]

** edit - see below **
The only caveat in the above configuration is the hard-coded id in the Query No Result Row. This is required because the LWT does not parse field result values in anything other than the Query Result Row. If the LWT could parse field values in Result Prefix Code, Result Affix Code and Query No Result Row, it would be utterly fantastic!

@Logican, is my above enhancement suggestion something that you may be planning for a furture version?

** Update **
Text in grey (above) is no longer relevant due to Logican's input. The example has now been enhanced to incorporate suggested php pre-query. Thanks Logican!

Anyway, I hope this gives an idea of what can be done. I am really just starting to learn certain aspects of the LWT, and it helps in learning mySQL syntax too, which is a plus! LWT rocks! :up: