Knowledgebase : Design Templates
   

To add navigation links on any area navigation bar ( trial / members etc) you'll need to edit the template file header.tpl on line 316. For the tour navigation bar you will need to edit /tour/header.tpl begining on line 121.

We highly recommend using template fields for the text areas of the navigation bar so they can be changed at a later date and so that they can have support for multiple languages.

Please let us know if you have any questions about editing the navigation bar links by opening a support ticket.

The CMS does NOT directly integrate with or interface with your payment processor.

If you have a single join URL you can enter it in your tour admins JOIN URL  setting for your tour. This will link up all join links to use that URL.

If you wish to have multiple payment processor options(Credit Card, Check, Phone, TEXT/SMS) then you'll need to edit the join.tpl file located in your theme area.

Included within your cms templates within

PHP Templates:

/cms_admin/phptemplates/[templatefolder]/tour/join.tpl

Within this template, you'll put the URL and text you want to display for each of the payment options. Take a look at the join pages of some sites and get ideas. Your payment processor will install their script to manage users and should be able to give you more info on the join forms and such. If you need help with customizing this form, let us know and we can recommend 3rd party coders and designers to help you.

You can use the debug to see what fields are available(Add the following to the URL of the generated gallery):

index_debug.html

This should display a list of fields available.

Take a look at:
$set['info']['models'][0]['extrafields']['age']

As an example.

Flags available within cmsinclude.ini.php

Here are a list of the current flags available within cmsinclude.ini.php.

Note - Some flags may only be supported by certain versions and may not work with older versions of the software. Use of these flags is only suggested for advanced users and may only apply to customizations made to XSL or Smarty templates. Support of the features listed here are not routinely considered part of our standard product support and additional support charges may apply for assistance with these features.


ADMINPREVIEW
If set to 1, shows all content in the future.  This is put in place so you can potentially set up an internal members area to preview new content before it's released to the public.

ALLSITES_EXCLUDE
On the index page, exclude these All Access sites from being listed.

AUTHFUNC
By default, ElevatedX determines what user is logged in by looking at the value of $_SERVER["PHP_AUTH_USER"].  If set, the system will instead look at a user-defined function that returns the username.
This is useful if the user is using third-party authentication, or internally developed authentication.  Note: Strongbox users won't need to use this function as StrongBox sets the value of $_SERVER["PHP_AUTH_USER"];

CACHE_LOCATION
By default, the CMS stores any cached files within the location /cms_admin/storage/cache/ However, if you have multiple servers, you MAY increase performance by storing your cached files locally instead of reading them over a network.  This variable lets you set the cache location.

CACHEDEPENDENCY_FUNC
This flag allows you to integrate custom code that lets you do manipulate the cache engine that the system uses.  You can find out more about this use under "Integrating Custom PHP Code" here:
https://support.elevatedx.com/index.php?/Knowledgebase/Article/View/85/0/integrate-custom-php-code

CACHE_GETVARS
By default, the system's caching system uses a list of parameters that specifies whether or not a cached copy of the page should be loaded, or a new page should be generated.
Sometimes, if a custom template is being used, a variable such as {$smarty.get.varname} might be used. This, however, is not recognized by our caching system. In order to mitigate this, CACHE_GETVARS allows a comma delimited list of $_GET variables that should be added to the caching engine.

CACHE_POSTVARS
By default, the system's caching system uses a list of parameters that specifies whether or not a cached copy of the page should be loaded, or a new page should be generated.
Sometimes, if a custom template is being used, a variable such as {$smarty.post.varname} might be used. This, however, is not recognized by our caching system. In order to mitigate this, CACHE_POSTVARS allows a comma delimited list of $_POST variables that should be added to the caching engine.

CACHE_COOKIEVARS
By default, the system's caching system uses a list of parameters that specifies whether or not a cached copy of the page should be loaded, or a new page should be generated.
Sometimes, if a custom template is being used, a variable such as {$smarty.cookie.varname} might be used. This, however, is not recognized by our caching system. In order to mitigate this, CACHE_COOKIEVARS allows a comma delimited list of $_COOKIE variables that should be added to the caching engine.

CACHE_REQUESTVARS
By default, the system's caching system uses a list of parameters that specifies whether or not a cached copy of the page should be loaded, or a new page should be generated.
Sometimes, if a custom template is being used, a variable such as {$smarty.request.varname} might be used. This, however, is not recognized by our caching system. In order to mitigate this, CACHE_REQUESTVARS allows a comma delimited list of $_REQUEST variables that should be added to the caching engine.

CALENDAR_ADDSITES
If set, includes other All-Access sites within the calendar apart from the standard site.

CATEGORY_ALLSITES
In an All-Access Setup, if this is set to 1, display all content from all All Access Sites instead of just content from the one All-Access Subsite.

CATEGORY_SORTSITEFIRST
If CATEGORY_ALLSITES is set to 1 and CATEGORY_SORTSITEFIRST is set to 1, show all content from all sites within All-Access, but display content from the folder's All-Access site id first.

