Whirlwind eCommerce Wiki - User contributions [en]

Wiki Suggestions

2008-12-14T18:23:08Z

James:

*adding a visual aid to the wiki on how the advertisers, campaigns, banners, and banner zones all work together would be helpful.

*I got a little stuck on the custom fields section. Apparently the "attributes" are case sensitive. For example "Textarea" != "textarea". The wiki section on custom fields indicates that "Textarea" is correct, which didn't seem to work for me.

Page Templates:Core Variables

2008-12-09T03:58:08Z

James: /* COMPONENTS */

{{Page Template Managers Shortcuts}}
The following are the core fields available for coding in Page Template Management. Reference them directly using the variable name:

==PAGE CONTENT==
*$pageId
*$printable
*$printableURL
*$sendPage2FriendURL
*$sendPage2FriendJS
*$message
*$pageIsEditable
*$pageEditLink

==GLOBAL==
*$usePageAuthorization
*$usePageBreadCrumb
*$usePageNotice
*$usePageSubTitle
*$usePageLinkText
*$usePageSummaryImageCaption
*$date
*$datemonth
*$dateday
*$dateyear
*$date12hour
*$date24hour
*$dateminute
*$datemonthName
*$datedayName
*$dateampm

==CONTENT==
*$language : depriciated
*$languageIndex : depriciated
*$languageQueryString : depriciated
*$title
*$subTitle
*$notice
*$breadCrumb
*$copy
*$summary
*$custom_field_fieldName : any custom fields created within this template will be accessible by calling "$custom_field_fieldName" where "fieldName" is replace by the custom field Field Name.

==PUBLISHER==
*$usePagePublisher
*$publisher
*$authorId
*$author_firstName
*$author_lastName
*$author_userImage
*$author_emailAddress
*$author_custom_field_fieldName : any custom fields created for users in administration settings will be accessible by calling "$author_custom_field_fieldName" where "fieldName" is replace by the custom field Field Name.
*$publishDate
*$publishDatemonth
*$publishDateday
*$publishDateyear
*$publishDate12hour
*$publishDate24hour
*$publishDateminute
*$publishDatemonthName
*$publishDatedayName

==META==
*$metaTitle
*$metaDescription
*$metaKeywords

==SITE SETTING==
*$siteUrl
*$securedSiteUrl
*$physicalRoot
*$virtualRoot

==USER/ACCESS==
Information about the current user logged in
*$userFirstName
*$userLastName
*$userEmailAddress
*$userHandle
$userIsPosting
$isSystemManager
$isLoggedIn

==User Shortcut forms==
*$userEZLoginForm1
*$userEZPostForm1
*$userEZPostForm2

==User related access variables==
*$loginURL
*$logoutURL
*$userAccountURL
*$userCreateAccountURL
*$systemManageURL
*$userCreateAccountLink
*$userEditAccountLink
*$authorizeUserFailureLocation
*$defaultLoginSuccessLocation
*$defaultLoginFailureLocation
*$defaultLogoutLocation

==BANNERS==
*$zone{id}Banner : replace {id} with the zoneId automatically created when the zone was added in banner administration

==COMPONENTS==
*$component{id}Template : replace {id} with the include template's templateId automatically create when the include template was added in template management.
Note: components cannot be referred to from within other components

Page Templates:Creating Your First Template

2008-12-09T03:04:56Z

James: /* Place PHP tags and Echo the whole thing */

{{Page Template Managers Shortcuts}}
This section assumes you have a completed html/css page that will be used to build this template.

Start by pasting the full code of the home page into your HTML editor of choice.

==Escape quotes==
As the template code is in PHP and all this content will have to be 'echo'd' be sure to escape all quotes so the echo statements do not fail. Search and Replace double quote (") with escaped double quote (\")

==Replace image / file paths==
Chances are the html was built referencing file and image paths that are not the same as the file structure set up on the ecommerce platform website. Search all file paths and replace with the path to the file on the new server. For example if the originating html uses "images/x/filename.jpg" and the images are located on the ecommerce platform website in "/files/imageshere/" you may want to search "images/" with "/files/imageshere". Don't forget to repath any javascript source and css files (I recommend creating css and js folders under the file folder designated for the site). Double check your files and images are uploaded to the correct folders on the ecommerce platform website. Note: if file paths are used in the CSS and JS files, they will need to be modified as well!

==Place PHP tags and Echo the whole thing==
Place an "echo" statement at the top and close the echo statement at the end

<source lang="php">
// start echo
echo "
... all html here ...
";
// end echo with ";
</source>

==Get your data==
The [[The Administration Console:Page Templates:Core Variables|Core Page Data]] is automatically available to you, but all additional content will need to be requested via the appropriate calling [[The Administration Console:Page Templates:Functions|functions]]. The ecommerce engine provides a series of [[The Administration Console:Page Templates:Functions|functions]] that return content in strings and arrays that can be used to control the html output. Initialize these functions at the beginning of your template. Example:

<source lang="php">
// start of template

// information to populate menu bars
$arrMenu = eV::pageMenuGet() ;
// children for this page. Note $pageId is a core variable available in the template
$arrChildren = eV::pageChildrenGet($pageId,"title,summary,summaryImage,link")
// get banner zones for this page
$zoneA = eV::pageZoneGet(1,$pageId);
$zoneB = eV::pageZoneGet(2,$pageId);
$zoneC = eV::pageZoneGet(3,$pageId);
// get data to populate breadcrumbs
$arrBC = eV::pageBreadcrumbsFamilyGet($pageId;
// get recently viewed items
$arrRV = eV::recentlyViewedGet("title,summaryImage,link");

// ... rest of template code ...
</source>
Only request the minimum number of functions, and fields within functions, necessary to support the template to ensure optimal performance.
Many functions are dependent on the existence of other objects in order to write the function. For instance, the eC::pageZoneGet() function requires the entry of a zoneId - the zone needs to be created in banner management before the ID exists, therefore you may need to create the banner zones before you can write the functions in your template code.

==Setup the 'message' output==
The ecommerce platform passes messages from page to page, action to page with the URL variable "message". The message is used to inform the visitor of actions that have occured (examples: "New coupon as been added to your cart", "invalid login - please try again", "You have been logged out", etc, etc). Many of these messages can by customized in the settings are of the administration console. You may also specify your own 'messages' when creating URLs in your code (example: href="index.php?pageId=123&message=You are in a very special page"). This message can be accessed in the page template code by the core variable "$message". It is recommended that on EVERY template you display this message prominently when passed. Example:

<source lang="php">
// ... code before message

if(!empty($message)) echo "$message";

// code after message ...
</source>

==Mark template include divisions==
Chances are, much of the code in this html will be reused in other templates. Most of the time a header and footer include can be identified, separated and later used as includes for other templates. The header usually includes all code from the beginning up until the center content that will vary from page to page, the footer begins immediately after the varying center content and continues to the end of the code. Often the header and footer are split into additional templates (header-top, header-left, footer-right, footer-bottom) in order to easily adapt to templates that may or may not use the left nav bar or right column contents.

Identify where these template includes began and end, end/begin echo statements at these points and mark them with comments denoting as such.

Note that sometimes the includes may by 'mostly' identical from template to template with some slight variations. Use variables to control these variations and pass values to the template include. For instance if the css file governing the page style is different for each template, substitute a variable for the css file path and set the variable in the template calling the include:

<source lang="php">
/* old code */

// start header-top include
echo "...<link href=\"/path/to/cssfile.css\" rel=\"stylesheet\" type=\"text/css\" media=\"screen\" />...";
// end header-top include

/* new code using variable */

// set path in template calling the include
$css= "/path/to/cssfile.css";
// change code in tag in include
// start header-top include
echo "...<link href=\"/$css\" rel=\"stylesheet\" type=\"text/css\" media=\"screen\" />...";
// end header-top include

</source>

This method is often used for banner ad zones, tag classes/ids that will vary from template to template but be part of a common include.

;Place variables in meta tags
Place the $metaTitle, $metaKeywords, $metaDescription in the meta tags so they will auto populate with page data:

<source lang="php">
echo "...
<title>$metaTitle</title>
<meta name=\"description\" content=\"$metaDescription\"/>
<meta name=\"keywords\" content=\"$metaKeywords\"/>
...";
</source>

==Setup the menus==
*Make sure you are calling the [[functions:pageMenuGet|pageMenuGet]] function in the beginning of your code.
*Identify which menus you will need (top, left, bottom, right). Any of the four menu areas can be placed anywhere on the template, the names are simply for easy reference - so if a template actually has two top menus (tabs and then and action bar) but no right menu, use the right menu as the 2nd top menu.
*Create a menu in administration via menu manager, so you have some data to test. Set the menu as the default. If any of your menus are tiered, be sure to set up those menu bars with tiered content for an adequate test subject.
*Build your menus into the code. Refer to [[functions:pageMenuGet|pageMenuGet]] for usage and examples.

==Setup the banner zones==
*Create the zones you will need for this page in Banner Management. Fill them with sample campaigns/banners so they will display when we test.
*Make sure you are calling the [[functions:pageZoneGet|pageZoneGet]] function once for each banner zone you will place on the page.
*Identify the locations of the banner zones and place the variables you assigned to the pageZoneGet functions at those locations.

==Setup Perpetual Cart==
Only perform this task if this page will display a perpetual cart
*Be sure you are calling the [[functions:orderGetSummary|orderGetSummary]] function to retrieve the summarized cart data.
*Use the [[functions:dollarFormat|dollarFormat]] function to convert decimal currency values to formatted dollar amounts.

==Setup Cart and Checkout Links==
The following links are available to jump to stages in the checkout process:
*Shopping Cart: index.php?fa=ORDER.cartView
*Checkout Registration Page: index.php?fa=ORDER.register
*Checkout Shipping Address Page: index.php?fa=ORDER.checkoutShipping
*Checkout Billing Address Page: index.php?fa=ORDER.checkoutBilling
*Checking Payment Entry Page: index.php?fa=ORDER.checkoutPayment
*Checkout Confirmation Page: index.php?fa=ORDER.checkoutConfirmation
Typically the links to the shopping cart and checkout registration page (checkout link) are used in the perpetual cart. Note that these will link to empty pages until the checkout process templates are created, pages are created with the checkout process templates assigned to them AND the pageIds are entered into settings: eCommerce area for each of these pages.

==Setup any Custom Search Group fields==
Custom search groups are used to control select drop downs that jump to specific pages when options are selected. You must first create the group via Custom Search Groups in the administration console, than you can output the select field in a page template. Using Custom Search Groups gives content managers the ability to modify the contents of the drop down, and the target locations, using the administration console.
*Identify candidates for custom search groups
*Create groups in Custom Search Groups for each candidate (enter some temporary options for testing if you do not have real options available). Mark down the group IDs as each Custom Search Group is created, you will need for the next step.
*Create the select fields in administration by first calling the [[functions:pageCustomSearchGroup|pageCustomSearchGroup]] function at the beginning of your template code, then coding the select field at the point in the template the field is to appear (see examples in the pageCustomSearchGroup function for options on how to utilize and output the select field)

==Setup Page Specific Content==
Page specific content is all content that will be controlled by page management that is specific to this page. Since menu bars, perpetual carts, banner zones and other items listed before this section are shared by multiple pages, they do not fall into this category. Typically the center page content qualifies for this category. This can be populated with utilizing the Content fields in the [[The Administration Console:Page Templates:Core Variables|Core Variables]]. Any areas of control that cannot use core variables can be controlled by creating [[The Administration Console:Custom Fields|Custom Fields]].
*Identify your core variable controlled content and place the core variables into the code.
*Identify your custom field controlled content, create the custom fields and place the custom field variables into the code.

==Setup Children==
Skip this area if this page template is not to display children (as controlled by relationships in Page Management)
*Place your call to the [[functions:pageChildrenGet|pageChildrenGet]] function at the beginning of your page template code
*Output the children data in the appropriate location(s) in the template code. See the pageChildrenGet function for examples.

==Setup breadcrumbs==
Skip this area if the template does not display breadcrumbs.
There are two methods of acquiring breadcrumbs:
*Use [[functions:pageBreadcrumbsFamilyGet|pageBreadcrumbsFamilyGet]] to build breadcrumbs by moving up through the relationships family tree.
*Use [[functions:pageBreadcrumbsHistoryGet|pageBreadcrumbsHistoryGet]] to build breadcrumbs based on the page visit history.

==Post Page Templates==
*Extract template includes and post each as an individual template
*Place template include code into remaining page template code ($component#Template)

Page Templates:Creating a Category Template

2008-12-07T00:33:24Z

James: /* Create a category template */

{{Page Template Managers Shortcuts}}
== Create a category template ==

Creating a category template is very similar to creating a [[Page Templates:Creating a Basic Template|basic template]], with the addition of children. Children are a list of homogeneous items, controlled by relationships in page management, that appear inside of a page. Children are synonymous with subcategories that are displayed in a category page, product pages that are displayed in a sub category page, photos that are displayed in a photo album page, cross sell product pages that appear in a product page, etc. Children are assigned to a page using relationship management in page management. Those assigned children (and associated data) are accessible via the [[Functions:pageChildrenGet|pageChildrenGet]] function.

<source lang="php">

// note that we are skipping several of the typical elements of a page template
// to focus on the children element
// please see the 'creating a basic template' for other items you typically see in a template
// including menu bars, etc.

// always start your templates with any functions you require
// to gather the data you need for the page

// lets start by getting our child data
$children = eV::pageChildrenGet($pageId,"title,summaryImage,summary,link");

// our opening html tags
echo "<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">
<html xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\" dir=\"ltr\">
";

// now for the head
// notice we use some core variables here to specify the title, meta keywords and description
// the contents of these variables are controlled by page management
// note the use of the php htmlspecialchars function to ensure no characters in the variable content 'break' the tags
echo "
<head>
<meta name=\"keywords\" content=\"" . htmlspecialchars($metaKeywords) . "\">
<meta name=\"description\" content=\"" . htmlspecialchars($metaDescription) . "\">
<title>" . htmlspecialchars($metaTitle) . "</title>
</head>
";

// start the body tag
echo "<body>";

// lets build an outer table to hold our page content
echo "<table width=779>";

// this is the top banner
echo "<tr><td align=center>WELCOME TO OUR WEB SITE</td></tr>";

// now lets display the center page content
echo "<tr><td valign=top>";

// first im going to display the message output
// this is a variable used to pass messages (errors, notifications, etc) from page to page for visitors
// you want this highlighted so it is brought to their attention
// only display this if it has value
if(!empty($attributes['message'])) echo "" . $attributes['message']] . " ";

// center page content
// pulled from core variables
// the contents of these variables is controlled via page management
echo "$title $subTitle $copy<hr>";

// now I am going to show the children below the copy
// note you can display the children any way you wish (listed, like articles, checkerboard, with/without images, etc)
// just make sure you call on the fields you require via the fieldList attribute in the pageGetChildren function
// I'm going to display a checkerboard list of children
echo "<table align=center border=2><tr>";

// setting a counter
// this is to keep track of each cell, so we know when to start the next row
$counter = 0;
// lets loop thru the children
// remember $children is what we assigned the results of the pageGetChildren function
foreach($children as $child) {
// if we are after the 3rd cell, lets start a new row
if($counter/3 == intval($counter/3) && $counter != 0) echo "</tr><tr>";
// increment the counter
$counter++
// output the cell
echo "<td valign=top width=200>";
echo "<a href=\"" . $child['link'] . "\"><img src=\"" . $child['summaryImage'] . "\" border=0></a>";
echo " <a href=\"" . $child['link'] . "\">" . $child['title'] . "</a> " . $child['summary'];
echo "</td>";
};
// close out the child table
echo "</tr></table>";

// now lets close out the center content cell
echo "</td></tr>";

// time for the bottom menu
echo "<tr><td colspan=2 align=center> | ";
foreach($bottomMenu as $menuItem) echo " <a href=\"" . $menuItem['link'] . "\" target=\"" . $menuItem['target'] . "\">" . $menuItem['text'] . "</a> | ";
echo "</td></tr>";

// close out the outer wrapping table
echo "</table>";

// close out the body and html
echo "</body>
</html>";

</source>

*For details on using children, and more examples, see the [[Functions:pageChildrenGet|pageChildrenGet]] function.
*To many children to display on one page gracefully? use the handy [[Functions:pagination|pagination]] function to allow visitors to 'page' through a large number of results.

Page Templates:Creating a Category Template

2008-12-07T00:32:21Z

James: /* Create a category template */

{{Page Template Managers Shortcuts}}
== Create a category template ==

Creating a category template is very similar to creating a [[Page Templates:Creating a Basic Template|basic template]], with the addition of children. Children are a list of homogeneous items, controlled by relationships in page management, that appear inside of a page. Children are synonymous with subcategories that are displayed in a category page, product pages that are displayed in a sub category pate, photos that are displayed in a photo album page, cross sell product pages that appear in a product page, etc. Children are assigned to a page using relationship management in page management. Those assigned children (and associated data) are accessible via the [[Functions:pageChildrenGet|pageChildrenGet]] function.

<source lang="php">

// note that we are skipping several of the typical elements of a page template
// to focus on the children element
// please see the 'creating a basic template' for other items you typically see in a template
// including menu bars, etc.

// always start your templates with any functions you require
// to gather the data you need for the page

// lets start by getting our child data
$children = eV::pageChildrenGet($pageId,"title,summaryImage,summary,link");

// our opening html tags
echo "<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">
<html xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\" dir=\"ltr\">
";

// now for the head
// notice we use some core variables here to specify the title, meta keywords and description
// the contents of these variables are controlled by page management
// note the use of the php htmlspecialchars function to ensure no characters in the variable content 'break' the tags
echo "
<head>
<meta name=\"keywords\" content=\"" . htmlspecialchars($metaKeywords) . "\">
<meta name=\"description\" content=\"" . htmlspecialchars($metaDescription) . "\">
<title>" . htmlspecialchars($metaTitle) . "</title>
</head>
";

// start the body tag
echo "<body>";

// lets build an outer table to hold our page content
echo "<table width=779>";

// this is the top banner
echo "<tr><td align=center>WELCOME TO OUR WEB SITE</td></tr>";

// now lets display the center page content
echo "<tr><td valign=top>";

// first im going to display the message output
// this is a variable used to pass messages (errors, notifications, etc) from page to page for visitors
// you want this highlighted so it is brought to their attention
// only display this if it has value
if(!empty($attributes['message'])) echo "" . $attributes['message']] . " ";

// center page content
// pulled from core variables
// the contents of these variables is controlled via page management
echo "$title $subTitle $copy<hr>";

// now I am going to show the children below the copy
// note you can display the children any way you wish (listed, like articles, checkerboard, with/without images, etc)
// just make sure you call on the fields you require via the fieldList attribute in the pageGetChildren function
// I'm going to display a checkerboard list of children
echo "<table align=center border=2><tr>";

