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.