COMINGSOON_OTHERSITEUPDATES
If set to 1, allows within the XML Document / Smarty Array to display future content from All-Access sites other than the current site.

DEFAULTLANGUAGE
By default, the system language served to a user logging into the site is LANGUAGE=0 (Generally English).  However, if you have multi-language support, you can use this flag to set the default language this area will load. It will still allow users to select other languages via a drop down.

Note: This cannot be used with the LANGUAGE flag.

HIDE_MEDIATYPES
If set, allows the system to hide specific media types from showing within a specific members / trial area.

INDEXLIST_LIMITMODEL
If set to 1, limit all index updates to this specific Model Id number.  E.g: If "Jane" is Model Id 7, setting INDEXLIST_LIMITMODEL to 7 will only show updates from "Jane" on the front page.

INDEX_OTHERSITEUPDATES
If this value is set, add to the XML Document / Smarty Array the ability to list updates from separate sites on the index page. e.g: If this value is set to "1,2:3,4", this will create two separate lists: One with sites 1 and 2, and the other with sites 3,4.

LANGUAGE
By default, the system language served to a user logging into the site is LANGUAGE=0 (Generally English).  However, if you have multi-language support, you can use this flag to set the language this area will load. It will disable the user from being able to select another language from the drop down.

Note: This cannot be used with the DEFAULTLANGUAGE flag.

MOBILE
If set to 1, turns off detection and unconditionally loads a mobile area / template.
If set to 0, turns off detection and unconditionally loads a desktop area / template.

MOBILE_SMARTY_FOLDER
If set, overrides the template folder used by the system when a mobile area is loaded.

MOBILE_TEMPLATELANGUAGE
If set, overrides the default template language used by the system when a mobile area is loaded.  Valid values are "xsl" and "smarty" (both must be lower case)

MODEL_GENDERLIMIT
If set, limits the model listing page to either Male or Female models. Valid values here are M or F.

NOOFFERS
If this value is set to 1, this area will not show any full page offers.

POSTPROCESS
This flag allows you to integrate custom code that lets you do alterations on any HTML that the system returns before printing it out.  You can find out more about this use under "Integrating Custom PHP Code" here:
 http://support.elevatedx.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=123

PUBLICAREA
If PUBLICAREA is set to 1, the system treats this area as public.  Within plugins such as News, one can set released content for either the internal members area, public area, or both.  Also, it is possible to go into setup and configure different templates to be used specifically for the public area.

REDIRECT_DESKTOP
If this value is set, redirect a desktop user to a separate URL. This way, this specific folder is only viewable to mobile devices.
Note: This cannot be used with the MOBILE flag being set.

REDIRECT_MOBILE
If this value is set, redirect a mobile user to a separate URL. This way, this specific folder is only viewable to desktop devices.
Note: This cannot be used with the MOBILE flag being set.

RSS
If this value is set to 1, load the RSS feed by default. This is useful if you're looking to have your RSS feed specifically within a separate folder. (e.g: /rss/)

SEARCH_OVERRIDEQUERY (deprecated)
This flag allows you to override the search query the system uses in case you wish to change the way searches are done via the database. In this case, you can define a custom function that will override search.php functionality and perform its own query against the database. The custom function should return the result set of the query you perform within the function. This result set is in an array form, and in Smarty is what gets populated in $root.page.results.result.

The hook for this system is similar to the POSTPROCESS flag used by the system. You can see more information on that here:
https://support.elevatedx.com/index.php?/Knowledgebase/Article/View/85/0/integrate-custom-php-code

SMARTY_FOLDER
If set, overrides the template folder used by the system.

SUBSITE_ID
If set, determines which site within all-access this members area folder should display.

TEMPLATELANGUAGE
If set, overrides the default template language used by the system.  Valid values are "xsl" and "smarty" (both must be lower case)

TOUR_ID
If set, determines which tour within the tour-plugin this area is using.

TRIAL
If set, determines which trial within the trial-plugin this area is using.

XSL_FOLDER
If set, overrides the template folder used by the system.

Gallery Builder Templates (Smarty)   (For PHP based FHG template guide please visit this link.)

Please follow the example files located in your smarty/smarty0 folder.

Using the included default templates as a guide you will need to edit the HTML of your own template files to include the code from the photos and/or videos smarty files. You’ll need to save your template using the extension .tpl

IMPORTANT –
The images folder must be named the same as the template so photos.tpl has a folder named photos. A template named blue_15pics.tpl would have a folder named /blue_15pics

Join Link Code Tags:

This tag will append the join URL you enter in the admin panel for this template. If you prefer not to have the system populate these tags you can hard code your join links into the templates.

<a href="{$root.template.JoinURL}"></a>

For each spot in the template you want a photo thumbnail to appear, use the following tag set.

{include file="photo_item.tpl" index="1"}