// setting a counter
// this is to keep track of each cell, so we know when to start the next row
$counter = 0;
// lets loop thru the children
// remember $children is what we assigned the results of the pageGetChildren function
foreach($children as $child) {
// if we are after the 3rd cell, lets start a new row
if($counter/3 == intval($counter/3) && $counter != 0) echo "</tr><tr>";
// increment the counter
$counter++
// output the cell
echo "<td valign=top width=200>";
echo "<a href=\"" . $child['link'] . "\"><img src=\"" . $child['summaryImage'] . "\" border=0></a>";
echo " <a href=\"" . $child['link'] . "\">" . $child['title'] . "</a> " . $child['summary'];
echo "</td>";
};
// close out the child table
echo "</tr></table>";

// now lets close out the center content cell
echo "</td></tr>";

// time for the bottom menu
echo "<tr><td colspan=2 align=center> | ";
foreach($bottomMenu as $menuItem) echo " <a href=\"" . $menuItem['link'] . "\" target=\"" . $menuItem['target'] . "\">" . $menuItem['text'] . "</a> | ";
echo "</td></tr>";

// close out the outer wrapping table
echo "</table>";

// close out the body and html
echo "</body>
</html>";

</source>

*For details on using children, and more examples, see the [[Functions:pageChildrenGet|pageChildrenGet]] function.
*To many children to display on one page gracefully? use the handy [[Functions:pagination|pagination]] function to allow visitors to 'page' through a large number of results.

Page Templates:Creating Your First Template

2008-12-07T00:22:48Z

James: /* Setup breacrumbs */

{{Page Template Managers Shortcuts}}
This section assumes you have a completed html/css page that will be used to build this template.

Start by pasting the full code of the home page into your HTML editor of choice.

==Escape quotes==
As the template code is in PHP and all this content will have to be 'echo'd' be sure to escape all quotes so the echo statements do not fail. Search and Replace double quote (") with escaped double quote (\")

==Replace image / file paths==
Chances are the html was built referencing file and image paths that are not the same as the file structure set up on the ecommerce platform website. Search all file paths and replace with the path to the file on the new server. For example if the originating html uses "images/x/filename.jpg" and the images are located on the ecommerce platform website in "/files/imageshere/" you may want to search "images/" with "/files/imageshere". Don't forget to repath any javascript source and css files (I recommend creating css and js folders under the file folder designated for the site). Double check your files and images are uploaded to the correct folders on the ecommerce platform website. Note: if file paths are used in the CSS and JS files, they will need to be modified as well!

==Place PHP tags and Echo the whole thing==
Place an "echo" statement at the top and close the echo statement at the end. Note the beginning and ending PHP tags will NOT be copied into the template code - I only place them in my editor so that it activates the color coding for the PHP code:

<source lang="php">
// start echo
<?php
echo "
... all html here ...
";
// end echo with ";
?>
</source>

==Get your data==
The [[The Administration Console:Page Templates:Core Variables|Core Page Data]] is automatically available to you, but all additional content will need to be requested via the appropriate calling [[The Administration Console:Page Templates:Functions|functions]]. The ecommerce engine provides a series of [[The Administration Console:Page Templates:Functions|functions]] that return content in strings and arrays that can be used to control the html output. Initialize these functions at the beginning of your template. Example:

<source lang="php">
// start of template

