The Web pages are Bootstrap 3. The general principles are:
The image below is a brief introduction to how the TMServers merge web pages with data from the database and present it to the patron. To change a web page, a web developer needs to:
You can integrate the main marketing site or social media sites in a few ways:
When visiting these sites, make sure and click on the 'tickets' or 'Buy' or 'Buy Now' buttons on these sites. You can also look at the our responsive web page demo web site if you prefer (the page shows a sample image and lets you play).
Twitter Bootstrap is the industry leading go-to technology used for web sites that respond automatically to the type of device that the web page is displayed on. Web Pages using Bootstrap look great on mobile devices, tablets, computers and Smart TVs.
Refer to editing web pages for the general process of customization. |
All Web Pages are stored within the WebPages directory found in the folder number equal to that of your Theatre Manager database. There can be several versions of the WebPages folders each customized based on language.
The naming convention for the default web pages is:
Theatre Manager requires it to have that name. An example would be 'TMhome.html'.
When you are altering page names, ensure that the page name fits the content of the page, and does not too closely resemble another page name. This will prevent future confusion.
If you are using a Linux Apache Server please note the Operating System is case sensitive. You MUST take this into consideration when modifying page names.
Programmer's Note: Changing page names will mean that you will have to check and make sure that other pages are linked to the new name. |
You can change any of the web pages.
While you are testing your web site, or your customers are using web sales, you may see text you think could be worded more suitably for your venue. The best way to find the page to change is doing a multi-file text search to find the text.
You can search within all the files in the HTDOCS folder on the NGINX server. Good options for multi-file text searching are:
We recommend:
On a Macintosh, you can use a tool like BBedit - Free Edition to compare two sets of web pages and move changes from one page to another. (Text Wrangler can do this comparison and its free, BBedit is a paid product from the same company).
If you don't know which file to edit or compare, you can use various methods to find the file |
You can do a comparison on either:
In either case, the approach is:
By copying the pages, you can make changes to the web pages and test them in a test environment.
If you are jumping a few versions, you will need the web pages changes between the current version you are running and the latest release, or you can simply download a full copy of the latest web pages.
Use BBedit - free edition (or similar file comparison tool) to compare all files in a folder.
In the find differences window that opens, put the names of the old and new WebPages folders as per the picture below and click Compare.
This shows you the list of files that are different (bottom left) and under that, the actual differences in the files. Clicking on any one difference will show you where in the file the differences are and you can apply them (or not) in either direction. Repeat this decision making for all files that are different.
You can do a comparison on either:
In either case, the approach is:
This is so you edit the web pages and test them in a test environment.
By copying the pages, you can make changes to the web pages and test them in a test environment.
Use WinMerge (or similar file comparison tool) to compare all files in a folder.
The list window opens. It tells you which files are in only one folder and which files have a difference.
Winmerge shows you the actual differences in the files highlighted in orange. Repeat this decision making for all files that are different.
There are a few techniques to use such as:
Web pages exist in two states: Those that have been overridden and those that have never been changed. This means you need to search in two locations
when the main template server is a Mac, you'll typically find them in /tmp/TMWebPages/0.100.94. On windows, the files are typically in c:\windows\temp\TMWebPages\0.100.94
NOTE: the 0.100.94 folder name changed to reflect the version of the TM server you are running, since each new TM server creates a new template folder and deletes the old one.
Note, once you find the file to edit, you might want to compare old and new versions. |
If you use the web site and test it out, you may run across a page that you want to change. If you right click and 'view the source' for the page, you should see some words near the top of the HTML that indicate which page you are viewing. Refer to the image below for a sample:
Some web pages include other web pages, so you can scroll down through the page looking for the text or object you want to change and you might see a comment with a Start and End that has a file name in front of it. It means that you only need to change the template to change that small bit of information.
When you are looking at a web page, there is often distinguishing text on the web page that might give a hint. For example, the checkout page typically has words like 'Credit Card' on it. To find out which file that could be, use one of the useful text editing tools and search for that text within the WebPagesEN folder. That will often indicate which page has what you desire to change. Then just edit it.
Searching the source files for the web pages
Web pages exist in two states: Those that have been overridden and those that have never been changed. This means you need to search in two locations
when the man template server is a Mac, you'll typically find them in /tmp/TMWebPages/0.100.25. On windows, the files are typically in c:\windows\temp\TMWebPages\0.100.25
NOTE: the 0.100.25 folder will need to be replaced with the version of the TM server you are running, since each new TM server creates a new template folder and deletes the old one.
In the main directory, the file names often refer to the usage of the file. If you cannot find a file based on searching for its contents, then the names often give a clue. 'TMCart', for example is the shopping cart page. TMTickets is the list of ticketed events. TMHome is the 'home' page. Most of these can be found by searching based on content (the first strategy).
However there are a number of helper folders as follows:
The Web Pages used by the Web Sales Module contain tags and strings required by Theatre Manager to send and receive the correct data to and from the database. The Pages themselves are provided by Arts Management Systems upon purchase of the Web Sales Module, and the source code remains the property of Arts Management Systems.
All pages can be edited to fit within the overall scheme of the pre-existing website and the web sales component will fit seamlessly.
However, there are many different strings and types of tags required to be kept as they are provided, so that the site will operate as it was designed.
You can edit the Web Pages provided, but Arts Management Systems is not responsible for supporting or debugging errors that may occur. |
There are several types of texts within the code of each page that use the comment tags (i.e. <!-- BLANK -->).
<!--#include virtual="TMtemplates/tmnavButtons.html" -->
Although the <include> tag looks like a comment tag, it is read in by the page.
If a mistake is made, or a user needs to be prompted to do something, a message appears at the top of the pages. By default this message appears in red. Within the code of the pages you these messages are pulled in by the <field>F_HTML_PAGE_MESSAGE</field>.
If you want to change the wording of these messages, you can edit the TMError.txt page in the WebPages directory. We recommend using Microsoft Excel to open the document. You may then edit the Error Text column. Change the wording of the messages to whatever you like.
Any message that has the double dollar signs ($$) in it indicates that a database field inside Theatre Manager is being pulled into the message. For example, if you look at error number 10021, the message is "Welcome $$". The dollar signs in this case represents the first name of the patron that will be pulled into the message. |
Almost every page uses Javascript. The Javascripts are called in at the beginning of each page using <include> tags. these should remain in the page through any changes, unless the developer is sure that the function of the javascript is not needed. If the javascript is removed, and the site is no longer able to function as it was intended, Arts Management Systems will not be responsible for recovering the code.
Click here for more detailed information about the different functions javascript plays in the web pages.
When viewing the web page code, there are strings that appear as <field>XXXXXXXXX</field>.
These fields are internal Theatre Manager fields, and should never be altered. In most cases, they reference information entered within Theatre Manager. If these values need to be changed, you should change them in Theatre Manager, not in the web page code. Any text within the
The Web Server URL field will contain the sub-domain or A record for the online ticketing site and will looks something like https://tickets.myvenue.org. The setup of the A record should point to the external IP address of the organization for routing purposes. The external IP can be determined by going to http://www.whatismyip.com. The internal network will then redirect the communication to the Apache machine.
<base href="https://tickets.yourvenue.org/1/WebPagesEN">
Where tickets.yourvenue.org is pulled from the F_HTML_FIREWALL reference and the F_HTML_IMAGE_SERVER adds the /1/WebPagesEN indicating the path of where the images will be referenced.
Click here for Internal Variable Theatre Manager Fields.
The buttons used by Theatre Manager for navigation within each Web Page (not tmnavSide.html) are regular form input buttons. They have been altered using Cascading Style Sheets and javascript so that they are customizable in colour and style.
Click here for information about Navigation Buttons.
The style sheets are used with the Web Pages are: stylePages.css and styleButtons.css. They are linked to each page with strings.
href="/installing-theatre-manager/stylebuttons">Click here for details on the different styles for the buttons.
href="/installing-theatre-manager/stylepages">Click here for details on the different styles for the pages.
These are the different types of internal Variable Theatre Manager Fields that can be used in almost all pages. There are some fields:
F_HTML_FIREWALL | The A record of the Web Server URL as set in the Apache tab of Company Preferences |
F_HTML_IMAGE_SERVER | Web Pages path of the Image/Gif server as set in Web Listener tab of Company Preferences in conjunction with the Outlet Number of the database. |
F_HTML_IMAGE_EBLAST_SERVER | path for images that are part of an e-blast to pull them from the second generation listener |
F_HTML_PAGE_IDENTIFIER | the Page Identifier which maintains the patron's connectivity during a session |
F_HTML_PAGE_MESSAGE | The Theatre Manager message relative to each page |
F_HTML_PARAMETER | an internal connectivity number that follows pages (should not be removed from the page) |
F_HTML_SELECTED | the selected line in the shown list |
F_HTML_CART_STATUS | Status of the shopping cart |
F_HTML_REMOVE_CART_ITEM_YN | Removing cart items (Yes or No) |
F_HTML_NEXT_BEST_SEAT | A field put in the confirm reserved seat page used for the 'find next best seat' function. This works in conjunction with 'btnBestAvail' and the value is filled in by Theatre Manager |
F_HTML_NEXT_BEST_AREA | Also put in the reserved seating confirmation page. This field pulls from the Best Seat Setting tab of the Map in Theatre Manager. It carries forward the section that the user was searching. |
F_HTML_EMAIL_ADDRESS | The current logged in user's Email Address |
F_HTML_LOGGED_IN | This is a boolean flag indicating if the user is logged in (0=not logged in, 1=logged in). It can be used to display state on the left navigation bar |
F_HTML_SOLD_PERCENT | This is a number (0-100) that indicates the percentage that a performance is sold. Can be used in rowTicketEvent.html to create a visual indicator of seat availability. |
F_HTML_MAIN_TEMPLATE | Indicates the name of the main page that is being loaded. Very useful for identifying the page in the googleheader.html file for google analytics or for debugging if you simply put that in the header file. |
F_HTML_CURRENT_TEMPLATE | indicates the name of the row template page being loaded - can be used for debugging |
F_HTML_CURRENT_OUTLET | shows the outlet that the page is for |
F_HTML_CURRENT_LANGUAGE | shows the language that the page was loaded for |
F_HTML_CURRENT_DATETIME | the current date and time which can be used in dat functions for comparison to now |
F_HTML_CURRENT_DATE | the current date which can be used in dat functions for comparison to today |
F_HTML_CURRENT_TIME | the current time which can be used in dat functions for comparison to the time |
F_HTML_DATETIME_FORMAT | the format of the date and time fields |
F_HTML_DATE_FORMAT | the format of the date fields |
F_HTML_TIME_FORMAT | the format of the time fields |
All of the list variables pull their information from the rowXXX.html and setXXX.html files that are in the TMtemplates folder of the WebPages folder.
F_HTML_BEST_SEATS_LIST - List of available best seats
F_HTML_CAMPAIGN_LIST - List of available Campaigns
F_HTML_COUNTRY_LIST - List of the active countries
F_HTML_CURRENT_CART_LIST - List of any current Shopping Carts
F_HTML_EVENT_LIST - List of any current Events
F_HTML_HISTORICAL_CART_DETAIL_LIST - List of details of past shopping carts
F_HTML_HISTORICAL_CART_LIST - List of past shopping carts
F_HTML_MONTH_LIST - List of months for event selection
F_HTML_PASS_LIST - List of available Passes/ Memberships
F_HTML_PAYMENT_LIST - List of available payment methods
F_HTML_PERFORMANCE_LIST - List of available performances
F_HTML_PREFER_HTML_LIST - List of patrons who prefer html emails to text
F_HTML_PROMOTIONS_LIST - List of available Sales Promotions
F_HTML_PROVINCE_LIST - list of available Provinces/ States
F_HTML_SUBSCRIBE_LIST - List of patrons who are subscribed to a specific mail list
F_HTML_TICKET_QTY_LIST - List of available quantities of tickets for the event
F_HTML_UNSUBSCRIBE_LIST - List of patrons who have Unsubscribed to a mail list
F_HTML_YEAR_LIST - List of years
Database Fields
For an up to date list of the merge fields and their meanings, from Theatre Manager, print the Utility Functions and Database Analysis report - Database Dictionary and Layout.
C_SEQ - Patron number
C_COMPANY - Patron's Company
C_TITLE - Patron's title at the company
C_FIRST_NAME - Patron's First Name
C_INITIAL - Patrons Middle Initial or name
C_LAST_NAME - Patron's Last Name
C_SEQ - patron gender (in code tables)
AD_ADDRESS1 - Patron's primary Address Line 1
AD_ADDRESS2 - Patron's primary Address Line 2
AD_CITY - Patron's City
AD_PROVINCE - Patron's province
AD_POSTAL_CODE - Patron's Postal Code
AD_COUNTRY - Patron's country
SPR_BACKUP_ELAPSED_TIME - Elapsed time into backup
SPR_FORCE_LOGOFF_DAILY_AT - Time at which users are forced off for backup
SPR_TAX1_DESC - Description of Tax Code #1
SPR_TAX2_DESC - Description of Tax Code #2
SPR_TAX3_DESC - Description of Tax Code #3
DD_CORPORATE - flag indicating a corporate gift (true or 1), or not (false or zero)
DD_AMOUNT_PLEDGE - Amount of gift given on the internet
DD_NAME_OF - Donor's name
DD_PROGRAM_YEAR - the program year in which the donor is to be recognized
DD_FLD1_FC_SEQ - key indicating the value of the donor popup field #1 - must be in code tables to be valid
DD_FLD2_FC_SEQ - key indicating the value of the donor popup field #2 - must be in code tables to be valid
DD_FLD3_FC_SEQ - key indicating the value of the donor popup field #3 - must be in code tables to be valid
DD_FLD4 - text field indicating a value for donor field 4 (can be used for a short comment if desired)
DD_NOTES - large text field for a description of the donation
D_DONATION_DESC - Description of this donation
D_DONOR1_DESC - Description of custom field 1 for donations
D_DONOR2_DESC - Description of custom field 2 for donations
D_DONOR3_DESC - Description of custom field 3 for donations
D_DONOR4_DESC - Description of custom field 4 for donations
D_FESTIVAL_DESC - Description of a Festival or General Admission event
D_MAIL_FEE_AMOUNT - Amount of mail Fee
D_MEMBER_DESC - Description of this Membership/Pass/Gift Certificate
D_SECTION_DESC - Site description for 'Section'
D_ROW_DESC - Site description of the 'Row'
D_SEAT_DESC - Site description for 'seat'
D_WEB_FEE_DESC - Description of this Web Fee
D_WEB_LISTENER_IP_PORT - the port that the web listener is listening on
D_WEB_REMOTE_IP_ADDR -
D_WEB_REMOTE_IP_PORT -
DC_CAMPAIGN - Donation Campaign name
DC_SEQ - Donation Campaign number
F_WEBPAGE_PASSWORD - Password for patron
FC_SEQ - Internal number on this Code Table
FC_RESULT1_NAME - Code Table value
FC_RESULT2_NAME - Code Table value
I_LOCAL_IP_ADDR -
M_PURCHASE_AMOUNT - Amount for which the membership/pass/gift certificate will be purchased for
MS_SECTION - Section the seats are in
MS_ROW_NUMBER - Row the seats are in
MS_SEAT_NUMBER - Seat numbers
MT_SEQ - Membership/ Pass type number (not control number)
MT_DESCRIPTION - Membership/Pass Description
ORD_SEQ -
ORD_TIX_PRINT_STATUS -
ORD_NOTES - Any notes on an order
ORD_DATE_ENTERED - Date that an order was entered
P_SEQ - Event number (not event code)
P_PLAY_TITLE - Event title
PAY_AUTH_REF_NO - Authorization number on card payments
PAY_CARD_NO - Credit card number
PAY_CARD_EXPIRY - Credit card Expiry Date
PAY_METHOD_FC_SEQ -
PAY_TOTAL_PAID - Amount of the payment
PB_PERFORM_DATE - Performance Date
PB_PERFORM_TIME - Performance Time
PC_DESCRIPTION -Description of the Price Code
PM_SHORT_NAME - Mail List name
PS_QUANTITY - Quantity of tickets for Festival Seating
SC_DESCRIPTION - The description of the promotion code
SCD_DON_AMOUNT - If non-zero, the donation amount applied to a campaign
SCD_MAIL_FEE - The mailing fee for the shopping cart
SCD_MT_AMOUNT - The amount of the membership that the patron wishes to purchase
SCD_PROGRAM_NAME - The name that the patron wishes to use for this donation in the sponsor program
SCD_QUANTITY - This value is 1 for reserved seating and could be more for festival seating tickets and membership
SCD_SEQ - The shopping cart number that this purchase belongs to
SCH_DATE_CHECKOUT - The date that the patron proceeded to check out the purchased (i.e. completed it). if blank, it was never completed
SCH_DATE_ENTERED - The date that the patron began the internet purchase using his shopping cart
SCH_DATE_UPDATED - The latest date that the patron made a change to the shopping cart
SCH_TAX1 - The total of this tax type for all items in this shopping cart
SCH_TAX2 - The total of this tax type for all items in this shopping cart
SCH_TAX3 - The total of this tax type for all items in this shopping cart
SCH_TIX_QUANTITY - The total number of tickets in this shopping cart
SCH_TOTAL_COST - The total cost of the items in the shopping cart, including taxes
There are approximately 350 web pages contained in the web module. Below is a list of the basic pages to be need to be edited. Additional pages can be altered as needed.
Pages altered within the WebPagesEN folder should be Copied, Pasted and Edited.
Files in the WebPages directory | ||
favicon.ico |
| |
index.html |
| |
Files in the WebpagesXX folder (/1/WebPagesXX) | ||
TMcart.html |
| |
Files in the tmGifs folder (/1/WebPagesXX/tmGifs) | ||
favicon.ico |
| |
tmCompanyLogo.jpg |
| |
ticketAd.png |
| |
custom.css |
| |
Files in the tmTemplates folder (/1/WebPagesXX/tmScripts) | ||
styles.html |
Can be used to update the default bootswatch theme.
| |
Files in the tmTemplates folder (/1/WebPagesXX/tmTemplates) | ||
tmCheckoutDonationReasonToBuy.html |
| |
tmContactHours.html |
| |
tmnavButtons.html |
| |
tmSocialMedia.html |
|
There are approximately 150 web pages contained in the web module. Below is a list of the primary pages that need to be edited:
Files in the WebPages directory | ||
favicon.ico | - Create a favicon.ico file to reflect the organizations branding. This is used for pages not processed by the TM Server. You should copy this to the tmGifs folder (or you can make a different one for each outlet). | |
index.html | - Replace "localhost" with the name of the web server to be accessed (tickets.yourtheatre.org).
- Replace '1' with the Company number found in Company tab of Company Preferences. | |
TMsysNoListeners.html | - Replace "www.yourtheatre.org" with the organization's main URL. | |
Files in the Outlet folder (WebPages/1) | ||
TMsysBusyListeners.html | - Replace "www.yourvenue.org" with the name of the web server to be accessed (tickets.yourtheatre.org). | |
TMsysBusyListenersNorefresh.html | - Replace "www.yourtheatre.org" with the name of the web server to be accessed (tickets.yourtheatre.org). | |
TMsysErrorListeners.html | - Replace "www.yourtheatre.org" with the name of the web server to be accessed (tickets.yourtheatre.org). | |
TMsysNoListeners.html | - Replace "www.yourvenue.org" with the organization's main URL. | |
Files in the WebpagesXX folder (/1/WebPagesXX) | ||
TMcart.html | - Alter the D_MEMBER_DESC field to accurately reflect the name of membership items sold online.
- Once changes have been made, this page should be saved to the /1/WebPagesXX folder | |
Files in the tmFee folder (/1/WebPagesXX/tmFee) | ||
tmBoxOfficePolicy.html | - Update the Box Office policies to accurately reflect those of the organization.
- Once changes have been made, this page should be saved to the /1/WebPagesXX/tmFee folder. | |
tmMailFee.html | - Alter the mail fee page to reflect the reason or purpose of the mailing fee.
- Once changes have been made, this page should be saved to the /1/WebPagesXX/tmFee folder. | |
tmMailDefault.html | - Edit the default mail fee page to reflect the reason for any additional mailing fees.
- Once changes have been made, this page should be saved to the /1/WebPagesXX/tmFee folder. | |
tmOrderFee.html | - Update the order fee page to reflect the reason or purpose of the order fee.
- Once changes have been made, this page should be saved to the /1/WebPagesXX/tmFee folder. | |
tmOrderFeeDefault.html | - Alter the order fee default page to describe the reason for any additional order fees.
- Once changes have been made, this page should be saved to the /1/WebPagesXX/tmFee folder. | |
Files in the tmGifs folder (/1/WebPagesXX/tmGifs) | ||
favicon.ico | - Copy the overall favicon so that there is one for each language or outlet, or create a custom one for this language/outlet in a multi company setup | |
pageHeader.gif | - Replace the existing pageHeader.gif with an image that reflects the organization's branding.
- If the image dimentions are larger then the original image the stylePages.css file will need to be updated accordingly. | |
styleButtons.css | - .Button - background-color, color, border
- .Buttonover - background-color, color, border - .New - background-color, color, border - .Newover - background-color, color, border | |
stylePages.css | - .Background - background-color, margin-top
- .Title - color - .Message - color - .Tablerowheader - background-color - .Tablerowdetail - background-color | |
Files in the tmTemplates folder (/1/WebPagesXX/tmTemplates) | ||
tmContactHours.html | - Update the contact hours to reflect those of the box office or organization.
- Once changes have been made this page should be saved to the /1/WebPagesXX/tmTemplates folder. | |
tmnavButtons.html | - Move any button references that are not used by the organization to the commented out section of the page.
- Change the names of the buttons as needed. - Once changes have been made, this page should be saved to the /1/WebPagesXX/tmTemplates folder. | |
tmtermsandcondiations.html | - Update the terms and conditions page to accurately reflect those of the organization.
- Once changes have been made, this page should be saved to the /1/WebPagesXX/tmTemplates folder. | |
tmTicketHandling.html | - Edit to include the ticket handling specifics of the organization.
- The options available will depend on the E-Ticket printing options within the database. - Once changes have been made, this page should be saved to the /1/WebPagesXX/tmTemplates folder. |
The following pages, when customized, are contained directly within the htdocs folder most commonly located on the TM Web server on a PC at:
C:\BoxOffice\WebPages
and on a Mac at:
/BoxOffice/WebPages
It is worth noting that at minimum, the pages linked here will need edits in order to customize the site for an organization.
A full set of the default pages can be downloaded from the Artsman Git Repository.
Clients using the Enterprise Edition of Theatre Manager generally only have a "1" folder. The "1" is the Outlet Number as defined in Company Preferences.
Those clients who have Outlet Edition will have a "1", "2", "3" (and so on) folder assigned to each outlet based on the number assigned to each in Company Preferences. This way, each company can have its own set of web pages customized however they'd like and selling their own merchandise.
The second generation listener is designed handle traffic for multiple outlets. At this time, however, each outlet still needs its own "classic" web listener (until they are retired). |
The pages beyond this folder mark the true beginning of the custom look of a client's online store.
Description:
Location:
htdocs/1
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1
Able to Call Page(s):
Called By Page(s):
Description:
Location:
htdocs/1
Able to Call Page(s):
Called By Page(s):
Clients who wish to have multilingual pages will need to do four things:
After a patron picks their language, the next time they log in, Theatre Manager will recall and use their personal language preference. |
Description:
Questions and Answers:
Q: What needs to be done to setup the TMattendance.html page for tracking attendance in Theatre Manager?
A: The page only needs to be accessed in order to use the attendance tracking feature. For additional details on setting up the scanning process please click here.
____________________________________________________________
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q:
A:
____________________________________________________________
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Description:
Questions and Answers:
Q: What is the Calendar Token for?
A: The Token is used for subscribing to a calendar. It is a unique value that allows for syncing with outside applications such as iCal, Outlook or Google Calendars.
____________________________________________________________
Q: Why would you reset a Calendar Token?
A: Reseting the token makes the previous token invalid. It prevents any previously subscribed calendar applications from accessing the calendar until the token has been updated in that program.
____________________________________________________________
Q: Is the Calendar Token needed to download the calendar?
A: The token is only needed when subscribing to a calendar.
____________________________________________________________
Q: What is the difference between Downloading and Subscribing to a Calendar?
A: When a calendar is downloaded the ICS file contains all Performances and Classes as of the download date. By subscribing to a calendar the details in the third party application will update as the information in the Theatre Manager database updates. If new Events are made available online the Performances or Classes will appear in the subscribed Upcoming Events calendar. When the patron purchases, exchanges or refunds tickets the details will automatically update in the subscribed My Upcoming Events calendar.
____________________________________________________________
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Custom pages can be created for an event by duplicating the existing default page. The word Default in the page name is then replaced with the donation campaign number. The donation campaign number is located in the Seq # column under Setup >> System Tables >> Donation Campaigns in Theatre Manager. If this column is not visible simply right click on any of the column headers and select it. The column with then display in the list.
Description:
Location:
htdocs/1/WebPagesEN/tmCampaign
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmCampaign
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmCampaign
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q:
A:
____________________________________________________________
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Q: Why are there no payment methods in the drop down list?
A: If your credit card payment methods do not appear in the drop down it may be the Merchant Account is not setup to be used online. In Theatre Manager go to Setup >> System Tables >> Merchant Accounts. Double click on the merchant account and ensure the By the Web Listener box is checked. Under the Cards tab in the merchant account double click on each card and ensure the Available At Internet box is checked. The card will also need a bullet in the Yes column for Authorize Via Credit Card Server.
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmContent
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmContent
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmContent
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmContent
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmContent
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmContent
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmContent
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmContent
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmContent
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmContent
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmContent
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmContent
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
This folder will contain a copy of each web page customized for an organizations online tickets site that does not pertain to the tmGifs folder. Online sales will review the tmCustom folder prior to the default web pages. If a custom page is located the online sales will display the custom page over the default page. For more information please click here.
This folder contains customized copies of the default pages from within the WebPagesEN folder. These pages have been edited to meet the design and desired look for the organizations online sales. Each page contained within a sub-folder should be saved to the corresponding folder within the tmCustom folder. For details on the default WebPagesEN folder click here.
This folder contains customized copies of the default pages from within the tmCampaign folder. These pages have been edited to meet the design and desired look for the organizations online sales. For details on the default tmCampaign folder click here.
This folder contains customized copies of the default pages from within the tmContent folder. These pages have been edited to meet the design and desired look for the organizations online sales. For details on the default tmContent folder click here.
This folder contains customized copies of the default pages from within the tmEvent folder. These pages have been edited to meet the design and desired look for the organizations online sales.
For details on the default tmEvent folder click here.
This folder contains customized copies of the default pages from within the tmFee folder. These pages have been edited to meet the design and desired look for the organizations online sales. For details on the default tmFee folder click here.
This folder contains customized copies of the default pages from within the tmMaps folder. These pages have been edited to meet the design and desired look for the organizations online sales. For details on the default tmMaps folder click here.
This folder contains customized copies of the default pages from within the tmPass folder. These pages have been edited to meet the design and desired look for the organizations online sales. For details on the default tmPass folder click here.
This folder contains customized copies of the default pages from within the tmScripts folder. These pages have been edited to meet the design and desired look for the organizations online sales. For details on the default tmScripts folder click here.
This folder contains customized copies of the default pages from within the tmSubscription folder. These pages have been edited to meet the design and desired look for the organizations online sales. For details on the default tmSubscription folder click here.
This folder contains customized copies of the default pages from within the TMtemplates folder. These pages have been edited to meet the design and desired look for the organizations online sales.
For details on the default TMtemplates folder click here.
This folder contains customized copies of the default pages from within the tmVenue folder. These pages have been edited to meet the design and desired look for the organizations online sales. For details on the default tmVenue folder click here.
Description:
Customizations if donation fields madatory
There are 3 fields on that are donor popup fields on the notes tab of the donation window. For the fields have been made mandatory, then you will need to have a code table value for custom donation field1, donation field2 and/or donation field3 in order for donations donations to be accepted online.
There is an include file for tmTemplates/tmDonationHiddenFields.html that may need revised if any of the donation fields have been made mandatory. If so, then you will need to look at that file and uncomment the appropriate fields below.
Change the value of xxx, yyy, or zzz in the input strings below to be the internal record number of the appropriate popup. Also, move the mandatory input field so that it is not uncommented
<INPUT NAME="DD_FLD1_FC_SEQ" TYPE=hidden id="DD_FLD1_FC_SEQ" value="xxx">
<INPUT NAME="DD_FLD2_FC_SEQ" TYPE=hidden id="DD_FLD2_FC_SEQ" value="yyy">
<INPUT NAME="DD_FLD3_FC_SEQ" TYPE=hidden id="DD_FLD3_FC_SEQ" value="zzz">
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Note that this feature that will be coming but has not yet been implemented.
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Location:
htdocs/1/WebPagesEN
You may change any error message that you wish to suit the needs of your venue. However, a few pertain to the sign-in process and may indicate that an email address cannot be used which you may not want to change.
During our Oct 2016 PCI audit, we were required to them generic because it is against PCI rules to divulge information or conditions that could make it easier for a hacker to gain access to a patrons account. Visa/Master Card's reasoning is simple: If you say the email exists, then a hacker would likely cross reference that with other information stolen or bought on the internet. Since people tend to use the same passwords across web sites, they would cross reference and might gain access. For your safety and the safety of your patrons, we ensure Theatre Manager passes the PCI Audit- to give you less to worry about. The PCI council places 100% web site security over empathy to make any commerce web site easier for patrons to use. |
Message # | Purpose of error message that could occur during login process | Message before being genericized for PCI Audit |
---|---|---|
10012 | error message if email address could not be found in the database during the login process. | Error - Please enter a valid email address and password combination. |
10013 | error message if email does exist in the database, but password is incorrect during login. Should be same message as 10012 to limit ability to delineate this condition | Error - invalid email address and password combination{br}(note: password is case sensitive). |
10032 | the response if email address found and message sent to patron. it is now generc to say that if the email address was found, then an email would be sent, which does not give away the fact that the email adddress does exist | A password reset has been sent to your email address at {email}.{br}Please look for the email and follow the instructions on it. |
10034 | response for email address not in the database. The message is set to be same as 10032 for PCI/OWASP compliance so that no information is conveyed back to the user as to success or failure of the request - it helps prevent finding information in the system for brute force attacks. | We're sorry, there are no accounts associated with the email address {email}. Please verify it. |
10255 | response indicating email address appears invalid because we are unable to lookup the mail exchange server for that email address. Again, according to PCI/OWASP, it is more secure to simply say the email address is invalid (and we suggest to contact the box office) | {contents} appears invalid. Unable to lookup the mail exchange server for that email address. |
10256 | response indicating email address appears invalid because we are unable to lookup the DNS server for that email address. Again, according to PCI/OWASP, it is more secure to simply say the email address is invalid (and we suggest to contact the box office) so this message is set to the same as 10255. | {contents} appears invalid. Unable to lookup the DNS server for that email address. |
10257 | response indicating email address is already on file and to use 'forgot password' instead. Again, according to PCI/OWASP, it is more secure to simply say the email address is invalid (and we suggest to contact the box office) so this message is set to the same as 10255. | {contents} is currently in use and cannot be used for the creation of a new account.{br}If this is your email address, please request your password instead. |
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Custom pages can be created for an event by duplicating the existing default page. The word Default in the page name is then replaced with the event number. The event number is located in the Event # column under Setup >> Events in Theatre Manager.
Location:
htdocs/1/WebPagesEN/tmEvent
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Location:
htdocs/1/WebPagesEN/tmEvent
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
An example of the default email reminder page tmLiveEventReminderEmailDefault.html for live events is below. This can be customized for each live event if you would like. | |
Email reminders must be enabled for the performances that you wish to send an automatic reminder for. |
Custom pages can be created for a fee by duplicating the existing default page. The word Default in the page name is then replaced with the fee sequence number. The fee number is located in the Fee # column under Setup >> System Tables >> Fee Types in Theatre Manager. If this column is not visible simply right click on any of the column headers and select Fee #. The column with then display in the list.
Description:
Location:
htdocs/1/WebPagesEN/tmFee
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmFee
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmFee
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmFee
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmFee
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmFee
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmFee/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Special Variables:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: Can this page be updated such that the print at home tickets will contain organization-specific or other information?
A: Yes, it can. The page itself can be updated to contain whatever text a client wishes to include. Please note that this same page is used for all events, so event-specific information or similar will print on all tickets generated from this page.
____________________________________________________________
Q: Can I add a logo to the print at home tickets?
A: Yes, you can. Simplest way is to put the logo image file inside tmGifs and then include a link on this page. The link should contain the full path to the image as appose to just a "img src="httpstmGifs/sponsorLogo.jpg" reference.. Please note that any logo included here will print on every ticket, regardless of event. So a sponsor logo for one show only would print on every show's tickets.
____________________________________________________________
Q: Can I add colour or a background colour to the tickets?
A: Yes, you can. We originally chose to have the page print in black and white to make things easier on the end user (and their toner cartridge) but if you'd like the tickets to have colour, you can edit the stylePages.css file. The areas to edit are those that end in "print," ie, backgroundprint or tablerowdetailprint.
____________________________________________________________
Q: Can I print one ticket per page?
A: Yes, you can. This page pulls ticket details from the rowFutureTicketPrintCourse.html, rowFutureTicketPrintFestival.html, rowFutureTicketPrintHeader.html and rowFutureTicketPrintReserved.html pages. These pages can be altered to fill one full page. The following web page gives examples on how to create page breaks http://www.w3.org/TR/css-print/#s.8.2.
____________________________________________________________
Q: The number under the bar code contains leading zeros, how important are these extra zeros?
A: The leading zeros are added to standardize the length of the ticket number. They are largely for esthetics. When the bar code is scanned Theatre Manager removes the leading zeros.
____________________________________________________________
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
This lets the patron set their own reason for not attending a class online. The process is:
Permission to do these functions is determined by:
You can have a direct link to the manage events page
On this window, patrons can indicate if they cannot make a class (in a course). The are allowed to select an attendance reason from a limited list set up in code tables.
If the user clicks on any of the absent icons as part of the list, they can add, change or clear the attendance reason on another web page.
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Individual bootstrap elements can be formatted in the custom.css page to create a unique design for the ticketing site.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/tmGifs/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
# | Item | Description |
1 | .button | References the buttons across the top of the online sales window. |
2 | .buttonover | The result of a mouse hovers over the buttons across the top of the online sales window. |
3 | .new | The buttons within the tables in the online sales window. |
4 | newover | The change in a button within the the tables when an mouse if hovered over it. |
Questions and Answers:
Q: Why are the navigation buttons appearing in deep red on Internet Explorer, but are normal on other browsers?
A: When the line below is uncommented in the style sheets the buttons appear a graded red in an Internet Explorer browser.
filter:progid:DXiMageTransform.microsoft.Gradient(GradientType=0,StartColorStr='#ff800000',EndColorStr='#ff800000');
For details on commenting out the crimson filter click here.
____________________________________________________________
Q: I do most of my web development testing with Safari or Chrome as a web browser, and eventually I get around to checking things with Internet Explorer. What I am seeing with our ticketing site is two vastly different color schemes. Is there a separate set of .css files or something that pertains specifically to Internet Explorer, or are they just different from the Mac browsers?
A: In part, this has to do with the color calibration of the monitor the patron is using to view your site. You can change the color calibration for your monitors - which is especially easy on a Mac. While Mac has color correction set up for your monitor, your browser may or may not use color correction for web content/images depending on its setup. Your color picker reports what your Operating System thinks it is rendering. Another browser may report something else.
Most Mac browsers (Safari, Firefox) use color management to display what is theoretically True Color. This means that it will read the colors that are embedded in original web page or image, match them to the color calibration of your monitor and display them appropriately. Unmanaged browsers (such as Internet Explorer) do not read the embedded color coding and apply colors according to a default set in a color palette - which may or may not match what the original web page designer intended.
So while this is not a solution, it is an explanation. The images and web page elements are being sent identically to all browsers. The various browsers, however, are interpreting the color palette differently. Safari and Firefox offer color calibration to your monitor. Other browsers may not.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/tmGifs/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
# | Item | Description |
1 | .background | Indicates the colour, image and attributes to be used for the background in most web pages within the online sales. |
2 | .backgroundPrint | The colour to be used as the background for print pages from within the web sales. |
3 | .backgroundSide | The colour used for the tmnavSide.htmlpage. When using frames, this attribute can be edited to meet the design requirements for the side panels. |
4 | .backgroundSidePrint | The colour of the side panels, when printed, while using frames within the web pages. |
5 | .limitedprofilelogin | Allows for the over all customization of the TMpatronLimitedProfile.html page. |
6 | .limitedprofileentry | The customization of the entry fields within the TMpatronLimitedProfile.html page. |
7 | .main | A text style mainly included within <P> tags in the web pages. Sets the font size and colour of text within a web page. |
8 | .mainPrint | The text colour for print pages from within the web sales. |
9 | .missingfield | The font used for fields where information must be entered to meet the mandatory data requirements within the Theatre Manager database. |
10 | .title | The header of the page that often appears at the top of the browser window. |
11 | .titlePrint | Header for print pages from within the web sales. |
12 | a.navlink | Attributes for the navigation links within the tmnavSide.html pages. It is also used in the TMattendancePalm.htmlpage. |
13 | a.navlinkPrint | The attributes of a.navlink when printed. |
14 | a.navlink:hover | The result of a mouse moving over a hyperlink in the tmnavSide.html page. |
15 | a.navlinkPrint:hover | The attributes of a.navlink:hover when a mouse is on top of it at the time the page is printed. |
16 | .message | The text pulled from the TMError.txt page. This text is found across the top of the web page. |
17 | .messagePrint | The attributes of .message when printed. |
18 | .waitmessage | This message appears on web pages where it make take a moment for the request to return with information from the database. |
19 | a.link | An <A HREF> style for links within the web pages. |
20 | a.linkPrint | The attributes of a.link when printed. |
21 | a.link:hover | The result of a mouse moving over the a.link hyperlink in the web pages. |
22 | a.linkPrint:hover | The attributes of a.link:hover when a mouse is on top of it at the time the page is printed. |
23 | .playinfo | The text within the season or ticket sales process that describes the performance details. |
24 | .playinfoPrint | The attributes of a.playinfo when printed. |
25 | .backgroundBottom | The colour used for the tmnavBottom.htmlpage. When using frames, this attribute can be edited to meet the design requirements for the bottom panels. |
26 | .backgroundBottomPrint | The colour of the bottom panels, when printed, while using frames within the web pages. |
27 | .tablerowheader | Descriptive information within the tables of the web pages. |
28 | .tablerowheaderprint | The attributes of .tablerowheader when printed. |
29 | .tablerowdetail | Active information within the tables of the web pages. |
30 | .tablerowdetailprint | The attributes of .tablerowdetail when printed. |
# | Item | Description |
31 | .calendarheader | For Future Implementation. |
32 | .calendarcellheadercurrentmonth | For Future Implementation. |
33 | .calendcellheadercurrentdate | For Future Implementation. |
34 | .calendarcellheaderothermonth | For Future Implementation. |
35 | .calendarcellheaderotherdate | For Future Implementation. |
36 | table.inner | For Future Implementation. |
37 | table.outer | For Future Implementation. |
38 | table.calendar | For Future Implementation. |
39 | table.calendar a.link | For Future Implementation. |
40 | table.calendar a.link:hover | For Future Implementation. |
41 | .calendar2 | For Future Implementation. |
42 | table.calendar tr | For Future Implementation. |
43 | table.calendar td | For Future Implementation. |
44 | .calendar2 | For Future Implementation. |
45 | .table.calendarother | For Future Implementation. |
46 | table.calendarother a.link | For Future Implementation. |
47 | table.calendarother a.link:hover | For Future Implementation. |
48 | .calendar2 | For Future Implementation. |
49 | table.calendarother td | For Future Implementation. |
50 | table.datenumber | For Future Implementation. |
51 | table.datenumber tr | For Future Implementation. |
52 | table.datenumber td | For Future Implementation. |
53 | table.datenumber td#green | For Future Implementation. |
54 | table.datenumberother | For Future Implementation. |
55 | table.datenumberother tr | For Future Implementation. |
56 | table.datenumberother td | For Future Implementation. |
57 | table.datenumberother td#noborder | For Future Implementation. |
Location:
WebPagesEN/tmGifs/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmGifs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
This is the home page to the online sales. It can be the first page patrons see after the login to the online sales. It is designed to provide all options available to the patron for managing their online account, such as:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
The Forgot my password button takes the patron to a web page where they can request their password to be re-sent to them.
Alternatively, if the patron is unable to do this for any reason, the box office can initiate a password reset from the patron window |
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: How can the mail lists that appear be altered.
A: The mail lists that display in the TMmaillistQuickAdd.html page are hard coded onto the page. The page can be edited to include as many mail list are are needed. In order to add a mail list the mail list sequence number is required. Please see the following link on how to find the mail list sequence number.
____________________________________________________________
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Custom pages can be created based on the venue by duplicating the existing default page. The word Default in the page name is then replaced with the map number. The map number is located in the Map # column under Setup >> Venue Maps in Theatre Manager.
There are three TMticketSection_MapDefault pages that look very similar. The page ending in a C is for courses. The page ending in a F is for festival seating or general admission performances. The page without an additional letter is for reserved seating performances. A custom page can be created for these three types of ticket sale and made specific to the venue.
Description:
Location:
htdocs/1/WebPagesEN/tmMaps
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmMaps
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q:How can the Pricing drop down order be altered?
A: The pricing drop down is sorted in descending order based on highest price to lowest price. The promotion external description will determine the sort if there are two or more price points of the same value. Promotions sort in ascending order. For steps on how to access the sales promotion click here. Please note not all Promotions or Price Codes are available online and altering promotions will only need to be done for those options that appear online.
____________________________________________________________
Q: How do you remove the price code name from the Pricing drop down?
A: Select the Web Options tab under Setup >> Company Preferences in Theatre Manager. Remove the check from the Show Price Code option in the Permitted Ticket Printing Options section of the page. Clear the cache on the web listener for the change to take effect. For detailed steps on how to clear the cache in Theatre Manager click here.
____________________________________________________________
Q: How do you remove the Promotion from the Pricing drop down?
A: Select the Web Options tab under Setup >> Company Preferences in Theatre Manager. Remove the check from the Show Sales Promotion option in the Permitted Ticket Printing Options section of the page. Clear the cache on the web listener for the change to take effect. For detailed steps on how to clear the cache in Theatre Manager click here.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/tmMaps
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmMaps
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmMaps
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: How can the Pricing drop down order be altered?
A: The pricing drop down is sorted in descending order based on highest price to lowest price. The promotion external description will determine the sort if there are two or more price points of the same value. Promotions sort in ascending order. For steps on how to access the sales promotion click here. Please note not all Promotions or Price Codes are available online and altering promotions will only need to be done for those options that appear online.
____________________________________________________________
Q: How do you remove the price code name from the Pricing drop down?
A: Select the Web Options tab under Setup >> Company Preferences in Theatre Manager. Remove the check from the Show Price Code option in the Permitted Ticket Printing Options section of the page. Clear the cache on the web listener for the change to take effect. For detailed steps on how to clear the cache in Theatre Manager click here.
____________________________________________________________
Q: How do you remove the Promotion from the Pricing drop down?
A: Select the Web Options tab under Setup >> Company Preferences in Theatre Manager. Remove the check from the Show Sales Promotion option in the Permitted Ticket Printing Options section of the page. Clear the cache on the web listener for the change to take effect. For detailed steps on how to clear the cache in Theatre Manager click here.
____________________________________________________________
Q: How can I make the entire map display?
A: Change the selected_border value in the image reference near the bottom of the page to be 999.
____________________________________________________________
Q: How can I change the color the seats appear as on the map?
A: Change the selected_color in the image reference near the bottom of the page to the desired hex color value.
____________________________________________________________
Q: How do you change the map image at the bottom of the page so it does not display the image from within Theatre Manager?
A:Add the desired image to the tmGifs folder with the WebPages. Comment out the existing image reference line at the bottom of the page. Add a new image reference for the desired image. The full path name is not required. /tmGifs/image.jpg can be used ad this page is already referencing the WebPages through the base reference.
____________________________________________________________
Location:
WebPages/1/WebPagesEN/tmMaps
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: Can I replace the map image with an image of my own?
A: Yes, the image can be replaced. Place the desired image in the tmGifs folder. Locate the line containing the F_HTML_SEATMAP references towards the bottom of the page. Comment out the line. Add an image reference to the page calling the desired image from the tmGifs folder. Please note the reference should only require the folder name (tmGifs) and the full image name.
____________________________________________________________
Q: Can I change the default value in the drop down for number of seats to purchase?
A: Yes, you can. The default value is controlled in the Performance details. It can be altered by going to Setup >> Events and searching for the desired event. Double click on the event and select the Performance tab. Double click on the desired performance to open the Performance Detail window. Select the Web Settings tab. The Suggested Purchase Qty field determines the default value in the drop down within the online sales.
____________________________________________________________
Q: Can I increase/decrease the value in the drop down for number of seats to purchase?
A: Yes, you can. This value is controlled by the over all cart limit, event limit and performance limits.
Location:
htdocs/1/WebPagesEN/tmMaps
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: Can I replace the map image with an image of my own?
A: Yes, the image can be replaced. Place the desired image in the tmGifs folder. Locate the line containing the F_HTML_SEATMAP references towards the bottom of the page. Comment out the line. Add an image reference to the page calling the desired image from the tmGifs folder. Please note the reference should only require the folder name (tmGifs) and the full image name.
____________________________________________________________
Q: Can I change the default value in the drop down for number of seats to purchase?
A: Yes, you can. The default value is controlled in the Performance details. It can be altered by going to Setup >> Events and searching for the desired event. Double click on the event and select the Performance tab. Double click on the desired performance to open the Performance Detail window. Select the Web Settings tab. The Suggested Purchase Qty field determines the default value in the drop down within the online sales.
____________________________________________________________
Q: Can I increase/decrease the value in the drop down for number of seats to purchase?
A: Yes, you can. This value is controlled by the over all cart limit, event limit and performance limits.
Location:
htdocs/1/WebPagesEN/tmMaps
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: Can I replace the map image with an image of my own?
A: Yes, the image can be replaced. Place the desired image in the tmGifs folder. Locate the line containing the F_HTML_SEATMAP references towards the bottom of the page. Comment out the line. Add an image reference to the page calling the desired image from the tmGifs folder. Please note the reference should only require the folder name (tmGifs) and the full image name.
____________________________________________________________
Q: Can I change the default value in the drop down for number of seats to purchase?
A: Yes, you can. The default value is controlled in the Performance details. It can be altered by going to Setup >> Events and searching for the desired event. Double click on the event and select the Performance tab. Double click on the desired performance to open the Performance Detail window. Select the Web Settings tab. The Suggested Purchase Qty field determines the default value in the drop down within the online sales.
____________________________________________________________
Q: Can I increase/decrease the value in the drop down for number of seats to purchase?
A: Yes, you can. This value is controlled by the over all cart limit, event limit and performance limits.
Location:
htdocs/1/WebPagesEN/tmMaps
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
at the bottom of the page is an <img> tag that shows the actual map:
<img src="<field>F_HTML_SEATMAP"</field>&reserved_colour=007700&reserved_boundary=true&reserved_seat_border=5&format=svg" width="80%"/>
See also tmpickYourSeatScripts.html for some options that can be made regarding zoom controls on scripts that handle the maps. |
format=xxx | specifies the graphic format in which to display your seat maps on a web page.
|
||
reserved_only=false |
specifies that the map image to be drawn contains only a zoomed in sub-set of the entire map, centred around the seats that are offered to the patron. It the parameter is ignored if the map is in pick-your-own-seat mode. Values are:
|
||
reserved_boundary=true |
Indicates that a boundary is to be drawn around the seats that are offered to the user (not avaliable when map is in pick-your-own mode)
|
||
reserved_seat_border=## | Specifies the distance (in seats) from the offered seats where the reserved_boundary will be placed. Reasonable values are 2 seats around the reserved seats or 4 seats around the reserved seats | ||
reserved_boundary_color=FF0000 | Specifies the colour of the boundary drawn around the seats that are offered (if not using pick your own) | ||
reserved_boundary_width=xx | Specifies the width of the boundary drawn around the offered seats (if not using pick your own). The default size is 3/4 of the average width of seats on the map. You can make it more or less. | ||
seat_color=FF0000 |
Specifies the colour of the unsold (available) seats on the map as a RGB hex string.
i.e. FF0000 means bright red and 007700 is green |
||
selected_color=000000 | Specifies the stroke (border) color of the selected seats as a RGB hex string. These seats that a patron is picking on the reserve your seat map. | ||
reserved_color=FF0000 | Specifies the fill color of the temporarily held best seats as a RGB hex string | ||
unavailable_color=00FF00 | Specifies the fill color of the unavailable seats as a RGB hex string. Seats are unavailable if they are already sold to another patron or held for any reason. | ||
unavailable_text=X | Specifies the single character that will be used to put in seats that are not available. This over-rides the '*' that TM will put in unavailable seats. You can use any ascii character you want such as 'X'. You may even use %20 (space), which if used in conjunction with unavailable_color will provide a solid square for unavailable seats. | ||
seat_font=X | The font to use for seat labels when using mouseover to show the door/section/row/seat and seat description (depends on what the description setup is in the SCG map on the pricing map setup) | ||
seat_size=X | The size of the fonts on the seat labels | ||
seat_font_scale=X | SVG scaling factor to apply to the font size (depends on the scale used when constructing the SVG map) | ||
seat_font_load=X | "embed": base64 embedded font, "local": locally loaded font from tmVendor, "cdn": remotely loaded font from Content Delivery Network (CDN) |
There is a comment in the file about halfway down (on/around line 41-42) that looks like:
// Initialize the widget with new pan and zoom values
widget.init();
To add the parameters to the web page code and create different settings, you would edit the two lines above so that they look like:
// Initialize the widget with new pan and zoom values
widget.init( {
“pan_step_distance”: 800,
“zoom_multiple”: 0.1
} )
These values do not apply when the patron is using a touch device because the hand gestures of pinch and swipe take over and the 'controls' are hidden from the user. They only work for the controls when they are visible on a computer web page. |
|
See also tmPickYourSeatMapDisplay.html for some options that can be made regarding colouring and fonts on the actual SVG map as the user interacts with the pick your seats process. |
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Custom pages can be created for a package by duplicating the existing default page. The word Default in the page name is then replaced with the package number. The package number is located in the Package # column under Setup >> System Tables >> Packages in Theatre Manager. If this column is not visible simply right click on any of the column headers and select it. The column with then display in the list.
Description:
Questions and Answers:
Q: How do I setup a Package for online sales?
A Please see Package Setup in our online help for details on creating a new package:
____________________________________________________________
Q: How can the Availability options column be changed?
A: The text in the Availability column is located in the rowPkgTicketFestival.html page. By accessing this template the percentage level for availability can be altered. In addition the colour of the text and the wording can be altered as desired.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/tmPackages
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Custom pages can be created for a pass by duplicating the existing default page. The word Default in the page name is then replaced with the pass type number. The pass type number is located in the Type # column under Setup >> System Tables >> Member Types in Theatre Manager. If this column is not visible simply right click on any of the column headers and select it. The column with then display in the list. Please note the word Member may have been altered in the database base for the organization.
Description:
Location:
htdocs/1/WebPagesEN/tmPass
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmPass
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
If the email address exists under two patrons, the same message/process occurs and the box office will need to de-duplicate the email address in Theatre Manager before they can get an email reset.
If the patron is unable to do reset their password for any reason, the box office can initiate a password reset from the patron window. A box office reset should only be used if the patron has requested it explicitly - it sends the same email as above. |
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: Where is the limited profile option enabled?
A: In Theatre Manager click Setup >> System Preferences. Select the Mandatory Data tab. Check the desired locations in the Allow Limited Profile Patron On section.
____________________________________________________________
Q: Where are the limited profile account settings in Theatre Manager?
A: In Theatre Manager click Setup >> System Preferences. Select the Mandatory Data tab. Place a check mark next to the desired fields for limited profile in the Limited Profile Web Sales Checkout Patron Data section.
____________________________________________________________
Q: How can I hid fields that are not mandatory?
A: Fields that are not mandatory can be commented out in the tmLoginLimitedPatron.html page.
____________________________________________________________
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Location:
/WebPagesEN/tmScripts
buttonRollover.html
Description:
<SCRIPT LANGUAGE="JavaScript">
<!--
function pviiClassNew(obj, new_style) {
obj.className = new_style;
}
//-->
</SCRIPT>
Since the buttons that are contained within the tmnavButtons.html page are form inputs, they require Cascading Style Sheets in order to customize their colours and styles. This script allows the buttons to roll from one style to another.
The variables onMouseOver="pviiClassNew(this,'buttonover')" onMouseOut="pviiClassNew(this,'button')" are included in each tag for each button.
dropDownMenuFuctions.html
Description:
<script language="Javascript">
<!--
function submitForm(form, action){
//Change the name of the hidden input, hiddenSubmit, to be the name of the action we need to perform
document.getElementById(form).hiddenSubmit.name = action;
document.getElementById(form).submit();
}
//-->
</script>
This function is used to submit a form when a <!select /> list is used. The page must include this function as well as a hidden parameter within the form, TMForm. <!input type=hidden name=hiddenSubmit value="">
navSideRollover.html
Description:
<SCRIPT language="JavaScript">
<!--
function NavRollOver(oTd) {if (!oTd.contains(event.fromElement)) {oTd.bgColor="";}}
function NavRollOut(oTd) {if (!oTd.contains(event.toElement)) {oTd.bgColor="";}}
//-->
</SCRIPT>
This script allows the cells within the navSide table to roll from one colour to another, creating dynamic buttons out of table data. The variables onmouseover="NavRollOver(this)" onmouseout="NavRollOut(this)" are contained within the
pleaseWaitMessageFuction.html
Description:
<script language="JavaScript">
<!--
function process() {
var processingMessage = 'Processing...please wait...this takes a few moments';
var messageHeight = '25px';
if (navigator.appName=="Microsoft Internet Explorer") {
pleaseWait.innerHTML = processingMessage;
document.all.pleaseWait.style.height = messageHeight;
document.all.pleaseWait.style.visibility = 'visible';
}
if (navigator.appName=="Netscape") {
document.getElementById("pleaseWait").innerHTML = processingMessage;
document.getElementById("pleaseWait").style.height = messageHeight;
document.getElementById("pleaseWait").style.visibility = 'visible';
}
if (navigator.appName=="Safari") {
document.getElementById("pleaseWait").innerHTML = processingMessage;
document.getElementById("pleaseWait").style.height = messageHeight;
document.getElementById("pleaseWait").style.visibility = 'visible';
}
}
//-->
</script>
showhidediv.html
Description:
<script language="javascript">
<!--
function divdisplay(layer_ref,state) {
if (document.all) { //IS IE 4 or 5 (or 6 beta)
eval( "document.all." + layer_ref + ".style.display = " + state);
}
if (document.layers) { //IS NETSCAPE 4 or below
document.layers[layer_ref].display = state;
}
if (document.getElementById &&!document.all) {
hza = document.getElementById(layer_ref);
hza.style.display = state;
}
}
//-->
</script>
This will show or hide a div statement by name on the screen state= 'none' if you want to see it on the screen state= 'block' if you want it to be disabled from the user.
<script language="javascript">
<!--
function divvisibility(layer_ref,state) {
if (document.all) { //IS IE 4 or 5 (or 6 beta)
eval( "document.all." + layer_ref + ".style.visibility = " + state);
}
if (document.layers) { //IS NETSCAPE 4 or below
document.layers[layer_ref].visibility = state;
}
if (document.getElementById &&!document.all) {
hza = document.getElementById(layer_ref);
hza.style.visibility = state;
}
}
</script>
this will change the visibility of a div by name on the screen state= 'visible' if you want to see it on the screen state= 'hidden' if you want it to be hidden off the screen from the user
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
_gaq.push(['_setAccount', 'UA-xxxxxxx-1']);
_gaq.push(['_setDomainName', '.yourvenue.org']);
Location:
htdocs/1/WebPagesEN/tmScripts
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmScripts
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmScripts
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmScripts
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/tmScripts/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Custom pages can be created for a season package by duplicating the existing default page. The word Default in the page name is then replaced with the season package number. The season package number is located in the Seq # column under Patron Sales >> Season Reservations >> Setup Season Packages in Theatre Manager.
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: How can I edit the text at the top of the window that says "You are not currently logged in. Subscriptions can be renewed here after login." ?
A: This text is located in the rowSubRenewAnonymous.html page. Open this page and edit the text as desired.
____________________________________________________________
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
An example of the file and how it affects the new patron window is shown below. In the default file, all items are commented out (with a '#' in the first column). In the sample, 5 entries were made:
some notes:
htdocs/1/WebPagesEN/TMtemplates/
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
You can enable rounding up the cart to an even amount of your choice with a donation. The feature must first be enabled in Company Preferences -> Web Options. After that, the web page defaults to prompt the user to round up the purchase:
Note: There is a difference between:
|
In the web page text below, there is a 1 that points to an opening condition at the top of the page and the bottom of the page. That indicates to only include the round up code if the cart does not round to an even dollar. You can change that number to $5.00, $7.50, $9.33 - any number you want. If the cart balance is NOT an even multiple of that amount, then the round up option will show in the web page.
The number you pick for this value be an even multiple of the round up suggestions. Examples: Make this number
The page suggests 3 values for rounding up (you can add more). However, if you want to change them, you can see the number 2 which points to a pair of dollar amounts. You must change both, since one is the input value and the other is the button description. Those 3 values are in smaller squares:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
What to Change:
Location:
htdocs/1/WebPagesEN/tmTemplates
Able to Call Page(s):
Called By Page(s):
The tmErrorMessageInfo.html is widely included throughout web sales to display error messages to the user. It is often shown on the left side of the screen (or top of the screen in mobile views)
In the example below, a donation amount was not entered, but the "Add Donation" button was clicked. You can see how the blue alert box was generated, ultimately telling the online shopper to "Enter The Required Fields".
Description:
Customizations if donation fields have been made madatory
There are 3 fields on that are donor popup fields on the notes tab of the donation window. If these fields have been made mandatory, then you will need to find the code table value for these custom fields:
Change the value of xxx, yyy, or zzz in the input strings below to be the internal record number (Seq #) of the appropriate popup. Also, move the mandatory input field above the <!-- comment: in the file so that it becomes uncommented and active in the web page.
<INPUT NAME="DD_FLD1_FC_SEQ" TYPE=hidden id="DD_FLD1_FC_SEQ" value="xxx">
<INPUT NAME="DD_FLD2_FC_SEQ" TYPE=hidden id="DD_FLD2_FC_SEQ" value="yyy">
<INPUT NAME="DD_FLD3_FC_SEQ" TYPE=hidden id="DD_FLD3_FC_SEQ" value="zzz">
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: How does Theatre Manager assign a ticket when someone other then the person logged in is selected from the drop down as the course participant?
A: Theatre Manager will gift the course to the member of the household the ticket is purchased for. This means the ticket will appear in both the purchaser and the attendees patron records. This allows for reporting one who attended a course and who purchased a course based on criteria.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: How can the mandatory fields be changed?
A: There are two steps. The first is the Asterisk can be removed from the field within this page. The second within Theatre Manager. Click Setup >> System Preferences. Select the Mandatory Data tab. Remove the checks from the Full Profile Patron Data fields as desired.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q:
A:
____________________________________________________________
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: How can a patron change they type of email address displayed in their account window?
A: This information is controlled in the database. If a patron wished to change an email from home to work or other they will need to contact the box office to update their patron record.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: Where is the limited profile option enabled?
A: In Theatre Manager click Setup >> System Preferences. Select the Mandatory Data tab. Check the desired locations in the Allow Limited Profile Patron On section.
____________________________________________________________
Q: Where are the limited profile account settings in Theatre Manager?
A: In Theatre Manager click Setup >> System Preferences. Select the Mandatory Data tab. Place a check mark next to the desired fields for limited profile in the Limited Profile Web Sales Checkout Patron Data section.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: How can items be added to a package?
A: For details on how to add items to a package see the following online help page:
http://help.theatremanager.com/theatre-manager-online-help/adding-items-package
____________________________________________________________
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: How can the name of the package be changed?
A: In Theatre Manager go to Patron Sales >> Season Subscriptions >> Setup Season Packages. Double click on the desires season package. Alter the External Description field to display the name of the package as it should appear online.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: Where can I edit the telephone number pulled in this message?
A: The telephone number is pulled from the Theatre Manager database. It's located in the Company tab of Setup >> Company Preferences.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: How can the Availability percentages be altered?
A: The Availability options are located in the rowTicketEventAvailability.html page.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: How can the Availability percentages be altered?
A: Each option (Good, Limited, Very Limited, Sold Out) are indicated based on the percentage of seats sold within the Theatre Manager database compared to the Reporting Capacity listed for the individual performance. The percent values are listed on the page in the F_SOLD_PERCENT statements and can be altered to meet the organizations needs.
____________________________________________________________
Q:How are the colors used in the Availability column altered?
A: Each option is listed following a font color. Altering the hex code associated with the font color will change the color of the text.
____________________________________________________________
<field>pick(F_SOLD_PERCENT<80,'','Good')</field>
<field>pick(F_SOLD_PERCENT>=80&F_SOLD_PERCENT<90,'','<font color="#FF00FF">Limited</font>')</field>
<field>pick(F_SOLD_PERCENT>=90&F_SOLD_PERCENT<100,'','<font color="#FF00FF">Very Limited</font>')</field>
<field>pick(F_SOLD_PERCENT>=100,'','<font color="#FF0000">Sold Out</font>')</field></td>
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Avail = SeatsInHouse - Total Sold - Box Office Holds - Internet Holds
Sold = number sold for event + tickets held at box office _ tickets held in shopping carts
The percent of tickets available is dependant on the values of seats available and reporting quantities. The percentage is dewtermined as follows.
Description:
Questions and Answers:
Q: How can the On Sale date be altered?
A: The On Sale date is pulled from the Web Settings tab inside the Performance Detail window.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: How can the Event Image be altered?
A: The Event Image is taken from the TicketTrove/Web field in the Marketing tab of the Event setup. A new image can be dragged and dropped onto the field to update it.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: Where can the details on this page be altered?
A: The Performance name, location and notes are all pulled from within the Event Setup and can be edited in their respective fields.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: Can the On Sale date be altered?
A: Yes, the date can be altered. See the rowTicketEventCallBoxOffice.html for more details.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: Can the pricing drop down be displayed as a list?
A: Yes, the drop down can be displayed as a list. For more details please visit the Creating A Price Code List page in the online help.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: Can the pricing drop down be displayed as a list?
A: Yes, the drop down can be displayed as a list. For more details please visit the Creating A Price Code List page in the online help.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Questions and Answers:
Q: How can the series list be customized to display something other then what is pulled from the Theatre Manager database?
A: To make the events in the subscription display as "First Sun in Run @8:00pm" the following would be used:
<field>pick(mid(PB_SERIES_CODE,1,1),'','First','Second','Third','Fourth','Fifth')</field>
The following example displays the series code on the screen in the popup box:
<field>mid(PB_SERIES_CODE,3,3)</field> in run @ <field>pick(pos(mid(PB_SERIES_CODE,7,1),'ME'),'8:00','2:00','8:00')</field>pm
____________________________________________________________
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: The location in Directions to our Box Office link is incorrect, how can it be fixed?
A: The location is based on the address in the Company tab of Company Preferences within Theatre Manager. If the address appears correctly in Theatre Manager it means Google has the location wrong. Contact Google to make the necessary changes.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: How can the mandatory fields be changed?
A: In Theatre Manager click Setup >> System Preferences. Select the Mandatory Data tab. Remove the check from the options in the Limited Profile Web Sales Checkout Patron Data section for the fields that should not be mandatory.
____________________________________________________________
Q: How can I hid fields that are not mandatory?
A: Fields that are not mandatory can be commented out in this page.
____________________________________________________________
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location: htdocs/1/WebPagesEN/TMtemplates/ Able to Call Page(s): Called By Page(s): Page(s) Referenced: |
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN/TMtemplates/
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: How can the Availability options column be changed?
A: The text in the Availability column is located in the rowTicketsEventAvailability.html page. By accessing this template the percentage level for availability can be altered. In addition the colour of the text and the wording can be altered as desired.
____________________________________________________________
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: How can I export event details from this page?
A: Please click here for details on how to export event data.
____________________________________________________________
Q: What if I want to change the information to be exported from this page?
A: To details on how to alter information in an export please click here.
____________________________________________________________
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Questions and Answers:
Q: How can I export event details from this page?
A: Please click here for details on how to export event data.
____________________________________________________________
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Custom pages can be created for a venue by duplicating the existing default page. The word Default in the page name is then replaced with the Pricing Map number. The Pricing Map number is located in the Map # column under Setup >> Theatre Maps in Theatre Manager.
Description:
Location:
htdocs/1/WebPagesEN/tmVenue
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs/1/WebPagesEN
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs
Able to Call Page(s):
Called By Page(s):
A favicon (short for favorite icon) is an icon associated with a particular website or webpage. A web designer can create such an icon and install it into a website (or webpage) by several means, and most graphical web browsers will then make use of it.
Browsers that provide favicon support typically display a page's favicon in the browser's address bar and next to the page's name in a list of bookmarks. Browsers that support a tabbed document interface typically show a page's favicon next to the page's title on the tab.
There are a few ways to make the icon that we know of. Two of them are:
Make sure to verify the favicon.ico on al browsers (chrome, firefox, safari, edge, opera, and mobile safari)
Google Chrome, for example, will not display the favicon unless it is minimum of 48x48 pixels. |
WebPages and 1/WebPagesEN/tmGifs
The favicon.ico file is one of the standard pages that should be changed
Able to Call Page(s):
Called By Page(s):
Description:
Location:
htdocs
Able to Call Page(s):
Called By Page(s):
Description:
Location:
htdocs
Able to Call Page(s):
Called By Page(s):
Description:
Location:
htdocs
Able to Call Page(s):
Called By Page(s):
Description:
Location:
htdocs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs
Able to Call Page(s):
Called By Page(s):
Page(s) Referenced:
Description:
Location:
htdocs
Able to Call Page(s):
Called By Page(s):
https:// tickets. yourvenue. org [/TheatreManager/1/login[?action=0|number][&lang=XX][&tmsource=YYY]]
The meaning of the parts of the above syntax is:
Note that parameters in a URL are case sensitive. Most keyword parameters are lower case unless they refer to an actual database variable. The documentation attempts to show examples in the appropriate case. |
|
It is possible to write an interface to extract the event information and upload it your main marketing web site. For example: you can use the extracted information to publish data from TM into a custom calendar object and create 'buy now' links using the patterns above. |
|
You can only use 'GET' style links on web pages in normal format or behind pictures of buttons.
You cannot simulate these links with 'posts' due to PCI compliance requirements to use form-tokens in each post per OWASP requirements to prevent cross-site scripting |
We recommend always adding a [&tmsource=YYY] to external links to identify where the patron first entered the web sales process. Carts are tagged with the source code and it provides the most direct correlation between:
|
The general starting place for all sales is usally a link like the one above which is placed on the main web site. This link directs the patron to the Event List within the online sales. It allows them to start their online shopping experience by selecting the first performance they are interested in purchasing.
Each direct link contains a reference to login. This allows the link to bypass the login window and access the desired location. When a link to only the login window is desired, leave out any additional parameters on the URL.
Parameters are:
They are displayed on the tmTickets.html web page
To create links beside each event advertise on your web site:
Click here to purchase tickets to Event #1 - https://tickets.yourvenue.org/TheatreManager/1/login&event=51
Click here to purchase tickets to Event #2 - https://tickets.yourvenue.org/TheatreManager/1/login&event=52
Click here to purchase tickets to Event #3 - https://tickets.yourvenue.org/TheatreManager/1/login&event=58
Click here to purchase tickets to Event #4 - https://tickets.yourvenue.org/TheatreManager/1/login&event=62
In the above examples the event value is defined by Theatre Manager as the unique event number for each different event. The event number is found by:
You can add other parameters to the event list such as:
Note: years are in yyyy format, Months are 0 to 12, genre # is from code tables, venue # is from list of venues. eg:
https://tickets.yourvenue.org/TheatreManager/1/login&event=51&year=2016&month&9&venue=5 |
This column in the Event List shows the unique sequence number for each item in the list. Use the Event # to replace the "xx" in the link above.
Parameters are:
This column displays the unique performance number for each performance of the Event. Replace the "xx" in the link above with the desired performance number to create a direct link to the performance.
Parameters:
This is the unique number representing the genera. It can be used to replace the "xx" in the link above.
The link above will go directly to the best available seats to the performance named by bestavail (by passing the event and performance selection).
Each of the items in the link (except bestavail) are optional | |
You can also use this to quickly select a number of general admission tickets for purchase |
You can put any combination of the parameters together that you wish. if the system cannot find seats based on your combination of selections, you'll be told.
The simplest form of the url to get any seats anywhere in the venue is
An example to allow pick your own without reserving seats first
This column displays the unique performance number for each performance of the Event. Replace the "xx" in the link above with the desired performance number to create a direct link to the performance.
This link will take the patron to your web site and, after they log in, will show them your future tickets. At that time, they can print those which allow print at home.
The example below shows that the future tickets web page looks like when a customer logs in online. They can see their events with:
Printable HTML: https://tickets.yourvenue.org/TheatreManager/1/login?futureticketsprint&[ cart=xxx] | [&order=yyyy]
PDF: https://tickets.yourvenue.org/TheatreManager/1/login?futureticketspdf&[ cart=xxx] | [&order=yyyy]
Theatre Manager supports print at home tickets in either bar or QR code format which means you can send URL's to the user via email to get ticket printed. Theatre Manager does the one for the cart automatically on the confirmation letter during the sales process
By adding options to the URL above, you can print tickets for
Note: if the patron owning the tickets is:
If you want to print a test PDF ticket to see what it looks like, use the URL(s) below
Printable HTML: https://tickets.yourvenue.org/TheatreManager/1/login?futureticketsprint&test=1
PDF content as HTML: https://tickets.yourvenue.org/TheatreManager/1/login?futureticketspdf&test=1&html=1
IF you are trying to make tickets that print on ticket printers, please see the documentation about ticket faces for ticket printers. |
To create links to show only events relating to a pre advertise on your web site:
Click here to purchase tickets to Event #1 - https://tickets.yourvenue.org/TheatreManager/1/login?event=51
Click here to purchase tickets to Event #2 - https://tickets.yourvenue.org/TheatreManager/1/login?event=52
Click here to purchase tickets to Event #3 - https://tickets.yourvenue.org/TheatreManager/1/login?event=58
Click here to purchase tickets to Event #4 - https://tickets.yourvenue.org/TheatreManager/1/login?event=62
In the above examples the event value is defined by Theatre Manager as the unique event number for each different event. The event number is found by:
This column in the Event List shows the unique sequence number for each item in the list. Use the Event # to replace the "xx" in the link above.
Other Parameters
The above can be used to create a direct link to a specific list of events (or date range of events) where a customized search is required. The options below are examples of search strings that can be used to replace the "XXXXXX" in the link above. Do NOT place quotes around the entire search parameter. Example:
An Example link directing patrons to TWO (2) specific events would appear like:
Refer to comments within WebPages/1/WebPages/TMTickets.html for more examples on searching for performances within the Ticketing Page.
To find the Event Sequence #:
The Event List window will open.
This is the unique sequence number for the event and can be used when creating a P_SEQ link.
To find the Performance Sequence #:
This number can be used with creating a link that references PB_SEQ.
To find the Venue Sequence #:
The Venue # can be used to create a link with a TM_SEQ reference.
The link above allow a reference to the Performance Flag within the Performance and will only display the Performances with the matching results within the field. The reference within the Performance Flag field will replace the A in the link. To locate or alter the Performance Flag follow the steps below:
This field will contain the value to replace the A from the link above. If a value is not present one can be added. Multiple values can be referenced at one time by separating the references with commas and using the 'in' clause.
For example: PB_PERF_FLAG in('A','B','C','D')
The above link uses the Sequence number associated with the Performance Type to create a direct link to select Performances. By using this link a defined list of performances can be grouped together and displayed for purchased. To locate the Sequence number references in the link follow the steps below:
This column will contain the value to replace the XX in the link above. Multiple values can be referenced at one time by separating multiple XX references with commas and defining the XX with each unique sequence number.
To locate or alter the Performance Type for a select Performance follow the steps below:
This field will contain the value referenced by the Performance. The value can be changed using the drop down. The link above will reference all performances where the value within this field matches the sequence number from the link.
You can also use many of the link that are ticket related if you provide the event # for the course
This link will take the patron to a select list of Performances based on the Sales Method for the Performance. The "xx" represents the Performance Sales Method sequence value from within Theatre Manager.
Sequence # | Performance Sales Method |
1 | Reserved Performances |
2 | Festival Seating Performances |
3 | Inventory |
6 | Courses |
This link will take the a staff member or volunteer with permission to manage events online to the 'manage event' page in the online sales. The "xx" represents the event # from within Theatre Manager. If the event number is zero, then the employee/volunteer will see a list of all events that they can manage.
Permission to manage an event online is occurs when three things are true:
This link displays the tmEventManagement.html web page. Once the Instructor is on this page, they can:
This URL takes a user to a list of all the campaigns that are available online as per the image below.
If no category is used, the above link will direct a patron to the Donation Campaign Page and show all donation campaigns in all categories, like the HTML page below, from which they can pick.
A sample is shown at the bottom of the help page.
General Parameters
You can specify one or more categories in the URL and only those categories will be shown. In this case, the category numbers must be the same as the code table entry number in the Donation Campaign Code Table shown above. Icons are entered on the Description Tab in Donation Campaign setup.
You might use this to show capital campaign or individual gifts on a separate web page.
You can also Link to specific donations if you wish.
This link will take the patron to the donation page in the online sales. It will show a fillable form where he patron can make changes to their choices, change amounts and then add the donation to their shopping cart.
NOTE: the normal route taken by the web server after adding the donation is to go to the shopping cart window. You can alter that destination in a form by using the hidden param below within your form
<input type="hidden" name="param" value="altbtn=btnCheckout" /> altbtn=btnCheckout can be substituted for other web pages, so you could, for example, take the patron to the gift certificate page. |
|
If you would like to show progress to a target, then edit the Statistics Tab on the donation campaign window and click the show on internet (meaning show the progress on internet) |
The Donation List window will populate with Donation Campaigns. Replace the "xx" in the link above with the appropriate donation sequence number to create a direct link to the donation.
For more information on the Donation List widow click here.
[&DD_FLD1_FC_SEQ=pp][& DD_FLD2_FC_SEQ=qq][& DD_FLD3_FC_SEQ =rr][&frequency=0][¶m=altbtn=btnCheckout][&tmsource=zzzzz]
This link allows you to add a donation to the shopping cart with minimal interaction. It means you can put it anywhere on any web page. The user does not get any choices. If you wish choices like Donate $10 or Donate $50, you will need to put multiple buttons on the page.
This URL supports quickly adding a donation to a cart from ANY web page including:
|
In the image above, the URL to quickly add a donation can be on any page. If it contains the minimum data needed, the diagram shows the flow that occurs for regular patron checkout and for guest checkout.
The following parameters can be added after the tickets.yourvenue.org/TheatreManager/1/login?
Use the param features if you want the patron to go directly to the checkout page. Patrons will:
Note: If any donor popup is mandatory in company preferences, you must specify this parameter and a value for it in the URL. |
Values of frequency are:
In this example, there are 4 actual links:
The links (above) are part of this sample fundraising form letter created in Theatre Manager with the purpose of emailing to ask people to donate. It is based on patrons so that I could use a mail list to determine the people to send to - meaning it could be volunteers plus donors in past year, plus ticket buyers with cancelled shows, etc.
The general steps to create the letter were:
NOTE: make sure to put the URL into the right field
It looks like a regular email sent to people. Theatre Manager tracks
In the sample letter, I clicked on both buttons to show the effect and logged in. Because I clicked on them one at a time, both donations got added to a shopping cart as per the image below. The buttons below are included and active in case you want to try them.
This illustrates an e-blast with a one button donation ask for specific amounts. All the user would need to do is log in (or create an anonymous profile that you can merge later) and pay. A donation can be done in 3 button clicks.
The example code is below the image
While the code below could be placed anywhere in an appropriate web page file in Theatre Managers 'WePages' folder, the following was added to TMtemplates/tmTicketCustomPatronInstructions.html as an existing convenient way to place buttons at the top of the event list. Other good places to add donation buttons are:
The TMtemplates/tmTicketCustomPatronInstructions.html file is used in all event lists and normally has nothing in it.
<div class="alert alert-warning fade in"> <!--#include virtual="TMtemplates/tmMessageDismiss.html" --> Please consider a donation to the theatre during this time of need. All donations are tax deductible. <br/> <br/> <a class="btn btn-info btn-sm" href="<field>F_HTML_FIREWALL</field>login?donationquick=1&amount=50.00¶m=altbtn=btnCheckout&tmsource=sometag"> <i class="fa fa-usd"> </i> 50 one time </a> <a class="btn btn-primary btn-sm" href="<field>F_HTML_FIREWALL</field>login?donationquick=1&amount=250.00¶m=altbtn=btnCheckout&tmsource=sometag"> <i class="fa fa-usd"> </i> 250 one time </a> <a class="btn btn-success btn-sm" href="<field>F_HTML_FIREWALL</field>login?donationquick=1&amount=10.00¶m=altbtn=btnCheckout&frequency=1&has tmsource=sometag"> <i class="fa fa-usd"> </i> 10 a month - I'd like to give a little for a little longer </a> </div> |
Three sample links are shown below that you can click on followed by the example web page in yellow.
Note: the web page looks very plain because all stylesheet information has been removed for clarity. You may need to add your own style sheets to create buttons like the example code within Theatre Managers event list |
The code below is a complete web page - including the head and body tags. You would only want to copy the links to place them into any of your existing web code such as facebook or wordpess sites
<!DOCTYPE html> <html lang="en"> <head> <title> Asking for a donation on a simple web page </title> </head> <body> Sample web page snippet asking for a donation. The links below have not been enhanced with any stylesheet themes <br/> <a href="https:∕∕tickets.artsman.com/TheatreManager/1/login?donationquick=1&amount=50.00¶m=altbtn=btnCheckout&morning&tmsource=mysourcetag" target="_blank"> Donate $50 one time </a> <br/> <a href="https:∕∕tickets.artsman.com/TheatreManager/1/login?donationquick=1&amount=250.00¶m=altbtn=btnCheckout&tmsource=mysourcetag" target="_blank"> Donate $250 one time </a> <br/> <a href="https:∕∕tickets.artsman.com/TheatreManager/1/login?donationquick=1&amount=10.00¶m=altbtn=btnCheckout&frequency=1&tmsource=mysourcetag" target="_blank"> Donate $10 a month - a little for a lot </a> </body> </html> |
The link above will take the patron directly to the package purchase window in the online sales.
Parameters:
The Package List window will open.
For more information on the Package List window, click here.
The Package # column will be the first column in the list. Replace the "xx" in the link above with the appropriate package number to create a link to the package.
Parameters
The Subscription number is in the far left column labeled Seq #. It can be used to replace the "xx" in the link above.
They are displayed on the tmpass.html web page
If no category is used, the above link will direct a patron to the Pass/Gift Certificate merchandise page and show all passes in all categories. The patron will see a list of all passes, like the HTML page below, from which they can pick.
A sample is shown at the bottom of the help page.
General Parameters
You can specify one or more categories in the URL and only those categories will be shown. In this case, the category numbers must be the same as the code table entry number in the Gift Certificate Categories Code Table shown to the right. Icons are entered on the Marketing Tab in Gift Certificate setup.
You might use this to show upcoming subscription passes for next year on a separate page, or gift certificates on a separate page.
You can also Link to specific pass if you wish.
The above link will direct a patron to the specific pass or gift certificate, ready to buy it.
or
The above link will direct a patron to the pass/Gift Certificate/merchandise page. The patron can then use the drop down options to choose the type of Pass, Gift Certificate or Membership they wish to purchase.
You can also have a link to one (or more) groupings (categories) of passes/memberships.
Other Parameters
The above link will direct a patron to the pass/Gift Certificate page that shows the current balance on any passes that still have a balance that can be used. The patron will need to log in first, if they are not currently logged in.
Other Parameters
Merchandise and Rentals are resources and found in the same location with Theatre Manager. If your organization offers both options online the ?merchandise link will display only those items where the Sales Method is set to For Sale.
For further definition of merchandise items you may wish to use &group=XX as an additional parameter to access resources based on their Resource Group. Each resource requires a Resource Group at the time of setup. To determine the value of XX you'll need to locate the Facility Resource Group number.
Merchandise are resources where the sales method is set to FOR SALE |
The Facility Resource Group number is in the far left column labelled Seq #. It can be used to replace the "xx" in the example link above.
Rentals and Merchandise are resources found in the same location with Theatre Manager. If your organization offers both options online the ?rental link will display only those items where the Sales Method is set to Rental.
For further definition of rental items you may wish to use &group=XX as an additional parameter to access resources based on their Resource Group. Each resource requires a Resource Group at the time of setup. To determine the value of XX you'll need to locate the Facility Resource Group number.
Merchandise are resources where the sales method is set to RENTAL |
The Facility Resource Group number is in the far left column labelled Seq #. It can be used to replace the "xx" in the example link above.
Resources can consist of a combination of Resources, Rentals and Merchandise. All of these options are setup in the same location with Theatre Manager. By using the ?resources link a full list of all Rentals and For Sale items, as defined in the Pricing & Inventory tab of the resource setup, will appear online.
For further definition of resource items you may wish to use &group=XX as an additional parameter to access resources based on their Resource Group. Each resource requires a Resource Group at the time of setup. To determine the value of XX you'll need to locate the Facility Resource Group number.
Merchandise are resources where the sales method is either RENTAL or FOR SALE |
The Facility Resource Group number is in the far left column labelled Seq #. It can be used to replace the "xx" in the example link above.
The link above will go directly to the resource or inventory item named by resource (by providing the resource/inventory item #).
Each of the items in the link (except resource) are optional | |
You can also use this to quickly select a number of merchandise or resources for purchase |
You can put any combination of the parameters together that you wish. if the system cannot find the resource based on your combination of selections, you'll be told.
The link above will ADD the resource or inventory item named by resource (by providing in the resource/inventory item).
Each of the items in the link (except resourcequick) are optional | |
You can also use this to quickly select a number of merchandise or resources for purchase |
You can put any combination of the parameters together that you wish. if the system cannot find the resource based on your combination of selections, you'll be told.
The image below shows what a resources if you were adding it normally. resourecequick bypasses this window and adds the item directly to the cart - as if it had filled in the fields that you see on the image. |
Coupon
Parameters:
Example of Pre-Access Codes added to a cart and displays all valid events for the pre-access
There are two aliases for 'redirect' that can be used interchangeably:
The above links will auto add a pre-access or coupon code for a patron.
The above link can be used when a venue has different type of events and a link is required to directly sell any performance in that venue.
Parameters:
This is the unique sequence number representing the map. It can be used to replace the "xx" in the link above.
The above link can be used when you wish to send an email to a patron to have them pay for the order online.
Parameters:
if you add the order number using order=xxx then the specific order will be automatically added to the cart. It means you can put a link in an email merge to pay for a specific order if you want.
This will land the patron on the Order Balance web page (after they log in) so that they can select the order to pay online.
The Calendar displays upcoming Performances and Classes available for purchase. Patrons can choose to download an existing copy of the calendar as it appears today in an ICS file format or subscribe to the calendar which will allow for automatic updates to their iCal, Outlook or Google calendar program.
This link will allow a patron to subscribe to the mail lists indicated by simply adding their first name, last name and email address.
The Mail Lists that are visible in this web page are those with the following characteristics:
You can use this link to allow people to see which mail lists they belong to. Since they have to log in, double opt in is not applicable, but can be used.
This will take the patron directly to the Mail List page within the online sales. Patrons can choose to subscribe and unsubscribe to Mail Lists after they have logged into the online sales.
The Mail Lists that are visible in this web page are those with the following characteristics:
You can access the images on the web site for events or venues. They are done in a heirarchy, so that if you ask for the event image and it is not available, you'll get the venue image. If that is not available, you'll get the outlet image.
While these web pages contain all the functionality, many venues like to change the look of the web pages to 'brand' the pages in their own image. To brand a site, the recommended steps are below. We recommend making a minimum of changes to the pages as it means that you can upgrade pages when we add future functionality quite easily. This is possible because we have tried to isolate the required changes to a few files at most. In practice, this works out very well.
The general approach to branding the web site is:
If you do want to change a page, copy that page into the same location in the WebPagesEN folder and make the changes to the COPY. Theatre Manager will reference the WebPagesEN folder first when looking for a web page then the default pages from within the TMServer if it finds none. Try to minimize changes to pages as it affects ability to upgrade pages later on. |
Before anything can be changed, you need to know where the web pages are. They are always installed in the WebPages folder of the Tm Web server that is set up when Theatre Manager is first installed. If you need remote access to this folder, we suggest using a GIT checkin/checkout process to edit pages locally and push the pages to your web server..
The Web Sales Modules is comprised of a number of different pages, such as, the content pages, login page, shopping cart and checkout pages to name a few. To change the pages to be specific to your venue, your web developer/designer will need to edit the appropriate pages.
The links on the side navigation beginning here, will guide you through the pages in the Web Sales Module and give you detailed information on how each web page is used by module.
You can alter the source code of the Web Sales pages to suit your needs. However, if you do, Arts Management Systems is not responsible for supporting or debugging errors that may occur.
Please ensure you have a backup of the web pages prior to make changes. |
Throughout this section of the help, you will see
Programmer's Note: These notes provide the web developer/designer with further information on how to customize the web pages. |
Programmer's Note: Remember that changing the name of any of the html files that come with the Web Sales Module will require you to check that any pages that link to the new renamed page has been revised to accomodate for that change. Otherwise you will have broken links or errors on your pages |
The other caveats:
Other than those general rules, open any page with your favorite page editor and make changes as you like. The pages that we find venues change most often are:
The fastest and best way to completely alter the look of the web pages is to change the theme using a customization tool like Bootstrap Live Customizer.
This can be done in minutes |
Alternatively the custom.css file can be altered to define individual element within the pages.
The web pages for the ticketing site:
The web page file structure consists of a WebPagesEN folder containing only those pages previously customized. A full set of the default pages are can be download from
https://gitlab.artsman.com/_public/tmresponsivewebpages.
When making edits to existing pages the latest default page should be downloaded and copied to the corresponding page within the local folder.
The logo at the top of the ticketing site in the navigation bar is a company logo. The quickest way to update the image would be to create a tmCompanyLogo.jpg file and place it in the /WebPagesEN/tmGifs folder. This will replace the default image.
Alternatively an image can be added to the /WebPagesEN/tmGifs folder and the tmnavButtons.html page (located in the /WebPagesEN/TMtemplages folder) can be updated with the image name.
Other commonly edited web pages are:
In the default stylePages.css, the buttons within the online sales will appear red when using an Internet Explorer browser. For some clients, this works with their default pages. Others would prefer not to have the buttons appear in red. Please see the steps below on how to alter the buttons.
filter:progid:DXiMageTransform.microsoft.Gradient(GradientType=0,StartColorStr='#ff800000',EndColorStr='#ff333333');
GitHub Desktop is one of many third party tools that can be used for accessing web pages hosted on the Artsman Cloud in a git repository. Git is a distributed version-control system. It's great at tracking who made changes to what and when.
To setup access to your specific company web pages via Git, email support@artsman.com with the full name of the employee who will be allowed to make changes to your pages, and their company email address. For security and tracking purposes, only employee specific email addresses are accepted, like "johnsmith@example.com".
To use GitHub Desktop simply download and install the program. Clone the git repository pages to your computer for editing locally. After edits are made Commit and Push to the master branch of the repository directly through GitHub Desktop.
Only previously customized web pages will appear in the Artsman Cloud git repository for your organization. If the page you wish to edit does not appear on your local machine it may not have previously been edited. You'll need to download the default responsive pages and move that desired page to the corresponding folder on your local machine before making edits. Your repository should only contain customized web pages.
Remember to download the latest responsive pages each time before you begin making edits. |
The GitLab Repository URL is needed when cloning the repository locally. The steps below should only need to be done once per repository during the initial setup.
Login information is requested through the Artsman Support team. If you have not previously been provided access please email the support team. When access is granted an email will be sent directly from GitLab to your email with steps for setting a password and logging in.
This will copy the URL for the repository to your computers clipboard making it ready to paste into GitHub Desktop for cloning.
You may be prompted to enter the your login credentials for the GitLab repository.
The web pages are now copied to your local computer for editing. When editing new pages always make sure to use the latest version of the responsive pages to ensure the page you are working on contains all the latest features.
It's important to always start any web page editing by Pulling changes from the existing repository. This ensures any changes made that are not currently in your local repository are pulled to your machine before you begin making edits.
Missing the step of Pulling means you may need to Rebase before completing the process of adding your changes to the repository. Rebasing a repository with conflicting changes requires a deeper understanding of git. For further information please see GitHub online documentation for assistance.
GitHub Desktop is great at picking up when new pages are available in a repository. Changes are often detected within moments of opening the program and notifications can be seen in the main display.
Any changes previously waiting to be pulled will now be in the folder on your local machine. The web pages are ready to be edited.
Once web pages have been editing locally they need to be Committed before they are Pushed to the Artsman cloud repository. This allows you to add select changes while continuing to make edits.
These changes are now ready to be pushed to the repository.
Pushing changes moves the pages up to the Artsman git repository. Only pages that have been Committed can be Pushed. Once the pages have been pushed they run through a series of tests before they are available to be accessed by the web listener. To see edits following the test process you many need to clear the cache on the web listener.
Changes have now been added to the online repository. Most changes will appear online within moments of editing. Items that are more deeply cached may require a clear cache and occasionally a restart of the Theatre Manager server. If you do not see your changes after clear the cache in Theatre Manager please contact the support team assistance.
The Download button can also be used to save the variables.less file, which can be used in the future to further change the theme in the Bootstrap Live Customizer
<link href="tmScripts/theme/css/theme.min.css" rel="stylesheet" />
If your web pages are hosted on Artsman Cloud and you do not have access to the git repository, please send the customized bootstrap.min.css and variables.less file to support and we'll put the customized theme in place for you. |
This page is under construction.
The kinds of changes that fall into this category and involve no web design work are:
These kinds of changes are simple text changes to various data fields within Theatre Manager or changes to options in the Company Preferences area. Most do not require any changes by a web designer as they are daily operational aspects of TM.
It is possible to add some html tags to some of the large descriptive fields like the event description. If there are html tags in those fields, you can have additional control over the display of text. eg, you can include <b><em><a><img> type tags very easily to create a desired look without changing pages. |
There are three options available for ticket handling in online sales.
The options available to the patron depend on the organization's policies. To set these options go to Setup >> Company Preferences and select the Web Options tab.
The Mail to Patron option, when checked, displays a button in the TMcart.html, TMcheckoutNoPayment.html and TMcheckout.html pages. When a patron clicks the button, the Order Ticket Mailed Status changes to 'Patron Wants Tickets Mailed.' This criteria can be used to batch print the tickets at the box office.
When the 'Mail to Patron' button is checked, a Mail Fee from the Fee Tables must be selected. The fee does not have to have a dollar value associated with it but is mandatory for the setup.
If the box is not checked, the button providing the option to have tickets mailed will not be visible. Removing the check from this box does not mean the default text on the checkout page regarding mailing options changes. The TMcheckout.html page may need to be altered to exclude the mailing details if an organization does not mail tickets.
If a patron selects mailing of tickets BUT there is a sales promotion that requires a coupon in the shopping cart, the mail tickets to patron setting is ignored and replaced by HOLD @ WILLCALL FOR COUPON. This can be changed in the sales promotion edits tab |
When the 'Print At Home' option is checked the patron can choose to check a box in the online sales process indicating they wish to print thier own tickets. This provides the option for the organization to allow patrons to print bar codes for some events and not others.
Checking the 'Print At Home' option will allow a bar code to be printed for performances where 'Print at home' is enabled at the Event or Performance level. This feature allows for later scanning when the patron arrives at the venue. There are two choices for bar code format:
If a patron chooses to print their tickets at home, the Ticket Printed field is updated with the date and time of the completed cart. The tickets are marked as printed in Theatre Manager. When a batch print of unprinted tickets is performed, the tickets printed at home will not be included.
If the options to mail tickets or print them at home are not enabled the default option is to 'Hold for Will Call.' This insinuates the patron will be picking up their own tickets. By default, if the 'Mail to Patron' and 'Print at Home' options are enabled but the patron does not choose either, the Order Status is set to 'Hold for Will Call.' 'Hold for Will Call' simply means there are no special handling rules for the tickets.
When the 'Hold for Will Call' box is checked, it allows the patron to choose not to print thier tickets or have them mailed. In some cases an organization may insist the patron' tickets not be held at will call. Unchecking the box forces the patron to choose between printing their tickets or having them mailed. This often happens when there will not be staff to manage ticket pick-ups at the venue prior to the performance.
There is a hierarchy to how the Permitted E-Ticket Delivery Options work. When the options listed are checked, they also become available for the Event and for the Performance.
To turn on the print at home option for a selected event or performance, you complete the following steps:
Click here for more information on the Web Options tab.
Click here for more information on finding events.
The confirmation dialog telling you "Turning on the print at home feature will update the ticket print options amd set this to be the same for all performances if you save the record. You can then individually edit a performance to customize settings if you wish.
Tickets for the Event and all of the performances can now be printed at home.
To turn OFF Print at Home for selected performances, you complete the following steps:
Many of our clients engage the services of, or have in-house, a web designer who prefers to customize the online ticketing web site themselves. Arts Management Systems is often asked how to set it up so that web designers can work independently and off site in a testing environment and see the effects of changes to the online ticketing web pages before making it live. The following outlines the steps to take to create a Web Designer Testing Environment:
Step #1: Duplicate the Current Web Templates
The directory for all the online web pages is located on the Web Server and depending on the platform:
AMS Cloud or GIT users need to do somerthing similar:
|
Step #2: Setup Remote Access
Step #3: Testing Changes in a Web Browser.
The TM Server is designed to be multi language. It comes provided with English (WebPagesEN) and French (WebPagesFR). To use the test pages, you just need to 'switch languages' using
https://tickets.myserver.com/TheatreManager/1/online&event=0&lang=TS |
where tickets.myserver.com is replaced with your ticket subdomain.
https://tickets.myserver.com/TheatreManager/1/online&event=0&lang=EN |
Step #4: Place the newly edited files.
When you like some or all of the pages you have changed in WebPagesTS
https://tickets.myserver.com/TheatreManager/1/online&event=0&lang=EN |
Each client is provided the standard web pages designed by Arts Management Systems. Some organizations choose to make minor adjustments to they style sheets in order to reflect their default homepage. Others choose a more customized design of the pages. Examples of customized pages can be found on the Sample Web Sites page.
Below you will find some examples other sites have used in their customization process. These examples can be used to create a more personal feel to your web site. If you are not familiar with html we would strongly recommend contacting your web designer for assistance.
There are many naming conventions for adding a merchandise button to the online ticketing site. Some organizations add a Shop button, others a Merchandise button and others a Rental button. The name of the button depends on the use of the resource module in Theatre Manager and the content to be accessed. The icon for the button may also vary depending on the buttons use. Options for the icon can be found on the Font Awesome website. We encourage you to use the naming convention and icon that work best for your organization.
The page tmnavButton.html is located in the WebPagesEN/TMtemplates folder.
<li> <a href="<field>F_HTML_FIREWALL</field>login?merchandise=0"> <i class="fa fa-shopping-cart"> </i> Merchandise </a> </li>
The recommended location would be after the Tickets, Gift Certificates and Donation buttons and before the Subscription button.
Or any other needs your Marketing and Development Department can identify.
This process includes web page editing. If you have a web designer on hand, they can perform these edits. If you wish to contract with Arts Management Systems to perform these or any customizations for you, please contact the Support Team at support@artsman.com
Note: There is a difference between:
|
OPTIONAL- An include directive can be added to any of these pages:
<field>pick(F_DONATION_ALLOWED,'<!-- comment: based on setting in company preferences to show suggested donation','')</field>
There are fields in the Notes tab of a Donation that can be added to the tmDonationHiddenFields.html so they appear on the TMdonation.html page in order to collect more details about the donation. The example below accesses the Donor#4 field. This is a text field. The patron can type information into the field within the online sales and the details will populate in the Donor#4 field in Theatre Manager once the Order is complete.
This process includes web page editing. If you have a web designer on hand, they can perform these edits. If you wish to contract with Arts Management Systems to perform these or any customizations for you, please contact the Support Team at support@artsman.com
<div class="form-group">
This web page provides instructions for:
The easiest way to update the header and/or footer for a print at home ticket is to create new files and place them into the WebPagesEN >> tmGifs folder.
In general, the width of each of the images should remain around 700 pixels. The height of the images can vary as long a the total height of both images causes the print at home ticket to remain on one page. You could, for example, make the top image 50 pixels high and use the remaining pixels in the lower area.
The sample pages were crated with conservative heights. You could probably get away with a total of 400 pixels or more in height between the header and footer.
If you want to change the header or footer for a single event, you can create a web page that over-rides the header and/or footer. This allows you to have:
As an example, let say you want to change the header (and/or) footer for only event 109 (See No Evil).
Changing the Header |
|
||
Changing the Footer |
|
If you want to change the header or footer for a single performance within the event, you can create a web page that overrides the header and/or footer. This allows you to have:
As an example, let say you want to change the header (and/or) footer for only event 443.
Changing the Header |
|
||
Changing the Footer |
|
Print at home tickets must be enabled in company preferences and for specific events before a patron can print them. | |
In the instructions below, the names of images and files are case sensitive. Please make sure they match exactly. |
The lines below are an example of how to create a button that will apply a specific Coupon Code to the online cart. This button can be added to any page within the online sales. It would most commonly appear on the TMtickets.html page or the TMcart.html page.
This process includes web page editing. If you have a web designer on hand, they can perform these edits. If you wish to contract with Arts Management Systems to perform these or any customizations for you, please contact the Support Team at support@artsman.com
<form action="<field>F_HTML_FIREWALL</field>online" METHOD=POST>
The Event Buy options can be edited and displayed in two different ways. The two options for the 'Buy' button when purchasing Events online are detailed below. We have the conventional 'Buy/Reserve' option;
There is also the option to change that display to show both the Date and Time within the Buy Button itself, option example below.
Options for editing the Buy button can be found by accessing and editing the rowTicketEventName.html.
If you want to have a 'calendar' like date on the right of the list of Events, then uncomment rowTicketEventCalendarButton.html, and comment rowTicketEventCalendarDate.html.
You will need to edit tmScripts/styleCal.html
and either uncomment/comment the include for the customCal.css to match what you did above.
The lines below are an example of a button that will add a specific member type to the cart with a fixed value and quantity. This button can be added to any page within the online sales. It would most commonly appear on the TMpass.html page or the TMcart.html page.
This process includes web page editing. If you have a web designer on hand, they can perform these edits. If you wish to contract with Arts Management Systems to perform these or any customizations for you, please contact the Support Team at support@artsman.com
<div align="right">
The html code below will provide a single option for pricing rather the the price code drop down list that is currently a part of the online sale pages. This text most commonly would effect the TMticketsPrice_MapDefault.html and TMsubscriptionPriceMapDefault.html pages.
<input name=SC_DESCRIPTION type=hidden value="<field>F_HTML_PROMOTIONS_LIST.1.SC_SEQ</field>>
<field>F_HTML_PROMOTIONS_LIST.1.PC_SEQ</field>
<field>F_HTML_PROMOTIONS_LIST.1.SCD_ORIGINAL_SC_SEQ</field>
<field>F_HTML_PROMOTIONS_LIST.1.SCD_ORIGINAL_PRICE_CODE</field>
<field>F_HTML_PROMOTIONS_LIST.1.SCD_SAVINGS</field>
<field>F_HTML_SELECTED</field>
<field>pick(D_WEB_SHOW_PROMOTION,'',con(F_HTML_PROMOTIONS_LIST.1.SC_DESCRIPTION,' '))</field>
<field>pick(D_WEB_SHOW_PRICE_CODE,'',con(F_HTML_PROMOTIONS_LIST.1.PC_DESCRIPTION,' '))</field><field>F_HTML_PROMOTIONS_LIST.1.PS_TOTAL_COST</field>
When setting up an event, that is not a Course or Reserved seating performance, the General Admission (Festival Seating) Sales Method is used. This allows for flexibility in capacity. It is commonly used for Live Stream or Pre Recorded videos. This poses a challenge when purchasing online as the default web pages display arrival notes that do not apply to Live events.
Hiding these notes requires created a customized web page referencing the Map Sequence number from Theatre Manager and the Sales Method. Below are the steps for removing the box containing the text from the page. Alternatively, a custom page containing notes specific to the streaming event could be created and added in place of the existing general admission arrival notes.
The steps below assume a basic understand of HTML and web page editing. Please contact your web designer should you need assistance with completing web page edits. |
Click here for steps on how to access the Venue List window.
The page containing the arrival notes is the TMticketsSection_MapDefaultf.html page located in the tmMaps folder. The " f " at the end of the page name indicates the Festival Seating page. This is the page that requires customization.
The final step is to edit the web page. The steps below outline how to remove the notes from the page.
If you have any mandatory fields set for donations (such as "Why Patron Gave" or other field on the Notes tab), then your online donors will need to have this field filled in for them automatically. Otherwise, they will not be able to donate online as the database will require the field, and the patron has no way of entering it. To determine which fields may be mandatory, go to:
To correct this for online sales, you have two options:
Option 1: Editing the web page (recommended)
This process includes web page editing. If you have a web designer on hand, they can perform these edits. If you wish to contract with Arts Management Systems to perform these or any customizations for you, please contact the Support Team at support@artsman.com
If you still wish those fields to be mandatory for the Box Office or Development Department, then you will need to make a slight adjustment to the tmDonationHiddenFields.html web page.
The process starts by obtaining a Sequence Value from Theatre Manager
Now you will need to go edit the tmDonationHiddenFields.html web page, located in the TMtemplates folder.
Option 2: A global change
You can make the field non-mandatory. This will make the field not required for both Web Sales and in the Box Office/Development Office. To make this global change:
You will see a section for "Mandatory Fields on Donor Window" as noted above.
There are two groups of buttons:
The menu Navigation buttons reside within the TMtemplates/tmnavButtons.html file, and are dynamically imported into each page via the <include> command. The command looks like:
<!--#include virtual="TMtemplates/tmnavButtons.html" -->
and creates buttons that look like:
Since buttons are subject to style changes, we are able to use the Bootstrap Style Sheets to make them fit whatever concept your site incorporates, such as:
These buttons default to the bootstrap stylesheets for the 'nav navbar-nav' class.and can be enhanced in the custom.css style sheet
Data Submit/Navigation Buttons
The other buttons in each page serve different purposes by sending data to the database. These buttons work exactly the same way as the menu buttons only they allow Theatre Manager to receive the data that has been entered into the page and then load a new page page based on that data. An example of this would be to click on the Buy Tickets button which will take the patron to the TMtickets.html page allowing you to select a performance to buy tickets for. The Data Submit buttons will look like the following (although the words may vary)
The Data Submit buttons default to the stylesheets for the 'btn' class and can be modified with 'btn-success', 'btn-warning', 'btn-info' and others such as 'btn-small'
Buttons Commands
This is a list of the button commands that Theatre Manager requires. They are entered as the name="xxx" portion of each input tag.
These commands cannot be altered.
When purchasing a ticket online a link can be added offering the patron an opportunity to see the view from their selected seats prior to adding tickets to their cart. This option requires some setup in order to work successfully online.
Once the setup is in place, the seat view button will become available. Clicking the button will open a new tab in the browser displaying the seat view image.
For details on how to access the Theatre Map window, click here.
For more information on the Seat Names tab, click here.
If you:
Once the above steps are complete, restart the Web Listener to clear any previously cached web pages.
The default appearance for unavailable seats online is the FontAwesome icon of a person. When a map contains many small seats this may not be ideal as the people might appear to overlap. It may be more desirable to have the unavailable seats appear in a solid colour (or other icon) separate from available seats and suggested seats.
To make this change you will want to edit the tmPickYourSeatMapDisplay.html web page. Locate line 43, it should look like this:
<object class="embed-responsive-item" data="<field>F_HTML_SEATMAP</field>&reserved_colour=00FF00&reserved_only=false&format=pick&unavailable_color=FFFFFF &unavailable_text=&seat_font=FontAwesome&seat_font_load=cdn" id="venue_map">
Change Line 43 to be:
<object class="embed-responsive-item" data="< field>F_HTML_SEATMAP< /field>&reserved_colour=00FF00&reserved_only=false&format=pick&unavailable_color=000000&unavailable_text=" " id="venue_map">
This will remove the people (seat_font=FontAwesome&seat_font_load=cdn) and make the sold seats appear black (unavailable_color=000000). The colour of the unavailable seats can be updated to the desired HEX colour.
For additional features regarding changing the map online please click here.
This process includes web page editing. If you have a web designer on hand, they can perform these edits. If you wish to contract with Arts Management Systems to perform these or any customizations for you, please contact the Support Team at support@artsman.com
<select class="form-control" id="SC_DESCRIPTION" name="SC_DESCRIPTION" size="1">
A button, directing you to a select list of Performances, can be created in the navigation buttons at the top of the online sales windows. This button can be used for Courses, Opening Nights, Special Events or other performances where you want to list a select group of Performances.
The key for this button is flagging the Performances with the same reference and using that reference in the button to pull the desired shows. The setup requires editing the performances and adding the button to the online sales.
To flag the performances, you perform the following steps:
Open the desired Performance.
In our example we have used the letter T.
A button can be added to the existing buttons across the top on the online sales window. Edit the tmnavbuttons.html page.
This process includes web page editing. If you have a web designer on hand, they can perform these edits. If you wish to contract with Arts Management Systems to perform these or any customizations for you, please contact the Support Team at support@artsman.com
<li>
A button can be added to the tmnavButtons.html which provides a link directly to courses currently available for sale online.
This process includes web page editing. If you have a web designer on hand, they can perform these edits. If you wish to contract with Arts Management Systems to perform these or any customizations for you, please contact the Support Team at support@artsman.com
<li>
Buttons can be created for all 7 types of Sales Methods. The most common online options are:
The lines below are an example of a button that will add a specific member type to the cart with a fixed value. This button can be added to any page within the online sales. It would most commonly appear on the TMpass.html page or the TMcart.html page.
<TABLE width="345" BORDER=0 CELLPADDING=1>
<TR>
<TD WIDTH=92 class="tablerowheader" align="center">
<P align="right">Type</P>
</TD>
<TD width="240" class="tablerowheader">
<FORM ACTION="<field>F_HTML_FIREWALL</field>online" METHOD=POST><DIV ALIGN="center">
<label for="Team"><strong>Gift Certificates</strong> </label>
<input type="hidden" name="MT_SEQ" value="14">
</DIV>
</TD>
<TR>
<TD WIDTH=92 class="tablerowheader">
<P align="right">Quantity</P>
</TD>
<TD class="tablerowdetail">
<select name="PS_QUANTITY" size="1" id="PS_QUANTITY">
<option value="1" selected>1</option>
<option value="2">2</option>
<option value="3">3</option>
</select>
</TD>
</TR>
<TR>
<TD valign="top" class="tablerowheader" align="right">Personalized Message</TD>
<TD class="tablerowdetail" align="left">
<textarea name="M_NOTES" cols="50" rows="5"><field>M_NOTES</field></textarea>
</TD>
</TR>
<tr class="tablerowheader">
<td colspan=2 align="center">
<input name="btnReservePass" type=submit value="Add Gift Certificate to Shopping Cart" class="new" onMouseOver="pviiClassNew(this,'newover')" onMouseOut="pviiClassNew(this,'new')" onClick="process()">
</FORM>
</TD>
</TR>
</TABLE>
When entering a coupon code in the online sales the patron clicks the Add Code button. This button appears in the TMtickets.html and TMcart.html pages. The button accepts the coupon or access code and returns the patron to the TMtickets.html page.
This process includes web page editing. If you have a web designer on hand, they can perform these edits. If you wish to contract with Arts Management Systems to perform these or any customizations for you, please contact the Support Team at support@artsman.com
<input name="param" type="hidden" value="altbtn=btnGetEventList"/>
The Genre setting with Theatre Manager are directly connected to the Ticket Trove application. This means the drop down is restricted to the current list of options and is not available for customization. You can however, create your own custom genre lookup using the Event code used to define each event within Theatre Manager OR the Performance Flag field which is associated with each performance within the database. This allows you to group together different types of performances or events and create your own sort options within the online sales.
Using the Event Code within Theatre Manager you can create your own customized drop-down for genre. Lets consider you have three style of theatre programming; Mainstage, Theatre for Young Audiences and Alternative Theatre. You can use a value of the event code to create a custom genre search for the web sales process. You then comment out on the TMtickets.html and add code to reference the Event Code.
The Event Genre will still apply in the TicketTrove application. |
When building events in Theatre Manager an event code is created. The event code consists of 6 characters with a default assumption that the code begins "XX-" where XX it traditionally the year/season of the event. Following the [-] dash you can then add your value. In this example lets assume MXX, YXX and AXX where M represents MainStage, Y represents Theatre for Young Audience and A represents Alternative Theatre.
When Building your Mainstage Series of events your event codes could look something like 13-M01 for the first mainstage event, 13-M02 for the second mainstage event and similar for the Theatre for Young Audiences ( 13-Y01 ) and Alternate Theatre (13-A01). Then considering the 4th character in the code i.e.: M for MainStage, Y for Young Audiences and A for alternative you would add coding to your template to result in a lookup that would appear like the following.
See Adding code to Web Page for details.
The customized code can be added to the TMtickets.html page. Look for the Genre field on the template; lines 76 to 80.
Add the comment values to comment out the present Genre Drop Down as follows:
Then copy and paste the following code either above or below the Genre code you comment out and you will have your new custom Genre lookup based on the value within the event code. Note that you can have as many lookups based on any value of the code you wish. Simply add as many [ option value="position('M' in P_SHOW_CODE)=4">Mainstage Theatre ] as you need. In this example we evaluate the fourth character in the Event code where M will show you MainStage Theatre.
Once the code above has been added to the TMtickets.html page the page should be saved in the WebPagesEN folder. Clear the Cache on the web listener and refresh the page in the browser. The updated changes should now be visible and available to select.
Your Web Templete will then appear as follows:
Your new lookup will then display as:
When selection is made and the search button is clicked it will return all events in this example with an event code 13-M.
Using the Performance Flag field within Theatre Manager you can create your own customized drop-down for genre. You then comment out on the TMtickets.html and add code to reference the Performance Flag.
The Event Genre will still apply in the TicketTrove application. |
To create your own customized Genre for online reporting, you perform the following steps:
The first step is renaming the existing Performance Flag to something that will make sense in the future. This is done in Company Preferences.
The Preferences window opens.
The Performance Field #1 may be used in other parts of Theatre Manager (such as course). If the fiedl contains something other than Perf Type, double check it is NOT being used elsewhere before changing any information. |
Yoiu can now add a unique list of Genres to your database. You do this in the code table. Click here for more information on Theatre Manager's Code Tables.
|
This is not to be mistake with the default Play Genre for the TicketTrove application. |
The Custom Genre (inserting) window opens.
Options may include items currently found in the Event Genre as well as those unique to the organization.
Repeat steps 3 through 5 above until all Genre's have been entered.
Once the list of Genres is created, you need to assign them to each Performance. This method allows for flexibility between individual Performances.
The event list opens.
Repeat the steps until all Performances have a Genre.
Each Custom Genre is assigned a unique sequence number when you add it to the database. This sequence number is needed to add the Custom Genres to the online sales web page.
This is not to be mistake with the default Play Genre for the TicketTrove application. The Sequence number will appear in the left column.
The customized code can be added to the TMtickets.html page. Look for the Genre field on the template; lines 76 to 80.
Add the comment values to comment out the present Genre Drop Down as follows:
Then copy and paste the following code either above or below the Genre code you comment out and you will have your new custom Genre lookup based on the value of the Performance Field #. The code can be found below. The PB_TYPE1_FC_SEQ is followed by a number. This number is the Custom Genre Sequence number from above. Note that you can have as many lookups based value of the Sequence number you wish. Simply add as many [ option value="PB_TYPE1_FC_SEQ='XXX'">Comedy ] as you need.
The result will be the same as shown for the Event code of the previous page.
Once the code above has been added to the TMtickets.html page the page should be saved in the WebPagesEN folder. Clear the Cache on the web listener and refresh the page in the browser. The updated changes should now be visible and available to select.
Regardless which option or approach you require - after placing javascript code or google tracking account into the database, test the web pages. If something breaks, take the pixel code out and fix it - then retest |
In most cases, tracking means you should only need to:
Use Google Analytics to determine which pages are accessed:
The following is a general reference for placing pixel code within Theatre Manager so that they appear on the appropriate web pages. | |
For employees of MogoArts, your pixels have been used in web pages at a number of Theatre Manager venues. Please refer to Mogo's internal corporate Wiki Pages that describe your internal processes for Theatre Manager. An image has been provided. | |
Variables can be used within pixels to get actual cart values. |
The general steps for implementing pixels are:
Pixels:
Mogo, Facebook, or Google pixels can be placed in Company Preferences->Web Listener tab as required to accomplish what you want without needing to edit any web pages. You can also edit web pages directly if you have unique requirements. | |
Conversion pixel codes imbedded in iFrames are not allowed by the Credit Card PCI Council on web pages due to a security risk called Click-Jacking (effectively a man-in-the-middle attack vector).
If the MOGO pixel provided is with an iFrame, please inform them to give you one that is javascript. For your own safety, Theatre Manager web pages do not support embedded iFrames because the PCI Council forbids it. |
A tracking code added to the Header or Footer field in Theatre Manager should be visible in the source code of all pages on the ticketing site. Code added to the Checkout field would be visible on the final page of the sales process. A sample link would be:
This is not an endorsement of pixels from MogoArts. |
We have seen MogoArts' internal documentation wiki. We are not sure of the exact web page, we believe it is called 12_44_43-Vendor - Ticketing Wiki - Google Sheets2222. It contains instructions that look like the image below.
** NOTE: All field references need to be added to the pixel code using <field> tags. An example would be
<field>SCH_ORD_SEQ</field> |
The following technique is a quick and mostly effective way to create translated pages. it is NOT supported, nor ENDORSED - properly translated web pages are always better. |
Sometimes you may be doing a show that caters to a language outside your usual cultural domain. The following is a quick and dirty way to get Google to translate your pages for you after they have been rendered. Effectively:
<!--Google Translate Code --> <div id="google_translate_element"> </div> <script type="text/javascript"> function googleTranslateElementInit() { new google.translate.TranslateElement({pageLanguage: 'en', layout: google.translate.TranslateElement.InlineLayout.SIMPLE, gaTrack: true, gaId: 'UA-xxxxxxxx-x'}, 'google_translate_element'); } </script> <script type="text/javascript" src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"> </script> |
The sample source for a web page footer can be pasted into Theatre Manager in Setup >> Company Preferences. The footer is added to each page within the default web pages. You will need to sign up to get a UA-XXXXX-X number that will replace the value in the sample code.
Theatre Manager's Company Preferences uses the Traditional Snippet and placement in the footer on your WebPages. For more information about Google's Traditional Snippet, click here. If you'd like to utilize Google's new Asynchronous Snippet, suggestions for doing so will be included at the bottom of this page. |
Once you have this set up in Theatre Manager, you can also include it in your eblasts. Analyzing the statistics occurs by logging in to the Google Analytics Login Page.
You can also track the direct source of why a cart was created using the &tmsource=yyy tag.
>
Additionally, there is a provision in Theatre Manager's word processor to add the Google Analytics code from the Web Listener Tab to a Form Letter, which can then be used as an Eblast to patrons in the database. For general information on how to create a Form Letter in Theatre Manager, click here. To add the Google Analytics code to a letter:
Once the letter has been emailed to patrons, the same sort of analysis that can be done with web pages can be done for your eblast. For more information on setting up for an eblast from within Theatre Manager, click here.
To make use of Google's Asynchronous Snippet, just enter your Google account number into the company preferences page above . Theatre Manager self configures the web pages to start tracking.
To Do This:
The ENTIRE document tells us something about what browsers the web site will support and how they will support those browsers. The key parts are described as follows.
The overall Score is near the top and may have a message or two. This looks like the image below.
Review the protocols supported. This will change from time to time and only get stronger. As of Sept 2016, the PCI council and the browser makers (Google, Safari, Firefox, etc) are all pushing TLS. The minimum current safe browsing standards are TLS 1.1 or TLS 1.2. Anything lower means your web site is vulnerable to some web attack. TM Server is designed to only allow TLS 1.2 at this time - because of PCI.
Please ensure that only TLS 1.2 is enabled.
A little further down the report is a complete list of many different browsers. The list includes many older ones and all the current versions and tells you:
In general, IE 11 cannot distinguish the various security methods automatically like other browsers and need to be told to ignore SSL 2.0: |
If your customers ask, this may be their problem.
If a person cannot create an account with a specific email address within Theatre Manager web sales, it is for one of 3 reasons:
Unless you have changed messages in tmError.txt to the contrary, use the above checklist to check email address rejection.
The forgot my password web page shows this generic message. |
Can Theatre Manager actually distinguish amongst the types of errors above? yes it can - there are actually separate error messages in the tmError.txt for all these situations. However, they just happen to say the same thing 'Email address can't be used'
Why is that? The PCI council (Visa and Mastercard) make all the rules as to what kinds of applications are compliant. Theatre Manager is audited and approved by the PCI council to make sure we follow the rules of safe storage of their credit card data and safe online web sales following their prescribed audit cycles.
One of the rules concerns privacy. A web site should NOT give back any information about accounts and login credentials. The thinking is that if there is an easy way for a bad buy to find out which email addresses are in a system, they are half way there to logging in. Thats because people tend to use the same id's and passwords at many sites. So, if they've cracked another site, then its easier to infiltrate venues that give out this kind of knowledge.