The index="1" refers to the location of the photo in the template. When you edit a template in the cms admin panel, Location 1 corresponds to this location. Each spot must be defined with a number that corresponds to its Location in the template as defined in admin. For example if you have a gallery with 10 photos, you would have 10 instances of the tag set above,  ranging from [1] to [10].

e.g:
{include file="photo_item.tpl" index="1"}

{include file="photo_item.tpl" index="2"}

{include file="photo_item.tpl" index="3"}

{include file="photo_item.tpl" index="4"}

{include file="photo_item.tpl" index="5"}

The same is done for movies, however, the template being loaded is movie_item.tpl as in the following example:

{include file="movie_item.tpl" index="1"}

{include file="movie_item.tpl" index="2"}

{include file="movie_item.tpl" index="3"}

Common tags that can be used to show content in a template:

Appear Date : {$root.contentgroup[0].AppearDate}
Expiration Date : {$root.contentgroup[0].ExpireDate}
Title : {$root.contentgroup[0].Title}
Description : {$root.contentgroup[0].Description}
Folder name in CMS : {$root.contentgroup[0].Directory}
Gallery Folder : {$root.folder}
Join URL : {$root.template.JoinURL}

Extra Fields:
{$root.contentgroup[0].extrafields.FIELDNAME[0]}
(Where FieldName is the extrafield you have set up for that set)

Models associated with update:
{foreach from=$root.contentgroup[0].PreviewXML.sets.set item="item" name="loopCN"}
{$item.ModelName[0]}
{if !$smarty.foreach.loopCN.last },&nbsp;{/if}
{/foreach}

Advanced templating (for Smarty Experts)
When generating a smarty gallery, the system creates a file called index_debug.html within the destination folder of the gallery. Viewing this file will give you a complete dump of the information available to the user. Please use this file or a reference if looking to do anything more advanced.




Note: This is for the deprecated XSL template system.  For version 3.2 of our software, check out the article:

Gallery Builder Templates (Smarty)

 

Gallery Builder Templates (XSL)

Please follow the example files located in your xsl/xsl0/gallerybuilder folder.

Using the included default templates as a guide you will need to edit the HTML of your own template files to include the code from the photos and/or videos xsl files. You’ll need to save your template using the extension .xsl

IMPORTANT –
The images folder must be named the same as the template so photos.xsl has a folder named photos. A template named blue_15pics.xsl would have a folder named /blue_15pics

Join Link Code Tags:

This tag will append the join URL you enter in the admin panel for this template. If you prefer not to have the system populate these tags you can hard code your join links into the templates.

<a href="{/root/template/JoinURL}"></a>

For each spot in the template you want a photo thumbnail to appear, use the following tag set.

<xsl:call-template name="showitem">
<xsl:with-param name="item" select="/root/content/item[@type='image'][1]" />
</xsl:call-template>

The [1] refers to the location of the photo in the template. When you edit a template in the cms admin panel, Location 1 corresponds to this location. Each spot must be defined with a number that corresponds to its Location in the template as defined in admin. For example if you have a gallery with 10 photos, you would have 10 instances of the tag set above, with the brackets ranging from [1] to [10].

The same is done for movies, however, type=’image’ should be changed to type=’movie’ as in the following example:

<xsl:call-template name="showitem">
<xsl:with-param name="item" select="/root/content/item[@type='movie'][1]" />
</xsl:call-template>

Towards the bottom of the template code you’ll see the following:

<a href=".{$item/files/file[@name='jpg']}">
<img style="border-color:#ffffff;" border="1" src=".{$item/files/file[@name='thumb']}" />
</a>

This controls the look of the thumbnail/video screen-cap images. You can edit the style of this as needed to change the border colors or add rollover effects, etc. but keep in mind that the code must be 100% complaint XHTML in order for the gallery builder to function without errors.

The sitemap functionality just requires 2 files be added to your Elevated X tour templates and tour area files and then you'll be able to submit the URL for the sitemap to be indexed by Google.

Tour Area file: sitemap.php
Template File: sitemap.tpl

These are included in our default templates and layouts.

Please open a ticket if you need these files added to one of your Elevated X tours or feel free to download them from the theme template zips:
https://support.elevatedx.com/newest_templates.php

In the version 4.0 PHP templates, to change the members area header image simply upload your header image over the existing members header image via FTP to the following location:

/members/images/header/members_header.jpg

To replace the headers( we call them headers as banners are what advertisements are referred to ) you can simply right-click on the header image and get the location and name of the file on the server. Then use FTP to upload your new header image to the same location. If you use thew same name you can just upload your file over the existing one.