// information to populate menu bars
$arrMenu = eV::pageMenuGet() ;
// children for this page. Note $pageId is a core variable available in the template
$arrChildren = eV::pageChildrenGet($pageId,"title,summary,summaryImage,link")
// get banner zones for this page
$zoneA = eV::pageZoneGet(1,$pageId);
$zoneB = eV::pageZoneGet(2,$pageId);
$zoneC = eV::pageZoneGet(3,$pageId);
// get data to populate breadcrumbs
$arrBC = eV::pageBreadcrumbsFamilyGet($pageId;
// get recently viewed items
$arrRV = eV::recentlyViewedGet("title,summaryImage,link");

// ... rest of template code ...
</source>
Only request the minimum number of functions, and fields within functions, necessary to support the template to ensure optimal performance.
Many functions are dependent on the existence of other objects in order to write the function. For instance, the eC::pageZoneGet() function requires the entry of a zoneId - the zone needs to be created in banner management before the ID exists, therefore you may need to create the banner zones before you can write the functions in your template code.

==Setup the 'message' output==
The ecommerce platform passes messages from page to page, action to page with the URL variable "message". The message is used to inform the visitor of actions that have occured (examples: "New coupon as been added to your cart", "invalid login - please try again", "You have been logged out", etc, etc). Many of these messages can by customized in the settings are of the administration console. You may also specify your own 'messages' when creating URLs in your code (example: href="index.php?pageId=123&message=You are in a very special page"). This message can be accessed in the page template code by the core variable "$message". It is recommended that on EVERY template you display this message prominently when passed. Example:

<source lang="php">
// ... code before message

if(!empty($message)) echo "$message";

// code after message ...
</source>

==Mark template include divisions==
Chances are, much of the code in this html will be reused in other templates. Most of the time a header and footer include can be identified, separated and later used as includes for other templates. The header usually includes all code from the beginning up until the center content that will vary from page to page, the footer begins immediately after the varying center content and continues to the end of the code. Often the header and footer are split into additional templates (header-top, header-left, footer-right, footer-bottom) in order to easily adapt to templates that may or may not use the left nav bar or right column contents.

Identify where these template includes began and end, end/begin echo statements at these points and mark them with comments denoting as such.

Note that sometimes the includes may by 'mostly' identical from template to template with some slight variations. Use variables to control these variations and pass values to the template include. For instance if the css file governing the page style is different for each template, substitute a variable for the css file path and set the variable in the template calling the include:

<source lang="php">
/* old code */

// start header-top include
echo "...<link href=\"/path/to/cssfile.css\" rel=\"stylesheet\" type=\"text/css\" media=\"screen\" />...";
// end header-top include

/* new code using variable */

// set path in template calling the include
$css= "/path/to/cssfile.css";
// change code in tag in include
// start header-top include
echo "...<link href=\"/$css\" rel=\"stylesheet\" type=\"text/css\" media=\"screen\" />...";
// end header-top include

</source>

This method is often used for banner ad zones, tag classes/ids that will vary from template to template but be part of a common include.

;Place variables in meta tags
Place the $metaTitle, $metaKeywords, $metaDescription in the meta tags so they will auto populate with page data:

<source lang="php">
echo "...
<title>$metaTitle</title>
<meta name=\"description\" content=\"$metaDescription\"/>
<meta name=\"keywords\" content=\"$metaKeywords\"/>
...";
</source>

==Setup the menus==
*Make sure you are calling the [[functions:pageMenuGet|pageMenuGet]] function in the beginning of your code.
*Identify which menus you will need (top, left, bottom, right). Any of the four menu areas can be placed anywhere on the template, the names are simply for easy reference - so if a template actually has two top menus (tabs and then and action bar) but no right menu, use the right menu as the 2nd top menu.
*Create a menu in administration via menu manager, so you have some data to test. Set the menu as the default. If any of your menus are tiered, be sure to set up those menu bars with tiered content for an adequate test subject.
*Build your menus into the code. Refer to [[functions:pageMenuGet|pageMenuGet]] for usage and examples.

==Setup the banner zones==
*Create the zones you will need for this page in Banner Management. Fill them with sample campaigns/banners so they will display when we test.
*Make sure you are calling the [[functions:pageZoneGet|pageZoneGet]] function once for each banner zone you will place on the page.
*Identify the locations of the banner zones and place the variables you assigned to the pageZoneGet functions at those locations.

==Setup Perpetual Cart==
Only perform this task if this page will display a perpetual cart
*Be sure you are calling the [[functions:orderGetSummary|orderGetSummary]] function to retrieve the summarized cart data.
*Use the [[functions:dollarFormat|dollarFormat]] function to convert decimal currency values to formatted dollar amounts.

==Setup Cart and Checkout Links==
The following links are available to jump to stages in the checkout process:
*Shopping Cart: index.php?fa=ORDER.cartView
*Checkout Registration Page: index.php?fa=ORDER.register
*Checkout Shipping Address Page: index.php?fa=ORDER.checkoutShipping
*Checkout Billing Address Page: index.php?fa=ORDER.checkoutBilling
*Checking Payment Entry Page: index.php?fa=ORDER.checkoutPayment
*Checkout Confirmation Page: index.php?fa=ORDER.checkoutConfirmation
Typically the links to the shopping cart and checkout registration page (checkout link) are used in the perpetual cart. Note that these will link to empty pages until the checkout process templates are created, pages are created with the checkout process templates assigned to them AND the pageIds are entered into settings: eCommerce area for each of these pages.

==Setup any Custom Search Group fields==
Custom search groups are used to control select drop downs that jump to specific pages when options are selected. You must first create the group via Custom Search Groups in the administration console, than you can output the select field in a page template. Using Custom Search Groups gives content managers the ability to modify the contents of the drop down, and the target locations, using the administration console.
*Identify candidates for custom search groups
*Create groups in Custom Search Groups for each candidate (enter some temporary options for testing if you do not have real options available). Mark down the group IDs as each Custom Search Group is created, you will need for the next step.
*Create the select fields in administration by first calling the [[functions:pageCustomSearchGroup|pageCustomSearchGroup]] function at the beginning of your template code, then coding the select field at the point in the template the field is to appear (see examples in the pageCustomSearchGroup function for options on how to utilize and output the select field)

==Setup Page Specific Content==
Page specific content is all content that will be controlled by page management that is specific to this page. Since menu bars, perpetual carts, banner zones and other items listed before this section are shared by multiple pages, they do not fall into this category. Typically the center page content qualifies for this category. This can be populated with utilizing the Content fields in the [[The Administration Console:Page Templates:Core Variables|Core Variables]]. Any areas of control that cannot use core variables can be controlled by creating [[The Administration Console:Custom Fields|Custom Fields]].
*Identify your core variable controlled content and place the core variables into the code.
*Identify your custom field controlled content, create the custom fields and place the custom field variables into the code.

==Setup Children==
Skip this area if this page template is not to display children (as controlled by relationships in Page Management)
*Place your call to the [[functions:pageChildrenGet|pageChildrenGet]] function at the beginning of your page template code
*Output the children data in the appropriate location(s) in the template code. See the pageChildrenGet function for examples.

==Setup breadcrumbs==
Skip this area if the template does not display breadcrumbs.
There are two methods of acquiring breadcrumbs:
*Use [[functions:pageBreadcrumbsFamilyGet|pageBreadcrumbsFamilyGet]] to build breadcrumbs by moving up through the relationships family tree.
*Use [[functions:pageBreadcrumbsHistoryGet|pageBreadcrumbsHistoryGet]] to build breadcrumbs based on the page visit history.

==Post Page Templates==
*Extract template includes and post each as an individual template
*Place template include code into remaining page template code ($component#Template)

Page Templates:Creating Your First Template

2008-12-07T00:06:54Z

James: /* Setup the banner zones */

{{Page Template Managers Shortcuts}}
This section assumes you have a completed html/css page that will be used to build this template.

Start by pasting the full code of the home page into your HTML editor of choice.

==Escape quotes==
As the template code is in PHP and all this content will have to be 'echo'd' be sure to escape all quotes so the echo statements do not fail. Search and Replace double quote (") with escaped double quote (\")

==Replace image / file paths==
Chances are the html was built referencing file and image paths that are not the same as the file structure set up on the ecommerce platform website. Search all file paths and replace with the path to the file on the new server. For example if the originating html uses "images/x/filename.jpg" and the images are located on the ecommerce platform website in "/files/imageshere/" you may want to search "images/" with "/files/imageshere". Don't forget to repath any javascript source and css files (I recommend creating css and js folders under the file folder designated for the site). Double check your files and images are uploaded to the correct folders on the ecommerce platform website. Note: if file paths are used in the CSS and JS files, they will need to be modified as well!

==Place PHP tags and Echo the whole thing==
Place an "echo" statement at the top and close the echo statement at the end. Note the beginning and ending PHP tags will NOT be copied into the template code - I only place them in my editor so that it activates the color coding for the PHP code:

<source lang="php">
// start echo
<?php
echo "
... all html here ...
";
// end echo with ";
?>
</source>

==Get your data==
The [[The Administration Console:Page Templates:Core Variables|Core Page Data]] is automatically available to you, but all additional content will need to be requested via the appropriate calling [[The Administration Console:Page Templates:Functions|functions]]. The ecommerce engine provides a series of [[The Administration Console:Page Templates:Functions|functions]] that return content in strings and arrays that can be used to control the html output. Initialize these functions at the beginning of your template. Example:

<source lang="php">
// start of template

// information to populate menu bars
$arrMenu = eV::pageMenuGet() ;
// children for this page. Note $pageId is a core variable available in the template
$arrChildren = eV::pageChildrenGet($pageId,"title,summary,summaryImage,link")
// get banner zones for this page
$zoneA = eV::pageZoneGet(1,$pageId);
$zoneB = eV::pageZoneGet(2,$pageId);
$zoneC = eV::pageZoneGet(3,$pageId);
// get data to populate breadcrumbs
$arrBC = eV::pageBreadcrumbsFamilyGet($pageId;
// get recently viewed items
$arrRV = eV::recentlyViewedGet("title,summaryImage,link");

// ... rest of template code ...
</source>
Only request the minimum number of functions, and fields within functions, necessary to support the template to ensure optimal performance.
Many functions are dependent on the existence of other objects in order to write the function. For instance, the eC::pageZoneGet() function requires the entry of a zoneId - the zone needs to be created in banner management before the ID exists, therefore you may need to create the banner zones before you can write the functions in your template code.

==Setup the 'message' output==
The ecommerce platform passes messages from page to page, action to page with the URL variable "message". The message is used to inform the visitor of actions that have occured (examples: "New coupon as been added to your cart", "invalid login - please try again", "You have been logged out", etc, etc). Many of these messages can by customized in the settings are of the administration console. You may also specify your own 'messages' when creating URLs in your code (example: href="index.php?pageId=123&message=You are in a very special page"). This message can be accessed in the page template code by the core variable "$message". It is recommended that on EVERY template you display this message prominently when passed. Example:

<source lang="php">
// ... code before message

if(!empty($message)) echo "$message";

// code after message ...
</source>

==Mark template include divisions==
Chances are, much of the code in this html will be reused in other templates. Most of the time a header and footer include can be identified, separated and later used as includes for other templates. The header usually includes all code from the beginning up until the center content that will vary from page to page, the footer begins immediately after the varying center content and continues to the end of the code. Often the header and footer are split into additional templates (header-top, header-left, footer-right, footer-bottom) in order to easily adapt to templates that may or may not use the left nav bar or right column contents.

Identify where these template includes began and end, end/begin echo statements at these points and mark them with comments denoting as such.

Note that sometimes the includes may by 'mostly' identical from template to template with some slight variations. Use variables to control these variations and pass values to the template include. For instance if the css file governing the page style is different for each template, substitute a variable for the css file path and set the variable in the template calling the include:

<source lang="php">
/* old code */

// start header-top include
echo "...<link href=\"/path/to/cssfile.css\" rel=\"stylesheet\" type=\"text/css\" media=\"screen\" />...";
// end header-top include

/* new code using variable */

// set path in template calling the include
$css= "/path/to/cssfile.css";
// change code in tag in include
// start header-top include
echo "...<link href=\"/$css\" rel=\"stylesheet\" type=\"text/css\" media=\"screen\" />...";
// end header-top include

</source>

This method is often used for banner ad zones, tag classes/ids that will vary from template to template but be part of a common include.

;Place variables in meta tags
Place the $metaTitle, $metaKeywords, $metaDescription in the meta tags so they will auto populate with page data:

<source lang="php">
echo "...
<title>$metaTitle</title>
<meta name=\"description\" content=\"$metaDescription\"/>
<meta name=\"keywords\" content=\"$metaKeywords\"/>
...";
</source>

==Setup the menus==
*Make sure you are calling the [[functions:pageMenuGet|pageMenuGet]] function in the beginning of your code.
*Identify which menus you will need (top, left, bottom, right). Any of the four menu areas can be placed anywhere on the template, the names are simply for easy reference - so if a template actually has two top menus (tabs and then and action bar) but no right menu, use the right menu as the 2nd top menu.
*Create a menu in administration via menu manager, so you have some data to test. Set the menu as the default. If any of your menus are tiered, be sure to set up those menu bars with tiered content for an adequate test subject.
*Build your menus into the code. Refer to [[functions:pageMenuGet|pageMenuGet]] for usage and examples.

==Setup the banner zones==
*Create the zones you will need for this page in Banner Management. Fill them with sample campaigns/banners so they will display when we test.
*Make sure you are calling the [[functions:pageZoneGet|pageZoneGet]] function once for each banner zone you will place on the page.
*Identify the locations of the banner zones and place the variables you assigned to the pageZoneGet functions at those locations.

==Setup Perpetual Cart==
Only perform this task if this page will display a perpetual cart
*Be sure you are calling the [[functions:orderGetSummary|orderGetSummary]] function to retrieve the summarized cart data.
*Use the [[functions:dollarFormat|dollarFormat]] function to convert decimal currency values to formatted dollar amounts.

==Setup Cart and Checkout Links==
The following links are available to jump to stages in the checkout process:
*Shopping Cart: index.php?fa=ORDER.cartView
*Checkout Registration Page: index.php?fa=ORDER.register
*Checkout Shipping Address Page: index.php?fa=ORDER.checkoutShipping
*Checkout Billing Address Page: index.php?fa=ORDER.checkoutBilling
*Checking Payment Entry Page: index.php?fa=ORDER.checkoutPayment
*Checkout Confirmation Page: index.php?fa=ORDER.checkoutConfirmation
Typically the links to the shopping cart and checkout registration page (checkout link) are used in the perpetual cart. Note that these will link to empty pages until the checkout process templates are created, pages are created with the checkout process templates assigned to them AND the pageIds are entered into settings: eCommerce area for each of these pages.

==Setup any Custom Search Group fields==
Custom search groups are used to control select drop downs that jump to specific pages when options are selected. You must first create the group via Custom Search Groups in the administration console, than you can output the select field in a page template. Using Custom Search Groups gives content managers the ability to modify the contents of the drop down, and the target locations, using the administration console.
*Identify candidates for custom search groups
*Create groups in Custom Search Groups for each candidate (enter some temporary options for testing if you do not have real options available). Mark down the group IDs as each Custom Search Group is created, you will need for the next step.
*Create the select fields in administration by first calling the [[functions:pageCustomSearchGroup|pageCustomSearchGroup]] function at the beginning of your template code, then coding the select field at the point in the template the field is to appear (see examples in the pageCustomSearchGroup function for options on how to utilize and output the select field)

==Setup Page Specific Content==
Page specific content is all content that will be controlled by page management that is specific to this page. Since menu bars, perpetual carts, banner zones and other items listed before this section are shared by multiple pages, they do not fall into this category. Typically the center page content qualifies for this category. This can be populated with utilizing the Content fields in the [[The Administration Console:Page Templates:Core Variables|Core Variables]]. Any areas of control that cannot use core variables can be controlled by creating [[The Administration Console:Custom Fields|Custom Fields]].
*Identify your core variable controlled content and place the core variables into the code.
*Identify your custom field controlled content, create the custom fields and place the custom field variables into the code.

==Setup Children==
Skip this area if this page template is not to display children (as controlled by relationships in Page Management)
*Place your call to the [[functions:pageChildrenGet|pageChildrenGet]] function at the beginning of your page template code
*Output the children data in the appropriate location(s) in the template code. See the pageChildrenGet function for examples.

==Setup breacrumbs==
Skip this area if the template does not display breadcrumbs.
There are two methods of acquiring breadcrumbs:
*Use [[functions:pageBreadcrumbsFamilyGet|pageBreadcrumbsFamilyGet]] to build breadcrumbs by moving up through the relationships family tree
*Use [[functions:pageBreadcrumbsHistoryGet|pageBreadcrumbsHistoryGet]] to build breadcrumbs based on the page visit history

==Post Page Templates==
*Extract template includes and post each as an individual template
*Place template include code into remaining page template code ($component#Template)

Page Templates:Creating Your First Template

2008-12-07T00:02:22Z

James: /* Get your data */

{{Page Template Managers Shortcuts}}
This section assumes you have a completed html/css page that will be used to build this template.

Start by pasting the full code of the home page into your HTML editor of choice.

==Escape quotes==
As the template code is in PHP and all this content will have to be 'echo'd' be sure to escape all quotes so the echo statements do not fail. Search and Replace double quote (") with escaped double quote (\")

==Replace image / file paths==
Chances are the html was built referencing file and image paths that are not the same as the file structure set up on the ecommerce platform website. Search all file paths and replace with the path to the file on the new server. For example if the originating html uses "images/x/filename.jpg" and the images are located on the ecommerce platform website in "/files/imageshere/" you may want to search "images/" with "/files/imageshere". Don't forget to repath any javascript source and css files (I recommend creating css and js folders under the file folder designated for the site). Double check your files and images are uploaded to the correct folders on the ecommerce platform website. Note: if file paths are used in the CSS and JS files, they will need to be modified as well!

==Place PHP tags and Echo the whole thing==
Place an "echo" statement at the top and close the echo statement at the end. Note the beginning and ending PHP tags will NOT be copied into the template code - I only place them in my editor so that it activates the color coding for the PHP code:

<source lang="php">
// start echo
<?php
echo "
... all html here ...
";
// end echo with ";
?>
</source>

==Get your data==
The [[The Administration Console:Page Templates:Core Variables|Core Page Data]] is automatically available to you, but all additional content will need to be requested via the appropriate calling [[The Administration Console:Page Templates:Functions|functions]]. The ecommerce engine provides a series of [[The Administration Console:Page Templates:Functions|functions]] that return content in strings and arrays that can be used to control the html output. Initialize these functions at the beginning of your template. Example:

<source lang="php">
// start of template

// information to populate menu bars
$arrMenu = eV::pageMenuGet() ;
// children for this page. Note $pageId is a core variable available in the template
$arrChildren = eV::pageChildrenGet($pageId,"title,summary,summaryImage,link")
// get banner zones for this page
$zoneA = eV::pageZoneGet(1,$pageId);
$zoneB = eV::pageZoneGet(2,$pageId);
$zoneC = eV::pageZoneGet(3,$pageId);
// get data to populate breadcrumbs
$arrBC = eV::pageBreadcrumbsFamilyGet($pageId;
// get recently viewed items
$arrRV = eV::recentlyViewedGet("title,summaryImage,link");

// ... rest of template code ...
</source>
Only request the minimum number of functions, and fields within functions, necessary to support the template to ensure optimal performance.
Many functions are dependent on the existence of other objects in order to write the function. For instance, the eC::pageZoneGet() function requires the entry of a zoneId - the zone needs to be created in banner management before the ID exists, therefore you may need to create the banner zones before you can write the functions in your template code.

==Setup the 'message' output==
The ecommerce platform passes messages from page to page, action to page with the URL variable "message". The message is used to inform the visitor of actions that have occured (examples: "New coupon as been added to your cart", "invalid login - please try again", "You have been logged out", etc, etc). Many of these messages can by customized in the settings are of the administration console. You may also specify your own 'messages' when creating URLs in your code (example: href="index.php?pageId=123&message=You are in a very special page"). This message can be accessed in the page template code by the core variable "$message". It is recommended that on EVERY template you display this message prominently when passed. Example:

<source lang="php">
// ... code before message

if(!empty($message)) echo "$message";

// code after message ...
</source>

==Mark template include divisions==
Chances are, much of the code in this html will be reused in other templates. Most of the time a header and footer include can be identified, separated and later used as includes for other templates. The header usually includes all code from the beginning up until the center content that will vary from page to page, the footer begins immediately after the varying center content and continues to the end of the code. Often the header and footer are split into additional templates (header-top, header-left, footer-right, footer-bottom) in order to easily adapt to templates that may or may not use the left nav bar or right column contents.

Identify where these template includes began and end, end/begin echo statements at these points and mark them with comments denoting as such.

Note that sometimes the includes may by 'mostly' identical from template to template with some slight variations. Use variables to control these variations and pass values to the template include. For instance if the css file governing the page style is different for each template, substitute a variable for the css file path and set the variable in the template calling the include:

<source lang="php">
/* old code */

// start header-top include
echo "...<link href=\"/path/to/cssfile.css\" rel=\"stylesheet\" type=\"text/css\" media=\"screen\" />...";
// end header-top include

/* new code using variable */

// set path in template calling the include
$css= "/path/to/cssfile.css";
// change code in tag in include
// start header-top include
echo "...<link href=\"/$css\" rel=\"stylesheet\" type=\"text/css\" media=\"screen\" />...";
// end header-top include

</source>

This method is often used for banner ad zones, tag classes/ids that will vary from template to template but be part of a common include.

;Place variables in meta tags
Place the $metaTitle, $metaKeywords, $metaDescription in the meta tags so they will auto populate with page data:

<source lang="php">
echo "...
<title>$metaTitle</title>
<meta name=\"description\" content=\"$metaDescription\"/>
<meta name=\"keywords\" content=\"$metaKeywords\"/>
...";
</source>

==Setup the menus==
*Make sure you are calling the [[functions:pageMenuGet|pageMenuGet]] function in the beginning of your code.
*Identify which menus you will need (top, left, bottom, right). Any of the four menu areas can be placed anywhere on the template, the names are simply for easy reference - so if a template actually has two top menus (tabs and then and action bar) but no right menu, use the right menu as the 2nd top menu.
*Create a menu in administration via menu manager, so you have some data to test. Set the menu as the default. If any of your menus are tiered, be sure to set up those menu bars with tiered content for an adequate test subject.
*Build your menus into the code. Refer to [[functions:pageMenuGet|pageMenuGet]] for usage and examples.

==Setup the banner zones==
*Create the zones you will need for this page in Banner Management. Fill them wish sample campaigns/banners so they will display when we test.
*Make sure you are calling the [[functions:pageZoneGet|pageZoneGet]] function once for each banner zone you will place on the page.
*Identify the locations of the banner zones and place the variables you assigned to the pageZoneGet functions at those locations.

==Setup Perpetual Cart==
Only perform this task if this page will display a perpetual cart
*Be sure you are calling the [[functions:orderGetSummary|orderGetSummary]] function to retrieve the summarized cart data.
*Use the [[functions:dollarFormat|dollarFormat]] function to convert decimal currency values to formatted dollar amounts.

==Setup Cart and Checkout Links==
The following links are available to jump to stages in the checkout process:
*Shopping Cart: index.php?fa=ORDER.cartView
*Checkout Registration Page: index.php?fa=ORDER.register
*Checkout Shipping Address Page: index.php?fa=ORDER.checkoutShipping
*Checkout Billing Address Page: index.php?fa=ORDER.checkoutBilling
*Checking Payment Entry Page: index.php?fa=ORDER.checkoutPayment
*Checkout Confirmation Page: index.php?fa=ORDER.checkoutConfirmation
Typically the links to the shopping cart and checkout registration page (checkout link) are used in the perpetual cart. Note that these will link to empty pages until the checkout process templates are created, pages are created with the checkout process templates assigned to them AND the pageIds are entered into settings: eCommerce area for each of these pages.

==Setup any Custom Search Group fields==
Custom search groups are used to control select drop downs that jump to specific pages when options are selected. You must first create the group via Custom Search Groups in the administration console, than you can output the select field in a page template. Using Custom Search Groups gives content managers the ability to modify the contents of the drop down, and the target locations, using the administration console.
*Identify candidates for custom search groups
*Create groups in Custom Search Groups for each candidate (enter some temporary options for testing if you do not have real options available). Mark down the group IDs as each Custom Search Group is created, you will need for the next step.
*Create the select fields in administration by first calling the [[functions:pageCustomSearchGroup|pageCustomSearchGroup]] function at the beginning of your template code, then coding the select field at the point in the template the field is to appear (see examples in the pageCustomSearchGroup function for options on how to utilize and output the select field)

==Setup Page Specific Content==
Page specific content is all content that will be controlled by page management that is specific to this page. Since menu bars, perpetual carts, banner zones and other items listed before this section are shared by multiple pages, they do not fall into this category. Typically the center page content qualifies for this category. This can be populated with utilizing the Content fields in the [[The Administration Console:Page Templates:Core Variables|Core Variables]]. Any areas of control that cannot use core variables can be controlled by creating [[The Administration Console:Custom Fields|Custom Fields]].
*Identify your core variable controlled content and place the core variables into the code.
*Identify your custom field controlled content, create the custom fields and place the custom field variables into the code.

==Setup Children==
Skip this area if this page template is not to display children (as controlled by relationships in Page Management)
*Place your call to the [[functions:pageChildrenGet|pageChildrenGet]] function at the beginning of your page template code
*Output the children data in the appropriate location(s) in the template code. See the pageChildrenGet function for examples.

==Setup breacrumbs==
Skip this area if the template does not display breadcrumbs.
There are two methods of acquiring breadcrumbs:
*Use [[functions:pageBreadcrumbsFamilyGet|pageBreadcrumbsFamilyGet]] to build breadcrumbs by moving up through the relationships family tree
*Use [[functions:pageBreadcrumbsHistoryGet|pageBreadcrumbsHistoryGet]] to build breadcrumbs based on the page visit history

==Post Page Templates==
*Extract template includes and post each as an individual template
*Place template include code into remaining page template code ($component#Template)

Custom Fields

2008-12-05T04:37:17Z

James: /* Custom Field Attributes */

{{Page Template Managers Shortcuts}}
Custom fields include new field definitions that can be created on the fly as a tool to allow customization of certain site functions to cater to specific client needs. These fields can be created by administrators and are then available for content managers.

==Areas of the site the support custom fields==
;Users
:(via the user tab in “settings”).
:User custom fields created will be available to apply to all users in the system.
;Pages
:(via “page template management”).
:Page custom field settings will be available to all pages that use the template(s) in which the custom fields are created.

==Custom Field Attributes==
Each custom field created asks for the following attributes:
;Field Name
:this is the suffix that will be used when calling on the field (ex: set to “myField” if you want to access it via “custom_field_myField”). This must follow traditional PHP variable name requirements (must begin with a letter, contain only letters, numbers, underscores).
;Location
:this dictates where in the administration form the field will display relative to permanent fields. Enter the target field name and the word “before” or “after” to dictate where it will appear relative to the target field this dictates the description of the field in the administration form. What is entered here is exactly what the content manager will see adjacent to the field itself, describing the field. HTML is supported in this field.
;Default
:sets the default value of the field.
;Settings
:controls the field type and attributes.
:The following field types are available:

{|border=3
|-
!Field
!Attributes
!Example*
|-
|text
|attributes
|Text:size=20 maxlength=50
|-
|Radio
|Attributes:value
|Radio:onClick=”function();”:1
Radio::2
|-
|Button
|Attributes:value
|Button:onClick=”function();” style=”styledata”:Click me
Button::Click here
|-
|Submit
|Attributes:value
|Submit:onClick=”checkForm();”:submit
Submit::Go!
|-
|Page (modified text field)
Used to allow selection of a page from the page library, includes pop up link to select a page.
|attributes
|Page:size=20 maxlength=50
|-
|Image (modified text field)
Used to allow selection of an image. Includes link to image library for selection and presentation of selected image below field.
|attributes
|Image:size=20 maxlength=50
|-
|Password
|Attributes
|Password:size=20 maxlength=50
|-
|File
Presented file field. If type is “image” than also presents the image itself below the field.
|Attributes:type(image,other)
|File:size=20 maxlength=50:other
|-
|Hidden
|Value
|Hidden:my hidden value
|-
|Checkbox
|Attributes:value
|Checkbox:onClick=”myfunction();”:1
Checkbox::0
|-
|Textarea
|Attributes
|Textarea:cols=50 rows=4
|-
|Select
Options are delimited by colon “:”. Value / Text pairs are delimited by pipe “|” where value is before the pipe, text after. If no pipe is presented BOTH the value and text will be the entered value.
|Attributes:val1[|text1[:val2[|text2]]]…
|Select:size=4:value1|text1:value2|text2
Select:multiple:valueA:valueB:valueC
Select::1|one:2|two:3|three:4|four
|-
|SepDate
Creates drop downs for month / day / year
|~none~
|sepdate
|-
|SepDateTime
Creates drop downs for month / day / year hour : minute
|~none~
|sepdate
|}

Page Templates

2008-12-05T04:22:17Z

James:

{{Page Template Managers Shortcuts}}
Page templates are used to dictate how BOTH the page management forms will operate, and how the content entered into those page management forms will display and behave to site visitors. Any number of page templates can be created to support the site requirements. Page templates can also be split into ‘includes’ to more easily manage repeated code. The templates created here will be available for selection in the page management area of administration when creating/editing pages.

===For more on page templates===

;About Page Templates:
''It is recommended you read all the following items before creating your first template''
*[[Page Templates:First Look]]
*[[Page field availability]] - How to turn off / turn on and rename core fields
*[[Custom Fields]] - How to add and organize your own, custom fields
*[[Page Templates:Core Variables]] - These variables will be available to you when creating/editing templates
*[[Page Templates:Functions]] - These functions will be available to you when creating /editing templates. Functions are used to:
:*Get child pages (cross sells, subcategories, upsells, products in pages...)
:*Get product information (pricing, options, content...)
:*Get order information (build perpetual carts, shopping cart, checkout pages and order receipts...)
:*Get user information (create account, blogs, account management, address book management, wish list management...)
:*Get web 2.0 content (blogs, polls, comments/forums...)
:*Get additional page content (ad banners, breadcrumbs, recently viewed...)
:*Useful information (get city, county, longitude, latitude and other information from a zip code)
:*Shortcuts to make your job easier (quick content for state drop downs, country drop downs, format numbers into dollar output)

;See [[Page Templates:Examples]] for template code ideas for many common applications.

Settings:First Use

2008-12-05T04:20:43Z

James: /* Users */

Advice: Keep it simple. Only enable functions that the client specifically asked for in order to avoid unnecessary clutter and confusion.

==Site Management==
*Enter the site URL “http://www.website.com” and secured site URLs (which may be the same as the site URL until the SSL certificate is received and installed).
*Set the physical root to the web site – this is required for many functions of the admin console to operate including image / file upload.
*Set the root folders for images and files. These will be used by the image and file management libraries as a starting point and top level restriction (users cannot navigate above these folders) for navigation to images and folders. The images folder can exist within the files folder if you wish. Make sure these folders exist on the server with appropriate rights and privileges assigned.
*If you are using multiple domains to access this web site, it is recommended to use the ‘force URLs to this domain option’ which will place all visitors into the same domain regardless of requested domain. This will satisfy cookies/sessions (as they prefer to be only available to their creating domain) and also makes third party web services happy (as many of them control access, and organize data based on domain name). Enter just the domain name without leading protocol ( example: www.mywebsite.com)
*Left menu bar should be checked unless the site isn’t using a left menu (very rare). Unchecking this box hides the left menu bar controls in the menu management area of administration.
*Leave languages empty unless you plan on supporting multiple languages on the website. If this is the case, please contact Whirlwind for requirements of using multiple languages.

==Page Management==
*“Reload page management on template change” should always be checked. This forces the page to reload when a template is selected, so the form will display the appropriate custom fields for that template. Only uncheck if the site will never use templates with custom fields.
*“Use Landing Pages” should be elected if the web site will use landing pages to govern different home pages based on user preferences.
*“Users that can manage pages” can be used to designate a group that has the rights to manage page content (create user groups in the Groups area of management). Administrators always have this ability (along with every possible privilege in administration). Only use this option is the client has expressed a need to have content managers who can manage page content but not have access to anything else.
*“Users that can edit pages but require approval from managers” sets a group who’s members can edit content that must be approved before going live. Note that page content changes submitted by these users are automatically emailed to users with the rights to manage pages. Only use this option if the client requires to have a junior level of content managers who’s changes and entries require approval before being posted live on the web site.
*Automated page email controls sets the email contents for the page approval process. Only enter data here if junior content editors will be used.
*“Page default template” sets the template that all new pages will be set to when created. You will probably be setting this after you get your templates into the system
*“Printable default template” and “Mobile default template” are used to pre-populate these template selections for new pages.
*“Selectable as an author for a page” dictates a group that will contain users that will be selectable as an author to a page in page management. You may need to create an author group in Groups before making this assignment. Only use this if you will be using page publishing fields (publisher, publish date, author) in page management (settable in the Page Fields tab of Settings).
*“Use page authorization” activates the page restriction functions of the web site. Turning this on will make all pages unavailable unless the user belongs to a group authorized to view the page. If enabled, a group assignment tool will be available in page management under the access tab. The everyone group can be used to make the page available to everyone, including folks not logged in (make sure your home page is set to everyone, if page authorization is elected or the site will be inaccessible). You can set default groups that pages will be assigned to using the “default user groups for new pages” option. Note that when page authorization is activated, all existing pages currently in the system will not belong to any groups and be inaccessible.
*“Style Sheets” sets the default style sheets (separated by commas) that will be used by the WYSIWYG editor in page management. These stylesheets can be overruled on a per template bases by setting the style sheets with the templates. Note that often specific style sheets need to be created for this area in addition to the style sheets actually used by the outputting page seen by visitors, as the WYSIWYG editor will not be subject to parent classes, ids that this content will be subject to when the page is displayed.
*“Search Page ID” sets the page id that will be used to display search results. This will most likely be set after the template and page are created for keyword search results.
*“404 (Not Found) Page ID” lets you set a page to be shown when a 404 error occurs. This requires the web server have 404 error set to go to index.php in the root of this web site.
*“Send2Friend Email Subject and Body” Set the contents of the email that is sent when the “send this page to a friend” function is used. Note the list of variables below the field which can be entered directly into the contents of the body or subject.
*“Summary Listing Details” dictates how admin search results for pages will be displayed. Alter this to use the fields that will be available to content managers.
*“Record Page Views” turns on advanced page activity tracking. With each page, all incoming and state variables (post, get, site, cookie, session) are recorded along with order and user data. Great for debugging, but uses a lot of system resources and can significantly handicap the speed of the web site.
*“Banner Management” makes banner management functions available in administration. A group can be created and assigned to have rights to manage banner ads.
*“Page Caching” makes server side page content caching available. Page caching significantly increases the performance of the site, especially on pages that have heavy processing requirements. Page caching cannot be used if any content on the page is to be session or state specific (perpetual carts, “Welcome Mr Jones”). Note that if enabled site wide (here), page caching can also be micromanaged on a per page basis – allowing heavily traffic’d pages to have session specific data removed and be cached, while other pages are not. Page caching is tightly integrated into the management console so that changes in administration that effect pages will trigger the effected pages to refresh in the cache automatically.
*“Pages as Events” adds event controls to page management. These allow a page to be set as an event, along with controlling start end dates. Event pages will qualify for event search functions that can be used to populate calendar pages.

==Page Fields==
*“Use Publisher information” makes the publishing fields available in the ‘other’ tab of page management. These include an author (selected from the users belonging to group assigned to author in the Page Management tab of Settings), a publisher and a publish date. These fields then become available in the template for output.
*“Publisher default” sets the default value of the publisher field.
*“Use breadcrumb, page notice, sub title, summary information link text, image caption” turn on / off these fields in page management. If they are not necessary for any of the templates then turning them off will remove unnecessary clutter from the page management form.
*The “Rename” fields allow you to change the name of the fields as they are presented in the page management form. This accommodates clients who are accustomed to specific language governing their content (for example, publishing clients use headline, subhead and deck in place of notice, title and subtitle). Often page name is substituted for notice giving page managers a way to uniquely identify each page in a recognizable manner. The rename fields can also allow for html to be included (for instance if you would like the meta title to copy the title value when a link is pressed, write the HTML for the link and javascript in here).

==Web 2.0==
Here forums, polling and blogging can be enabled and configured. Note that templates will have to be created to support each, if they are to be used. Only activate if the client requires these functions.
*“forums available” turns on / off forum availability on the site
*“Page forum template” sets the default template when a content manager elects to create a forum via page management.
*“Users that can manage forums” sets the user group that has the rights to view, approve and edit forum posts.
*“Embed forum replies in parent post” actually places the post content of target posts into reply postings. This is useful if regularly purging the system of old posts (so replies still retain the source post even after the source post is deleted). For ‘commenting’ pages (commenting on products) this is not necessary since they typically do not incorporate ability to reply like typical forums.
*“Submissions are posted live” will circumvent the approval process. If unchecked posts will not be visible to web site visitors until approved via the forums queue. If checked, they will be visible immediately.
*“Require Login for Forum Posts” requires visitors to be logged into user accounts to post. This disallows anonymous posting. While this does make forum users a little less likely to post objectionable /inappropriate content, it will make the posting process more difficult therefore visitors will be less likely to use it.
*“Submissions posted live by these users” allows designation of a user group that circumvents the queue approval process of posts (a.k.a. trusted forum users).
*“Days to keep forum posts before purging” will automatically purge posts after a certain period of time. With excessive post activity, the system could slow down after months, years of posts. Purging old posts will help keep the database a manageable size and improve performance.
*“Polling Available” turns on / off polling availability on the site.
*“Require Login” requires that poll visitors be logged into an account in order to submit a poll vote.
*“Poll Default Template” sets the default template for all “new polls” created in page management.
*“Blogging available” turns on / off blogging availability on the site.
*“Blog default template” sets the default template for all “new blogs” created in page management. Also sets the template to be adopted when users create their own blogs, if this is available on the web site.
*“Users that can have a blog” allows restriction of blog creation and management to users belonging to a specific group
*“Blog entries default template” sets the template to be adopted by each blog entry posted to a blog. Note that the blog itself is a page and each entry is also another page in page management.
*“Blog entries default as forums” will set blog entries to have forum controls available automatically, allowing visitors to comment on the blog. Templates must be designed with forums in mind in order to display them when the blog page is a forum.

==Campaigns==
*“Email campaign available” turns on / off the availability of campaign management tools
*“Users that can manage email campaigns” allows a group’s user members to have the privilege of using campaign management tools.
*“Double Opt In Success URL” dictates the URL the visitor is forwarded to after they have successfully opted into the email campaign via the automated email. Example “/index.php?pageId=123&message=You%20are%20now%20registered!”
*“Double opt in failure URL” dictates the URL the visitor is forwarded to on failed double opt in attempts. These could be the result of hack attempts or malformed URLs in the emails due to client email browsers performing physical wraps mid URL. Example: “/index.php?pageId=234&message=Failed%20registration%20attempt”
*“Double opt out success URL” dictates the URL the visitor is forward to following successfully opting out of the campaign system. Example: “/index.php?pageId=345&message=You%20have%20will%20no%20longer%20receive%20emails”
*“Double opt out failure URL” dictates the URL the visitor will forward to following a failed double opt out attempt. These could be the result of hack attempts or malformed URLs in the emails fur to client email browsers performing physical wraps min URL. Example: “/index.php?page=456&message=Invalid%20opt%20out%20attempt”
*“Registration Email” fields dictate the contents of the automated email that is sent upon registration for the campaign system. “Registration Email PageId” allows for the use of a page in the page management system as the sent email instead of the “Registration Email Body” – enter only the page ID here.
*“Registration Type” dictates if the system is opt in (requiring the registering visitor to verify via an automated email before they qualify) or opt out (meaning the registering visitor is automatically qualified after submitting an email address via the website, but will receive an email with instructions on how to opt out). Opt in, while less convenient for visitors, ensures all registrations are legitimate which will help to avoid being blacklisted by spam systems.

==eCommerce==
*“eCommerce available” turns on/ off the availability of eCommerce and related tools.
*“Page IDs” (cart, registration, shipping, billing, payment, checkout…) dictate the pages that will be used as these stages in the shopping cart and purchase process. Simply enter the Page IDs into these fields after they are created in the system. The eCommerce URLs will utilize these pages to build their content (CART.view, ORDER.register, ORDER.checkoutShipping, ORDER.checkoutBilling, ORDERcheckoutPayment, ORDER.checkoutConfirmation, ORDER.checkoutComplete)
*“Email Invoice” fields will control the email that is automatically delivered to a customer following an order. The “Emailed Invoice Header” and “Emailed Invoice Footer” will “wrap” around the actual receipt that will be present in the email.
*“Product Configuration Available” turns on/off the product configuration tool in product management. The product configuration tool allows managers to control “personalized” products and their presentation. For example: greeting cards, personalized logod pens, and other products that give visitors a significant amount of control over product presentation.
*“Pricing Matrices Available” turns on / off shared pricing level / matrix tools. These tools allow content managers to set per-quantity price discount ‘groups’ that can be reused from product to product. With this component disabled, content managers may still manage per-quantity pricing matrices on a per product basis, though they will not be able to use ‘shared’ matrices between multiple products.
*“TriggerEmailMarketing” fields turn on / off, and configure the ACORN Trigger Email Marketing functions.
*“Users that can manage products” dictates a user group that has control over product management functions (this includes product management, price matrix, shared product options, tax management, shipping management, discount management)
*“Users that can manage orders” dictates a user group that can lookup and manage orders in the system.

==Users==
*“Users that can manage users and access” dictates a group that can lookup, edit, add and change access of all users.
*“Failed Access Authorization URL forward” dictates the URL that a visitor will be forwarded to in the event they attempt to access something (a page, document, etc) that they do not have access for. Example: “/index.php?pageId=124&message=Invalid%20access%20attempt”
*“Login successfully URL forward” dictates the default URL that a visitor will be forwarded to following a successful login. This can be overridden by use of the “redirect” form field in the login form. Example: “/index.php?pageId=112&message=You%20have%20successully%20logged%20in”. This is set to “index.php?fa=PAGE.manage” be default so that logging into the initial login form will present the administration console.
*“Failed attempt login URL forward” dictates the default URL that a visitor will be forward to following a failed login attempt. The can be overridden by use of the “redirectOnFailure” form field in the login form. Typically this is set to forward back to the login form itself with a message about the failed login. Example: “/index.php?pageId=135&message=Invalid%20login%20please%20try%20again”
*“Logout URL forward” dictates the default URL that a visitor will be forwarded to following logout. This can be overridden by use of the “redirect” querystring attribute in the logout URL (example of override in querystring: index.php?fa=USER.logout&redirect=my/redirect.page). Example Logout URL forward value: “/index.php?pageId=432&message=You%20have%20been%20logged%20out”
*“Password expired link” is the URL the visitor will be forwarded to when attempting to log into an account that has an expired password. Typically this is forwarded to the account management form that allows a visitor to set their password. Example: “index.php?pageId=146&message=Password%20expired%20please%20change%20your%20password”
*“Lost password settings” set the contents of the email that is automatically sent when a visitor requests their lost password.
*“Custom User Fields” allows creation of custom fields that will be available for user accounts. These fields will be automatically presented in the user management form located in “users’ of the administration console. Template managers will be required to specially call and integrate these fields into each management form they wish to present them within. For additional information on custom field setup, see “custom fields” below.

Settings:First Use

2008-12-05T04:13:18Z

James: /* Campaigns */

Advice: Keep it simple. Only enable functions that the client specifically asked for in order to avoid unnecessary clutter and confusion.

==Site Management==
*Enter the site URL “http://www.website.com” and secured site URLs (which may be the same as the site URL until the SSL certificate is received and installed).
*Set the physical root to the web site – this is required for many functions of the admin console to operate including image / file upload.
*Set the root folders for images and files. These will be used by the image and file management libraries as a starting point and top level restriction (users cannot navigate above these folders) for navigation to images and folders. The images folder can exist within the files folder if you wish. Make sure these folders exist on the server with appropriate rights and privileges assigned.
*If you are using multiple domains to access this web site, it is recommended to use the ‘force URLs to this domain option’ which will place all visitors into the same domain regardless of requested domain. This will satisfy cookies/sessions (as they prefer to be only available to their creating domain) and also makes third party web services happy (as many of them control access, and organize data based on domain name). Enter just the domain name without leading protocol ( example: www.mywebsite.com)
*Left menu bar should be checked unless the site isn’t using a left menu (very rare). Unchecking this box hides the left menu bar controls in the menu management area of administration.
*Leave languages empty unless you plan on supporting multiple languages on the website. If this is the case, please contact Whirlwind for requirements of using multiple languages.

==Page Management==
*“Reload page management on template change” should always be checked. This forces the page to reload when a template is selected, so the form will display the appropriate custom fields for that template. Only uncheck if the site will never use templates with custom fields.
*“Use Landing Pages” should be elected if the web site will use landing pages to govern different home pages based on user preferences.
*“Users that can manage pages” can be used to designate a group that has the rights to manage page content (create user groups in the Groups area of management). Administrators always have this ability (along with every possible privilege in administration). Only use this option is the client has expressed a need to have content managers who can manage page content but not have access to anything else.
*“Users that can edit pages but require approval from managers” sets a group who’s members can edit content that must be approved before going live. Note that page content changes submitted by these users are automatically emailed to users with the rights to manage pages. Only use this option if the client requires to have a junior level of content managers who’s changes and entries require approval before being posted live on the web site.
*Automated page email controls sets the email contents for the page approval process. Only enter data here if junior content editors will be used.
*“Page default template” sets the template that all new pages will be set to when created. You will probably be setting this after you get your templates into the system
*“Printable default template” and “Mobile default template” are used to pre-populate these template selections for new pages.
*“Selectable as an author for a page” dictates a group that will contain users that will be selectable as an author to a page in page management. You may need to create an author group in Groups before making this assignment. Only use this if you will be using page publishing fields (publisher, publish date, author) in page management (settable in the Page Fields tab of Settings).
*“Use page authorization” activates the page restriction functions of the web site. Turning this on will make all pages unavailable unless the user belongs to a group authorized to view the page. If enabled, a group assignment tool will be available in page management under the access tab. The everyone group can be used to make the page available to everyone, including folks not logged in (make sure your home page is set to everyone, if page authorization is elected or the site will be inaccessible). You can set default groups that pages will be assigned to using the “default user groups for new pages” option. Note that when page authorization is activated, all existing pages currently in the system will not belong to any groups and be inaccessible.
*“Style Sheets” sets the default style sheets (separated by commas) that will be used by the WYSIWYG editor in page management. These stylesheets can be overruled on a per template bases by setting the style sheets with the templates. Note that often specific style sheets need to be created for this area in addition to the style sheets actually used by the outputting page seen by visitors, as the WYSIWYG editor will not be subject to parent classes, ids that this content will be subject to when the page is displayed.
*“Search Page ID” sets the page id that will be used to display search results. This will most likely be set after the template and page are created for keyword search results.
*“404 (Not Found) Page ID” lets you set a page to be shown when a 404 error occurs. This requires the web server have 404 error set to go to index.php in the root of this web site.
*“Send2Friend Email Subject and Body” Set the contents of the email that is sent when the “send this page to a friend” function is used. Note the list of variables below the field which can be entered directly into the contents of the body or subject.
*“Summary Listing Details” dictates how admin search results for pages will be displayed. Alter this to use the fields that will be available to content managers.
*“Record Page Views” turns on advanced page activity tracking. With each page, all incoming and state variables (post, get, site, cookie, session) are recorded along with order and user data. Great for debugging, but uses a lot of system resources and can significantly handicap the speed of the web site.
*“Banner Management” makes banner management functions available in administration. A group can be created and assigned to have rights to manage banner ads.
*“Page Caching” makes server side page content caching available. Page caching significantly increases the performance of the site, especially on pages that have heavy processing requirements. Page caching cannot be used if any content on the page is to be session or state specific (perpetual carts, “Welcome Mr Jones”). Note that if enabled site wide (here), page caching can also be micromanaged on a per page basis – allowing heavily traffic’d pages to have session specific data removed and be cached, while other pages are not. Page caching is tightly integrated into the management console so that changes in administration that effect pages will trigger the effected pages to refresh in the cache automatically.
*“Pages as Events” adds event controls to page management. These allow a page to be set as an event, along with controlling start end dates. Event pages will qualify for event search functions that can be used to populate calendar pages.

==Page Fields==
*“Use Publisher information” makes the publishing fields available in the ‘other’ tab of page management. These include an author (selected from the users belonging to group assigned to author in the Page Management tab of Settings), a publisher and a publish date. These fields then become available in the template for output.
*“Publisher default” sets the default value of the publisher field.
*“Use breadcrumb, page notice, sub title, summary information link text, image caption” turn on / off these fields in page management. If they are not necessary for any of the templates then turning them off will remove unnecessary clutter from the page management form.
*The “Rename” fields allow you to change the name of the fields as they are presented in the page management form. This accommodates clients who are accustomed to specific language governing their content (for example, publishing clients use headline, subhead and deck in place of notice, title and subtitle). Often page name is substituted for notice giving page managers a way to uniquely identify each page in a recognizable manner. The rename fields can also allow for html to be included (for instance if you would like the meta title to copy the title value when a link is pressed, write the HTML for the link and javascript in here).

==Web 2.0==
Here forums, polling and blogging can be enabled and configured. Note that templates will have to be created to support each, if they are to be used. Only activate if the client requires these functions.
*“forums available” turns on / off forum availability on the site
*“Page forum template” sets the default template when a content manager elects to create a forum via page management.
*“Users that can manage forums” sets the user group that has the rights to view, approve and edit forum posts.
*“Embed forum replies in parent post” actually places the post content of target posts into reply postings. This is useful if regularly purging the system of old posts (so replies still retain the source post even after the source post is deleted). For ‘commenting’ pages (commenting on products) this is not necessary since they typically do not incorporate ability to reply like typical forums.
*“Submissions are posted live” will circumvent the approval process. If unchecked posts will not be visible to web site visitors until approved via the forums queue. If checked, they will be visible immediately.
*“Require Login for Forum Posts” requires visitors to be logged into user accounts to post. This disallows anonymous posting. While this does make forum users a little less likely to post objectionable /inappropriate content, it will make the posting process more difficult therefore visitors will be less likely to use it.
*“Submissions posted live by these users” allows designation of a user group that circumvents the queue approval process of posts (a.k.a. trusted forum users).
*“Days to keep forum posts before purging” will automatically purge posts after a certain period of time. With excessive post activity, the system could slow down after months, years of posts. Purging old posts will help keep the database a manageable size and improve performance.
*“Polling Available” turns on / off polling availability on the site.
*“Require Login” requires that poll visitors be logged into an account in order to submit a poll vote.
*“Poll Default Template” sets the default template for all “new polls” created in page management.
*“Blogging available” turns on / off blogging availability on the site.
*“Blog default template” sets the default template for all “new blogs” created in page management. Also sets the template to be adopted when users create their own blogs, if this is available on the web site.
*“Users that can have a blog” allows restriction of blog creation and management to users belonging to a specific group
*“Blog entries default template” sets the template to be adopted by each blog entry posted to a blog. Note that the blog itself is a page and each entry is also another page in page management.
*“Blog entries default as forums” will set blog entries to have forum controls available automatically, allowing visitors to comment on the blog. Templates must be designed with forums in mind in order to display them when the blog page is a forum.

==Campaigns==
*“Email campaign available” turns on / off the availability of campaign management tools
*“Users that can manage email campaigns” allows a group’s user members to have the privilege of using campaign management tools.
*“Double Opt In Success URL” dictates the URL the visitor is forwarded to after they have successfully opted into the email campaign via the automated email. Example “/index.php?pageId=123&message=You%20are%20now%20registered!”
*“Double opt in failure URL” dictates the URL the visitor is forwarded to on failed double opt in attempts. These could be the result of hack attempts or malformed URLs in the emails due to client email browsers performing physical wraps mid URL. Example: “/index.php?pageId=234&message=Failed%20registration%20attempt”
*“Double opt out success URL” dictates the URL the visitor is forward to following successfully opting out of the campaign system. Example: “/index.php?pageId=345&message=You%20have%20will%20no%20longer%20receive%20emails”
*“Double opt out failure URL” dictates the URL the visitor will forward to following a failed double opt out attempt. These could be the result of hack attempts or malformed URLs in the emails fur to client email browsers performing physical wraps min URL. Example: “/index.php?page=456&message=Invalid%20opt%20out%20attempt”
*“Registration Email” fields dictate the contents of the automated email that is sent upon registration for the campaign system. “Registration Email PageId” allows for the use of a page in the page management system as the sent email instead of the “Registration Email Body” – enter only the page ID here.
*“Registration Type” dictates if the system is opt in (requiring the registering visitor to verify via an automated email before they qualify) or opt out (meaning the registering visitor is automatically qualified after submitting an email address via the website, but will receive an email with instructions on how to opt out). Opt in, while less convenient for visitors, ensures all registrations are legitimate which will help to avoid being blacklisted by spam systems.

==eCommerce==
*“eCommerce available” turns on/ off the availability of eCommerce and related tools.
*“Page IDs” (cart, registration, shipping, billing, payment, checkout…) dictate the pages that will be used as these stages in the shopping cart and purchase process. Simply enter the Page IDs into these fields after they are created in the system. The eCommerce URLs will utilize these pages to build their content (CART.view, ORDER.register, ORDER.checkoutShipping, ORDER.checkoutBilling, ORDERcheckoutPayment, ORDER.checkoutConfirmation, ORDER.checkoutComplete)
*“Email Invoice” fields will control the email that is automatically delivered to a customer following an order. The “Emailed Invoice Header” and “Emailed Invoice Footer” will “wrap” around the actual receipt that will be present in the email.
*“Product Configuration Available” turns on/off the product configuration tool in product management. The product configuration tool allows managers to control “personalized” products and their presentation. For example: greeting cards, personalized logod pens, and other products that give visitors a significant amount of control over product presentation.
*“Pricing Matrices Available” turns on / off shared pricing level / matrix tools. These tools allow content managers to set per-quantity price discount ‘groups’ that can be reused from product to product. With this component disabled, content managers may still manage per-quantity pricing matrices on a per product basis, though they will not be able to use ‘shared’ matrices between multiple products.
*“TriggerEmailMarketing” fields turn on / off, and configure the ACORN Trigger Email Marketing functions.
*“Users that can manage products” dictates a user group that has control over product management functions (this includes product management, price matrix, shared product options, tax management, shipping management, discount management)
*“Users that can manage orders” dictates a user group that can lookup and manage orders in the system.

==Users==
*“Users that can manage users and access” dictates a group that can lookup, edit, add and change access of all users.
*“Failed Access Authorization URL forward” dictates the URL that a visitor will be forwarded to in the event they attempt to access something (a page, document, etc) that they do not have access for. Example: “/index.php?pageId=124&message=Invalid%20access%20attempt”
*“Login successfully URL forward” dictates the default URL that a visitor will be forwarded to following a successful login. This can be overrided by use of the “redirect” form field in the login form. Example: “/index.php?pageId=112&message=You%20have%20successully%20logged%20in”. This is set to “index.php?fa=PAGE.manage” be default so that logging into the initial login form will present the administration console.
*“Failed attempt login URL forward” dictates the default URL that a visitor will be forward to following a failed login attempt. The can be overrided by use of the “redirectOnFailure” form field in the login form. Typically this is set to forward back to the login form itself with a message about the failed login. Example: “/index.php?pageId=135&message=Invalid%20login%20please%20try%20again”
*“Logout URL forward” dictates the default URL that a visitor will be forwarded to following logout. This can be overrided by use of the “redirecte” querystring attribute in the logout URL (example of override in querystring: index.php?fa=USER.logout&redirect=my/redirect.page). Example Logout URL forward value: “/index.php?pageId=432&message=You%20have%20been%20logged%20out”
*“Password expired link” is the URL the visitor will be forwarded to when attempting to log into an account that has an expired password. Typically this is forwarded to the account management form that allows a visitor to set their password. Example: “index.php?pageId=146&message=Password%20expired%20please%20change%20your%20password”
*“Lost password settings” set the contents of the email that is automatically sent when a visitor requests their lost password.
*“Custom User Fields” allows creation of custom fields that will be available for user accounts. These fields will be automatically presented in the user management form located in “users’ of the administration console. Template managers will be required to specially call and integrate these fields into each management form they wish to present them within. For additional information on custom field setup, see “custom fields” below.

Settings:First Use

2008-12-05T03:58:27Z

James: /* Web 2.0 */

Advice: Keep it simple. Only enable functions that the client specifically asked for in order to avoid unnecessary clutter and confusion.

==Site Management==
*Enter the site URL “http://www.website.com” and secured site URLs (which may be the same as the site URL until the SSL certificate is received and installed).
*Set the physical root to the web site – this is required for many functions of the admin console to operate including image / file upload.
*Set the root folders for images and files. These will be used by the image and file management libraries as a starting point and top level restriction (users cannot navigate above these folders) for navigation to images and folders. The images folder can exist within the files folder if you wish. Make sure these folders exist on the server with appropriate rights and privileges assigned.
*If you are using multiple domains to access this web site, it is recommended to use the ‘force URLs to this domain option’ which will place all visitors into the same domain regardless of requested domain. This will satisfy cookies/sessions (as they prefer to be only available to their creating domain) and also makes third party web services happy (as many of them control access, and organize data based on domain name). Enter just the domain name without leading protocol ( example: www.mywebsite.com)
*Left menu bar should be checked unless the site isn’t using a left menu (very rare). Unchecking this box hides the left menu bar controls in the menu management area of administration.
*Leave languages empty unless you plan on supporting multiple languages on the website. If this is the case, please contact Whirlwind for requirements of using multiple languages.

==Page Management==
*“Reload page management on template change” should always be checked. This forces the page to reload when a template is selected, so the form will display the appropriate custom fields for that template. Only uncheck if the site will never use templates with custom fields.
*“Use Landing Pages” should be elected if the web site will use landing pages to govern different home pages based on user preferences.
*“Users that can manage pages” can be used to designate a group that has the rights to manage page content (create user groups in the Groups area of management). Administrators always have this ability (along with every possible privilege in administration). Only use this option is the client has expressed a need to have content managers who can manage page content but not have access to anything else.
*“Users that can edit pages but require approval from managers” sets a group who’s members can edit content that must be approved before going live. Note that page content changes submitted by these users are automatically emailed to users with the rights to manage pages. Only use this option if the client requires to have a junior level of content managers who’s changes and entries require approval before being posted live on the web site.
*Automated page email controls sets the email contents for the page approval process. Only enter data here if junior content editors will be used.
*“Page default template” sets the template that all new pages will be set to when created. You will probably be setting this after you get your templates into the system
*“Printable default template” and “Mobile default template” are used to pre-populate these template selections for new pages.
*“Selectable as an author for a page” dictates a group that will contain users that will be selectable as an author to a page in page management. You may need to create an author group in Groups before making this assignment. Only use this if you will be using page publishing fields (publisher, publish date, author) in page management (settable in the Page Fields tab of Settings).
*“Use page authorization” activates the page restriction functions of the web site. Turning this on will make all pages unavailable unless the user belongs to a group authorized to view the page. If enabled, a group assignment tool will be available in page management under the access tab. The everyone group can be used to make the page available to everyone, including folks not logged in (make sure your home page is set to everyone, if page authorization is elected or the site will be inaccessible). You can set default groups that pages will be assigned to using the “default user groups for new pages” option. Note that when page authorization is activated, all existing pages currently in the system will not belong to any groups and be inaccessible.
*“Style Sheets” sets the default style sheets (separated by commas) that will be used by the WYSIWYG editor in page management. These stylesheets can be overruled on a per template bases by setting the style sheets with the templates. Note that often specific style sheets need to be created for this area in addition to the style sheets actually used by the outputting page seen by visitors, as the WYSIWYG editor will not be subject to parent classes, ids that this content will be subject to when the page is displayed.
*“Search Page ID” sets the page id that will be used to display search results. This will most likely be set after the template and page are created for keyword search results.
*“404 (Not Found) Page ID” lets you set a page to be shown when a 404 error occurs. This requires the web server have 404 error set to go to index.php in the root of this web site.
*“Send2Friend Email Subject and Body” Set the contents of the email that is sent when the “send this page to a friend” function is used. Note the list of variables below the field which can be entered directly into the contents of the body or subject.
*“Summary Listing Details” dictates how admin search results for pages will be displayed. Alter this to use the fields that will be available to content managers.
*“Record Page Views” turns on advanced page activity tracking. With each page, all incoming and state variables (post, get, site, cookie, session) are recorded along with order and user data. Great for debugging, but uses a lot of system resources and can significantly handicap the speed of the web site.
*“Banner Management” makes banner management functions available in administration. A group can be created and assigned to have rights to manage banner ads.
*“Page Caching” makes server side page content caching available. Page caching significantly increases the performance of the site, especially on pages that have heavy processing requirements. Page caching cannot be used if any content on the page is to be session or state specific (perpetual carts, “Welcome Mr Jones”). Note that if enabled site wide (here), page caching can also be micromanaged on a per page basis – allowing heavily traffic’d pages to have session specific data removed and be cached, while other pages are not. Page caching is tightly integrated into the management console so that changes in administration that effect pages will trigger the effected pages to refresh in the cache automatically.
*“Pages as Events” adds event controls to page management. These allow a page to be set as an event, along with controlling start end dates. Event pages will qualify for event search functions that can be used to populate calendar pages.

==Page Fields==
*“Use Publisher information” makes the publishing fields available in the ‘other’ tab of page management. These include an author (selected from the users belonging to group assigned to author in the Page Management tab of Settings), a publisher and a publish date. These fields then become available in the template for output.
*“Publisher default” sets the default value of the publisher field.
*“Use breadcrumb, page notice, sub title, summary information link text, image caption” turn on / off these fields in page management. If they are not necessary for any of the templates then turning them off will remove unnecessary clutter from the page management form.
*The “Rename” fields allow you to change the name of the fields as they are presented in the page management form. This accommodates clients who are accustomed to specific language governing their content (for example, publishing clients use headline, subhead and deck in place of notice, title and subtitle). Often page name is substituted for notice giving page managers a way to uniquely identify each page in a recognizable manner. The rename fields can also allow for html to be included (for instance if you would like the meta title to copy the title value when a link is pressed, write the HTML for the link and javascript in here).

==Web 2.0==
Here forums, polling and blogging can be enabled and configured. Note that templates will have to be created to support each, if they are to be used. Only activate if the client requires these functions.
*“forums available” turns on / off forum availability on the site
*“Page forum template” sets the default template when a content manager elects to create a forum via page management.
*“Users that can manage forums” sets the user group that has the rights to view, approve and edit forum posts.
*“Embed forum replies in parent post” actually places the post content of target posts into reply postings. This is useful if regularly purging the system of old posts (so replies still retain the source post even after the source post is deleted). For ‘commenting’ pages (commenting on products) this is not necessary since they typically do not incorporate ability to reply like typical forums.
*“Submissions are posted live” will circumvent the approval process. If unchecked posts will not be visible to web site visitors until approved via the forums queue. If checked, they will be visible immediately.
*“Require Login for Forum Posts” requires visitors to be logged into user accounts to post. This disallows anonymous posting. While this does make forum users a little less likely to post objectionable /inappropriate content, it will make the posting process more difficult therefore visitors will be less likely to use it.
*“Submissions posted live by these users” allows designation of a user group that circumvents the queue approval process of posts (a.k.a. trusted forum users).
*“Days to keep forum posts before purging” will automatically purge posts after a certain period of time. With excessive post activity, the system could slow down after months, years of posts. Purging old posts will help keep the database a manageable size and improve performance.
*“Polling Available” turns on / off polling availability on the site.
*“Require Login” requires that poll visitors be logged into an account in order to submit a poll vote.
*“Poll Default Template” sets the default template for all “new polls” created in page management.
*“Blogging available” turns on / off blogging availability on the site.
*“Blog default template” sets the default template for all “new blogs” created in page management. Also sets the template to be adopted when users create their own blogs, if this is available on the web site.
*“Users that can have a blog” allows restriction of blog creation and management to users belonging to a specific group
*“Blog entries default template” sets the template to be adopted by each blog entry posted to a blog. Note that the blog itself is a page and each entry is also another page in page management.
*“Blog entries default as forums” will set blog entries to have forum controls available automatically, allowing visitors to comment on the blog. Templates must be designed with forums in mind in order to display them when the blog page is a forum.

==Campaigns==
*“Email campaign available” turns on / off the availability of campaign management tools
*“Users that can manage email campaigns” allows a group’s user memebers to have the privilege of using campaign management tools.
*“Double Opt In Success URL” dictates the URL the visitor is forwarded to after they have successfully opted into the email campaign via the automated email. Example “/index.php?pageId=123&message=You%20are%20now%20registered!”
*“Double opt in failure URL” dictates the URL the visitor is forwarded to on failed double opt in attempts. These could be the result of hack attempts or malformed URLs in the emails due to client email browsers performing physical wraps mid URL. Example: “/index.php?pageId=234&message=Failed%20registration%20attempt”
*“Double opt out success URL” dictates the URL the visitor is forward to following successfully opting out of the campaign system. Example: “/index.php?pageId=345&message=You%20have%20will%20no%20longer%20receive%20emails”
*“Double opt out failure URL” dictates the URL the visitor will forward to following a failed double opt out attempt. These could be the result of hack attempts or malformed URLs in the emails fur to client email browsers performing physical wraps min URL. Example: “/index.php?page=456&message=Invalid%20opt%20out%20attempt”
*“Registration Email” fields dictate the contents of the automated email that is sent upon registration for the campaign system. “Registration Email PageId” allows for the use of a page in the page management system as the sent email instead of the “Registration Email Body” – enter only the page ID here.
*“Registration Type” dictates if the system is opt in (requiring the registering visitor to verify via an automated email before they qualify) or opt out (meaning the registering visitor is automatically qualified after submitting an email address via the website, but will receive an email with instructions on how to opt out). Opt in, while less convenient for visitors, ensures all registrations are legitimate which will help to avoid being blacklisted by spam systems.

==eCommerce==
*“eCommerce available” turns on/ off the availability of eCommerce and related tools.
*“Page IDs” (cart, registration, shipping, billing, payment, checkout…) dictate the pages that will be used as these stages in the shopping cart and purchase process. Simply enter the Page IDs into these fields after they are created in the system. The eCommerce URLs will utilize these pages to build their content (CART.view, ORDER.register, ORDER.checkoutShipping, ORDER.checkoutBilling, ORDERcheckoutPayment, ORDER.checkoutConfirmation, ORDER.checkoutComplete)
*“Email Invoice” fields will control the email that is automatically delivered to a customer following an order. The “Emailed Invoice Header” and “Emailed Invoice Footer” will “wrap” around the actual receipt that will be present in the email.
*“Product Configuration Available” turns on/off the product configuration tool in product management. The product configuration tool allows managers to control “personalized” products and their presentation. For example: greeting cards, personalized logod pens, and other products that give visitors a significant amount of control over product presentation.
*“Pricing Matrices Available” turns on / off shared pricing level / matrix tools. These tools allow content managers to set per-quantity price discount ‘groups’ that can be reused from product to product. With this component disabled, content managers may still manage per-quantity pricing matrices on a per product basis, though they will not be able to use ‘shared’ matrices between multiple products.
*“TriggerEmailMarketing” fields turn on / off, and configure the ACORN Trigger Email Marketing functions.
*“Users that can manage products” dictates a user group that has control over product management functions (this includes product management, price matrix, shared product options, tax management, shipping management, discount management)
*“Users that can manage orders” dictates a user group that can lookup and manage orders in the system.

==Users==
*“Users that can manage users and access” dictates a group that can lookup, edit, add and change access of all users.
*“Failed Access Authorization URL forward” dictates the URL that a visitor will be forwarded to in the event they attempt to access something (a page, document, etc) that they do not have access for. Example: “/index.php?pageId=124&message=Invalid%20access%20attempt”
*“Login successfully URL forward” dictates the default URL that a visitor will be forwarded to following a successful login. This can be overrided by use of the “redirect” form field in the login form. Example: “/index.php?pageId=112&message=You%20have%20successully%20logged%20in”. This is set to “index.php?fa=PAGE.manage” be default so that logging into the initial login form will present the administration console.
*“Failed attempt login URL forward” dictates the default URL that a visitor will be forward to following a failed login attempt. The can be overrided by use of the “redirectOnFailure” form field in the login form. Typically this is set to forward back to the login form itself with a message about the failed login. Example: “/index.php?pageId=135&message=Invalid%20login%20please%20try%20again”
*“Logout URL forward” dictates the default URL that a visitor will be forwarded to following logout. This can be overrided by use of the “redirecte” querystring attribute in the logout URL (example of override in querystring: index.php?fa=USER.logout&redirect=my/redirect.page). Example Logout URL forward value: “/index.php?pageId=432&message=You%20have%20been%20logged%20out”
*“Password expired link” is the URL the visitor will be forwarded to when attempting to log into an account that has an expired password. Typically this is forwarded to the account management form that allows a visitor to set their password. Example: “index.php?pageId=146&message=Password%20expired%20please%20change%20your%20password”
*“Lost password settings” set the contents of the email that is automatically sent when a visitor requests their lost password.
*“Custom User Fields” allows creation of custom fields that will be available for user accounts. These fields will be automatically presented in the user management form located in “users’ of the administration console. Template managers will be required to specially call and integrate these fields into each management form they wish to present them within. For additional information on custom field setup, see “custom fields” below.

Settings:First Use

2008-12-05T03:57:56Z

James: /* Page Fields */

Advice: Keep it simple. Only enable functions that the client specifically asked for in order to avoid unnecessary clutter and confusion.

==Site Management==
*Enter the site URL “http://www.website.com” and secured site URLs (which may be the same as the site URL until the SSL certificate is received and installed).
*Set the physical root to the web site – this is required for many functions of the admin console to operate including image / file upload.
*Set the root folders for images and files. These will be used by the image and file management libraries as a starting point and top level restriction (users cannot navigate above these folders) for navigation to images and folders. The images folder can exist within the files folder if you wish. Make sure these folders exist on the server with appropriate rights and privileges assigned.
*If you are using multiple domains to access this web site, it is recommended to use the ‘force URLs to this domain option’ which will place all visitors into the same domain regardless of requested domain. This will satisfy cookies/sessions (as they prefer to be only available to their creating domain) and also makes third party web services happy (as many of them control access, and organize data based on domain name). Enter just the domain name without leading protocol ( example: www.mywebsite.com)
*Left menu bar should be checked unless the site isn’t using a left menu (very rare). Unchecking this box hides the left menu bar controls in the menu management area of administration.
*Leave languages empty unless you plan on supporting multiple languages on the website. If this is the case, please contact Whirlwind for requirements of using multiple languages.

==Page Management==
*“Reload page management on template change” should always be checked. This forces the page to reload when a template is selected, so the form will display the appropriate custom fields for that template. Only uncheck if the site will never use templates with custom fields.
*“Use Landing Pages” should be elected if the web site will use landing pages to govern different home pages based on user preferences.
*“Users that can manage pages” can be used to designate a group that has the rights to manage page content (create user groups in the Groups area of management). Administrators always have this ability (along with every possible privilege in administration). Only use this option is the client has expressed a need to have content managers who can manage page content but not have access to anything else.
*“Users that can edit pages but require approval from managers” sets a group who’s members can edit content that must be approved before going live. Note that page content changes submitted by these users are automatically emailed to users with the rights to manage pages. Only use this option if the client requires to have a junior level of content managers who’s changes and entries require approval before being posted live on the web site.
*Automated page email controls sets the email contents for the page approval process. Only enter data here if junior content editors will be used.
*“Page default template” sets the template that all new pages will be set to when created. You will probably be setting this after you get your templates into the system
*“Printable default template” and “Mobile default template” are used to pre-populate these template selections for new pages.
*“Selectable as an author for a page” dictates a group that will contain users that will be selectable as an author to a page in page management. You may need to create an author group in Groups before making this assignment. Only use this if you will be using page publishing fields (publisher, publish date, author) in page management (settable in the Page Fields tab of Settings).
*“Use page authorization” activates the page restriction functions of the web site. Turning this on will make all pages unavailable unless the user belongs to a group authorized to view the page. If enabled, a group assignment tool will be available in page management under the access tab. The everyone group can be used to make the page available to everyone, including folks not logged in (make sure your home page is set to everyone, if page authorization is elected or the site will be inaccessible). You can set default groups that pages will be assigned to using the “default user groups for new pages” option. Note that when page authorization is activated, all existing pages currently in the system will not belong to any groups and be inaccessible.
*“Style Sheets” sets the default style sheets (separated by commas) that will be used by the WYSIWYG editor in page management. These stylesheets can be overruled on a per template bases by setting the style sheets with the templates. Note that often specific style sheets need to be created for this area in addition to the style sheets actually used by the outputting page seen by visitors, as the WYSIWYG editor will not be subject to parent classes, ids that this content will be subject to when the page is displayed.
*“Search Page ID” sets the page id that will be used to display search results. This will most likely be set after the template and page are created for keyword search results.
*“404 (Not Found) Page ID” lets you set a page to be shown when a 404 error occurs. This requires the web server have 404 error set to go to index.php in the root of this web site.
*“Send2Friend Email Subject and Body” Set the contents of the email that is sent when the “send this page to a friend” function is used. Note the list of variables below the field which can be entered directly into the contents of the body or subject.
*“Summary Listing Details” dictates how admin search results for pages will be displayed. Alter this to use the fields that will be available to content managers.
*“Record Page Views” turns on advanced page activity tracking. With each page, all incoming and state variables (post, get, site, cookie, session) are recorded along with order and user data. Great for debugging, but uses a lot of system resources and can significantly handicap the speed of the web site.
*“Banner Management” makes banner management functions available in administration. A group can be created and assigned to have rights to manage banner ads.
*“Page Caching” makes server side page content caching available. Page caching significantly increases the performance of the site, especially on pages that have heavy processing requirements. Page caching cannot be used if any content on the page is to be session or state specific (perpetual carts, “Welcome Mr Jones”). Note that if enabled site wide (here), page caching can also be micromanaged on a per page basis – allowing heavily traffic’d pages to have session specific data removed and be cached, while other pages are not. Page caching is tightly integrated into the management console so that changes in administration that effect pages will trigger the effected pages to refresh in the cache automatically.
*“Pages as Events” adds event controls to page management. These allow a page to be set as an event, along with controlling start end dates. Event pages will qualify for event search functions that can be used to populate calendar pages.

==Page Fields==
*“Use Publisher information” makes the publishing fields available in the ‘other’ tab of page management. These include an author (selected from the users belonging to group assigned to author in the Page Management tab of Settings), a publisher and a publish date. These fields then become available in the template for output.
*“Publisher default” sets the default value of the publisher field.
*“Use breadcrumb, page notice, sub title, summary information link text, image caption” turn on / off these fields in page management. If they are not necessary for any of the templates then turning them off will remove unnecessary clutter from the page management form.
*The “Rename” fields allow you to change the name of the fields as they are presented in the page management form. This accommodates clients who are accustomed to specific language governing their content (for example, publishing clients use headline, subhead and deck in place of notice, title and subtitle). Often page name is substituted for notice giving page managers a way to uniquely identify each page in a recognizable manner. The rename fields can also allow for html to be included (for instance if you would like the meta title to copy the title value when a link is pressed, write the HTML for the link and javascript in here).

==Web 2.0==
Here forums, polling and blogging can be enabled and configured. Note that templates will have to be created to support each, if they are to be used. Only activate if the client requires these functions.
*“forums available” turns on / off forum availability on the site
*“Page forum template” sets the default template when a content manager elects to create a forum via page managemenr.
*“Users that can manage forums” sets the user group that has the rights to view, approve and edit forum posts.
*“Embed forum replies in parent post” actually places the post content of target posts into reply postings. This is usefull if regularly purging the system of old posts (so replies still retain the source post even after the source post is deleted). For ‘commenting’ pages (commenting on products) this is not necessary since they typically do not incorporate ability to reply like typical forums.
*“Submissions are posted live” will circumvent the approval process. If unchecked posts will not be visible to web site visitors until approved via the forums queue. If checked, they will be visible immediately.
*“Require Login for Forum Posts” requires visitors to be logged into user accounts to post. This disallows anonymous posting. While this does make forum users a little less likely to post objectionable /inappropriate content, it will make the posting process more difficult therefore visitors will be less likely to use it.
*“Submissions posted live by these users” allows designation of a user group that circumvents the queue approval process of posts (a.k.a. trusted forum users).
*“Days to keep forum posts before purging” will automatically purge posts after a certain period of time. With excessive post activity, the system could slow down after months, years of posts. Purging old posts will help keep the database a manageable size and improve performance.
*“Polling Available” turns on / off polling availability on the site.
*“Require Login” requires that poll visitors be logged into an account in order to submit a poll vote.
*“Poll Default Template” sets the default template for all “new polls” created in page management.
*“Blogging available” turns on / off blogging availability on the site.
*“Blog default template” sets the default template for all “new blogs” created in page management. Also sets the template to be adopted when users create their own blogs, if this is available on the web site.
*“Users that can have a blog” allows restriction of blog creation and management to users belonging to a specific group
*“Blog entries default template” sets the template to be adopted by each blog entry posted to a blog. Note that the blog itself is a page and each entry is also another page in page management.
*“Blog entries default as forums” will set blog entries to have forum controls available automatically, allowing visitors to comment on the blog. Templates must be designed with forums in mind in order to display them when the blog page is a forum.

==Campaigns==
*“Email campaign available” turns on / off the availability of campaign management tools
*“Users that can manage email campaigns” allows a group’s user memebers to have the privilege of using campaign management tools.
*“Double Opt In Success URL” dictates the URL the visitor is forwarded to after they have successfully opted into the email campaign via the automated email. Example “/index.php?pageId=123&message=You%20are%20now%20registered!”
*“Double opt in failure URL” dictates the URL the visitor is forwarded to on failed double opt in attempts. These could be the result of hack attempts or malformed URLs in the emails due to client email browsers performing physical wraps mid URL. Example: “/index.php?pageId=234&message=Failed%20registration%20attempt”
*“Double opt out success URL” dictates the URL the visitor is forward to following successfully opting out of the campaign system. Example: “/index.php?pageId=345&message=You%20have%20will%20no%20longer%20receive%20emails”
*“Double opt out failure URL” dictates the URL the visitor will forward to following a failed double opt out attempt. These could be the result of hack attempts or malformed URLs in the emails fur to client email browsers performing physical wraps min URL. Example: “/index.php?page=456&message=Invalid%20opt%20out%20attempt”
*“Registration Email” fields dictate the contents of the automated email that is sent upon registration for the campaign system. “Registration Email PageId” allows for the use of a page in the page management system as the sent email instead of the “Registration Email Body” – enter only the page ID here.
*“Registration Type” dictates if the system is opt in (requiring the registering visitor to verify via an automated email before they qualify) or opt out (meaning the registering visitor is automatically qualified after submitting an email address via the website, but will receive an email with instructions on how to opt out). Opt in, while less convenient for visitors, ensures all registrations are legitimate which will help to avoid being blacklisted by spam systems.

==eCommerce==
*“eCommerce available” turns on/ off the availability of eCommerce and related tools.
*“Page IDs” (cart, registration, shipping, billing, payment, checkout…) dictate the pages that will be used as these stages in the shopping cart and purchase process. Simply enter the Page IDs into these fields after they are created in the system. The eCommerce URLs will utilize these pages to build their content (CART.view, ORDER.register, ORDER.checkoutShipping, ORDER.checkoutBilling, ORDERcheckoutPayment, ORDER.checkoutConfirmation, ORDER.checkoutComplete)
*“Email Invoice” fields will control the email that is automatically delivered to a customer following an order. The “Emailed Invoice Header” and “Emailed Invoice Footer” will “wrap” around the actual receipt that will be present in the email.
*“Product Configuration Available” turns on/off the product configuration tool in product management. The product configuration tool allows managers to control “personalized” products and their presentation. For example: greeting cards, personalized logod pens, and other products that give visitors a significant amount of control over product presentation.
*“Pricing Matrices Available” turns on / off shared pricing level / matrix tools. These tools allow content managers to set per-quantity price discount ‘groups’ that can be reused from product to product. With this component disabled, content managers may still manage per-quantity pricing matrices on a per product basis, though they will not be able to use ‘shared’ matrices between multiple products.
*“TriggerEmailMarketing” fields turn on / off, and configure the ACORN Trigger Email Marketing functions.
*“Users that can manage products” dictates a user group that has control over product management functions (this includes product management, price matrix, shared product options, tax management, shipping management, discount management)
*“Users that can manage orders” dictates a user group that can lookup and manage orders in the system.

==Users==
*“Users that can manage users and access” dictates a group that can lookup, edit, add and change access of all users.
*“Failed Access Authorization URL forward” dictates the URL that a visitor will be forwarded to in the event they attempt to access something (a page, document, etc) that they do not have access for. Example: “/index.php?pageId=124&message=Invalid%20access%20attempt”
*“Login successfully URL forward” dictates the default URL that a visitor will be forwarded to following a successful login. This can be overrided by use of the “redirect” form field in the login form. Example: “/index.php?pageId=112&message=You%20have%20successully%20logged%20in”. This is set to “index.php?fa=PAGE.manage” be default so that logging into the initial login form will present the administration console.
*“Failed attempt login URL forward” dictates the default URL that a visitor will be forward to following a failed login attempt. The can be overrided by use of the “redirectOnFailure” form field in the login form. Typically this is set to forward back to the login form itself with a message about the failed login. Example: “/index.php?pageId=135&message=Invalid%20login%20please%20try%20again”
*“Logout URL forward” dictates the default URL that a visitor will be forwarded to following logout. This can be overrided by use of the “redirecte” querystring attribute in the logout URL (example of override in querystring: index.php?fa=USER.logout&redirect=my/redirect.page). Example Logout URL forward value: “/index.php?pageId=432&message=You%20have%20been%20logged%20out”
*“Password expired link” is the URL the visitor will be forwarded to when attempting to log into an account that has an expired password. Typically this is forwarded to the account management form that allows a visitor to set their password. Example: “index.php?pageId=146&message=Password%20expired%20please%20change%20your%20password”
*“Lost password settings” set the contents of the email that is automatically sent when a visitor requests their lost password.
*“Custom User Fields” allows creation of custom fields that will be available for user accounts. These fields will be automatically presented in the user management form located in “users’ of the administration console. Template managers will be required to specially call and integrate these fields into each management form they wish to present them within. For additional information on custom field setup, see “custom fields” below.

Settings:First Use

2008-12-05T03:22:39Z

James: /* Site Management */

Advice: Keep it simple. Only enable functions that the client specifically asked for in order to avoid unnecessary clutter and confusion.

==Site Management==
*Enter the site URL “http://www.website.com” and secured site URLs (which may be the same as the site URL until the SSL certificate is received and installed).
*Set the physical root to the web site – this is required for many functions of the admin console to operate including image / file upload.
*Set the root folders for images and files. These will be used by the image and file management libraries as a starting point and top level restriction (users cannot navigate above these folders) for navigation to images and folders. The images folder can exist within the files folder if you wish. Make sure these folders exist on the server with appropriate rights and privileges assigned.
*If you are using multiple domains to access this web site, it is recommended to use the ‘force URLs to this domain option’ which will place all visitors into the same domain regardless of requested domain. This will satisfy cookies/sessions (as they prefer to be only available to their creating domain) and also makes third party web services happy (as many of them control access, and organize data based on domain name). Enter just the domain name without leading protocol ( example: www.mywebsite.com)
*Left menu bar should be checked unless the site isn’t using a left menu (very rare). Unchecking this box hides the left menu bar controls in the menu management area of administration.
*Leave languages empty unless you plan on supporting multiple languages on the website. If this is the case, please contact Whirlwind for requirements of using multiple languages.

==Page Management==
*“Reload page management on template change” should always be checked. This forces the page to reload when a template is selected, so the form will display the appropriate custom fields for that template. Only uncheck if the site will never use templates with custom fields.
*“Use Landing Pages” should be elected if the web site will use landing pages to govern different home pages based on user preferences.
*“Users that can manage pages” can be used to designate a group that has the rights to manage page content (create user groups in the Groups area of management). Administrators always have this ability (along with every possible privilege in administration). Only use this option is the client has expressed a need to have content managers who can manage page content but not have access to anything else.
*“Users that can edit pages but require approval from managers” sets a group who’s members can edit content that must be approved before going live. Note that page content changes submitted by these users are automatically emailed to users with the rights to manage pages. Only use this option if the client requires to have a junior level of content managers who’s changes and entries require approval before being posted live on the web site.
*Automated page email controls sets the email contents for the page approval process. Only enter data here if junior content editors will be used.
*“Page default template” sets the template that all new pages will be set to when created. You will probably be setting this after you get your templates into the system
*“Printable default template” and “Mobile default template” are used to pre-populate these template selections for new pages.
*“Selectable as an author for a page” dictates a group that will contain users that will be selectable as an author to a page in page management. You may need to create an author group in Groups before making this assignment. Only use this if you will be using page publishing fields (publisher, publish date, author) in page management (settable in the Page Fields tab of Settings).
*“Use page authorization” activates the page restriction functions of the web site. Turning this on will make all pages unavailable unless the user belongs to a group authorized to view the page. If enabled, a group assignment tool will be available in page management under the access tab. The everyone group can be used to make the page available to everyone, including folks not logged in (make sure your home page is set to everyone, if page authorization is elected or the site will be inaccessible). You can set default groups that pages will be assigned to using the “default user groups for new pages” option. Note that when page authorization is activated, all existing pages currently in the system will not belong to any groups and be inaccessible.
*“Style Sheets” sets the default style sheets (separated by commas) that will be used by the WYSIWYG editor in page management. These stylesheets can be overruled on a per template bases by setting the style sheets with the templates. Note that often specific style sheets need to be created for this area in addition to the style sheets actually used by the outputting page seen by visitors, as the WYSIWYG editor will not be subject to parent classes, ids that this content will be subject to when the page is displayed.
*“Search Page ID” sets the page id that will be used to display search results. This will most likely be set after the template and page are created for keyword search results.
*“404 (Not Found) Page ID” lets you set a page to be shown when a 404 error occurs. This requires the web server have 404 error set to go to index.php in the root of this web site.
*“Send2Friend Email Subject and Body” Set the contents of the email that is sent when the “send this page to a friend” function is used. Note the list of variables below the field which can be entered directly into the contents of the body or subject.
*“Summary Listing Details” dictates how admin search results for pages will be displayed. Alter this to use the fields that will be available to content managers.
*“Record Page Views” turns on advanced page activity tracking. With each page, all incoming and state variables (post, get, site, cookie, session) are recorded along with order and user data. Great for debugging, but uses a lot of system resources and can significantly handicap the speed of the web site.
*“Banner Management” makes banner management functions available in administration. A group can be created and assigned to have rights to manage banner ads.
*“Page Caching” makes server side page content caching available. Page caching significantly increases the performance of the site, especially on pages that have heavy processing requirements. Page caching cannot be used if any content on the page is to be session or state specific (perpetual carts, “Welcome Mr Jones”). Note that if enabled site wide (here), page caching can also be micromanaged on a per page basis – allowing heavily traffic’d pages to have session specific data removed and be cached, while other pages are not. Page caching is tightly integrated into the management console so that changes in administration that effect pages will trigger the effected pages to refresh in the cache automatically.
*“Pages as Events” adds event controls to page management. These allow a page to be set as an event, along with controlling start end dates. Event pages will qualify for event search functions that can be used to populate calendar pages.

==Page Fields==
*“Use Publisher information” makes the publishing fields available in the ‘other’ tab of page management. These include an author (selected from the users belonging to group assigned to author in the Page Management tab of Settings), a publisher and a publish date. These fields then become available in the template for output.
*“Publisher default” sets the default value of the publisher field.
*“Use breadcrumb, page notice, sub title, summary information link text, image caption” turn on / off these fields in page management. If they are not necessary for any of the templates then turning them off will remove unnecessary clutter from the page management form.
*The “Rename” fields allow you to change the name of the fields as they are presented in the page management form. This accomidates clients who are accustomed to specific language governing their content (for example, publishing clients use headline, subhead and deck in place of notice, title and subtitle). Often page name is substituted for notice giving page managers a way to uniquely identify each page in a recognizable manner. The rename fields can also allow for html to be included (for instance if you would like the meta title to copy the title value when a link is pressed, write the HTML for the link and javascript in here).

==Web 2.0==
Here forums, polling and blogging can be enabled and configured. Note that templates will have to be created to support each, if they are to be used. Only activate if the client requires these functions.
*“forums available” turns on / off forum availability on the site
*“Page forum template” sets the default template when a content manager elects to create a forum via page managemenr.
*“Users that can manage forums” sets the user group that has the rights to view, approve and edit forum posts.
*“Embed forum replies in parent post” actually places the post content of target posts into reply postings. This is usefull if regularly purging the system of old posts (so replies still retain the source post even after the source post is deleted). For ‘commenting’ pages (commenting on products) this is not necessary since they typically do not incorporate ability to reply like typical forums.
*“Submissions are posted live” will circumvent the approval process. If unchecked posts will not be visible to web site visitors until approved via the forums queue. If checked, they will be visible immediately.
*“Require Login for Forum Posts” requires visitors to be logged into user accounts to post. This disallows anonymous posting. While this does make forum users a little less likely to post objectionable /inappropriate content, it will make the posting process more difficult therefore visitors will be less likely to use it.
*“Submissions posted live by these users” allows designation of a user group that circumvents the queue approval process of posts (a.k.a. trusted forum users).
*“Days to keep forum posts before purging” will automatically purge posts after a certain period of time. With excessive post activity, the system could slow down after months, years of posts. Purging old posts will help keep the database a manageable size and improve performance.
*“Polling Available” turns on / off polling availability on the site.
*“Require Login” requires that poll visitors be logged into an account in order to submit a poll vote.
*“Poll Default Template” sets the default template for all “new polls” created in page management.
*“Blogging available” turns on / off blogging availability on the site.
*“Blog default template” sets the default template for all “new blogs” created in page management. Also sets the template to be adopted when users create their own blogs, if this is available on the web site.
*“Users that can have a blog” allows restriction of blog creation and management to users belonging to a specific group
*“Blog entries default template” sets the template to be adopted by each blog entry posted to a blog. Note that the blog itself is a page and each entry is also another page in page management.
*“Blog entries default as forums” will set blog entries to have forum controls available automatically, allowing visitors to comment on the blog. Templates must be designed with forums in mind in order to display them when the blog page is a forum.

==Campaigns==
*“Email campaign available” turns on / off the availability of campaign management tools
*“Users that can manage email campaigns” allows a group’s user memebers to have the privilege of using campaign management tools.
*“Double Opt In Success URL” dictates the URL the visitor is forwarded to after they have successfully opted into the email campaign via the automated email. Example “/index.php?pageId=123&message=You%20are%20now%20registered!”
*“Double opt in failure URL” dictates the URL the visitor is forwarded to on failed double opt in attempts. These could be the result of hack attempts or malformed URLs in the emails due to client email browsers performing physical wraps mid URL. Example: “/index.php?pageId=234&message=Failed%20registration%20attempt”
*“Double opt out success URL” dictates the URL the visitor is forward to following successfully opting out of the campaign system. Example: “/index.php?pageId=345&message=You%20have%20will%20no%20longer%20receive%20emails”
*“Double opt out failure URL” dictates the URL the visitor will forward to following a failed double opt out attempt. These could be the result of hack attempts or malformed URLs in the emails fur to client email browsers performing physical wraps min URL. Example: “/index.php?page=456&message=Invalid%20opt%20out%20attempt”
*“Registration Email” fields dictate the contents of the automated email that is sent upon registration for the campaign system. “Registration Email PageId” allows for the use of a page in the page management system as the sent email instead of the “Registration Email Body” – enter only the page ID here.
*“Registration Type” dictates if the system is opt in (requiring the registering visitor to verify via an automated email before they qualify) or opt out (meaning the registering visitor is automatically qualified after submitting an email address via the website, but will receive an email with instructions on how to opt out). Opt in, while less convenient for visitors, ensures all registrations are legitimate which will help to avoid being blacklisted by spam systems.

==eCommerce==
*“eCommerce available” turns on/ off the availability of eCommerce and related tools.
*“Page IDs” (cart, registration, shipping, billing, payment, checkout…) dictate the pages that will be used as these stages in the shopping cart and purchase process. Simply enter the Page IDs into these fields after they are created in the system. The eCommerce URLs will utilize these pages to build their content (CART.view, ORDER.register, ORDER.checkoutShipping, ORDER.checkoutBilling, ORDERcheckoutPayment, ORDER.checkoutConfirmation, ORDER.checkoutComplete)
*“Email Invoice” fields will control the email that is automatically delivered to a customer following an order. The “Emailed Invoice Header” and “Emailed Invoice Footer” will “wrap” around the actual receipt that will be present in the email.
*“Product Configuration Available” turns on/off the product configuration tool in product management. The product configuration tool allows managers to control “personalized” products and their presentation. For example: greeting cards, personalized logod pens, and other products that give visitors a significant amount of control over product presentation.
*“Pricing Matrices Available” turns on / off shared pricing level / matrix tools. These tools allow content managers to set per-quantity price discount ‘groups’ that can be reused from product to product. With this component disabled, content managers may still manage per-quantity pricing matrices on a per product basis, though they will not be able to use ‘shared’ matrices between multiple products.
*“TriggerEmailMarketing” fields turn on / off, and configure the ACORN Trigger Email Marketing functions.
*“Users that can manage products” dictates a user group that has control over product management functions (this includes product management, price matrix, shared product options, tax management, shipping management, discount management)
*“Users that can manage orders” dictates a user group that can lookup and manage orders in the system.

==Users==
*“Users that can manage users and access” dictates a group that can lookup, edit, add and change access of all users.
*“Failed Access Authorization URL forward” dictates the URL that a visitor will be forwarded to in the event they attempt to access something (a page, document, etc) that they do not have access for. Example: “/index.php?pageId=124&message=Invalid%20access%20attempt”
*“Login successfully URL forward” dictates the default URL that a visitor will be forwarded to following a successful login. This can be overrided by use of the “redirect” form field in the login form. Example: “/index.php?pageId=112&message=You%20have%20successully%20logged%20in”. This is set to “index.php?fa=PAGE.manage” be default so that logging into the initial login form will present the administration console.
*“Failed attempt login URL forward” dictates the default URL that a visitor will be forward to following a failed login attempt. The can be overrided by use of the “redirectOnFailure” form field in the login form. Typically this is set to forward back to the login form itself with a message about the failed login. Example: “/index.php?pageId=135&message=Invalid%20login%20please%20try%20again”
*“Logout URL forward” dictates the default URL that a visitor will be forwarded to following logout. This can be overrided by use of the “redirecte” querystring attribute in the logout URL (example of override in querystring: index.php?fa=USER.logout&redirect=my/redirect.page). Example Logout URL forward value: “/index.php?pageId=432&message=You%20have%20been%20logged%20out”
*“Password expired link” is the URL the visitor will be forwarded to when attempting to log into an account that has an expired password. Typically this is forwarded to the account management form that allows a visitor to set their password. Example: “index.php?pageId=146&message=Password%20expired%20please%20change%20your%20password”
*“Lost password settings” set the contents of the email that is automatically sent when a visitor requests their lost password.
*“Custom User Fields” allows creation of custom fields that will be available for user accounts. These fields will be automatically presented in the user management form located in “users’ of the administration console. Template managers will be required to specially call and integrate these fields into each management form they wish to present them within. For additional information on custom field setup, see “custom fields” below.

The Administration Console:First Look

2008-12-05T03:08:23Z

James:

Upon logging in you will be presented with a series of links to access the administration areas of the web site. Which links are available is governed by what functions are ‘turned on’ for the web site (manageable by the ‘Settings’ area) and what functions you have rights to access. The administrators group (which the default administration account belongs to) has rights to access everything.

A quick breakdown of all the site functions (links you see at the top of the administration console) and what they do:

;Logout
:logs you out and places you in the home page.

;Home
:links to the home page of the web site

;Pages
:used to manage all pages of the website. Note that this system does not follow the typical paradigm of separating categories, subcategories, products and information pages. All pages are accessible and manageable through page management including the aforementioned pages, shopping cart, checkout process, user registration and account functions, etc. If it is a page the web site visitor can see, it exists in page management.

;Images
:pops up the image management library where you can upload, edit, delete images that will be available to web site pages, products, etc.

;Libraries

;URL Map
:Especially useful for conversions from older website platforms, url mapping allows you to create ‘alias’ urls to pages in the website. This will allow you to keep old links in tact so web site conversions don’t lose their search engine listings or accessibility from links on other sites.

;Menus
:Used to create the CNav menu bar links that will be consistent on all pages. Though most sites use one menu set throughout the site, you have the ability to create multiple menu sets, swap them out or assign different ones to different templates if you wish to show different menu bar options in varying areas of the site.

;Landing Pages
:Allows you to set different home pages for different users based on their account specifics. If the user goes to the root of the web site and qualifies for a landing page, that landing page will be displayed instead of the home page.

;Form submissions
:Whenever a custom form is submitted on the web site, the submission will be stored in this area for future reference. Custom forms are used for catalog orders, newsletter registration, ask us forms, contact us forms or any other forms that are used to collect user information / requests.

;Pending approval
:The system supports staged approvals of pages, if required by the client. This requires two distinct user groups: page editors (which can modify pages, but modifications require approval before being visible by web site visitors) and page managers (who’s page changes go live immediately, and also have the ability to view and approve submissions made by page editors). Pending approval will list the pages waiting to be approved by managers.

;Custom Search Groups
:allows for creation of groups containing options that visitors may select from in order to find certain content (products, pages, etc). This is especially useful for select drop downs where visitors can select from a series of product or content groups. Custom search groups accommodates the creation of groups, creation of options within the groups and assignment of pages to each option which will be returned upon selection of the option.

;Users
:Once a visitor creates an account, this account will be accessible via the users area. Site administrative access is also controlled by this area, so if you have a new admin then create an account in users and give them the rights and privileges you wish.

;Sessions
:A running report of who is logging in to use the website and when.

;Groups
:Groups are used to aggregate users and control rights and permissions. Groups can be created and assigned administrative rights via Settings (page managers, page editors, campaign managers, product managers, etc..etc). Once the group is created and assigned privileges, all users belonging to that group (assign users to groups in the Users area) will gain those privileges. As the system also supports content security (disabling page access for certain users), grouping can be used to create page content access groups: each group can be allowed access to certain restricted pages and users belonging to that group will benefit from that access.

;Forums
:all comment / forum posts will be accessible here. Posts can be viewed, edited, deleted or hidden as necessary. If forums is structured to have all posts require approval before being visible (controllable via Settings), than this queue will provide the means to monitor and approve those posts.

;Campaigns
:Email campaigns can be created, distributed and monitored here.

;Campaign Subscribers
:Visitors electing to receive emails from the site will be listed and manageable here. Note that visitors can subscribe without creating an account so users and subscribers are not synonymous. Check out the easy way to include subscription as an option in any custom form on the web site via Custom Forms.

;Banners
:Allows creation, management, placement and control of banner ads throughout the website. Note that banner ‘zones’ must be created and assigned within templates for banners to appear.

;Products
:Products can be created and managed here. Products are also assigned to pages here (and vice-verse you can assign products to a page from within page management). A product will not appear anywhere unless assigned to a page who’s template accommodates displaying products!

;Shipping
:Allows for management of shipping matrices that will govern shipping costs for purchases. Any number of shipping methods and price thresholds can be created. Note that each product has the ability to augment shipping costs with additional charges.

;Tax Management
:Freeform creation of tax rules. Tax charges can be set by location and as many tax rules as you wish may exist. Note that products can be disqualified from taxes in product management.

;Discounts
:Allows creation of coupons and special offers on the web site. Any number of coupons/offers can be created. Each offer is subject to conditions (date frame, order amount, specific product application) and affords benefits (%/$ off sale, free shipping, free product) to those who qualify for the conditions set. Discounts can be set to automatically enable once the order qualifies (they will just appear in the cart once conditions are met) or only appear when a specific coupon code is entered by the user.

;Orders
:allows look up, viewing and editing of all web orders. Note that an order is created once a visitor first enters the web site, so this tool can be used to look up orders in progress as well as completed orders.

;Cart Report
:A handy report that shows activity/sales based on email campaigns, source codes, date frames and referring web sites. Use to monitor ROI on campaigns and advertisements and to also identify bottlenecks in the purchase process where improvements should be considered.

;Page Templates
:used to create and control how page content is managed by content managers and presented to visitors. Any number of templates can be created. Each page created must select a template which will govern what data and content are manageable within page management and how this information will appear to the visitor.

;Settings
:The core of the engine controls, settings dictates what tools are turned on and off on the website and how these tools operate. Controls are available for image/file, page, banner, service side caching, events, forums, polling, blogging, secure document, email campaigning, ecommerce, user and data library availability, preferences and behaviors.

;IP blocks
:All functions that accept user submissions (forum posts, custom forms, purchases, etc) allow for ‘blocking’ of submitting visitors. This is handy for spammers who wish to submit inappropriate information. Once blocked, they cannot use any submission functions on the web site. IP blocks lists all current blocks, reasons for blocking and provides the means to unblock the visitors.

The Administration Console:First Look

2008-12-05T02:58:07Z

James:

Upon logging in you will be presented with a series of links to access the administration areas of the web site. Which links are available is governed by what functions are ‘turned on’ for the web site (manageable by the ‘Settings’ area) and what functions you have rights to access. The administrators group (which the default administration account belongs to) has rights to access everything.

A quick breakdown of all the site functions (links you see at the top of the administration console) and what they do:

;Logout
:logs you out and places you in the home page.

;Home
:links to the home page of the web site

;Pages
:used to manage all pages of the website. Note that this system does not follow the typical paradigm of separating categories, subcategories, products and information pages. All pages are accessible and manageable through page management including the aforementioned pages, shopping cart, checkout process, user registration and account functions, etc. If it is a page the web site visitor can see, it exists in page management.

;Images
:pops up the image management library where you can upload, edit, delete images that will be available to web site pages, products, etc.

;Libraries

;URL Map
:Especially useful for conversions from older website platforms, url mapping allows you to create ‘alias’ urls to pages in the website. This will allow you to keep old links in tact so web site conversions don’t lose their search engine listings or accessibility from links on other sites.

;Menus
:Used to create the CNav menu bar links that will be consistent on all pages. Though most sites use one menu set throughout the site, you have the ability to create multiple menu sets, swap them out or assign different ones to different templates if you wish to show different menu bar options in varying areas of the site.

;Landing Pages
:Allows you to set different home pages for different users based on their account specifics. If the user goes to the root of the web site and qualifies for a landing page, that landing page will be displayed instead of the home page.

;Form submissions
:Whenever a custom form is submitted on the web site, the submission will be stored in this area for future reference. Custom forms are used for catalog orders, newsletter registration, ask us forms, contact us forms or any other forms that are used to collect user information / requests.

;Pending approval
:The system supports staged approvals of pages, if required by the client. This requires two distinct user groups: page editors (which can modify pages, but modifications require approval before being visible by web site visitors) and page managers (who’s page changes go live immediately, and also have the ability to view and approve submissions made by page editors). Pending approval will list the pages waiting to be approved by managers.

;Custom Search Groups
:allows for creation of groups containing options that visitors may select from in order to find certain content (products, pages, etc). This is especially useful for select drop downs where visitors can select from a series of product or content groups. Custom search groups accommodates the creation of groups, creation of options within the groups and assignment of pages to each option which will be returned upon selection of the option.

;Users
:Once a visitor creates an account, this account will be accessible via the users area. Site administrative access is also controlled by this area, so if you have a new admin then create an account in users and give them the rights and privileges you wish.

;Sessions
:A running report of who is logging in to use the website and when.

;Groups
:Groups are used to aggregate users and control rights and permissions. Groups can be created and assigned administrative rights via Settings (page managers, page editors, campaign managers, product managers, etc..etc). Once the group is created and assigned privileges, all users belonging to that group (assign users to groups in the Users area) will gain those privileges. As the system also supports content security (disabling page access for certain users), grouping can be used to create page content access groups: each group can be allowed access to certain restricted pages and users belonging to that group will benefit from that access.

;Forums
:all comment / forum posts will be accessible here. Posts can be viewed, edited, deleted or hidden as necessary. If forums is structured to have all posts require approval before being visible (controllable via Settings), than this queue will provide the means to monitor and approve those posts.

;Campaigns
:Email campaigns can be created, distributed and monitored here.

;Campaign Subscribers
:Visitors electing to receive emails from the site will be listed and manageable here. Note that visitors can subscribe without creating an account so users and subscribers are not synonymous. Check out the easy way to include subscription as an option in any custom form on the web site via Custom Forms.

;Banners
:Allows creation, management, placement and control of banner ads throughout the website. Note that banner ‘zones’ must be created and assigned within templates for banners to appear.

;Products
:Products can be created and managed here. Products are also assigned to pages here (and vice-verse you can assign products to a page from within page management). A product will not appear anywhere unless assigned to a page who’s template accommodates displaying products!

;Shipping
:Allows for management of shipping matrices that will govern shipping costs for purchases. Any number of shipping methods and price thresholds can be created. Note that each product has the ability to augment shipping costs with additional charges.

;Tax Management
Freeform creation of tax rules. Tax charges can be set by location and as many tax rules as you wish may exist. Note that products can be disqualified from taxes in product management.

;Discounts
:Allows creation of coupons and special offers on the web site. Any number of coupons/offers can be created. Each offer is subject to conditions (date frame, order amount, specific product application) and affords benefits (%/$ off sale, free shipping, free product) to those who qualify for the conditions set. Discounts can be set to automatically enable once the order qualifies (they will just appear in the cart once conditions are met) or only appear when a specific coupon code is entered by the user.

;Orders
:allows look up, viewing and editing of all web orders. Note that an order is created once a visitor first enters the web site, so this tool can be used to look up orders in progress as well as completed orders.

;Cart Report
:A handy report that shows activity/sales based on email campaigns, source codes, date frames and referring web sites. Use to monitor ROI on campaigns and advertisements and to also identify bottlenecks in the purchase process where improvements should be considered.

;Page Templates
:used to create and control how page content is managed by content managers and presented to visitors. Any number of templates can be created. Each page created must select a template which will govern what data and content are manageable within page management and how this information will appear to the visitor.

;Settings
:The core of the engine controls, settings dictates what tools are turned on and off on the website and how these tools operate. Controls are available for image/file, page, banner, service side caching, events, forums, polling, blogging, secure document, email campaigning, ecommerce, user and data library availability, preferences and behaviors.

;IP blocks
:All functions that accept user submissions (forum posts, custom forms, purchases, etc) allow for ‘blocking’ of submitting visitors. This is handy for spammers who wish to submit inappropriate information. Once blocked, they cannot use any submission functions on the web site. IP blocks lists all current blocks, reasons for blocking and provides the means to unblock the visitors.

The Administration Console:First Look

2008-12-05T02:44:12Z

James:

Upon logging in you will be presented with a series of links to access the administration areas of the web site. Which links are available is governed by what functions are ‘turned on’ for the web site (manageable by the ‘Settings’ area) and what functions you have rights to access. The administrators group (which the default administration account belongs to) has rights to access everything.

A quick breakdown of all the site functions (links you see at the top of the administration console) and what they do:

;Logout
:logs you out and places you in the home page.

;Home
:links to the home page of the web site

;Pages
:used to manage all pages of the website. Note that this system does not follow the typical paradigm of separating categories, subcategories, products and information pages. All pages are accessible and manageable through page management including the aforementioned pages, shopping cart, checkout process, user registration and account functions, etc. If it is a page the web site visitor can see, it exists in page management.

;Images
:pops up the image management library where you can upload, edit, delete images that will be available to web site pages, products, etc.

;Libraries

;URL Map
:Especially useful for conversions from older website platforms, url mapping allows you to create ‘alias’ urls to pages in the website. This will allow you to keep old links in tact so web site conversions don’t lose their search engine listings or accessibility from links on other sites.

;Menus
:Used to create the CNav menu bar links that will be consistent on all pages. Though most sites use one menu set throughout the site, you have the ability to create multiple menu sets, swap them out or assign different ones to different templates if you wish to show different menu bar options in varying areas of the site.

;Landing Pages
:Allows you to set different home pages for different users based on their account specifics. If the user goes to the root of the web site and qualifies for a landing page, that landing page will be displayed instead of the home page.

;Form submissions
:Whenever a custom form is submitted on the web site, the submission will be stored in this area for future reference. Custom forms are used for catalog orders, newsletter registration, ask us forms, contact us forms or any other forms that are used to collect user information / requests.

;Pending approval
:The system supports staged approvals of pages, if required by the client. This requires two distinct user groups: page editors (which can modify pages, but modifications require approval before being visible by web site visitors) and page managers (who’s page changes go live immediately, and also have the ability to view and approve submissions made by page editors). Pending approval will list the pages waiting to be approved by managers.

;Custom Search Groups
:allows for creation of groups containing options that visitors may select from in order to find certain content (products, pages, etc). This is especially useful for select drop downs where visitors can select from a series of product or content groups. Custom search groups accommodates the creation of groups, creation of options within the groups and assignment of pages to each option which will be returned upon selection of the option.

;Users
:Once a visitor creates an account, this account will be accessible via the users area. Site administrative access is also controlled by this area, so if you have a new admin than create an account un users and give them the rights and privileges you wish.

;Sessions
:A running report of who is logging in to use the website and when.

;Groups
:Groups are used to aggregate users and control rights and permissions. Groups can be created and assigned administrative rights via Settings (page managers, page editors, campaign managers, product managers, etc..etc). Once the group is created and assigned privileges, all users belonging to that group (assign users to groups in the Users area) will gain those privileges. As the system also supports content security (disabling page access for certain users), grouping can be used to create page content access groups: each group can be allowed access to certain restricted pages and users belonging to that group will benefit from that access.

;Forums
:all comment / forum posts will be accessible here. Posts can be viewed, edited, deleted or hidden as necessary. If forums is structured to have all posts require approval before being visible (controllable via Settings), than this queue will provide the means to monitor and approve those posts.

;Campaigns
:Email campaigns can be created, distributed and monitored here.

;Campaign Subscribers
:Visitors electing to receive emails from the site will be listed and manageable here. Note that visitors can subscribe without creating an account so users and subscribers are not synonymous. Check out the easy way to include subscription as an option in any custom form on the web site via Custom Forms.

;Banners
:Allows creation, management, placement and control of banner ads throughout the website. Note that banner ‘zones’ must be created and assigned within templates for banners to appear.

;Products
:Products can be created and managed here. Products are also assigned to pages here (and vice-verse you can assign products to a page from within page management). A product will not appear anywhere unless assigned to a page who’s template accommodates displaying products!

;Shipping
:Allows for management of shipping matrices that will govern shipping costs for purchases. Any number of shipping methods and price thresholds can be created. Note that each product has the ability to augment shipping costs with additional charges.

;Tax Management
Freeform creation of tax rules. Tax charges can be set by location and as many tax rules as you wish may exist. Note that products can be disqualified from taxes in product management.

;Discounts
:Allows creation of coupons and special offers on the web site. Any number of coupons/offers can be created. Each offer is subject to conditions (date frame, order amount, specific product application) and affords benefits (%/$ off sale, free shipping, free product) to those who qualify for the conditions set. Discounts can be set to automatically enable once the order qualifies (they will just appear in the cart once conditions are met) or only appear when a specific coupon code is entered by the user.

;Orders
:allows look up, viewing and editing of all web orders. Note that an order is created once a visitor first enters the web site, so this tool can be used to look up orders in progress as well as completed orders.

;Cart Report
:A handy report that shows activity/sales based on email campaigns, source codes, date frames and referring web sites. Use to monitor ROI on campaigns and advertisements and to also identify bottlenecks in the purchase process where improvements should be considered.

;Page Templates
:used to create and control how page content is managed by content managers and presented to visitors. Any number of templates can be created. Each page created must select a template which will govern what data and content are manageable within page management and how this information will appear to the visitor.

;Settings
:The core of the engine controls, settings dictates what tools are turned on and off on the website and how these tools operate. Controls are available for image/file, page, banner, service side caching, events, forums, polling, blogging, secure document, email campaigning, ecommerce, user and data library availability, preferences and behaviors.

;IP blocks
:All functions that accept user submissions (forum posts, custom forms, purchases, etc) allow for ‘blocking’ of submitting visitors. This is handy for spammers who wish to submit inappropriate information. Once blocked, they cannot use any submission functions on the web site. IP blocks lists all current blocks, reasons for blocking and provides the means to unblock the visitors.

The Administration Console:First Look

2008-12-05T02:42:36Z

James:

Upon logging in you will be presented with a series of links to access the administration areas of the web site. Which links are available is governed by what functions are ‘turned on’ for the web site (manageable by the ‘Settings’ area) and what functions you have rights to access. The administrators group (which the default administration account belongs to) has rights to access everything.

A quick breakdown of all the site functions (links you see at the top of the administration console) and what they do:

;Logout
:logs you out and places you in the home page.

;Home
:links to the home page of the web site

;Pages
:used to manage all pages of the website. Note that this system does not follow the typical paradigm of separating categories, subcategories, products and information pages. All pages are accessible and manageable through page management including the aforementioned pages, shopping cart, checkout process, user registration and account functions, etc. If it is a page the web site visitor can see, it exists in page management.

;Images
:pops up the image management library where you can upload, edit, delete images that will be available to web site pages, products, etc.

;Libraries

;URL Map
:Especially useful for conversions from older website platforms, url mapping allows you to create ‘alias’ urls to pages in the website. This will allow you to keep old links in tact so web site conversions don’t lose their search engine listings or accessibility from links on other sites.

;Menus
:Used to create the CNav menu bar links that will be consistent on all pages. Though most sites use one menu set throughout the site, you have the ability to create multiple menu sets, swap them out or assign different ones to different templates if you wish to show different menu bar options in varying areas of the site.

;Landing Pages
:Allows you to set different home pages for different users based on user account specifics. If you user goes to the root of the web site and qualifies for a landing page, that landing page will be shows instead of the home page.

;Form submissions
:Whenever a custom form is submitted on the web site, the submission will be stored in this area for future reference. Custom forms are used for catalog orders, newsletter registration, ask us forms, contact us forms or any other forms that are used to collect user information / requests.

;Pending approval
:The system supports staged approvals of pages, if required by the client. This requires two distinct user groups: page editors (which can modify pages, but modifications require approval before being visible by web site visitors) and page managers (who’s page changes go live immediately, and also have the ability to view and approve submissions made by page editors). Pending approval will list the pages waiting to be approved by managers.

;Custom Search Groups
:allows for creation of groups containing options that visitors may select from in order to find certain content (products, pages, etc). This is especially useful for select drop downs where visitors can select from a series of product or content groups. Custom search groups accommodates the creation of groups, creation of options within the groups and assignment of pages to each option which will be returned upon selection of the option.

;Users
:Once a visitor creates an account, this account will be accessible via the users area. Site administrative access is also controlled by this area, so if you have a new admin than create an account un users and give them the rights and privileges you wish.

;Sessions
:A running report of who is logging in to use the website and when.

;Groups
:Groups are used to aggregate users and control rights and permissions. Groups can be created and assigned administrative rights via Settings (page managers, page editors, campaign managers, product managers, etc..etc). Once the group is created and assigned privileges, all users belonging to that group (assign users to groups in the Users area) will gain those privileges. As the system also supports content security (disabling page access for certain users), grouping can be used to create page content access groups: each group can be allowed access to certain restricted pages and users belonging to that group will benefit from that access.

;Forums
:all comment / forum posts will be accessible here. Posts can be viewed, edited, deleted or hidden as necessary. If forums is structured to have all posts require approval before being visible (controllable via Settings), than this queue will provide the means to monitor and approve those posts.

;Campaigns
:Email campaigns can be created, distributed and monitored here.

;Campaign Subscribers
:Visitors electing to receive emails from the site will be listed and manageable here. Note that visitors can subscribe without creating an account so users and subscribers are not synonymous. Check out the easy way to include subscription as an option in any custom form on the web site via Custom Forms.

;Banners
:Allows creation, management, placement and control of banner ads throughout the website. Note that banner ‘zones’ must be created and assigned within templates for banners to appear.

;Products
:Products can be created and managed here. Products are also assigned to pages here (and vice-verse you can assign products to a page from within page management). A product will not appear anywhere unless assigned to a page who’s template accommodates displaying products!

;Shipping
:Allows for management of shipping matrices that will govern shipping costs for purchases. Any number of shipping methods and price thresholds can be created. Note that each product has the ability to augment shipping costs with additional charges.

;Tax Management
Freeform creation of tax rules. Tax charges can be set by location and as many tax rules as you wish may exist. Note that products can be disqualified from taxes in product management.

;Discounts
:Allows creation of coupons and special offers on the web site. Any number of coupons/offers can be created. Each offer is subject to conditions (date frame, order amount, specific product application) and affords benefits (%/$ off sale, free shipping, free product) to those who qualify for the conditions set. Discounts can be set to automatically enable once the order qualifies (they will just appear in the cart once conditions are met) or only appear when a specific coupon code is entered by the user.

;Orders
:allows look up, viewing and editing of all web orders. Note that an order is created once a visitor first enters the web site, so this tool can be used to look up orders in progress as well as completed orders.

;Cart Report
:A handy report that shows activity/sales based on email campaigns, source codes, date frames and referring web sites. Use to monitor ROI on campaigns and advertisements and to also identify bottlenecks in the purchase process where improvements should be considered.

;Page Templates
:used to create and control how page content is managed by content managers and presented to visitors. Any number of templates can be created. Each page created must select a template which will govern what data and content are manageable within page management and how this information will appear to the visitor.

;Settings
:The core of the engine controls, settings dictates what tools are turned on and off on the website and how these tools operate. Controls are available for image/file, page, banner, service side caching, events, forums, polling, blogging, secure document, email campaigning, ecommerce, user and data library availability, preferences and behaviors.

;IP blocks
:All functions that accept user submissions (forum posts, custom forms, purchases, etc) allow for ‘blocking’ of submitting visitors. This is handy for spammers who wish to submit inappropriate information. Once blocked, they cannot use any submission functions on the web site. IP blocks lists all current blocks, reasons for blocking and provides the means to unblock the visitors.

The Administration Console:First Look

2008-12-05T02:39:51Z

James:

Upon logging in you will be presented with a series of links to access the administration areas of the web site. Which links are available is governed by what functions are ‘turned on’ for the web site (manageable by the ‘Settings’ area) and what functions you have rights to access. The administrators group (which the default administration account belongs to) has rights to access everything.

A quick breakdown of all the site functions (links you see at the top of the administration console) and what they do:

;Logout
:logs you out and places you in the home page.

;Home
:links to the home page of the web site

;Pages
:used to manage all pages of the website. Note that this system does not follow the typical paradigm of separating categories, subcategories, products and information pages. All pages are accessible and manageable through page management including the aforementioned pages, shopping cart, checkout process, user registration and account functions, etc. If it is a page the web site visitor can see, it exists in page management.

;Images
:pops up the image management library where you can upload, edit, delete images that will be available to web site pages, products, etc.

;Libraries

;URL Map
:Especially useful for conversions from older website platforms, url mapping allows you to create ‘alias’ urls to pages in the website. This will allow you to keep old links in tact so web site conversions don’t lose their search engine listings or accessibility from links on other sites.

;Menus
:Used to create the CNav menu bar links that will be consistent on all pages. Though most sites use one menu set throughout the site, you have the ability to create multiple menu sets, swap them out or assign different ones to different templates if you wish to show different menu bar options in varying areas of the site.

;Landing Pages
:Allows you to set different home pages for different users based user account specifics. If you user goes to the root of the web site and qualifies for a landing page, that landing page will be shows instead of the home page.

;Form submissions
:Whenever a custom form is submitted on the web site, the submission will be stored in this area for future reference. Custom forms are used for catalog orders, newsletter registration, ask us forms, contact us forms or any other forms that are used to collect user information / requests.

;Pending approval
:The system supports staged approvals of pages, if required by the client. This requires two distinct user groups: page editors (which can modify pages, but modifications require approval before being visible by web site visitors) and page managers (who’s page changes go live immediately, and also have the ability to view and approve submissions made by page editors). Pending approval will list the pages waiting to be approved by managers.

;Custom Search Groups
:allows for creation of groups containing options that visitors may select from in order to find certain content (products, pages, etc). This is especially useful for select drop downs where visitors can select from a series of product or content groups. Custom search groups accommodates the creation of groups, creation of options within the groups and assignment of pages to each option which will be returned upon selection of the option.

;Users
:Once a visitor creates an account, this account will be accessible via the users area. Site administrative access is also controlled by this area, so if you have a new admin than create an account un users and give them the rights and privileges you wish.

;Sessions
:A running report of who is logging in to use the website and when.

;Groups
:Groups are used to aggregate users and control rights and permissions. Groups can be created and assigned administrative rights via Settings (page managers, page editors, campaign managers, product managers, etc..etc). Once the group is created and assigned privileges, all users belonging to that group (assign users to groups in the Users area) will gain those privileges. As the system also supports content security (disabling page access for certain users), grouping can be used to create page content access groups: each group can be allowed access to certain restricted pages and users belonging to that group will benefit from that access.

;Forums
:all comment / forum posts will be accessible here. Posts can be viewed, edited, deleted or hidden as necessary. If forums is structured to have all posts require approval before being visible (controllable via Settings), than this queue will provide the means to monitor and approve those posts.

;Campaigns
:Email campaigns can be created, distributed and monitored here.

;Campaign Subscribers
:Visitors electing to receive emails from the site will be listed and manageable here. Note that visitors can subscribe without creating an account so users and subscribers are not synonymous. Check out the easy way to include subscription as an option in any custom form on the web site via Custom Forms.

;Banners
:Allows creation, management, placement and control of banner ads throughout the website. Note that banner ‘zones’ must be created and assigned within templates for banners to appear.

;Products
:Products can be created and managed here. Products are also assigned to pages here (and vice-verse you can assign products to a page from within page management). A product will not appear anywhere unless assigned to a page who’s template accommodates displaying products!

;Shipping
:Allows for management of shipping matrices that will govern shipping costs for purchases. Any number of shipping methods and price thresholds can be created. Note that each product has the ability to augment shipping costs with additional charges.

;Tax Management
Freeform creation of tax rules. Tax charges can be set by location and as many tax rules as you wish may exist. Note that products can be disqualified from taxes in product management.

;Discounts
:Allows creation of coupons and special offers on the web site. Any number of coupons/offers can be created. Each offer is subject to conditions (date frame, order amount, specific product application) and affords benefits (%/$ off sale, free shipping, free product) to those who qualify for the conditions set. Discounts can be set to automatically enable once the order qualifies (they will just appear in the cart once conditions are met) or only appear when a specific coupon code is entered by the user.

;Orders
:allows look up, viewing and editing of all web orders. Note that an order is created once a visitor first enters the web site, so this tool can be used to look up orders in progress as well as completed orders.

;Cart Report
:A handy report that shows activity/sales based on email campaigns, source codes, date frames and referring web sites. Use to monitor ROI on campaigns and advertisements and to also identify bottlenecks in the purchase process where improvements should be considered.

;Page Templates
:used to create and control how page content is managed by content managers and presented to visitors. Any number of templates can be created. Each page created must select a template which will govern what data and content are manageable within page management and how this information will appear to the visitor.

;Settings
:The core of the engine controls, settings dictates what tools are turned on and off on the website and how these tools operate. Controls are available for image/file, page, banner, service side caching, events, forums, polling, blogging, secure document, email campaigning, ecommerce, user and data library availability, preferences and behaviors.

;IP blocks
:All functions that accept user submissions (forum posts, custom forms, purchases, etc) allow for ‘blocking’ of submitting visitors. This is handy for spammers who wish to submit inappropriate information. Once blocked, they cannot use any submission functions on the web site. IP blocks lists all current blocks, reasons for blocking and provides the means to unblock the visitors.

Talk:Installation

2008-12-05T02:36:56Z

James:

Mark,
The intro paragraph to the Table Fixes for Linux section is a little confusing. I get the general idea but could you break it up into smaller bites for me?

-James

Talk:Installation

2008-12-05T02:35:40Z

James: Comment

Mark,
The intro paragraph to this section is a little confusing. Could you break it up into smaller bites?

-James

Whirlwind eCommerce Engine Wiki

2008-12-04T01:07:42Z

James: /* Whirlwind eCommerce Engine */

== Whirlwind eCommerce Engine ==
{{Page Template Managers Shortcuts}}

Welcome to the Whirlwind eCommerce Engine Wiki.

* [[Installation]]
* [[Initial Setup]]

* [[Getting Started]] : Overview of The System
* [[Configuration]] : Integrator's Guide to Operations and Template Development
* [[Content Management]] : Site Manager's Guide to Using The System
** [[Pages]]: Page Content Management
** [[Image Library]]: Image Management Library
** [[File Library]]: File Management Library
** [[Content Libraries]]: Reusable, Selectable Content and Image Lists
** [[URL Map]]: Keeping old links intact and Alias URLs
** [[Menus]]: Persistent menu bar links
** [[Landing Pages]]: Specialized home pages targeted to specific users
** [[Form Submissions]]: Lookup any, all custom forms submissions
** [[Documents]]: Secure files for specific user access
** [[Pending Approval]]: View, edit and post page content changing pending approval
** [[Custom Search Groups]]: Manage Keyword drop downs that jump to specific page(s)
** [[Users]]: Lookup, add and edit users and user group membership.
** [[Sessions]]: View who is logging into the website and when
** [[Groups]]: Create user groups that can be used to manage administration or content access
** [[Forums]]: Approve pending forum/comment posts. Lookup, edit, delete all forum/comment posts.
** [[Campaigns]]: Create, manage and track email campaigns.
** [[Campaign Subscribers]]: Lookup, edit campaign subscribers.
** [[Banners]]: Create and manage banner ads, campaigns and zones for campaign/banner placement.
** [[Products]]: Add, edit delete products. Link products to pages.
** [[Product Price Matrices]]: Manage price matrices (volume discounting) that are available to all products.
** [[Product Option Groups]]: Manage groups of selectable options that are available to all products.
** [[Shipping]]: Control shipping options available and pricing
** [[Tax Management]]: Set tax rules for purchases
** [[Discounts]]: Manage coupons and automatic promotional discounts
** [[Orders]]: Lookup and edit orders (both completed, and shopping carts in progress)
** [[Cart Report]]: See return on investment for advertisements, campaigns. Find bottlenecks in the purchase process.
** [[Page Templates]]: Create page templates that govern how pages are managed and viewed
** [[Settings]]: Setup the site, activate site functions, manage site wide attributes
** [[IP Blocks]]: View list of computers blocked from form submissions. Add/remove blocks.