As an example, the header image for the members area is this:
http://domain-name.com/members/images/header/members_header.jpg
located on the server at:
/domain-name.com/public_html/members/images/header/members_header.jpg
The dimensions of the header image(as reported by FireFox's "View image info" right-click) is:
1,988px × 300px (scaled to 994px × 150px)
So if you create the header image at 1,988px × 300px it will scale it down to 994px × 150px on normal monitors but it will show the full resolution on displays that have high resolution.

Inside the zip file for the latest default templates( located at https://support.elevatedx.com/newest.php  ), you will find the area PHP files in their prospective folders (members, tour, trial, etc).
If you look inside the sub-folder named '/cms_defaults/4.0/ you'll see 3 more folders:

/cms_admin/
/members/
/tour/

The 'members' and 'tour' folders contain the design related files for their respective areas.

If you grab the files from both 'members' areas and combine them, you'll have all the files for the members area.
If you grab the files from both 'tour' areas and combine them, you'll have all the files for the tour area.

The template files for the desktop areas are located inside the '/cms_defaults/4.0/cms_admin/phptemplate/site0
The template files for the mobile areas are located inside the '/cms_defaults/4.0/cms_admin/phptemplate/site0_mobile

Each area(members,trail, tour, etc.) will have a declaration in its 'cmsinclude.ini.php' file that tells the areas which template files to use. The default is to look for and use the number of the site ID after the template name 'site' Example for site ID 0 the default would look for 'site0' if there was no declaration made in the 'cmsinclude.ini.php' file.

If this is too confusing, please let us know and we'll set up the default templates for you at whatever location you tell us to if you open a support ticket.


For the tour areas if your payment processor allows you disable the warning page you can remove the code in:

< your php template template folder >/tour/globals/globals.tpl

usually at the end there is a simple include like:

<?php include "globals/splash.tpl"; ?>

If you remove that line the splash warning page will not show.


In the member's areas if you have the area protected the splash page shouldn't show.


Integrate Custom PHP Code

Note - This is not part of our standard installation. Use of our tech support staff for assistance with custom coding will result in additional support charges.

Sometimes, a custom piece of PHP code needs to be integrated into the CMS.  Here is how you can set this up.

Step 1) Go to the file cmsinclude.ini.php.  Under the requires tab, you'll see a list of files that are loaded when a user accesses the members area.  These files are part of the CMS, but you can add to them:

require[] = "trial.php"
require[] = "$_SERVER[DOCUMENT_ROOT]/cms_admin/includes/alwaysexec.php"
require[] = "$_SERVER[DOCUMENT_ROOT]/cms_admin/includes/membersMain.class.php"
Under require3, you can add your own lines that will include a PHP file:
require[] = "myfile1.php"
require[] = "myfile2.php"
Note: Older installs may have lines that use require1, require2, require3, like so:
require1 = "trial.php"
require2 = "$_SERVER[DOCUMENT_ROOT]/cms_admin/includes/alwaysexec.php"
require3 = "$_SERVER[DOCUMENT_ROOT]/cms_admin/includes/membersMain.class.php"
Regardless of if you see this, we recommend you still use require[] for any adding new lines instead of the numerical version.

Step 2) Create the file myfile1.php and put in any custom code that's needed.

Altering the output from the CMS

Sometimes, a custom piece of PHP needs to alter the output from the CMS.  Here's how this can be done:

Step 1) Go back to the file cmsinclude.ini.php.  Under the flags tab, you'll want to add the following:
 POSTPROCESS=myFunction

What this does is tell the CMS to load a function named "myFunction" after the template output has been generated.

Step 2) Within myfile1.php (or whatever filename you added to the system up above), add the following function

function myFunction($input)
{
  $output = $input;

  // $input is the HTML code generated after Smarty does its render process.

  // Your custom code will go here
  // Example: This will replace any instance of ##randomnumber## in the template with a random number.
  // $output = str_replace("##randomnumber##", mt_rand(), $output);

  return $output;

  // return $output, which is modified $input. This is what is displayed on screen to the end user.
}

Note - The name of the function you'll need to do is based on what you put within the POSTPROCESS setting.  So if you set the POSTPROCESS flag to "Custom", then you will need to call your custom function "Custom"

Note - As of build 3280, multiple functions are supported.

Example:

POSTPROCESS=customfunction1,customfunction2,customfunction3

 

Adding Smarty Variables to the CMS

Sometimes, custom smarty variables need to be assigned within the system

Step 1) Go back to the file cmsinclude.ini.php.  Under the flags tab, you'll want to add the following:
SMARTY_CUSTOMIZE_VARIABLES=variable_append

What this does is tell the CMS to load a function named "variable_append" after the template output has been generated.

Step 2) Within myfile1.php (or whatever filename you added to the system up above), add the following function

function variable_append(&$smarty)
{
  //Your custom code will go here
  // Example: This will assign a variable named $test with the value "This is a test" (not in quotes).
  // $smarty->assign("test", "This is a test");

}

Note - The name of the function you'll need to do is based on what you put within the SMARTY_CUSTOMIZE_VARIABLES setting.  So if you set the SMARTY_CUSTOMIZE_VARIABLES flag to "Custom", then you will need to call your custom function "Custom"

Note - Multiple functions are allowed here.

Example:

SMARTY_CUSTOMIZE_VARIABLES=customfunction1,customfunction2,customfunction3

This guide provides documentation and steps for setting up a NEW area using our PHP templates available here:

https://support.elevatedx.com/newest_templates.php

New Elevated X CMS Pro Design Themes (PHP)

Contemporary (Default) (contemporary-default Build 9): Contemporary (Default)

Classic (classic Build 13): Classic Totally Tubular (totallytubular Build 5): Totally Tubular
Elegant Modern (elegantmodern Build 5): Elegant Modern Going Solo (goingsolo Build 5): Going Solo Sleek Modern (sleekmodern Build 4):
Sleek Modern


We always recommend installing new templates into a 'dev.' subdomain so you can work on these areas while your existing area runs on the older templates.

1) Download the zip file for the templates you wish to use and extract the zip file to your local computer from the page above.

2) Inside the extracted folder you'll find 5 folders(cms_admin,members,tour,trial,vod) the area files are located inside the various area folders.
The files for the tour templates are located in the 'tour' subfolder.
The files for the members area are located in the 'members area subfolder.

3) Upload these files from the various area to your new area on your dev.subdomain.

Example:
Upload the files from the 'members' folder to the area you want the members area to be located on your dev.subdomain.com area.

4) Upload the the template files located inside the cms_admin/phptemplate/ to your cms_admin/phptemplate folder on your server.

5) Create(or ask your host to create for you) a symlink to your existing members/content/ folder inside your new dev member's area named 'content'

6) Create a new tour ID entry that references the new templates by using the import setting drop-down menu inside the "add a new tour" dialogue of the tour admin.(Selecting the templates you wish to use). Make sure you naviaget tot he admin home page after adding the tour and click the "set defaults" link if present.

7) Edit each areas' 'cmsinclude.ini.php' file in a text editor and modify the fields for this area. You'll nee to make sure the following entries are correct for your area:(Replace x with the ID number of the new site you are working with.
SITE ID=X

and if you are editing a new tour, also edit the tour DI to match your new tour ID you created.

TOUR ID= X

Also, please make sure to update the following:
$_SERVER[DOCUMENT_ROOT]/cms_admin

with your servers path to the cms_admin.

(You can always find the 'path to cms_admin' by going to your admin panel home page, locate the warnings area and click the link for "Click here for an Expanded/Detailed View" then scroll down to the 4th entry from the bottom, "Path".  across form it you will see the path to admin that you will want to copy and replace the '$_SERVER[DOCUMENT_ROOT]/cms_admin' line of your 'cms_admin' file.

Save and re-upload to your server. Then you should be able to access the areas.

When you first visit the area, you'll be prompted to either log into the admin panel(if you are not currently) or click a link to create a new area entry in the system by clicking the link. Please read the instructions and follow them.

If you run into any trouble please open a support ticket and we'll get back to you as soon as possible at http://support.elevatedx.com/

Setup a Transparent Tour

Step 1) FTP to your server and locate the members folder for one of your existing sites. Copy all of the cms related php files, css file, .js files and any other applicable files e.g. images folder, etc. and upload a copy of these files to the new transparent tour folder. Note - php files need to be uploaded in binary mode.

DO NOT copy the content folder.

Note: If your are copying the CMS members area via FTP, please make sure you do a BINARY  file transfer. If you use AUTO or ASCII settings, your encoded PHP files may be corrupted in the transfer process. For more information on how to do a BINARY transfer, please consult your FTP client's documentation.

Step 2) Locate your template folder (If PHP templates look in /cms_admin/phptemplate/ if you are using smarty, look in /cms_admin/smarty/ folder )  and make a copy of the template folder you want to use for the tour. Rename the folder to be a different name  that you can identify with no spaces.

Example:  /cms_admin/phptemplate/mysite_trial/  (where 'mysite' is the name of your template folder)

Step 3) In your CMS admin, go to Plugins >> Trials.
Create a new trial ID that will be used for the setting of you transparant tour. This will be where you can restrict content and set join links. Please note the ID # of the trial that you are setting up for use in the next step.

Step 4) Inside your new tour folder, edit cmsinclude.ini.php. Specify a different template folder by adding one of the following:

Either:

PHP_FOLDER =
foldername
or
SMARTY_FOLDER = foldername

And edit/add the following:

TRIAL=X

Where X is the numberof the trial you setup. (From step 3)

Step 5) Create a symlink (or ask your host to do this for you) to your content folder:

Create a symlink named 'content' that links your members area 'content' folder inside your transparent tour folder. 

Step 6) Edit the transparent tour templates( mysite_trial ) to remove sections that only work inside the site such as poll, ratings, comments and favorites and remove links to content pages and/or replace them with links to your join page. You can assign a trailer to appear if you have one indexed by the system as part of your normal sets.

Please be aware that we consider all of the above to be general Webmaster tasks and that being the case may not cover us assisting with setup or troubleshooting of transparent tours as part of our included standard product support. Additional charges for support time may be required.

Step 7) Makes sure you read the article regarding trial content protection located here:  https://support.elevatedx.com/index.php?/Knowledgebase/Article/View/189/0/trial-content-protection

Version 3.2: Smarty Template Reference

IMPORTANT VERSION NOTICE: This template reference is for CMS version 3.2 only – Other versions have different templates and template names than those listed here.

Developers - Please download our Smarty Reference Doc for a more technical breakdown of how to edit smarty code:

https://support.elevatedx.com/index.php?/Knowledgebase/Article/View/186/11/templating-elevated-x-using-the-smarty-templating-language

Smarty Templates edited on your server VIA FTP. They may also be downloaded and edited in a HTML editor and then uploaded.

WARNING: Some HTML editors including popular ones such as Dreamweaver add and create their own code that may break your templates. ALWAYS backup your template folder locally before making any changes. We do not have backup copies of your design or templates.

Smarty templates can be edited by anyone who is HTML fluent and comfortable hand editing HTML. By default, the templates reference external stylesheets style.css and mobilestyle.css as well as CSS files inside folder /js/ for jQuery areas such as the coming soon carousel.

Template files are located on your server inside your cms_admin/smarty/ folder. You will have 1 folder of templates for each of your sites.


Smarty Template Index  

config

 This folder contains the configuration variables used by the members, tour and trial areas. Included in each template in this folder are paths for CSS, content and RSS.


Top Level Templates  


Top level templates control the page layout. Within each template are calls to sub templates for the different sections of the page. These are called using a tag {include file="$spath/bonus/SUB-TEMPLATE-NAME.tpl"}

The top level templates call sub-templates that reside in their own sub-folder. Global, site-wide shared elements are located inside the sub-folder /general/. Sub-templates related to each page are located in their own folder. For example the search page’s main template is search.tpl and its sub-templates are inside a folder named /search.

advancedsearch.tpl

 The template used for the members/trial/network style tour page advancedsearch.php

bonus.tpl

 The template used for the members/trial/network style tour page bonus.php

This page shows the bonus sites, video feeds, audio files, erotic stories, cam and friends bonus content.

calendar.tpl

 The template used for the members /trial/network style tour page calendar.php

category.tpl

 The template used for the member s/trial/network style tour page category.php

This page shows the photos index, movies index and models index. It also shows a listing of matching content when a user clicks a model link or keyword tag.

category_outside.tpl

 The template used for the episode style tour page category.php

This page shows the models index. It also shows a listing of matching content when a user clicks a model link or keyword tag.

dvds.tpl

 The template used for the members/trial/network style tour page dvds.php

error.tpl

 The template used for the members/trial/ network style tour error page error.php

faq.tpl

 The template used for the members/trial/network style tour page faq.php

favorites.tpl

 The template used for the members/trial/network style tour page favorites.php

gallery.tpl

 The template used for the members/trial/network style tour page gallery.php

This page shows the photo gallery thumbnails and video links and embedded video.

image.tpl

 The template used for the members/trial/ network style tour error page image.php

This page shows the full size photos including the slideshow. It also shows embedded movie clips and video for all but the main/primary embedded video that plays on gallery.php.

index.tpl

 The template used for the main members/trial/network style tour page index.php

mailbox.tpl

 The template used for the members/trial private message page mailbox.php

news.tpl

 The template used for the main members/trial/network style tour page news.php

news_outside.tpl

 The template used for the episode style tour page news.php

offers.tpl

 The template used for the members/trial/network style tour page offers.php

This page shows a full page offer when a user first logs into a site.

search.tpl

 The template used for the main members/trial/network style tour page search.php

This page shows the search results when someone uses a search form.

sets.tpl

 The template used for the main members/trial/network style tour page sets.php

This page shows the updates/sets that are associated to a model. It also shows the model bio and related upsells.

tour1.tpl

 The template used for the episode style tour page index.php

This page shows the tour index page and the individual episode view for each update.

trailer.tpl

 The template used for the episode style tour page trailer.php

This page shows the tour embedded trailer page and the individual episode view for each update.


Sub Templates


Each top level template has a separate folder that holds its sub templates. The name of the folder matches the name of the top level template it belongs to.

Sub-templates are split up. Each sub-template controls 1 part of the page.

 bonus folder


 Used by members/trial/network style tour

bonuscontent.tpl

 This template controls where the page navigation (page numbers and previous/next links) are shown. It also controls the layout for the individual rows of bonus content.

bonusindex.tpl

 This template controls the index of text links leading to the bonus content options. This is only shown on the site if someone access bonus.php directly.

bonustable.tpl

 This template controls the layout of the table that shows the bonus content listings.

pagenav.tpl

This template controls the page numbers and previous/next links.

showbonus.tpl

This template controls the layout of the table that shows the bonus content including the title, thumbnail and description.

showstory.tpl

This template controls the layout of the table that shows the erotic story listings.

story_item.tpl

This template controls the layout of the erotic story.

xmlfeed.tpl

This file is used by automatically updated 3rd party feeds and should not be edited.

xmlfeeditem.tpl

This file is used by automatically updated 3rd party feeds and should not be edited.

category folder


Used by members/trial/ network style tour

category_item.tpl

This template controls the layout of the table that shows the category page listing including the title, thumbnail and description of each update.

pagenav.tpl

This template controls the page numbers and previous/next links.

pg_category.tpl

This template controls the link behavior for the category page navigation. This template should not be edited.

category_outside folder


Used by episode style tour

category_item_outside.tpl

This template controls the layout of the table that shows the category page listing including the title, thumbnail and description of each update.

pagenav.tpl

This template controls the page numbers and previous/next links.

pg_category.tpl

This template controls the link behavior for the category page navigation. This template should not be edited.

dvds folder


Used by members/trial/ network style tour

dvd1.tpl

This template controls the layout of the individual DVD title page including the title, boxcover, description and the location on the page of the scene listing.

dvd_index.tpl

This template controls the layout of the DVD listing page showing 5 DVD boxes per row.

dvd_item.tpl

This template controls the layout of the DVD item including boxcover, and link to view the DVD that’s shown on dvd_index.tpl.

pagenav.tpl

This template controls the page numbers and previous/next links.

scene_item.tpl

This template controls the layout of the individual scene listing including the title, thumbnail, description, categories and model links.

faq folder


faq1.tpl

This template controls the layout of the FAQ page contents.

favorites folder


favorites_item.tpl

This template controls the layout of the favorite update.

favoriteslink.tpl

This template controls the icon and link to add/remove an update from favorites.

tag_item.tpl

This template controls the layout of the tagged update.

taglist.tpl

This template controls the layout of the list of keyword tags.

viewtags.tpl

This template controls the layout of the listing of tagged updates.

gallery folder


additionalphotosizes.tpl

This template controls the layout of the table that shows the links to the different photo sizes and Zip files available for an update.

commentsui.tpl

This template controls the layout of the users comments section.

favoriteslink.tpl

This template controls the layout of the add to/remove from favorites link.

fulldownload_link.tpl

This template controls the layout of the table that shows the links to the different full length movie download formats and sizes available for an update.

gallery1.tpl

This template controls the layout of the bulk of the gallery page. Due to the amount of functions it contains, this page is one of the more difficult to edit.

gallery_trial_js_movie.tpl

This file is used for video playback. This template should not be edited.

gallerynav.tpl

This template controls the previous/next links for gallery pages and video clips.

js_picarr.tpl

This file is used for video playback. This template should not be edited.

playflash.tpl

This template controls the layout of the wrapper table for the flash file. This template does not typically require editing - the background color is controlled in the CSS file.

playmovie.tpl

This template controls the layout of the wrapper table for embedded movies. This template does not typically require editing - the background color is controlled in the CSS file.

showlink.tpl

This template controls the layout of the video clip play and download links for each clip.

showthumb.tpl

This template controls the layout of each photo gallery thumbnail.

suggestedupdates.tpl

This template controls the layout of the relevant/suggested updates table.

suggesttags.tpl

This template controls the layout of the table that shows the link to suggest keyword tags and the suggestion form that shows when clicked.

trial_pg_image.tpl

This template is used for trial area functionality. This template should not be edited.

update_item.tpl

This template controls the layout of each update listed in the suggested updates table.

vid-link.tpl

This template controls the layout of the video clip thumbnail and the table/grid of format and delivery options for the video clips.

ziplink.tpl

This template controls the layout of photo Zip file download link.

general folder

a-zlinks.tpl

This template controls the layout of the A-Z list of model name text links.

display_movielength.tpl

This template controls the layout of the text showing the movie length for each update.

fulldownload_link.tpl

This template controls the layout of the full movie download link.

header.tpl

This template controls the layout of the header image.

languagebar.tpl

This template controls the layout of the multiple language dropdown menu.

mailinglistform.tpl

This template controls the layout of the mailing list subscription form.

news_small.tpl

This template controls the small news update teaser shown on the index page.

page_bottom.tpl

This template controls the wrapper file for the bottom of the page including the HTML footer elements.

page_top.tpl

This template controls the wrapper file for the top of the page including the HTML header elements.

pagenav.tpl

This template controls the page numbers and previous/next links.

pg_gallery.tpl

This template controls gallery link behavior. This template should not be edited.

pg_image.tpl

This template controls image link behavior. This template should not be edited.

poll.tpl

This template controls the layout of the poll.

searchbar.tpl

This template controls the layout of the search bar.

showbanner.tpl

This template controls the layout of the default banners.

showmodel.tpl

This template controls the layout of the models on the top rated model top list.

showtextad.tpl

This template controls the layout of the default text ad shown at the bottom of the members index page.

sitelink.tpl

This template controls the site link for listing the name of the All Access Network sub-site an update belongs to. This template is only used by sites with the All Access Network Setup.

sitesdd.tpl

This template controls the dropdown menu of links for All Access Network sub-sites. This template is only used by sites with the All Access Network Setup.

stdimage.tpl

This template controls the standard image HTML tag and allows passing of priority variables.

toplist_models.tpl

This template controls the layout of the top list that shows the top rated models.

toplist_stats.tpl

This template controls the layout of the top list that shows statistics such as most viewed updates.

toplist_updates.tpl

This template controls the layout of the top list that shows the top rated updates.

topnav.tpl

This template controls the top navigation bar of text links.

trial_pg_image.tpl

This template controls trial image link behavior. This template should not be edited.

votefrm.tpl

This template controls the layout of the wrapper for the vote/rating stars.

votefrm_model.tpl

This template controls the layout of the wrapper for the model vote/rating stars.

votefrm_model_sub.tpl

This template controls the layout of the model vote/rating stars.

votefrm_sub.tpl

This template controls the layout of the vote/rating stars.

Index folder


 

comingsoon_item.tpl

This template controls the layout of the coming soon/future update item.

dvd_item.tpl

This template controls the layout of the DVD item including boxcover, and link to view the DVD.

latestdvds.tpl

This template controls the layout of the latest DVD listings.

latestupdates.tpl

This template controls the layout of the latest update listings.

pg_index.tpl

This template controls page link behavior. This template should not be edited.

update_item.tpl

This template controls the layout of the latest update including the title, thumbnail and description.

whatshot.tpl

This template controls the layout of the featured What’s Hot section.

mailbox folder


mailbox_composemessage.tpl

This template controls the layout of the compose message page.

mailbox_messagelist.tpl

This template controls the layout of the message listing page.

mailbox_readmessage.tpl

This template controls the layout of the read message page.

news folder


commentsui.tpl

This template controls the layout of the users comments section.

news1.tpl

This template controls the layout of the news listing page and the page that shows the news article.

pagenav.tpl

This template controls the page numbers and previous/next links.

pg_news.tpl

This template controls page link behavior. This template should not be edited.

search folder


advancedsearch_box.tpl

This template controls the layout and contents of the advanced search form.

pagenav.tpl

This template controls the page numbers and previous/next links.

search_item.tpl

This template controls the layout of the table that shows the search result including the title, thumbnail and description of each update.

sets folder


pagenav.tpl

This template controls the page numbers and previous/next links.

set_item.tpl

This template controls the layout of the table that shows the model’s updates including the title, thumbnail and description of each update.

tour1 folder


comingsoon_item.tpl

This template controls the layout of the coming soon/future update item.

episode.tpl

This template controls the layout of the update episode table.

episode_undertext.tpl

This template controls the text links that are alternated after each episode table.

footer.tpl

This template controls the page footer.

header.tpl

This template controls the header including the rotation of header images placed inside the images/header folder.

moreupdates.tpl

This template controls the layout of the table of thumbnails for past updates.

moreupdates_item.tpl

This template controls the layout of the coming soon/future update item including the title, thumbnail and link to the episode.

news1.tpl

This template controls the layout of the outside/tour news page articles.

page_top.tpl

This template controls the wrapper file for the top of the page including the HTML header elements.

pg_tour.tpl

This template controls page link behavior. This template should not be edited.

sitelink.tpl

This template controls the site link for listing the name of the All Access Network sub-site an update belongs to. This template is only used by sites with the All Access Network Setup.

toplist.tpl

This template controls the layout of the most popular updates table.

toplist_item.tpl

This template controls the layout of the most popular update item including the title, thumbnail and link to the episode.

topnav.tpl

This template controls the top navigation bar of text links.

votefrm.tpl

This template controls the layout of the wrapper for the vote/rating stars.

votefrm_sub.tpl

This template controls the layout of the vote/rating stars.

 


Tour Themes

Themes are all packaged up and committed to their own separate repositories.

All of them are available here:
 
Installation instructions
 
1) Download the zip file, unzip it.

2) Within the zip, there are two folders:
  smarty
  tour
 
3) On the remove server, there will be a /cms_admin/smarty/, create a folder on there. Name it whatever you want. In the case of this example, we'll call it NEWFOLDER.
 
4) Upload the contents of /smarty/ within the zip file into /cms_admin/smarty/NEWFOLDER/      (*Where "NEWFOLDER" is the name of your new tour as mentioned above )
 
5) Now, within the CMS, go to Tours and add a new tour. At the top of the page, there will be a list of items to import. In this case, choose the settings that correspond with the tour template that you've installed (For example, if you've downloaded Theme 1, choose the item for **default** theme 1)
 
6) After you've clicked import, edit the other fields, and make sure the paths are correct. For instance, make sure the path to the tour is listed properly. In this case, we will use /path/to/TOUR/ as the example of where the tour should be.
 
7) On the remove server, create a folder that will house your tour. In this case, we will call this folder TOUR, which sits in /path/to/TOUR/  Upload the files located inside the 'tour' folder from the zip.
 
8) Edit cmsinclude.ini.php. Make sure the TOUR_ID is specified correctly, as well as SMARTY_FOLDER variable, as well as the path to CMS_ADMIN.
 
(If your tour folder is named anything other than 'tour' please edit the conf files(locatd in your smarty folders /config/ folder.) to adjust the path to content and SEO URL info.)