Installing Theatre Manager

This PA-DSS guide provides a process for installing or upgrading Theatre Manager that is very similar on all platforms. Since Theatre Manager is a point of sale application for your venue that can deal with credit card information, care must be taken to install it in a PCI compliant manner using the steps that follow.

The installation of the database server, Theatre Manager and web sales is relatively simple and can be done in a few minutes.

Achieving PCI compliance for your venue comes with how you install it on your network and other protections you put in place. These protections are mandated by PCI standards regardless of whether or not you use software in your operation. We hope that our instructions make it easy for a merchant to meet PCI DSS compliance.

We have placed alerts similar to this throughout the installation documentation to signify areas of particular concern to the PCI standards council. Please pay particular attention to these alerts as they contain valuable information to assist venues meeting PCI compliance.

The steps that follow indicate how to install and run Theatre Manager in a manner that will help you meet your PCI compliance requirements as outlined in the PCI 1.2 quick reference guide. A venue that chooses to opt out of some of the safety and security measures in this document needs to be aware that they have chosen to bypass some aspects of the compliance required in the merchant agreement with their bank and the PCI Security Standards Council that is operated by the credit card companies.

Venues may opt out of any compliance step by signing the appropriate area. The credit card companies have placed the onus on all point of sale software providers to help merchants meet compliance (instead of the banks) and highlight areas to address.

Theatre Manager assists you in meeting PCI compliance because:

Step Purpose Optional Installation instructions or link Who
1. Network Setup Mandatory Setting up network for PCI compliance Artsman Venue
2. Installation of Postgres Server Mandatory Platform specific install instructions ArtsMan
3. Installation of Theatre Manager Mandatory Platform specific install instructions Venue
4. Installation of a customer database Optional If this is the first time that Theatre Manager is being installed at a venue, an 'empty' venue specific serialized database will be provided. It will only contain the zip code lookup table and sample code tables. ArtsMan
5. Credit Card Authorization Optional Theatre Manager provides two options for credit card authorization.
  • Paymentech Orbital: involves no setup of additional software. Enter the merchant information and go.
  • PCCharge™: this installed on a Windows machine behind the DMZ using the standard PCCharge™ installers following the PCCharge™ Secure Implementation Guide.
When setting up Credit card authorization, customers have the choice of how long credit card data is to be stored in order to meet Schedule "C" or "D".

Venue Artsman

6. Installation of the Apache Server Optional Installation of the apache server is platform specific if you are using web sales. ArtsMan
7. Setup SSL certificate Optional If you are using web sales, you must set up an SSL certificate and configure your firewall to allow web traffic. You will need to set up a DNS record for 'tickets.yourvenue.org' rather than assigning the SSL to a static IP address. ArtsMan
8. Upgrade of existing web pages Optional This step indicates the general changes to existing web pages that must be made when migrating from any version to any other version.

In addition, a venue must be aware of OWASP and should bookmark it in their browser. This site has a 'top 10' list of ongoing security considerations and standards for web site development. Arts Management reviews and implements each years suggestions annually - see this years top 10.

Finally, if you accept credit cards on the internet, you may need an application firewall as per PCI requirement 6.6 and the web pages are significantly changed. We are looking at mod_security and may put that into a future release of the apache server on your behalf.

Venue
9. Initial settings in TM Mandatory After Theatre Manager and the database have been installed, you will need to review minimum key standards and other security features for PCI compliance. ArtsMan Venue
10. Remote Access Optional This step is a discussion on remote access and what a venue need to do if they wish to provide that for themselves, for Remote Box Offices.

There are considerations for using RDP within the network and enabling security.

Arts Management uses a tool for remote remote support called teamviewer.

ArtsMan Venue
11. Policy Manual Additions mandatory These are some policies that should be added to the customer service and/or security policy manual at a venue for PCI compliance. Venue ArtsMan

PCI Compliance

A Merchant's PCI compliance is obtained by setting up the network and office policies in the appropriate manner and following a few simple rules (green in the diagram). This is required regardless of software used to process credit cards and can generally be done at reasonable cost.

The software or hardware provided by any vendor is only a portion of the merchant's ability to meet PCI compliance. Software provided by vendors must meet the PABP 1.4 standard prior to Sept 2010 and the PA DSS 1.2 standard after that date (red) to assist the merchant meet overall PCI compliance.

Meeting compliance requires some due diligence and is determined by the PCI compliance level your organizations needs to attain. Unless you are using old fashioned dial up credit card authorization terminals, the minimum level for Face-to-Face merchants is Schedule C.

The life cycle of a standard provided by the PCI Security Standards Council is approximately every 2 years.

The following table illustrates a brief historical summary of Theatre Manager PCI compliance

Version Standard Status Action
6 **Self Assessed implements most of PCI security features including medium card encryption and should not be considered PCI compliant. Upgrade to version 9 ASAP
7 **Self Assessed implements almost all standards required of PABP 1.4, including high encryption of cards and does not store any track II or CVV2 information. However, this version is neither audited nor certified.
8 PABP 1.4 meets the PABP 1.4 standard and was certified in Oct 2008. Please refer to our certificate and approval by Visa - page 6.
9 PCI PA/DSS 1.2 Meets the PCI PA/DSS 1.2 standard and approved by the PCI council in Dec 2010. Upgrade by Jan, 2011

** Please note: PCI requirements have changed over the years. At one time, the PCI security council required that vendors of software 'self assess' that they have followed the guidelines. At Arts Management, we have always taken card security and privacy of information seriously and implemented many PCI features before there were published rules. That is why we felt able to meet the self assessment criteria in force at the time. However, there is a much greater need for security than ever before and we encourage merchants to fulfill their obligations to merchant agreements and upgrade to the 'certified' versions of Theatre Manager - which have been audited by external companies as meeting all the rules in effect at the time of the audit.

Network Diagram for PCI Compliance

The block diagram below explains the general setup of a network that is required to implement Theatre Manager in a PCI compliant manner.

Feel free to print this setup document. If any part of the network setup cannot be made to comply with the diagram, you will need to address that at a later date to become PCI compliant. Some sample machine requirements are in the table in the picture, or you can view descriptive information on sample computer specs.

(Click to enlarge the pdf)

PCI compliance requirements for Credit Card authorization

Overview

There are 5 parts to the basic network in the diagram above that are described in more detail in the following sections. The firewall is the glue that connects them all together, yet protects each part from the other (also see firewall rules). These parts are:

  1. Outside the firewall - basically the internet, remote box office setup, and customers purchasing online
  2. VENUE Lan - all staff wireless devices or scanners used at the office
  3. the DMZ - contains only the Apache server and restricts what can be accessed from the internet.
  4. OFFICE Lan - all wired devices in the office. Computers that access any Credit Card information should always be hardwired, or access via a VPN (per remote box office)
  5. Remote box office

PCI Password Requirements

Theatre Manager implements fully PCI DSS compliant 3DES encrypted passwords per PCI DSS standard 8.5 and this feature cannot be changed or overridden.

In addition, Merchants must use PCI DSS-compliant passwords to access to all system components (i.e. any computer, firewall, router, etc. on the network) and these passwords must be changed from any vendor supplied initial values. However, do not reduce the level of authentication complexity or compliance in these other system components if it will result in PCI non-compliance.

This means all login passwords must be:

  • reviewed and changed every 90 days. Theatre Manager will enforce password changes automatically. This must be manually done on those devices that do not force change of passwords like routers and firewalls. (PCI DSS 8.5.9)
  • 7 characters or more (PCI DSS 8.5.10)
  • mixed case consisting of at least uppercase and one lower case letter (PCI DSS 8.5.11)
  • contain at least one number and special character (PCI DSS 8.5.11)
  • cannot be the same as an previous 12 passwords (PCI DSS 8.5.12)
  • cannot have characters or numbers repeated together
Changed all passwords from any vendor default password that might be used for installation per PCI DSS 2.1. For example, you must:
  • Change the Theatre Manager 'Master User' password when the system is installed
  • Change the user and and password on any router from anything printed in the manufacturer's documentation
  • Make sure that accessing each computer requires a password and does not 'auto-login'
  • ensure that screen savers are implemented that requires passwords to be entered whenever the screen saver is activated. Screensavers (or some other mechanism for locking computers) must activate after 15 minutes of idle time or less (PCI DSS 8.5.15) on all workstations and servers.

Each user that has access to any systems in your network must have a unique user id and password per PCI-DSS standard 8.5.8

Never use the Master User account for daily operation. It should only be used when creating other accounts or for other very specialized needs as directed by Arts Management Systems.

If your network has 'master' domain server (or open directory on OSX) available that could control password authentication for all machines, please ensure that the security policies on the domain/directory server is set to enforce PCI/DSS passwords and that all machines in the network log in using authentication from the server.

If a domain/open directory server is not available to enforce password settings, then each machine/user must use PCI/DSS compliant passwords.

If a user tries more than 6 times to gain access to the system, Theatre Manager automatically resigns the user - which means that they are locked out permanently until manually re-instated per PCI-DSS standard 8.5.13 and 8.5.14

Main Firewall

A router (with DMZ and VLAN capability) and two subnets are required within the office to implement PCI compliance. These can be reasonably priced such as the GUI configurable Cisco/Linksys RV082 VPN Firewall (approx $260 in 2010 prices) or more if you want more features. Please check www.techsoup.com if you are a not for profit organization as they have full cisco routers that you may be eligible to purchase at a discount.

We do not recommend a router/firewall without at least DMZ capability if you are doing web sales. However, it is possible to implement full PCI compliance with two routers. Please refer to the Apache Server section for more information.

Your firewall need to restrict connections between untrusted networks and any system components in the card holder environment (PCI requirement 1.2).
  • Routers be a dedicated device, preferably a hardware router. If it is a software router such as one built on linux, then it must only be used only for this purpose and contain no other services.
  • It should be configured to shut down all incoming and outgoing ports except those required for business as per follows.

Firewall/Router Rules

The main router/firewall is protection from the outside world. If the router has DMZ capability, please set up the DMZ IP address to have the same subnet range as the office lan. This will make it easier to scale up web listeners that talk to the Apache Server.

This diagram identifies which traffic is required for Theatre Manager to work in the card holder environment per PCI requirement 1.2.1.

In the example below, we'll refer to all addresses in the office VLAN as 192.168.1.x, addresses in VLAN2 (containing wireless devices) as 192.168.2.x. If you are doing web sales, lets set the DMZ to be 192.168.1.10 (for example). Refer to the SSL Certificate Setup for more detail. The lighter colours red on the diagram represent very restricted rules for specific machines.

The number in the first column refers to the same number on the diagram to give an idea what kind of rules are required for each component. If you combine some services on to the same machine, you will need to aggregate the rules.

For example: #1, the postgres server, only needs port 5432 incoming to that device. You would turn on the personal firewall on the machine so that it only opens that port.

Item Machine Inbound Port Rules Outbound Port Rules
1 PostgreSQL server 5432 from 192.168.1.x
all to 192.168.1.x
37 to time server
2 PCCharge 31419 from 192.168.1.x 5008 to internet
all to 192.168.1.x
3 Remote Box Office
(terminal server)
xxxx from internet all to internet
4 Web Listeners 5111 from 192.168.1.10
80 to 192.168.1.10
25 to SMTP server
37 to time server
53 to internet
80 to maps.googleapis.com/maps/api/geocode
(generally 443 to ANY is a good rule instead of specific IP's)
443 to 192.168.1.10
443 to orbital1.paymentech.net (Orbital)
443 to orbital2.paymentech.net (Orbital)
443 to secure.authorize.net (Authorize.net)
443 to api.authorize.net (Authorize.net)
443 to www3.moneris.com (Moneris)
31419 to 192.168.1.x (PCCharge)
5432 to 192.168.1.x
ICMP (ping) to www2.artsman.com
MX Lookup for email addresses
5 Ticket Printer 10001 from 192.168.1.x all to 192.168.1.x
6 Workstations all from 192.168.1.x 5432 to 192.168.1.x
25 to SMTP server
110 to POP server
37 to time server
53 to internet (MX lookup)
80 to 192.168.1.10
80 to theatremanagerhelp.com
80 to www.artsman.com
80 to www2.artsman.com
80 to maps.googleapis.com/maps/api/geocode
80 to www.google.com/maps/api/staticmap
20,21 to 192.168.1.10
6116 to www2.artsman.com
ICMP (ping) to www2.artsman.com
MX Lookup for email addresses
(generally 443 to ANY is a good rule instead of specific IP's)
443 to 192.168.1.10
443 to orbital1.paymentech.net (Orbital)
443 to orbital2.paymentech.net (Orbital)
443 to secure.authorize.net (Authorize.net)
443 to api.authorize.net (Authorize.net)
443 to www3.moneris.com (Moneris)
31419 to 192.168.1.x (PCCharge)
7 Apache Server 80, 443 from internet
80, 443 from 192.168.1.x
20,21 from 192.168.1.x
5111 to 192.168.1.x
37 to time server
8 Outside of Firewall 80 from internet
443 from internet
xxxx (terminal services)
 
9 wireless all from 192.168.1.1 all to 192.168.1.1
10 VLAN2 (non office computers and wireless ticket scanners) all from 192.168.1.1 all to 192.168.1.1
80 to 192.168.1.10 (apache)

Ports used by Theatre Manager

The table below describes which ports various components in Theatre Manager uses. With few exceptions, it is possible to change the ports that are being used if you wish. The only ports that should not (or cannot) be changed are:
  • ports 80 & 443 externally for web sales.
  • outgoing port 5008 for PC charge authorizations
  • Outgoing port 443 for Paymentech Orbital authorizations
  • port 37 for a time server
  • port 53 for MX record lookup via a DNS server

Port Meaning Security Note
20,21 FTP. Only used between the workstation and the apache server to place pictures/jpegs on the Apache server for WYSIWYG e-blasts TM users will not know the userid and password. It is specified in Company Preferences and cannot be customized by a user.
25 SMTP: outgoing email access for web sales, eblasts and meeting scheduling only. We recommend that you place a small SMTP server within your network so that TM talks to it and it relays to the internet. This will control outgoing access.
37 Time Server. OSX and Windows machines use this to syncronize clocks. All machines should be able to perform this so that transactions are acurately recorded when the happen.  
53 MX lookup. When users and customers enter email addresses into the system, Theatre Manager verifies that their is a mailbox that will accept the domain of the email address - for edit checks. This is done by looking up MX records through DNS services. This can be turned off inside TM at the expense of data accuracy - if desired
80 Standard HTTP port only required incoming for Apache server. Recommended outgoing to theatremanager help.com and teamviewer servers. Machines that are web listeners must also be specified in the httpd.conf file to ensure that no outside machine can receive requests set to the Apache server.

Teamviewer can go out on ports 80 and/or 5938.

110 Standard POP3 port TM has a scheduling function that lets users set up calendar event and send the invitations to users, patrons and volunteers. The incoming port is only checked by TM, and only mails with valid outlook or iCal attachements are read. All others are discarded. No user checks this email address.
443 Standard HTTPS port required for web sales (incomming) and for Paymentech Orbital (outgoing)
5008 Standard port used by PC Charge to talk to any credit card service provider. All comunications are encrypted only required if using PC Charge
5432 Standard port used to talk to Postgres Database. It is only used to talk within the LAN. The pg_hba.conf file on the postgres server also specifies which IP addresses can talk to it - otherwise it does not respond.
6116 this is used for a number of purposes. It is the update checking port to look to see if there are newer versions of Theatre Manager. It is used to provide feedback to the routers outside IP address (like whatsmyip.org but to a known DNS). It is used to verify that PC Charge or Orbital has possible internet access and that the system could function properly. can be confined to talking to www2.artsman.com
10001 Ticket printer port. Workstations send a string of characters to print a ticket. The printer responds with status requests as need be. no outside machine needs access to a ticket printer.
31419 Standard port used by workstations in the office lan to talk to PC charge no outside machine should have access to this port
xxxx Represents setup of Remote Box Office using terminal services. a VPN connection between router1 and the remote box office is recommended for security purposes, even though RDC and terminal services establishes secure connections.

Office Lan

The office lan should be set up to isolate computers that may access credit cards from other general purpose machines. These machines should be hardwired to ethernet hubs and routers. Generally, this just means putting it on a different VLAN than the rest of the office to provide maximum cardholder security (PCI requirement 2.1.1)

For example, if there is an area that provides free wireless in the lobby, or access to the internet for actors in the green room, those access points should be part of the 'Venue Lan' and not part of the 'Office Lan'

You should not be able to access the internet from the database server or any machine that contains credit card information. (PCI requirement 1.3.2)
This section describes the components of the Office Lan.

Ports that should be open are:

  • Acceptance of any traffic from the apache server to the web listener(s)
  • Port 5008 (outbound) for credit card authorization if using PC charge
  • Port 443 outbound to the orbital servers if using Paymentech Orbital
  • Port 25 (outbound) for SMTP mail service that is created by Theatre Manager
  • Port 5432 for access to the database server within the lan
  • Port 6113 to 6117 (outbound) for update checking
  • Port 37 (outbound) for time services checking
  • Port 53 (outbound) for MX record checking
  • Port 80, 443 to the apache server
  • Port 80 to theatremanagerhelp.com
  • Port 80 to www2.artsman.com
  • other ports as required for business

PostgresQL Server

Postgres listens on 5432 by default. Only this port need be open on this server and others can be closed in the operating system. This can be changed by editing the Postgresql.conf file, or during the install.

Misc Recommendations

  • Combining the Postgres and Credit card server in a windows environment is a common practice.
  • We generally recommend that file services for the network be placed on another machine.
  • Do not install virus software on the Postgres Server if there is no file sharing permitted. Install virus software if file sharing is permitted but specifically exclude:
    • any TCP/IP traffic on ports 5432, 31419 (PostGres or PCCharge™)
    • Any file used by PostGres (generally C:\Program Files\Postgresql -or- C:\Program Files (x86)\Postgresql)
    • Any file used by PCCharge™ (C:\Program Files\Active-Charge -or- C:\Active-Charge)
    • Under OSX and Linux, the need for virus checking on the Postgres server is generally not required as they are often stand-alone machines)
  • Turn off windows auto updater. Instead, perform regular maintenance at a time of your choosing (every second Monday for example, more often if the news reports critical viruses) to download and install updates. For 24/7 web sales service, it is important that the Postgresql server run constantly and only be maintained at a time of your choosing.
  • On OSX, turn of Software Update and run regular maintenance every second week, similar to Windows Environment

Deploy anti-virus software on all systems commonly affected by malicious software (particularly personal computers and file servers) (PCI requirement 5.1)

Credit Card Server

There are two choices for credit card authorization.

Paymentech Orbital

You will need to provide outgoing https (port 443) access to the following two URL's:

  • orbital1.paymentech.net/Authorize'
  • orbital2.paymentech.net/Authorize'

PCCharge™

PCCharge™ listens on port 31419 by default. Open this port on the workstation for incoming and allow 5008 for outgoing. This can be changed be configuring both PCCharge™ and the merchant preferences in Theatre Manager.

Normally, in a PC environment, the Postgres and PCCharge™ servers are combined onto one machine.

Web Listeners

Any web listener listens on port 5111 by default (can be changed inside default data in Theatre Manager)

Multiple web listeners can be set up to talk to apache. If you wish to restrict specific machines to be web listeners, enter the IP addresses of those machines in the Apache configuration.

If desired, you can install anti virus software on this machine. Since it is not used for any other purpose and listens only to the API's from the apache server, you should not need any.

Deploy anti-virus software on all systems commonly affected by malicious software (particularly personal computers and servers) (PCI requirement 5.1)

Box Office Admin Computers

Office computers can be classified in two categories - those with credit card swipes and those without.

Machines accepting Credit Card data (especially with swipes attached)

Any computer where credit card information is entered or that has an attached credit card swipe is effectively a point of sale device and needs to be protected from a particularly nasty form of virus called 'Bots'.

These are especially prevalent on PC's and if a computer were to become infected, this type of virus scans keystrokes at the computer and sends those key strokes to the 'bad guys' outside the network. Preventing this involved closing ports and denying access to the outside world, especially for mail and web browsing.

For this reason, on those computers, you should:

  • close down all outgoing ports except 5432 (the database server), 31419 (PCCharge™ server), 53 (MX lookup), 25 (SMTP send from TM), 110 (pop3 receive for scheduling), 6116 for PCI version checking
  • Close down port 80 for web browsing, except if you can allow people to access theatremanagerhelp.com for online help
  • disallow internet access via the web browser to prevent the most common source of infection
  • install virus protection software on these machines and regularly run it and update the software. There are a number of good alternatives from freeware like Avast! to Symantec (our least favourite)
Deploy anti-virus software on all systems commonly affected by malicious software (particularly personal computers and servers) (PCI requirement 5.1)


Machines that do not accept credit card information

Machines not being used with Theatre Manager (or where there is no entry of credit card numbers), can be allowed internet access.

If those computers are on the same network segment as the machines accepting card numbers then they fall into the scope of a PCI assessment for the venue. This means those machines would need all of the anti-virus and anti-malware software as well as file integrity monitory, log management, access control, etc. just like the machines that accept the cards.

To reduce the scope of the venue's PCI assessment needs, the venue should consider placing those machines (back office or manager machines usually) on a separate network segment with just the necessary ports between them and the cardholder data network open. In this case, follow the previous setup suggestions for port and virus software installation

Deploy anti-virus software on all systems commonly affected by malicious software (particularly personal computers and servers) (PCI requirement 5.1)

Venue Lan

Machines in your office that generally do not need access to Theatre Manager need to be in a separate VLAN so that they do not accidentally compromise credit card data. Rules should be put in place so that these VLAN's cannot talk to the servers in the Office VLAN per PCI requirement 1.2.3

It may be a good practice to have one or more VLANs beside the primary office network, especially if you have wireless access points, public WI-FI in your lobby, green room access for Actors, etc. Separating those kinds of users form the office lan is beneficial from a security and bandwidth management point of view. Network segments not dealing with cardholder information may be unprotected, use WEP or WPA.

However, if you do require that some computers access cardholder data over a wireless network, you must use strong encryption technology for authentication and transmission of data such as hidden SSID, specified MAC addresses, and WPA2 or better on a separate VLAN than other wireless access points and change vendor supplied passwords per PCI requirement 2.1.1.

You must never transmit card information over a network with WEP encryption per PCI requirement 4.1.1.

Wireless Access Points

Wireless routers must be connected in their own VLAN. Configuration of these should include:
  • turn off all SSID broadcasting
  • enter the MAC addresses (00:00:xx:xx:xx:xx) of the scanners into the acceptable list if devices at the remote site and only allow those devices to gain access to the network
  • Use WPA2 or better password access control if possible. The MC55 ticket scanners support this authentication method. The older MC50 scanners only support WEP.

Ticket Scanners

If the ticket scanners are used for a venue in the building and connected to a wireless access point between the routers, use the same rules as for scanners at a remote venue.

The only difference is that you can use the IP address of the Apache server directly (e.g. 192.168.1.x) in the scanner, or you can use local DNS services to point to the Apache server within the network. It is generally easier to use the direct IP address unless you have access to the technical resources to set up DNS for this purpose.

Wireless Computer Access

If you permit wireless access to your network within your office, PCI compliance states that these computers should go through at least one router before accessing the office network or any part of the network where credit card information is stored.

The DMZ (Apache Server)

The Apache server is the only part of the Theatre Manager system placed within the DMZ. It will be protected by the main firewall. You should turn on the built in firewall on the machine (OSX or Windows) and should only need to open ports:
  • 80 and 443 to allow web sales

Since Apache is on this machine, it should auto start as a service upon reboot. This means nobody need login at all. However, configure the screen saver to require a password after it is activated.

This machine is only responding to requests from the internet via Apache, it is not actively accessing anything on the internet using a browser or reading email - so the risk if is acquiring viruses is very minimal.

If you put a virus scanner on it, set it to scan the hard drive once a day, preferably early morning or at a time of day when online sales is expected to be at its minimum. Some antivirsus software applications are CPU intensive and have the potential to severely slow down the Apache response time to web requests.

The best setup conditions would be:

  • To install a firewall (if it is not operating) on the machine
  • Turn off windows auto updater. Instead, perform regular maintenance at a time of your choosing (every second Monday for example, more often if the news reports critical viruses) to download and install updates. For 24/7 web sales service, it is important that the Apache server run constantly and only be maintained at a time of your choosing.
  • On OSX, turn of Software Update and run regular maintenance every second week, similar to Windows Environment
  • Do not allow anybody to access this machine except under controlled circumstances
  • Remove access to Outlook and/or other mail clients on the machine
  • Make sure that accessing the internet through internet explorer or other browser on that machine is limited to certain URL's
  • Don't scan incoming requests to Apache on port 80 or 443 - because that is the working ports for Apache.

Note that card holder data should never be stored or placed on the Apache server for any reason. Theatre Manager does not require it. (PCI requirement 1.3.7)
Deploy anti-virus software on all systems commonly affected by malicious software (particularly personal computers and servers) (PCI requirement 5.1)

Policy Manual

PCI compliance requires some additions to your policy manuals, some of which are described below and relate to safeguarding your network and the credit card information. We recommend making these additions immediately.

Refer to Section 12 in the PCI DSS implementation guide for complete information

Policy Description
1. Credit Card information must not be stored on any machine that is in the DMZ.

This generally means laptops that connect to the network wirelessly should be examined for files that contain card information and that information must be deleted.

2. Do not transport credit card information outside the secure firewall without:
  • 3DES encrypting each card or the complete file containing any cards (never auto de-encrypt the file when starting a machine)
  • transporting the data in a secure password protected device -or-
  • sending via SSL or over a VPN if doing remote backups electronically to a secure site
3. Never email a credit card number to anyone.
4. Never read back an entire credit card to a patron if they call in asking for one. Always have the patron tell you the card and confirm it only if it right. You can confirm a card number that the patron just told you in entirety.

Remote Box Office

Depending on the remote access solution (Citrix, Terminal Services, Timbuktu, LogMeIn), you may need to open the appropriate ports on your router(s) and server for this feature:
  • On the firewall built into this machine
  • On the 'second' firewall protecting this machine with forwarding of the appropriate ports to this machine
  • On the 'first' firewall protecting the office with forwarding to the appropriate ports on this machine.

Access to the terminal server from outside the main network should be include VPN or packet encrypton.

If the remote box office solution permits the feature, you should also set it up so that only specific applications can be launched and the user cannot get to the Desktop. For example, Citrix provides a web interface under is ISA services that allows you to only permit Theatre Manager to run. With Terminal Server, you can also force it to start Theatre Manager automatically.

Always disable outgoing web access on citrix or terminal server so that people cannot browse the internet (this will prevent all viruses).

Deploy anti-virus software on all systems commonly affected by malicious software (particularly personal computers and servers) (PCI requirement 5.1)

Remote Ticket Selling

In most cases, the best way to do remote box office is to set up a Terminal Services server inside your network and provide a VPN solution from the remote site to the router.

An inexpensive Linksys VPN router will provide adequate router to router VPN services inexpensively - or will provide remote VPN software for computer to router VPN. More expensive routers like Cisco have VPN software that accompanies the router as well.

In all cases, remote box office or work at home should be set up using a VPN connection.

Note: if installing on terminal server 2003, you may need to switch it between 'execute' and 'install' mode to actually install Theatre Manager.

If you are using remote box office and ticket scanning for access control at the same venue, it is advisable to set up the wireless access point to talk to the VPN router and send all data through the VPN tunnel as a point of extra security.

Remote Ticket Scanners

If your venue uses wireless ticket scanners for remote venues, you will need to set up a wireless access point at the remote venue to connect to the internet. These devices only confirm a ticket was used or a person exits the venue, through a very controlled API on the scanner.

The setup of the wireless access point should be:

  1. turn off all SSID broadcasting
  2. Enter the MAC addresses (00:00:xx:xx:xx:xx) of the scanners into the acceptable list if devices at the remote site
  3. use WPA2 passwords for access (the Symbol MC55 device supports WPA2)

The setup and functioning of the symbol MC55 wireless device is described in a separate document.

When you need to enter in the IP address, you can use tickets.yourvenue.org/TheateManager/1 if you have set up a DNS or you can use the static IP address of the outside router.

You can also specify port 80 or 443 (or some other port if you wish to do address redirection within the router for additional security).

Even if you are scanning tickets at you local venue, it is often a simple matter of setting up a small hub in front of your main router so that the access points are connected to it - and they would be outside the firewall for security.

Remote Access

Remote access for Theatre Manager usually means situations for remote box office or work at home. There are a number of tools that can be used, such as Remote Desktop Connection (RDP), LogMeIn, Go To My PC, and more.

In all cases of remote access for box office, you should implement either VPN tunnel and/or SSH access - where the communication and session has strong encryption or is a private connection per PCI DSS 4.1

There may be additional setup consideration as described in the following sections base on the software you use. Your IT person should ensure that whichever software is used, that it employs VPN or SSH.

PCI compliance requires that remote access have a user id and password, and an additional authentication factor that includes, but is not limited to items such as a smart card, token, PIN, Biometrics, VPN.
For people with remote access, you must establish passwords according to PCI DSS requirements 8.1, 8.2, 8.4 and ann requirements of all sections of 8.5. In other words, the requirements for remote access passwords and authentication are exactly the same as for access to your office lan.

Microsoft Remote Access

If you are using remote access, you need to set up terminal server to use high security access for Remote Desktop and it should be set to disconnect or lock the terminal after a period of inactivity. (PCI requirement 12.3)

Windows 2003/2008 Server

When connecting from any workstation to 2003/2008 Server, the server defaults to high encryption. It is good practice to verify that the setting has not been lowered.

Step Purpose Installation instructions or link
1. Verify Terminal Server settings

The following links detail the security settings in Windows Server 2003. Server 2003 defaults to High encryption, but it is a good practice to make sure it hasn't been lowered accidentally.

support.microsoft.com/kb/814590

technet2.microsoft.com/windowsserver/en/library/a92d8eb9-f53d-4e86-ac9b-29fd6146977b1033.mspx?mfr=true

2. Verify RDP settings RDP should be set to always prompt for a password.

 

Windows 2000 Server

When connecting from any workstation to 2000 server, the server setting workstation is allowed to specify the security level, and unfortunately, it defaults to the lowest security level. You need to make some changes to the settings to connect at the high security level.

Step Purpose Installation instructions or link
1. Set up Terminal Server Settings

The Encryption Levels settings in Terminal Server should be set to High for the Remote Desktop Protocol. Refer to the technote on the microsoft web site for the proper procedure.

2. Verify RDP settings RDP should be set to always prompt for a password.

TeamViewer Remote Support

Theatre Manager uses TeamViewer for remote support. This is designed to never be active, unless the user contacts Arts Management and permits the technical staff to have access to their machine for the purpose of diagnosing a problem on a one time basis. It is to be disconnected after use per PCI requirement 12.3.9. Theatre Manager never requires permanent access to your networks for any reason.

The process for actual access to the remote machine is as follows:

  • The customer has initiated a support request that involves a phone conversation
  • In that phone conversation, it is determined that a timely resolution involves connecting remotely to provide assistance
  • Arts Management confirms our identity to the customer by providing the customer number or the case number to continue with support (PCI requirement for second authentication).
  • The customer then starts the remote assistance software. It is not active by default.
  • The customer uses the remote assistance software to generate two keys: a random id and a random generated password. Both of these are told to the support representative.
  • Arts Management Support activates remote assistance manager and enters both keys to gain remote access
When Remote Access is disconnected, another remote support session requires a new set of keys to be provided. The customer is in complete control of the session at all times with a visual indicator showing the connection status.

How does it work

TeamViewer uses SSH for authentication and brokering of session keys. It communicates with the master cluster is through DNS names, which delegates the brokering of the session to the TeamViewer servers. Connection to the routing server and KeepAlive server is done directly via IP addresses.

The servers are spread across the globe and located at large data centers, their IP addresses are not organized in common subnets or IP ranges. Teamviewer continuously top scales the server network as the number of TeamViewer users grows, so it is not possible to have a fixed set of IP addresses, because this list would very soon be outdated.

Communication is done to URL's of the format:

  • *.teamviewer.com
  • *.dyngate.com
By default TeamViewer uses only the outgoing port 80 (HTTP) so that no firewall configuration is necessary. Alternatively you can open port 5938 (TCP) for outgoing connections if you wish to block port 80.

Outside the Firewall (the internet)

The internet is everything that occurs outside your firewall perimeter and represents everything that is beyond your control to protect.

This is where your customers will be.

Customer Access

Customers buying on the web need to be able to access the Apache web server through ports 80 and 443 in the DMZ. The web server sends cookies back to them.

Web Page Design Considerations

  • Your main web site should direct links to the Apache server via https so that the majority of access to online ticket sales is secure.
  • If a customer tries to access tickets.yourvenue.org through port 80, the first thing that the index page does is redirect them to a secure port.
  • If a customer does alter the URL and tries to access a page via port 80, the Theatre Manager web listener always responds back with a secure page and the next interaction will be through port 443
  • Ultimately, if you only wish secure access through the DMZ, you can turn off port 443 and customers will be forced to access via https. This is quite aggressive approach and has some marketing implications - the safeguards above ensure that people are move to https after hitting the web site for the first time.

What a Customer needs to do (Nothing)

A customer has zero configuration to do on their machines, other than to allow cookies from your site if they cannot browse the web pages. The Theatre Manager Web Listener will alert them to turn on cookies as it detect people trying to move through pages without cookies enabled.

PCI Audit Logs

PCI DSS compliance sections 10.2 and 10.3 require that Theatre Manager maintain audit logs for certain system events. These primarily deal with who has seen or could have seen credit card information.

The transaction logs in Theatre Manager deal with all these requirements because Theatre Manager has always maintained and 'audit log' of certain system events that tracks the events required in PCI section 10.2 and the a minimum of the data elements in PCI section 10.3.

The following screen shot is a sample of an audit log that is contained within the transaction records in Theatre Manager.

All financial and access audit log transactions are kept forever. Specifically transactions like Login, Logout, Invalid Access, and Viewing Complete Card Data are kept in perpetuity. Transaction types are 'coded' and 'dated' for easy finding and sorting.

there are some non-fiancial transactions like 'ticket unprint' which are kept a minimum of 1 year or longer depending on settings. These do not affect finance or PCI compliance so retention is optional.

td>
PCI Std. Requirement Theatre Manager Implementation
10.2 Implement automated audit trails for all system components to reconstruct the following events:
10.2.1 All individual accesses to cardholder data Theatre Manager creates an 'AC' transaction to track whenever a user sees the entire credit card number. By default, Theatre Manager displays masked card numbers in all windows and reports. Only in specific places will Theatre Manager display card information to those who have specific authorization to see cards. Therefore, you should expect to see very little information in the audit log if you minimize who has access to see full card data.

The act of accepting a credit card at the box office is tracked with a PT audit transaction - i.e. the actual payment - and can be tracked by user that way.

None of these transactions can be purged.

10.2.2 All actions taken by any individual with root or administrative privileges An administrative user is subject to the same rigorous requirements as all other users.
10.2.3 Access to all audit trails Theatre Manager does not track who views audit trails because they cannot be changed, manipulated or altered by the user in any way. We believe that when users know this information is tracked for PCI compliance, it acts as an additional deterrent. None of the logs ever display sensitive data.
10.2.4 Invalid logical access attempts Theatre Manager tracks who access's Theatre Manager and logs in or out via the 'ALI' and 'ALO' transactions.

'ALX' transactions track invalid login attempts (after 3 mistyped passwords), or when the user account is locked out.

These transactions cannot be purged.

10.2.5 Use of identification and authentication mechanisms Theatre Manager uses login and authentication mechanisms. All users of the application must log in.
10.2.6 Initialization of the audit logs The audit logs can never be 'initialized' by the user, nor can be they be cleared except under programatic control. The minimum retention time is 365 days for audit transactions with the default being forever. Payment logs indicating who took the actual payment are retained forever and cannot be deleted.
10.2.7 Creation and deletion of system-level objects  
10.3 Record at least the following audit trail entries for all system components for each event:
10.3.1 User identification yes - see log example
10.3.2 Type of event yes - see log example
10.3.3 Date and time yes - see log example
10.3.4 Success or failure indication yes - see log example
10.3.5 Origination of event yes - see log example
10.3.6 Identity or name of affected data, system component, or resource yes - see log example

Misc PCI Requirements

The following section documents some of the final miscellaneous additional PCI compliance requirements that merchants will need to know or be aware of. These are presented here as 'things to do or know about' because they are not relevant in other parts of the installation guide.

Please use these as ticklers to yourself.

If card data is to be transmitted over a public network (i.e. outside your firewall), it must be sent using secure encryption technology like IPSEC, VPN or via SSL/TLS per PCI DSS 4.1.
Do not send any credit card data 'in the clear' such as pasting a card number into an email, or into an IM per PCI DSS 4.2 unless you are using secure encryption with these messaging technologies. Do not encourage customers to send cards, cvv2, name, expiry or any other such data to you via the same technologies.

Theatre Manager does not provide this feature due to PCI compliance and only presents the final 4 characters to users for this reason.

If you are upgrading from a prior system that might have had unencrypted credit card information, you must throw that data into the trash and secure erase it with a tool like ERASER (free) on the PC or do a file->Secure erase on the Mac.

PostgreSQL Database Server

The following instructions are used to set up a PostGreSQL server for use with the Theatre Manager application. Please follow the directions appropriate for the server platform you are using.

Macintosh PostgreSQL Server

The following instructions are used to set up a Macintosh PostGreSQL server for use with the Theatre Manager application. Click if you are doing Windows setup

The server needs to be set up on one machine and the application can be set up on as many machines as you wish.

Follow these steps if you are using the TheatreManager TM PostGresSetup installer program and you may want to bookmark this page in your browser in case you want to refer to these installation steps. If you are only installing a demo, refer to the last column for required steps.

task Description Full Install Demo
1 If the server is OSX-LION (10.7.0 or later) and there are two drives in the computer (you will probably see two disk icons on the desktop or look in disk utilities), we strongly recommend STRIPING the two drives due to a very significant performance improvement. If you have this situation (very common in Mac Mini Servers), refer to this page to prepare the hardware and reinstall the operating system as Lion is not shipped with the drives striped.

The steps are similar for those using OSX 10.6.x or earlier - but you will have install DVD which makes is a bit easier. The process is similar.

yes no
2 download the PostGres installer for Mac yes yes
3 the installation of the PostGres SQL server yes yes
4 installing the demo database and the main TheatreManager User optional yes
5 configuration of the server parameters for maximizing performance in a production database yes no
6 creating a daily backup job in using cronnix to run the backup yes no
7 Turn off energy saving, airport and other energy saving features yes no

Notes and Assumptions:

  • This install process assumes you have NEVER installed PostGres or Theatre Manager on your computer before. If you have, you may need to refer to Updating Postgres Instructions
  • You MUST turn all virus protection while running the installer (especially Norton if you are using it). Virus software always interferes with proper software installation.
  • If this installer is being used to create a demo installation, then you only really need do steps 1, 2 and 3.
  • This process assumes that you have never installed Theatre Manager or Postgres on your machine. If you have already installed Postgres:
    • you will be asked if you want to un-install Postgres (you may want to do that and then try to re-install after)
    • you may need to remove the 'postgres' user from your computer if one exists, unless you know the password for the use.

Mac OSX-Lion Multiple Drive Setup and Install

The steps below are an outline of how to setup an Mac Mini (or Mac Pro) with OS-X Lion Server that has two or more drives.

The steps outlined are similar if you have a Mac Mini or Mac Pro running OSX 10.6.x or earlier. You will have and install DVD and can do most of the steps without connecting to the internet.

The general process to prepare such as machine for optimal performance is:

  • Stripe the drives
  • re-install lion server
  • Install Postgres as normal.
  • Restore a database to that server

The steps have a degree of technical complexity and assume you are able to interpret and adapt to variations in the process yourself.

Striping a Mac with two or more drives under Lion

Since Lion does not come with any install disks, you will need to follow a special procedure to stripe the drives on a lion servers as follows:

  • Make a backup of any data on the computer that you deem important if you have been using it for a while
  • Connect the Mac Mini/Mac Pro to the internet, a monitor and keyboard. The internet is important as it will be required to restore the operating system.
  • restart the mac with the Apple and R keys held down. This will boot from the internal lion partition on the drive.
  • When the machine responds with the OS-X operating system installer screen, select the language of your choice and begin the install
  • The next screen will be the utilities window. Select Disk Utility and:
    • After selecting a drive, click on the the 'RAID' tab.
    • Select 'STRIPED RAID SET' for the 'RAID Type' prompt. The default is a mirrored drive set, so be careful otherwise you might end up starting over.
    • Drag both drives into the Raid Stripe and verify that the estimated size of the RAID set is the total of both drives.
    • Create the Raid Striped Set.
    • After confirming you want to do this, partition utility will bring the raid array back online.
    • Quit 'Disk Utility'
  • On the main window, you should now select 'Reinstall Mac OSX Lion' (optionally, you could restore from a time machine backup). Follow any/all prompts and reinstall Lion. It may say that file vault or some other features are disabled. So be it -- its the price of gaining a lot of performance from the dual drive server.
  • The download from the Apple web site may take a while, so let the installer do its thing.

Post Installation Steps

Step 1: Install PostGreSQL database server

When you run the installer for the database components, it will put the actual installer files into the Macintosh HD/Users/Shared directory along with all the support files needed for the rest of the steps.

At the and of the TM PostGres file installation phase, the actual Postgres install process will begin immediately. If you cancel the setup of PostGres, you can always start it again by repeating the process from the start.

Installing Postgresql on a Macintosh

1. Double click on the TMPostgresSetup application. You will be asked to authenticate the installation by OS-X. Please type the appropriate user id and password.

2. Click 'Continue' on the splash screen

3. Read the licence agreement and click 'Continue' to accept it.

4. Click 'Agree' on this screen

5. Click 'Install' on this screen.

5. Click 'Install' on this screen.

6. You will see the installer complete the work.

7. When it is done, you will see a notice that postgres was installed. Click 'Continue'

8. Click 'Quit' on this screen and restart the computer.

Step 2: Create user and import Database

The installation of postgres in step 1 should have imported the demo database for you. If you start Theatre Manager and cannot see a demo database, you may need to perform these steps.

In most circumstances, you can skips this and the remainder of the steps if you are only installing a demo. If you are not, you will need to proceed to steps 3 and 4.

Installing a demo if one was not installed

The database server needs a specific user called TheatreManager with specific privileges that will be assigned as the owner of each database. We also want to import a demo database. This step assumes that you have installed things into the /Users/Shared directory. If you did not, then you will need to edit the script and do this step manually

1. Go to /Users/Shared directory. You should see some files and folders with names that look like below.

Import1

2. Start terminal and change the user to 'postgres' by typing:
su - postgres
Press RETURN
and then type the postgres user's password (password will not display anything)

import2

3. Drag the script '/Users/Shared/CreateDemoDB.sql onto the terminal window. This shortcut saves typing anything.
Click into the terminal window and then press RETURN to start the command.
If it does not run, then possible issues are:
  1. You need to have execute permissions on the 'CreateDemoDB.sql' script. Use File Examiner to check or fix that (or use unix chmod commands to give permission).
  2. Make sure that postgres was configured with 'trust' permissions for the local machine.
  3. Make sure that postgres was installed into the /Library/Postgresql8 directory.
import3
4. The script will run and load up the TheatreManagerDemo database. You can modify this script to load up a customer database if necessary by editing it in BBedit or in textedit (make sure to save it as text if you use textedit - its preference, unfortunately, is to save as an rtf document). Note, any WARNING messages from the TheatreManagerDemo database creation can be ignored. These warnings are normal.

step4

Step 3: Configure the PostGreSQL server parameters

When you are able to connect to the database using Theatre Manager, its time to tune some of the parameters for PostGresSQL that are specific to your machine and setup. On a Mac, this needs to be done with VI under the postgres user account.

The general steps are:

  • Edit the pg_hba.conf file to indicate which IP addresses may talk to the database server
  • Edit the postgresql.conf file to adjust some memory settings for performance
  • Edit the .bash_profile if you plan on using terminal to access the database on a frequent basis

    This step is optional to do and is done for you automatically when you run the Theatre Manager postgres database installer

  • Change the shared memory settings on OS-X to allocate more memory to the database server.

    This step is done automatically for you if you have used the Theatre Manager postgres database installer and you have more than 2 gigs of ram on the sever

PG_HBA.conf file

What does this file do? This file controls all access by users to the PostgreSQL server.

In order for clients to connect to the server, their IP address must be in the allowed list of users. The two common authentication methods that you will see being used for Theatre Manager clients are MD5 and trust.

  • MD5 does md5 password authentication and should be used for just about all entries to this file.
  • Trust allows clients to connect without password authentication, the only 'trust' entry should should be for the local server machine and/or localhost.

1. The first changes to make involve the pg_hba.conf file and the postgres.conf file. To do so, you'll need to use VI (a text editor) and be the postgres user in terminal. To do this, start terminal and type

su - postgres

enter the password

2. Go to the postgres data directory by typing

cd data

3. Edit the postgres pg_hba.conf file that contains the addresses to listen on. Type

VI pg_hba.conf

You should see a page of information. If you do not, then type 'Shift Q' and then just a 'q' - after which you can start the process over. If you see the list of text similar to the right, then:

Use the down arrow on your keyboard to go to the very end of the file

4. EditHba

When you are at the end of the file, use the up arrow on your keyboard so that you are right after the first line in the IPv4 settings there it says 'host all all 127.0.0.1/32 trust'. In the example the cursor is on the '#' on the line after.

type the

I

key and the message at the bottom will change to Insert.

5. EditHba

Edit the pg_hba.conf so that its final settings are similar to the window on the right.

Type directly into Terminal so the data looks like the window above. Use the delete key to get rid of characters. You will likely end up typing the following lines where the first one is your subnet. This is the most typical example we've seen at venues

host all all 192.168.1.0/24 md5

NOTE: For the 127.0.0.1/32 option, edit the handshaking to be TRUST at the end of the line to allow backups to run unaided.

NOTE: If your machine uses IPv6 (the new internet IP setting standard), you may also need to set ::1/128 to be TRUST instead of md5. If so, edit that line to look like:

host all all ::1/128 trust

NOTE: If you are running version 9.0 or higher of postgres in a Mac environment the local all all line should be set to TRUST.

NOTE: You may also need to edit the local all all line from md5 to TRUST. This can be determined if the backup script will not run without a password after changing the settings above for 127.0.0.1 and ::1/128.

The line you added (or need to add) are for:

  • The local subnet - as in 192.168.9.0/24
  • Other subnets that need to access the data - as in 10.1.5.0/24
  • Any single machines that must have access - as in 55.66.77.88/32 (via VPN)

At the end of the subnet, the /24 refers to a complete subnet when you want any machine on the subnet to access the database. This is what is used most often.

The /32 refers to a particular machine. If you use this option, you will need to provide the exact computer IP that you want to allow to access the database.

6. EditHba

At the end, type, in this order:

hit the 'esc' key

(the insert mode will dissappear)

Shift Q

(the window will show the 'Entering Ex mode' message)

wq

and the window will clear.

 

Reference for settings in the pg hba.conf file www.postgresql.org/docs/9.0/interactive/auth-pg-hba-conf.html

POSTGRESQL.conf file

The postgresql.conf file contains parameters to help configure and manage performance of the database server. You can use most parameters as installed out of the box, but the server will go much faster if you alter about have a dozen key settings.

1. You will need to start by changing to the postgres user in Terminal. To do this, start terminal and type

su - postgres

enter the password

2. Go to the postgres data directory by typing

cd data

3. EditHba

This will also use VI to edit it. Type

VI postgresql.conf

when the list appears, type

I

to go into insert mode and use the up and down arrows to find the options below

 

Find and edit the parameters in the list below and change them to the suggested values, if they are not already set to that value.

if any line contains a '#' at the beginning and you need to change that line as per the instructions below, make sure to remove the '#' as it uncomments the parameter. If there is no '#', then just change the values.

For any setting that is about disk space or memory, you can type 1GB, 1000MB, 1000000KB and they are the equivalent. Do not leave a space between the number and the memory amount at the GB, MB or KB otherwise postgres will not start.

4.
listen_addresses This value should always = '*'

It will probably look like #Listen_address = 'localhost'. Remove the # from the front of the line (if any) to activate that parameter and change 'localhost' to '*'

bonjour If you wish your postgres server to be discoverable using bonjour services so that the mac version of TM can automatically locate a server on the network, this value can be uncommented and changed from off to on

It will probably look like #bonjour = off. Remove the # from the front of the line (if any) to activate that parameter and change off to on

max_connection This is the number of simultaneous connections. If it is not at the default of 100, please change it to be 100.
maintenance_work_mem This value should be 50MB for machines with 1 GB of RAM or more and 20MB for those with less. Enter values as xxMB.
shared_buffers This value should be 20-25% of the total system total RAM. You find this value on the task manager as the total phyiscal memory. Enter values as xxMB.
temp_buffers This value should be 50MB for machines with 2GB of RAM or more and 20MB for those with less. Enter values as xxMB.
work_mem This value should be 50MB for machines with 1GB of RAM or more and 20MB for those with less. Enter values as xxMB.
effective_cache_size This value should be roughly the amount of 'available' memory (always round down to the nearest 50 MB) as seen in the Activity Monitor without PostgreSQL running. If there are other applications that will also run, you want to subtract their memory footprint. It is good to take the reading before installing PostgreSQL.

Reference for postgres.conf file parameters http://www.postgresql.org/docs/9.0/interactive/runtime-config.html

5. Once the changes are made, type, in this order:

hit the 'esc' key

(the insert mode will dissappear)

Shift Q

(the window will show the 'Entering EX mode' message)

wq

and the window will clear and you will be back at terminal

.bash_profile in terminal

The .bash_profile settings should to be entered in the terminal session for the postgres user to establish the commonly used paths for the database and the executable binary files. This is always setup if you are using the Theatre Manager installers for postgres. If you install your own version of Postgres, you may need to do this IF YOU PLAN ON USING TERMINAL to interface with postgres on a frequent basis.

Otherwise, this step is not required under most circumstances.

1. Start Terminal and navigate to the home directory for postgres user.

Type:

cd /Library/PostgreSQL/9.1

2. Next, lets update the profile for terminal to that it makes life easier in postgres from this point on. Type

vi ~/.bash_profile

it will open with an empty window as below.

bashProfile

Just like when using VI for the other two files, type:

I

to put you in insert mode

3. bashProfile

Type the two lines into the file exactly as shown. When done, type, in this order:

hit the 'esc' key

(the insert mode will dissappear)

Shift Q

(the window will show the 'Entering Ex mode' message)

wq

and the window will clear and you will be back at terminal. The next time you start terminal under the postgres user account, you will have access to the postgres commands and data directory in a more convenient fashion.

OS X Shared Memory Settings

Why do I need this?: This is done so that you can increase the shared_buffers parameter to more than the standard 128MB. Shared buffers allows PostgreSQL to use much more memory and can improve performance quite dramatically.

If you used the Theatre Manager postgres installer, it will detect if you have more than 2 gigs of ram in your machine and automatically insert these into the /etc/sysctl.conf file for you. After installing postgres the first time, simply reboot the server - these settings will have been done for you and you need not continue with the steps below.

BEFORE STARTING: Ensure you are in terminal at your own user, not postgres. This is a fairly technical topic and the reference: http://www.postgresql.org/docs/9.0/interactive/kernel-resources.html

1.

Open terminal again and type: su - [Your UserName]

Type

vi /etc/sysctl.conf

Type I to insert data

Add the lines:

kern.sysv.shmmax=2202009600
kern.sysv.shmmin=1
kern.sysv.shmmni=64
kern.sysv.shmseg=16
kern.sysv.semmns=130
kern.sysv.shmall=550502400
kern.sysv.maxproc=2048
kern.maxprocperuid=512

These settings reflect the maximum size of a shared buffer. These settings assume you are running at least 2GB of RAM. If you have less RAM, these settings may need to be altered. shmmax is the key setting; it is in bytes. If the machine has more memory to use, then this could be increased as well. shmall is the shmmax setting divided by 4.

Hit the Esc key

Hit Shift Q

Type wq

Hit Enter

Restart OS X after doing this. This is required to apply the changes.

sysctlThere is a sample of this file in /users/Shared/ from the install. If your machine has 2GB of RAM or more, you could move it to the right folder instead by:

cd /users/shared sudo mv sysctl.conf /etc

 

Restart OS X after doing this. This is required to apply the changes.

Step 4: PostGreSQL server backups

Once the database is set up, you will need to establish a back up frequency that is appropriate for your venue. Mostly, setting up one backup daily to the backup directory should be enough and let it run late at night.

However, it is perfectly ok to set up 2 or more daily backups while Theatre Manager is running. You may wish to do this on a high volume site and pick times like 8:00am, 1:30pm and 8:00pm, for example. Backups can run while Theatre Manager is being used.

Manual Backup

You can also do a manual backup at any time by going into Terminal and running the 'backupTM.php' file mentioned in this section, even if Theatre Manager is running. You would do this using terminal on the server by typing

php /Users/Shared/backupTM.php

based on what you had already done to configure the script using the instructions below.

This backup process only exports data from the database and creates a compressed backup file. You will need to take those backups and copy them to another machine and/or establish a backup rotation and take some offsite.

Editing the backup script

1. If you used the installer to place files into the correct location, you can skip to Step 2 in this section. If you did not, then you will need a copy of the backup script files and then:
  1. Create a directory called /Users/Shared/Backups
  2. Get a copy of the file backupTM.php and place them into the /Users/Shared directory
2. If the files are in the correct place because they were installed by the installer, then we will need to edit the backupTM.php file. Note, if you have multiple databases to backup, make a copy of this file for each database you want to backup and edit accordingly.
  1. Navigate to the /Users/Shared directory and find the 'backupTM.php' file.
  2. Right click on the file and edit with Text Edit
    edit
  3. Change the line
    $backupDB = 'TheatreManagerDemo';
    to be
    $backupDB = 'xxxxxx';
    where xxxxx is the name of the database set up in PostGreSQL. Note that the name of the database is case sensitive and must match what is seen in PGAdmin III, or what s used to log on to the database via Theatre Manager.
  4. If you wish to alter the backup location, change the path mapping in the line that is highlighted. Normally, it is not changed.
    $localFolder = '/Users/Shared/Backups';
    edit2
  5. The backup script can be set to automatically log into a remote FTP site and upload the database right at the end of the backups. If you wish to do that, set the values of $ftpHost, $ftpUser, $ftpPass, and $ftpFolder (if need be). If you do not want to do this, then leave the $ftpHost blank
    Close the batch file and save the changes.
    edit2

Test the Batch Script

1. backuprun

Test the batch file by starting up terminal and typing the highlighted command
php /Users/Shared/backupTM.php
and terminal should come back with a listing of the files being dumped. If you get errors about access denied, then there are likely issues:

  1. The backupTM.php script needs to have execute permissions. Use file examiner to fix that in Leopard. Get info should work on OSX 10.4
  2. Make sure that the local user in the pg_hba.conf file has 'trust' access to the database. You might need to enable it for 127.0.0.1/32 and/or ::1/128 if your network uses IPv6
When done and the terminal window closes, go to the /Users/Shared/Backups directory and see if there is a recent backup for your database. Note that there should be some size to the database backup. It should not be zero bytes in size. In this sample, we have the two backups of the TheatreManagerDemo. The highlighted one was made on 20080116 at 07:34:49 in the afternoon. There will be a new file here each time the backup is run.

backuplist

Creating a Daily backup Job

1. Create a timed backup for the database by going to the /applications directory and starting a program called CronniX. A copy was installed by the PostGres Setup program. CronniX is shareware and can be found at www.abstracture.de/projects-en/cronnix

scheduledTask

Only do this on the machine that has the database server on it and make sure you are logged on as the administrator.

2. Double click on the 'CronniX.app' icon (it may or may not have .app at the end). This will start the CronniX task Scheduler. On a side note, Cronnix is an interface to the Unix CRON facility. CRON has been around for a long time and is one of the task scheduling tools that is built into the unix operating system. You don't have to worry if it is on your system.... it just is.

addTask

Click the New icon on the upper left. It will open a new window with a sample script at the bottom that says:

echo "Happy New Year!"

Replace this with the same command used to start a backup in the preceding section.

php /Users/Shared/backupTM.php

Click on the expert tab and make the settings in the upper half of the screen as per the example. These settings adjust your backup schedule. For example if you want a daily 2am and 2pm backup:

  • minute is on the hour (0)
  • hour is 2am and 2pm (2,14)
  • day of month is anything (*)
  • month is anything (*)
  • day of week is anything (*)

This will effectively schedule two per day backup of your database and is the recommended backup schedule to setup.

Entries for any of the items can be like:

  • * means 'always' for any entry. If minute said 10 and hour said *, it would mean every 10 minutes, regardless of hour.
  • 1,4,7,10 means on the 1,4,7, and 10. If this was hour, then there would be 4 backups at that time. If this was day, then only on the 1st of the month, 4th of the month, etc.
  • If you wish to read about more esoteric cron settings, please refer to internet sites by googling for 'cron settings'

wizard1

Note: you can schedule backupTM to run as many times as you want during the day by changing the parameters of the one CRON job, or by creating more jobs. Once or twice per day is normally enough but you may feel that more times is better for your backup requirements on busy days.

Update or Remove PostGreSQL

If you have already installed the Postgres database engine on a server and need to update it, then follow the update steps. Removing and installing postgres will cause all data to be lost, so you must have just made a backup before starting.

These steps are valid if you are using version 9 of Theatre Manager or later.

Updating Postgres

Download the latest postgres installer from the Artsman web site. Once you have it, make sure you have done the following steps:

  1. Check the version of postgres you are running. This is in the 'About Theatre Manager' menu. Verify that the version is at least 9.1 by looking at the bottom left of the about screen. You will see your database name followed by (9.1.x). If you have version 8.3.x, 8.4.x, or 9.0.x do not attempt the upgrade process without consulting Arts Management Support.
  2. If you have version 9.1 or later, log everybody out of Theatre Manager, including web listeners
  3. Make sure you have made a backup of the database, using the procedures in the daily backup job process
  4. Once you have confirmed the backup exists and have made another copy of that in a different place (just to be safe), then follow the specific instructions for your platform.

Remember, do not attempt to try this unless you just made a backup of your database. Preferably, you should also have restored that backup on another machine for safety, logged into it using Theatre Manager to prove that you can restore a backup and that it has 100% integrity.

  1. Make sure you are running postgres version 9.1 or later.
  2. Refer to downloading the latest Mac Installer for postgres
  3. Make sure you have just made a backup of the databases in the server
  4. use terminal and PG_CTL to 'stop' the database
    a) start terminal
    b) type su - postgres
    c) provide the password
    d) type pg_ctl stop -m immediate

  5. Run the installer which will update and restart an existing PostgreSQL installation
  6. try log in to Theatre Manager afterwards

Upgrading older Versions of Postgres

If you have postgres 9.0.x (or older), the upgrade process involves some extra steps and can be done by Arts Management Support team if you are not comfortable following the steps below. These are:

  1. making a backup of the database
  2. recording the PG_HBA.CONF and the POSTGRESQL.CONF settings unique to this server
  3. stopping the server
  4. Removing the old postgres server and data directories by running the un-installer found in the /librapry/postgres/x.x directory.
  5. installing the new postgres server using the Theatre Manager postgres installer
  6. creating the new database with the owner 'TheatreManager', and using encoding "UTF8'. If the TheatreManager user is not in the database, contact support right away and do not continue.
  7. Importing the new database
  8. redoing the configuration parameters for postgres for PG_HBA.CONF and the POSTGRESQL.CONF
  9. setting up the backup job again
  10. You should peek in the /Library/LaunchDaemons folder. If you are running postgresql 9.1 or later and there are files there called

    com.edb.launchd.postgresql-8.3.plist
    com.edb.launchd.postgresql-8.4.plist
    com.edb.launchd.postgresql-9.0.plist

    Please delete those file and restart your machine. If you uninstalled the older servers properly, they should not be there. Do not delete the file corresponding to the current version of the server.

    Make sure that postgres 9.1 is still running

Removing an Installation of Postgres

  1. Stop the postgres database using the 'pg_ctl stop -m immediate' command
  2. When the server is stopped, use the un-install program in the /library/postgres/x.x directory to get rid of it properly
  3. throw out the entire folder called /Library/PostgreSQL
  4. restart the mac

Server Power Saving Settings

Additional Setup Considerations

The following settings should be made on all servers (postgres, apache and web listeners) that are installed on Macintosh.

1 Make sure to turn off all energy saving options such as prevent hard disk sleep, do not allow the CPU to go into low processor mode, etc.
2 Make sure to turn airport OFF if the Mac comes with it. Airport will cause the mac to temporarily freeze while it looks for a network to connect to - and will lock out sales while it does that.

This is done by opening the control panel, clicking on the airport interface and then clicking on the 'gear' at the bottom to select the option 'make service inactive'. If you do this, the status will go from 'off' to 'inactive'

3 Make sure to physically plug in a Monitor to the Mac -or- connect a KVM switch into it that is powered up. If you disconnect a monitor from the Mac, it will stop working as a listener and web sales appear frozen. (it is an OSX thing)
4 Turn off Spotlight Indexing on Snow Leopard using

sudo mdutil -a -i off

On Lion, use the following command

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist

This will prevent the operating system doing un-neccessary work while serving web pages. you will know if Spotlight is running on a server if you see the 'mds' application running. It can take a lot of CPU.

5 Do not use the postgres server for Time Machine backups - use the backup script and move the backups to another machine

Windows PostgreSQL Server

The following instructions are used to set up a Windows PostGreSQL server for use with the Theatre Manager application. Click if you are doing Mac or Unix setup.

The server needs to be set up on one machine and the application can be set up on as many machines as you wish.

Follow these steps if you are using the TheatreManager TM PostGresSetup installer program and you may want to bookmark this page in your browser in case you want to refer to these installation steps. If you are only installing a demo, refer to the last column for required steps.

task Description Full Install Demo
1 download the PostGres installer for Windows yes yes
2 the installation of the PostGreSQL server. Please make sure to read any caveats for the version of Windows you are using. yes yes
3 installing the demo database and the main Theatre Manager User optional  
4 configuration of the server parameters for maximizing performance in a production database yes  
5 creating a daily backup job in Windows Task Scheduler to run the backup yes  
6 Considerations for installing virus protection on the Postgresql server - please do not include the posrgres data folder. yes  
7 Turn off Microsoft disk indexing on the volume that the database is running on. yes  

Notes and Assumptions:

  • This install process assumes you have NEVER installed PostGreSQL or Theatre Manager on your computer before. If you have, you may need to refer to Updating PostGreSQL Instructions
  • You MUST turn all virus protection while running the installer (especially Norton if you are using it). Virus software always interferes with proper software installation.
  • If this installer is being used to create a demo installation, then you only really need do steps 1, 2 and 3.
  • This process assumes that you have never installed Theatre Manager or PostGreSQL on your machine. If you have already installed PostGreSQL:
    • you will be asked if you want to un-install PostGreSQL (you may want to do that and then try to re-install after)
    • you may need to remove the 'postgres' user from your computer if one exists, unless you know the password for the use.

Step 1: Install PostGres Database Server

Caution: Please read to see if this applies to your installation:

Windows Small Business Server For Windows Small Business Server, you MUST turn off 'disk quota' for all users prior to installing PostGres (and leave it off). Otherwise you may run out of space for the installer and any databases that get installed.
  1. Double-click on My Computer
  2. Right-click on C: drive (or the drive letter that Postgres is installed under)
  3. Select Properties from the popup context menu
  4. Click the Quota tab
  5. Turn OFF "Enable quota management"
  6. Click Apply
  7. Click OK
  8. Reboot your computer
VISTA or Windows 7 For VISTA/Windows 7, you may need to turn off UAC (user access control) because it is acting as a server. You can run Theatre Manager on other workstations with UAC on. To turn UAC off for a server:
  1. open the control panel
  2. click user accounts
  3. click the link that says 'turn User Control On/Off'
  4. and in the next window that shows up, turn it off
  5. reboot your computer.
DOMAIN CONTROLLER If you want to run postgres on server that is acting as a DOMAIN CONTROLLER, you will need to:
  • Log in as the LOCAL machine administrator, otherwise the database server will not install
  • If you are running 2008 server as a Domain Controller, you may need to have remote assistance to do this.
Microsoft Windows Server 2008 If you are running Microsoft Windows Server 2008, the following steps should be followed when running the installation programs:
  1. Do not install PostgreSQL using a generic user account that has Administrative privileges. Use the actual Administrator user's account for this installation process otherwise passwords for the postgres user may not get set correctly and the installation process may fail.
  2. You may need to log into the server as the "Local" Administrator account, if there is a Domain server within the network. This is required when the passwords for the postgres user are not being accepted and password security setup errors are shown during the postgres user creation process.
  3. If there is a domain server, prior to installing postgreSQL you may need to manually create the postgres user on the Domain server. During the PostgreSQL installation process we have found that it references the Domain Server's user accounts at the same time as using the "local" postgres user account. If the Domain Server does not have the postgres user account, the final step in the PostgreSQL installation process where the initialization of the database cluster happens, may fail. It appears that the "local" postgres user account is referenced for starting/stopping the PostgreSQL database, however the Domain Server's postgres user is referenced when the database cluster is first initialized.
  4. Right-Click on the installers and select "Run As Administrator" and "remove" the option to run with restricted access
  5. In some cases, the PostgreSQL installer may need be run outside of the TMPostgresSetup installer (Run as Administrator) if the passwords for the postgres user are not being accepted and password security setup errors are shown during the postgres user creation process.
XP, 2000, or 2003 There are no known caveats with XP, 2000. With Windows 2003 server, you may need to refer to the the Microsoft Windows Server 2008 - depending on how your 2003 server is configured.

Run Main TMPostgresSetup Installer

When you run the installer for the database, accept all the defaults.

Click Ok Right click on the TMPostgresSetup.exe application and use 'Run As' to begin the install. Select a LOCAL administrator as the user ID to use for the install. If a checkbox that implies "Protect My Computer" or "Run with Restrictions" is available and enabled, uncheck the box to allow the installer to run with full install privileges.

Click next
Click next
Click next
Click next This will put the actual installer files into a C:\BoxOffice directory along with all the support files needed for the rest of the steps. Note: If you have multiple drives, you may want to install the database server on a larger data drive like D:\BoxOffice

Click next
Click Yes At the and of the TM PostGres installer, you will be asked if you want to actually install the PostGreSQL database in the dialog below.

If you say yes, follow the instructions to install postgres on the next section. Alternatively, you can do this later manually by:

  • going to C:/BoxOffice
  • clicking the PostGresInstall Icon
  • Follow the instructions to install postgres.

Run Postgres Installer

Accept all the defaults on the screens that follow except the last one that references 'stackbuilder'.
Click next
Click Next

NOTE: if you wish to install PostGres on another drive instead of the C: drive, click the Browse button and select another drive.

  • If you change this, you must also change the backupTM.bat files later to refer to this other drive.
  • If you changed the install location to D:\BoxOffice, this should have already changed for you in this window

NOTE: please be aware that the standard install location depends on 32 or 64 bit version of the operating system

  • If you are using 32 bit server, the standard install location starts with C:\Program Files\PostgeSQL ..
  • If you are using 64 bit server, the standard install location stars with C:\Program Files (x86)\PostgreSQL ...
Click Next

Accept the default for the ' Account Password' for the postgres user. However, if this is a demo. In that case, please pick a user password that you remember - we suggest 'Master'.

NOTE: For a purchased version of Theatre Manager, this will be set up for you by your trainer who will use a specific AMS password for this server that should not be changed.

Click Next

Leave the Port Number as 5432 (if you change the standard port, you will also have to change it in Theatre Manager login window)

Click Next

Leave both these settings as shown.

Click Next
Click Next

You will need to wait for a bit while the database server is installed

Click Finish

Important: Uncheck the 'Launch Stackbuilder at Exit' setting. There are no additional modules to install into your database at this time.

At this time, the database should have installed successfully and should be runnning.

Load Demo Database

You will be given an option to install a demo database. If you would like to do this, click 'Yes'. It is recommended that you do.
Click Yes
Wait

Wait while a DOS window pops up and shows the progress of the demo database being imported. Depending on the performance and RAM in your machine, this could take a few minutes to finish.

  When the DOS window closes, the database server is installed, and the TheatreManagerDemo database is imported.

Step 2: Create user and import Database

Only perform this step if you did not install the demo database when installing server.

After the database server is installed, we need to create a specific user called TheatreManager and give them privileges. We also want to import a demo database. This step assumes that you have installed things into the C: drive into a directory called C:\BoxOffice. If you did not, then you will need to edit the bat files and do this step manually

1.

go to C:\BoxOffice directory. You should see some files and folders with names that look like below

2.

Double click on the 'ImportDemo' bat file that is highlighted above. This will start a DOS prompt and start the bat file running.

Note: if the server is 64 bit, then you will need to change the ImportDemo.bat' file to refer to C:\Program Files (x86).

If you altered the install directory, you will need to change the path name to point to the location that Postgres was installed in. Normally, this is just changing the drive letter.

3.

You will be asked for the password in order to create the 'TheatreManager' user. Type the password you used for the installation of the database in the preceding section. If this is a demo database install, this might have been 'master' that you used when installing the server.

Note: the password will not be echoed to you and you will not see the cursor move. There is no visual feedback that even a character was typed. You'll just have to get it right. If any of the steps are not right, you can start at the top of this step at any time.

import2

4.

You will be asked for the password in order to create a 'TheatreManagerDemo' database. Type the same password used above and elsewhere in the install instructions

import3

5.

You will be asked again for the password in order to import data into the TheatreManagerDemo database. Type the same password again and you will see a lot of lines displayed to you after that point as the demo database is imported.

step4

Step 3: Configure PostGreSQL server parameters

When you are able to connect to the database using Theatre Manager, its time to tune some of the parameters for PostGresSQL that are specific to your machine and setup.
1.

Start the PG Admin III database management application. This is found using Start Menu->Programs->PostGresSQL-> PG Admin III.

PGAdmin

If you get any helpful tips, click 'close' to get rid of them.

2.

Click on the server for this machine and login. Use the password you created when installing the database server

Double Click on the server name as per the diagram to the right Server

Type in the same password that has been used elsewhere in the install instructions. For demo database, the suggestion was 'master'.

For production databases, this wll be different.

Then click 'ok'

password

You should see a list of objects in the server.

On the 'Databases' line, there should be (2) if you have imported the database or created your own database.

 

Database
3. Click on the Databases line to begin the next step of configuration.
4.

edit the pg_hba.conf file.

Go to the Tools menu and pick Server Configuration->pg_hba.conf file. hbaconf

Edit the pg_hba.conf so that its final settings are similar to the list below below (see *** a few lines down).

edithba
The procedure for editing is done by double clicking on an empty line and typing in the proper values for your venue - one line at a time. Make sure that:

  • Enabled is checked
  • Type is 'host'
  • Database is 'all'
  • User is 'all'
  • IP Address is described as below. You will need at least the local subnet four your network. This example shows the entry for the 192.168.0 subnet
  • Method is md5 - this is the handshaking/encryption scheme used by the clients to talk to the server.
  • NOTE: for the 127.0.0.1/32 option, set the handshaking to be TRUST to allow backups to run unaided.
  • NOTE: on Windows Vista and/or if the machine uses IPv6 (the new internet IP setting standard), you may also need to set ::1/128 to also be TRUST

 

Add lines for:

  • The local subnet - as in 192.168.9.0/24
  • Other subnets that need to access the data - as in 10.1.5.0/24
  • Any single machines that must have access - as in 55.66.77.88/32 (via VPN)

At the end of the subnet, the /24 refers to a complete subnet when you want any machine on the subnet to access the database. This is what is used most often.

The /32 refers to a particular machine. If you use this option, you will need to provide the exact computer IP that you want to allow to access the database.

*** At the end, the final hba file should look similar to the list at the right. It may have more lines in it for larger venues with multiple subnets or for remote computer access.

 

 

finalhba
Once the changes are made, click the Save icon to save the changes. Then on the main menu, select File >> Reload Server. Reload
You will be asked to confirm that the changes. Click Yes. Confirm

Click the close box and you will be asked if you want to save your changes.

Click Yes.

 
5.

Edit the postgesql.conf file

Go to the Tools menu and pick Server Configuration-> postgreSQL.conf file. postgresconf

You will then see a list of properties of the database server that can be configured.

list

Unfortunately, they are not in alphabetical order, so you may need to scroll up and down to find the ones that are in the list below. We've tried to put them in the order that you will find them in the config file. (see *****)

Do not change any parameters other than the suggested ones, or unless you have been advised to do so by an expert in PostGres databases.

For any setting that is about disk space or memory, you can type 1GB, 1000MB, 1000000KB and they are the equivalent. Do not leave a space between the number and the memory amount at the GB, MB or KB otherwise postgres will not start.

To edit any one of the lines, scroll to find it and then double click on it.

editBuf

Most of the parameters will tell you something about them. The key values to edit are:

  • The 'Enabled' flag. If you want to turn a parameter on, then click enabled
  • Value - is what you want to set the parameter to. There are specific values for some of the parameters as described in the table below
  • Comment - this may exist as a description of what the parameter is.

 

***** Find and edit the parameters in the list to the right and change them to the suggested values, if they are not already set to that value.

listen_addresses This value should always = '*'
effective_cache_size This value should be roughly the amount of 'available/free' memory (always round down to the nearest 50 MB) as seen in the Task Manager or Activity Monitor without PostgreSQL running. It is good to take the reading before installing PostgreSQL.
maintenance_work_mem This value should be 50 MB for machines with 1 GB of RAM or more and 20 MB for those with less. Enter values as xx MB.
shared_buffers

This value should be 20-25% of the total system total RAM. You find this value on the task manager as the total phyiscal memory. Enter values as xx MB.

Note: if you are using 64 bit server, the current maximum for this parameter seems to be 1024MB. If you make it more than that, please check that Postgres will start up when the server is rebooted. If not, adjust this parameter so that it is 1024MB or lower.

temp_buffers This value should be 50 MB for machines with 2GB of RAM or more and 20 MB for those with less. Enter values as xx MB.
work_mem This value should be 50 MB for machines with 1GB of RAM or more and 20 MB for those with less. Enter values as xx MB.
 

Note: the best place to get memory values is from the 'Activity Monitor' on the 'Task Manager'. See an example below for what this screen looks like.

To find it, right click on the task bar and pick 'Task Manager'.

taskManager
Once the changes are made, go to the 'File' menu and pick 'Reload Server' (alternatively, use the green arrow on the toolbar that is the 3rd icon from the right).

You will be asked to confirm the changes.

Step 4: Database Backups

Once the database is set up, you will need to establish a back up frequency that is appropriate for your venue. Mostly, setting up one backup daily to the backup directory should be enough and let it run late at night.

However, it is perfectly ok to repeat the steps below and set up 2 or more backups daily while Theatre Manager is running. You may wish to do this on a high volume site and pick times like 8:00am, 1:30pm and 8:00 pm, for example. Backups can run while Theatre Manager is being used.

Manual Backup

You can also do a manual backup at any time by double clicking on the 'BackupTM.bat' file mentioned in this section - again, even if Theatre Manager is running. It is generally found in the C:\BoxOffice folder, although it may be on another drive on the database server. The location of this file is where you placed it using the instructions on the rest of this page.

This backup process only exports data from the database and creates a compressed backup file. You will need to take those backups and copy them to another machine and/or establish a backup rotation and take some offsite.

1.

If you used the installer to place files into the correct location, you can skip to step 2 in this section. If you did not, then you will need a copy of two files and then:

  1. Create a directory called C:\BoxOffice (or on D: or E: .. as appropriate)
  2. Create a directory called C:\BoxOffice\Backups (or on D: etc.)
  3. Get a copy of the files backupTM.bat and realdate an place them into the C:\Boxoffice directory (or D: etc.)
2.

If the files are in the correct place, then we will need to edit the BackupTM.bat file. Note, if you have multiple databases to backup, make a one copy of this file for each database you want to backup and edit accordingly.

Navigate to the C:\BoxOffice directory and find the 'BackupTM.bat file.

backupbat
Right click on the file and edit with WordPad or NotePad. edit

change the line

set DATABASE_NAME=TheatreManager
to be
set DATABASE_NAME=xxxxx

where xxxxx is the name of the customer database set up in postgres.

Note that the name of the database is case sensitive and must match what is seen in PGAdmin III, or what you used to log on to the database.

If you altered the install location of Postgres or the box office directory, change the drive mappings in the two lines that are highlighted. edit2

Set POSTGRESQL_PATH=C: ..... to D:
set BOXOFFICE_DIR=C:\ .... to D: etc

normally, these are not changed

Close the batch file and save the changes.  
3.

test the batch file by double clicking on the TMBackup.bat to see that it runs. You may be asked for a password. if so, enter it and you should see a bunch of feedback as the database is backed up. If you do have to enter a password, refer to #4 (below)

backuprun

When done and the DOS window closes, go to the C:\BoxOffice\Backups directory and see if there is a recent backup for your database. Note that there shold be some size to the database backup.. is should not be zero bytes. In this sample, we have the original demo and a backup made on 20070913 at 12:40:04 in the afternoon. There will be a new file here each time the backup is run.

backuplist

4

If you entered a password to make the backups run, then you need to tell the postgres to allow 'Trust' permissions for the local machine so that backups will run un-aided.

On XP, you may just need to provide trust access to 127.0.0.1/32. On Vista, you may need to provide 'trust' access to ::1/128 as well. Refer to the section on editing the pg_hba.conf. file

Creating a Daily backup Job

1.

Create a timed backup for the database by going to Start->Settings->Control Panels->Scheduled Tasks.

Only do this on the machine that has the database server on it.

If you are using vista or do not have a 'classic' view of the task scheduler, then you may wish to change the control panel view to 'classic' mode. Somehow, this just seems easier to find things.

scheduledTask

2.

Double click on the Scheduled Task icon to begin the setup process

Click the 'Add Scheduled Task' icon.

This will start the Scheduled Task Wizard.

addTask
Click Next wizard1
On the list of applications, click the 'Browse' button. wizard2

On the 'Select Program to Schedule' dialog, navigate to the C:\BoxOffice folder and click on the 'BackupTM' icon.

Then click 'Open'

PickApplicaiton

You will then have the ability to pick a frequency for the backup.

Daily is suggested, then click 'Next'

Scheduel

Pick the time that you want the backup to run. 2:00 am is as good a time as any.

Then Click Next

RunTime

Enter the password for the administrator of the machine. Note that this is not the same as the password for the postgres user

Then Click Next

RunTime

Click 'Finish' to save the job. There is no need to go to the advanced properties.

RunTime

If the task is created in Windows 7 or Windows Server 2008 the Wizard will be slightly different. When creating the Schedule Task on these platforms the option for Run With Highest Privileges must be checked to ensure the database is updated with the backup size and the vacuum process runs.

RunTime

you can schedule backupTM to run as many times as you want during the day by creating more jobs.

Once is normally enough but you may feel that more times is better for your backup requirements.

Update or Remove PostGreSQL

If you have already installed the Postgres database engine on a server and need to update it, then follow the update steps. Removing and installing postgres will cause all data to be lost, so you must have just made a backup before starting.

These steps are valid if you are using version 9 of Theatre Manager or later.

Updating Postgres

Download the latest postgres installer from the Artsman web site. Once you have it, make sure you have done the following steps:

  1. Check the version of postgres you are running. This is in the 'About Theatre Manager' menu. Verify that the version is at least 9.1 by looking at the bottom left of the about screen. You will see your database name followed by (9.1.x). If you have version 9.0.x or earlier, do not attempt the upgrade process.
  2. If you have version 9.1.0 or later, log everybody out of Theatre Manager, including web listeners
  3. Make sure you have made a backup of the database, using the procedures in the daily backup job process
  4. Once you have confirmed the backup exists and have made another copy of that in a different place (just to be safe), then follow the specific instructions for your platform.

Remember, do not attempt to try this unless you just made a backup of your database. Preferably, you should also have restored that backup on another machine for safety, logged into it using Theatre Manager to prove that you can restore a backup and that it has 100% integrity.

  1. Make sure you are running postgres version 9.1.0 or later.
  2. Refer to the overall instructions to download the latest TMPostGresSetup installer.
  3. run the TMPostGresSetup installer.
    1. This will place all the install files into the C:\BoxOffice folder.
    2. Do not install the latest version when asked by the installer
    3. Let the installer complete and quit out of it.
  4. Go to C:/BoxOffice and find the latest version of postgres. It will have a file with a name similar to the one below - with a different version number on it reflecting the latest one. As of November 2011, the current shipping vesrion will be 'Postgresql-9.1.1-1' or later.
  5. Double click on it.
  6. It will start up the installer and default most of the settings based on the existing installation.
  7. Follow the instructions and you will generally only need to use the 'next' key to continue (a few times) until the upgrade (or install) begins.
  8. At the end you will need to restart the server.
  9. Check that you can log in to Theatre Manager from the serer or any workstation.
    1. If the Postgres Service did not start, make sure that the Postgres User password (system settings or active directory) is the same as the password for the Postgres Service in the services panel
    2. If Postgres did startup, you are done.

Upgrading older Versions of Postgres

If you have postgres 9.0.5 (or any earlier version), the upgrade process involves some extra steps and can be done by Arts Management Support team if you are not comfortable following the steps below. These are:

  1. making a backup of the database
  2. recording the PG_HBA.CONF and POSTGRESQL.CONF settings unique to this server
  3. stopping the server
  4. deleting the old postgres server data directories
  5. installing the new postgres server
  6. creating the new database (owner 'TheatreManager', Encoding "UTF8')
  7. Importing the new database
  8. redoing the configuration parameters for postgres (item 4 at the top of the page)
  9. setting up the backup job again

Removing an Installation

  1. Preferred Method:
    1. Go to Setup->Settings->Control Panel->Add/Remove Programs
    2. Find the line that refers to your Postgres installation
    3. Use the remove option
    4. Delete the C:\Program Files\PostgreSQL folder to remove your database
  2. Secondary Method:
    1. Run the PostGres installer and 'uninstall' the database first, and then run the install process -and/or-
    2. Delete the C:\Program Files\PostgreSQL folder -and/or-
    3. Remove the 'postgres' user from you list of users using the admin tools -and/or-
    4. make sure that the PostGres server is not running as a service and has been removed using RegEdit

Postgres User Password

Postgres is installed using a secure password for the 'service' user under windows. It may be changed by the venue if they wish and if you do so, then you may need to:
  • Find the local 'postgres' user on the computer using the Windows Administrative tools an edit the user id. You can change the password the way you would normally change the password for any other user (and is dependant on your version of windows)
  • If you change the service password, then you must also open the 'services' control panel and find the postgres service. Change the password there as well. To confirm that you got it right, please stop and start the postgres server. if it stops and starts, its safe to bet that the server will restart on the next reboot of the server.
  • Normally, the backups are set to run as administrator using the task scheduler. However, if you altered them to run as the 'Postgres' user, then please change the password under the task scheduler as well - other wise you'll get messages that backups are not running.

Turn off Indexing and performance

On a windows machines:
  • Turn off auto-updates completely. These are something to be done manually and on a periodic scheduled basis. You do not want servers restarting in the middle of the night, nor do you want downloading to affect performance of your servers.
  • make sure to look at the properties of the drive that database is on and turn of microsoft indexing for all directories and sub directories.
  • Disable any disk quota management on the disk drive
  • turn off any virus scanning for ports used by postgres
  • turn off any virus scanning against the database directory which is usually

    C:\Program Files\PostgreSQL

  • turn off any energy saving options
  • do not use the machine for saving snapshots of files by turning off 'use shadow copies' on the appropriate drives. (This is set in the properties of the drive)

Leaving any of those on will affect performance of the server for the database

Linux PostgreSQL Server

The following instructions are used to set up a Linux PostGreSQL server for use with the Theatre Manager application. Click if you are doing Windows setup or Click if you are doing Macintosh setup.

As of Oct, 2010, the current minimum acceptable version of Postgres is 8.4.4 (or later). Theatre Manager has been tested with version 9.0 and works with the bytea_encoding set to escape (see parameters in step 4).

The server needs to be set up on one machine and the application can be set up on as many machines as you wish.

Follow these steps and you may want to bookmark this page in your browser in case you want to refer to these installation steps. If you are only installing a demo, refer to the last column for required steps.

task Description Full Install Demo
1 download the PostGres installer for Linux from Postgresql.org yes yes
2 the installation of the PostGres SQL server yes yes
3 installing the demo database and the main TheatreManager User optional yes
4 configuration of the server parameters for maximizing performance in a production database yes  
5 creating a daily backup job in using cronnix to run the backup yes  

Notes and Assumptions:

  • This install process assumes you have NEVER installed PostGres or Theatre Manager on your computer before. If you have, you may need to refer to Updating Postgres Instructions
  • You MUST turn all virus protection while running the installer (especially Norton if you are using it). Virus software always interferes with proper software installation.
  • If this installer is being used to create a demo installation, then you only really need do steps 1, 2 and 3.
  • This process assumes that you have never installed Theatre Manager or Postgres on your machine. If you have already installed Postgres:
    • you will be asked if you want to un-install Postgres (you may want to do that and then try to re-install after)
    • you may need to remove the 'postgres' user from your computer if one exists, unless you know the password for the use.

Step 1: Install PostGreSQL Database Server

PostgreSQL for a Linux implementation is the responsibility of your organization to provide the necessary expertise to install, configure, upgrade and maintain the database server.

Installing Postgresql on Linux

1. Install the PostgreSQL application.

Step 2: Create user and import Database

Installing a demo database

The database server needs a specific user called TheatreManager with specific privileges that will be assigned as the owner of each database. We also want to import a demo database. This step assumes that you have installed things into the /Users/Shared directory. If you did not, then you will need to edit the script and do this step manually

1. Go to /Users/Shared directory. You should see some files and folders with names that look like below.

Import1

2. Start terminal and change the user to 'postgres' by typing:
su - postgres
Press RETURN
and then type the postgres user's password (password will not display anything)

import2

3. Drag the script '/Users/Shared/CreateDemoDB.sql onto the terminal window. This shortcut saves typing anything.
Click into the terminal window and then press RETURN to start the command.
If it does not run, then possible issues are:
  1. You need to have execute permissions on the 'CreateDemoDB.sql' script. Use File Examiner to check or fix that (or use unix chmod commands to give permission).
  2. Make sure that postgres was configured with 'trust' permissions for the local machine.
  3. Make sure that postgres was installed into the /Library/Postgresql8 directory.
import3
4. The script will run and load up the TheatreManagerDemo database. You can modify this script to load up a customer database if necessary by editing it in BBedit or in textedit (make sure to save it as text if you use textedit - its preference, unfortunately, is to save as an rtf document). Note, any WARNING messages from the TheatreManagerDemo database creation can be ignored. These warnings are normal.

step4

Theatre Manager Application

Installing or Updating??

The install instructions are part of this section and require a link to the installer to be provided from Arts Management Systems.

If you already have Theatre Manager, please refer to the link to find out how to get the latest updater.

In either case, once you have the installer or the updater, you can follow the instructions for Macintosh or Windows.

If you are upgrading the database from version 7 or 8, you simply run the latest installer. If appropriate, this will automatically generate a random new PCI seed key and re-encrypt credit cards using that key (unless they have been previously shredded). In the process, this destroys any previous crypto keys per PCI DSS standard 3.6.

Refer to re-encrypting cards if you wish to do this manually.

Upgrading from version 6 requires upgrading the database to version 7 and then following all remaining instructions. Our PABP 1.4 certification covers this process for the few remaining venues.

Theatre Manager has never stored CVV2, Track II or any other non PCI compliant information so removal is not necessary per PCI DSS standard 3.3. Version 8 was certified PABP 1.4 compliant. This audit provided verifiability that there was no CVV2 data. Upgrades to versions beyond version 8 will not have this data.

Macintosh Theatre Manager

Now that the database server is setup and a sample database is imported, then we can install Theatre Manager on the machine. These instructions are for installing on Macintosh. If you are using a mixed environment, please refer to the Windows instructions as well.

1. Download the Theatre Manager Mac installer if you have not done so. This link is supplied upon request.
When downloading any update for Theatre Manager, please make sure your personal firewall is turned on (PCI requirement 1.4)
2. Run the TMSetup.app program and respond to all prompts as follows. Enter the user id and password of the administrator to authenticate the installer.

Click continue

Click continue

Click continue and read the licence agreement

Click 'Agree' to accept the agreement and continue

Click install

The installer will begin putting Theatre Manager into the 'Applications' folder.

Click Quit

3.

This step is only for clients installing a fully licensed copy of Theatre Manager ON A NEW MACHINE. This step may not be required for those installing a demo copy of the software or those upgrading an existing copy of Theatre Manager.

When the installation finishes, you will need to replace the serial.txt file in the Theatre Manager program files.

  1. Download the Theatre Manager serial number file if you have not done so. The link to this file is supplied upon request.
  2. Extract the serial.txt file from the serial.zip file (if it did not automatically extract) to your desktop
  3. Go into \Macintosh HD\Applications
  4. Right-Click on the Theatre Manager icon and select "Show Package Contents"
  5. Go into \Contents\MacOS
  6. Move the serial.txt file from your desktop into the \Macintosh HD\Applications\Theatre Manager\Contents\MacOS folder replacing the existing serial.txt file

4. After installation, look for Theatre Manager link on the desktop and double click on it to start it up. There will also be a file called TMPreview.pdf on the desktop that illustrates some key features of TM.
5. If you get asked to find a database, enter the IP address 127.0.0.1 below and click search. Normally, you should not need to do this as the Demo database is always assumed to be on the local machine.

If you cannot connect to the database, check the following settings:

  • make sure port 5432 is open on your machine
  • make sure that the TheatreManagerDemo database got installed by using pgAdmin3 as per the section below... then come back and try connecting again.
6. If you are running a demonstration copy of the Theatre Manager application, you will see a first time setup screen asking you for your company information. All fields except the second line of address and the web site are mandatory. After you put this in the first time, you will not see it again.

These fields are used during the demo to show how Theatre Manager verifies information for you. For example, the city, state and country you enter becomes the default country for new patrons that you may add to the database. The area code for the phone number fields becomes the default for patron entry, etc.

Notice how Theatre Manager converts what ever you type into the proper case as it tries to assist in data entry.

7. Then, if you are able to connect to the database and enter the company information, then you will see the login window below. The password for any of the users in the demo is 'master' (without the single quotes).

8. In a production environment, once connected to the database in step 5, you can run this the TMSetup file on any other machine in the network. After changing the pg_hba.conf file, and editing the serial.txt file, you should be able to connect to the database.

You will need to use the IP address of the server to connect instead of 127.0.0.1 and if you cannot connect to the server:

  • make sure port 5432 is open on the server
  • make sure that the real database is installed and setup using pgAdmin3
  • there are no firewalls blocking access
  • the pg_hba.conf ip settings are correct and the sever has been restarted

Windows Theatre Manager

Now that the database server is setup and a sample database is imported, then we can install Theatre Manager on the machine. These instructions are for installing on Windows. If you are using a mixed environment, please refer to the Macintosh instructions as well.

Note: if you are installing on 2003 Terminal Server, you may need to switch the server from 'execute' mode to 'install' mode before using the TMSetup.exe program. After installing, you may need to switch back to 'execute' mode. (This does not apply to any other version of Windows that we know of).

1. Download the TheatreManager PC installer if you have not done so. This link is supplied upon request
When downloading any update for Theatre Manager, please make sure your personal firewall is turned on (PCI requirement 1.4)
2. Run the TMSetup.exe program and respond to all prompts as follows.

Right click on the TMSetup.exe application and use 'Run As' to begin the install. Select an administrator as the user ID to use for the install. If a checkbox that implies "Protect My Computer" or "Run with Restrictions" is available and enabled, uncheck the box to allow the installer to run with full install privileges.

Click 'Ok' to see the TM installer screens

Click 'Next'

Read the licence agreement and click 'Yes'

Click 'Next'

The installer will begin putting Theatre Manager into the 'C:\Program Files' folder.

Click 'Close'

3.

This step is only for clients installing a fully licensed copy of Theatre Manager ON A NEW MACHINE. This step may is not required for those installing a demo copy of the software or those upgrading an existing copy of Theatre Manager.

When the installation finishes, you will need to replace the serial.txt file in the Theatre Manager program files.

  1. Download the Theatre Manager serial number file if you have not done so. The link to this file is supplied upon request.
  2. Extract the serial.txt file from the serial.zip file
  3. Move the serial.txt file into the "C:\Program Files\Theatre Manager" folder replacing the existing serial.txt file
4.

After installation, look for TheatreManager on the desktop or in the Start Menu and open Theatre Manager

5.

If you get asked to find a database, enter the IP address 127.0.0.1 below and click search. Normally, you should not need to do this as the Demo database is always assumed to be on the local machine.

If you cannot connect to the database, check the following settings:

  • make sure port 5432 is open on your machine
  • make sure that 'everyone' has access to all files in the 'C:\Program Files\Theatre Manager' directory
  • make sure that the demo database was installed by using PG admin III as per the section below... then come back and try connecting again.
6.

If you are running a demonstration copy of the Theatre Manager application, you will see a first time setup screen asking you for your company information. All fields except the second line of address and the web site are mandatory. After you put this in the first time, you will not see it again.

These fields are used during the demo to show how Theatre Manager verifies information for you. For example, the city, state and country you enter becomes the default country for new patrons that you may add to the database. The area code for the phone number fields becomes the default for patron entry, etc.

Notice how Theatre Manager converts what ever you type into the proper case as it tries to assist in data entry.

7.

Then, if you are able to connect to the database and enter the company information, then you will see the login window below. The password for any of the users in the demo is 'master'

8.

In a production environment, once you are connected to the database in step 5, you can run this the TMSetup.exe file on any other machine in the network. After changing the pg_hba.conf file, you should be able to connect to the database.

You will need to use the IP address of the server to connect instead of 127.0.0.1 and if you cannot connect to the server:

  • make sure port 5432 is open on the server
  • make sure that 'everyone' has access to all files in the 'C:\Program Files\Theatre Manager' directory
  • make sure that the real database is installed and setup using PG Admin III

Installing OpenSSL for Windows

Windows installs may require you to do one of the following if you get errors starting Theatre Manager. Most Windows installs may not require this step unless you have manually excluded some parts of the Theatre Manager installer.

Credit Card Authorization

Theatre Manager provides a few different mechanisms for credit card authorization, along with two modes of operating each option (schedule "C" or Schedule "D" compliance mode). All are PCI PA/DSS 1.2 verified.

It is the client's responsibility to choose an option from those below and contact a processor or aggregator to set up a merchant account. We encourage clients to first advise the Arts Management Sales Team of their choice, as we have contact information for each option that can be used to seamlessly and quickly set up the proper type of account for use with Theatre Manager.

Definitions

There is often confusion between the purpose of a bank, a processor, and an aggregator, and understanding the difference helps make sense of the authorization options available to you.

The reason that processors and banks are separate is historical. Banks started as local or regional entities in the USA. Most were not big enough to handle the infrastructure of authorizing credit cards. When cards became very popular in the 70's, they farmed out the business of authorizing cards to a processor as an economical means of providing cards to their customers without the expense of hosting large computer centres.

Processors provide the infrastructure to authorize cards and then deposit YOUR funds in ANY bank.

Paymentech Orbital™ Authorize.net™ Moneris™ Elavon™

These options for credit card authorization allow the venue to connect directly to one of the major processors in the world - and avoid installing middleware like PCCharge. Theatre Manager talks directly to the processor over a secure https connection who talks to your bank and places money in it at the end of the day. These online processors are able to manage multiple authorizations at once, making for a faster and smoother buying experience both for direct Theatre Manager users and for patrons buying online.

PCCharge™

This option requires that a middleware credit card server called PCCharge be installed on Windows machine behind the DMZ. A venue needs to set up a merchant account with one of the 15 +/- supported processors (Paymentech, Elavon and Moneris are three of them). Installation is done using the standard PCCharge™ installers following the PCCharge™ Secure Implementation Guide.

System Flow

With either type solution, the money always gets to your bank account. You enter or swipe the card information into Theatre Manager and it sends all the correct information to the appropriate service provider. The primary difference is that with the middleware PCCharge™, there are a few more potential points of failure in the communication chain - a TCP error at any point can cause Theatre Manager and the bank to see different things. It's not too critical as the difference is made obvious in the end of day process, and you can then go off and find (and correct) it. But it takes time. The following illustrates the difference in flow of the authorization. In any case, a merchant has to maintain a PCI-compliant office setup.

Advantages and Disadvantages

  Pro Con
Paymentech, Authorize.net, Moneris, Elavon
  • supports CVV2 and address verification in USA AND Canada (Paymentech and Elavon)
  • supports mutliple simultaneous credit card authorization which is more suitable for web sales, concert onsales spikes or large volume venues.
  • faster authorizations (generally under 1 second)
  • direct connection to processor (one less software component to manage for PCI compliance needed as there is no local database)
  • Always PCI compliant with no action required by you
  • for Mac only venues, no 'black box' PC is required
  • view card batches online from anywhere
  • can be set up for easier remote authorizations
  • world wide direct authorization capabilities - in 158 countries
  • small monthly fee
  • Paymentech only operates as 'card not present' (means address verification and CVV2 only)
  • Moneris is only available at this time in Canada
  • Authorize.net is only available at this time in the US
PCCharge
  • supports CVV2, address verification and sending track II information
  • connect to any number of service providers - North America only
  • does one authoriztion at a time
  • slower authorizations (approx 3 to 4 seconds)
  • user must access the PCCharge server to view batch history
  • some maintenance required to mange passwords and compress the pccw.mdb file when it reaches a threshold
  • software upgrade every 2 years to meet ongoing PCI PA-DSS compliance when Visa changes PCI requirements

Elavon Installation

Page is under construction

The information that Theatre Manager requires from your Elavon setup will be:

  • Agency ID: xxxxxxxxxx
  • Admin: xxxxxx
  • Password: xxxxxxxxxx
  • Primary URL for authorizations:
  • Port #: 443

The Agency ID, Admin ID and password will be sent to you in a document from Elavon. That document will also contain instructions for you to log in to the Elavon online gateway to activate your account.

Activating your Elavon Payment Gateway

This page is under construction

Setting Up the Theatre Manager Elavon Merchant Account

This page is under construction

Click here for detailed information on creating a merchant account in Theatre Manager.

Give a name to your Merchant Account. It could be your organization name or it could reference the merchant provider. Card use should be enabled at both box office and by the web listener (for clients using web sales). Server Software and Merchant Provider drop-downs should be populated with the Elavon options. The Agency ID from the document sent by Elavon to the client goes in the Software Type Tab.

Admin ID and Password from the Elavon document go on the Connection Info Tab. The Primary URL and Port should be populated for you. If not, make sure they match the above image.

For fraud prevention, Elavon accounts in Theatre Manager will be automatically set up to send address info and Track II data - just check to make sure your Authorization Tab matches the above image.

The Employees and Cards Tabs are populated the same as described here.

PC Charge Installation

PCCharge licensing is provided by Arts Management along with our custom PCCharge Adaptor module to support credit card authorization. The installation is done for you on site by Arts Management training staff on a machine that is inside the main network and isolated from the internet.

The installation instructions and operating manual is a downloadable PDF document. You will need to follow its PCI implementation guidelines.

During the upgrade to version 9, PC Charge must be upgraded from version 5.71 to 5.90 or later to maintain PCI PA/DSS 1.2 compliance.

Please refer to the PCCharge Setup process for everything required to setup a merchant account and any timelines suggested for new merchant accounts.

PC Charge implements user id and password authentication over SSL connections with the various service providers (generally via port 5008) to ensure compliance with PCI DSS 4.1

Arts Management does not support Global Payments as a service provider with for new installations in Canada.

Paymentech Orbital Installation

Arts Management Systems provides the Orbital Adaptor module to support credit card authorization. The installation is done for you on site by Arts Management training staff on any Theatre Manager Workstation.

Paymentech Orbital implements either user id and password authentication; or access from specified IP addresses over https connections to provide compliance with PCI DSS 4.1

Installation is quite straightforward. You would contact Paymentech using information provided by Arts Management and they create a Merchant Account for you. Money gets authorized by Paymentech as 'Card Not Present' and then deposited right to your own bank upon settlement from Theatre Manager. This account information that you are provided is all you need to set up in the merchant setup window below to provide secure credit card authorization.

Paymentech Orbital will need to provide the following 2 account setups (both are required):

  1. Orbital Virtual Terminal - uses the Orbital Gateway via a web browser to "view the transactions" that have occurred. This account setup is used during the EOD deposit process to review your transactions prior to the settlement process.
  2. Certified Connection for User ID and Password - uses the Orbital Gateway to allow authorizations to occur but not be viewed. This information is what needs to be entered into Theatre Manager's Merchant account to allow authorizations to occur.

The user ids and passwords for both of the above are completely different and should not be interchanged or confused with each other. Follow the appropriate setup steps for each.

After following the setup for both accounts, make sure to test the gateway.

Gateway Account

The Orbital Gateway Certified Connection for User ID and Password setup is obtained from Paymentech Orbital and is entered into the Setup --> System Tables --> Merchant Accounts window as below:

Software Type

The following values are set on the software type tab per the diagram below:

  • Set the server software to be Paymentech Orbital
  • The merchant provider will automatically be set for you
  • PNS number is provided by Paymentech and will need to go into the PNS/Merchant number field - enter in the PNS# (not the merchant number) for your Orbital account which is typically 12 digits and generally starts with 720000

Connection Info

The following entries are set on the Connection Info tab per the diagram below:

  • User/Server id - provided by Paymentech and is the user id for the Certified Connection gateway, not to the Orbital Virtual Terminal (they are not the same thing - the Orbital Virtual Terminal is the online interface).
  • Password - provided by Paymentech and is the password for the Certified Connection gateway. It is also not the password for the Orbital Virtual Terminal.
  • Primary URL - is always orbital1.paymentech.net/Authorize
  • Secondary URL - is always orbital2.paymentech.net/Authorize
  • Port - is always 443
  • Terminal ID - provided by Paymentech and is usually 001
  • BIN number - provided by Paymentech and is always 000002 for North American credit card processing

Employee and Card Setup

On the Merchant Setup window (see account setup), the final bit of setup is to determine which employees and which payment methods are associated with this merchant account.
  • To assign employees to this merchant account, click on the Employee tab and find the employees to assign. In a multi merchant setup situation, drag those employees that should default to use this merchant account from the same employee tab in another merchant record. While some employees may have permission to use multiple merchant accounts, viewing their name here shows the default merchant account assigned to them for charging cards. If the employee is able to use another merchant account, they will need to select it on the payment window.
  • Click on the Card tab to select which credit card payment methods are associated with this merchant account.

    If you need to have multiple merchant accounts and both are to take Visa (for example), you will need two Visa payment methods and assign one of them to each merchant account.

if you are switching from PC Charge to another merchant services provider software, you can open both merchant accounts and drag the employees from one window to the other. You can do the same for the credit card payment methods - to make the switch easy and fast.

Any future dated 'post dated payments' associated with the card you drag to another merchant provider will automatically be re-assigned to authorize on the new merchant provider card network.

Orbital Virtual Terminal

The Orbital Virtual Terminal requires:
  • User ID - provided by Paymentech and is the user id for the Orbital Virtual Terminal gateway.
  • Password - provided by Paymentech and is the password for the Orbital Virtual Terminal gateway
  • Orbital Virtual Terminal Gateway - is always accessed via a web browser through https://secure.paymentech.com/manager. This is used to verify current and past batches, look at transactions, generate reports and manage your Orbital Gateway account.

All users of the Orbital Virtual Terminal in conjunction with Theatre Manager are encouraged to download the Virtual Terminal Users Manual directly from Chase Paymentech. There is also a Virtual Terminal Quick Reference Guide available from the same site.

Orbital Virtual Terminal - Account Setting for Manual Settlement

Once you have activated your new Virtual Terminal account by logging in there is one very important setting that you need to adjust. This particular setting will adjust the behavour of your account settlement process and is vital for accurate reconciliation. You will need the following.
  • User ID - provided by Paymentech and is the user id for the Orbital Virtual Terminal gateway.
  • Password - you created after your initial access/activation for the Orbital Virtual Terminal gateway
  • Orbital Virtual Terminal Gateway - is always accessed via a web browser through https://secure.paymentech.com/manager.

    This is used to verify current and past batches, look at transactions, generate reports and manage your Orbital Gateway account.

  1. Log into your Virtual Terminal Account and from the Tab selection at the top click on Admin, then General Admin from the drop-down menu as shown in the following image.

  2. The following setting window will appear.

    Note the Auto Settle Section of the settings.

  3. Make sure the Auto Settle Time is set to NONE.

  4. Save your changes by clicking the save button at the bottom of the settings window

Testing Orbital Gateway

After setting up the Orbital Gateway in the Merchant Account setup, you will need to test that it works. The best way to do this is:
  • Find yourself in the database or create a new patron that is yourself
  • Create a new order and attempt to by a ticket
  • On the payment window, select the credit card you want to use and do a test authorization
  • If you get an authorization with a message indicating AVS match and/or CVV2 match, then the setup is correct
  • Log in to your Orbital Virtual terminal account and view the batch to see that your transaction is there
  • In Theatre Manager, void the credit card payment and then confirm in the orbital Virtual Terminal that the charge is marked as void
    • Trouble Shooting

      If you get a response that looks like it is HTML or XML and indicates that it was not authorized, then your user id/password is probably wrong (please verify), or Paymentech set up the account to require a specific IP. Contact your Paymentech representative and tell them of the issue so that they can correct it. They may put you in touch with the gateway people. The message to the Paymentech Gateway support staff is that you need to be able to authorize via user id and password (per their standard setup instructions for Theatre Manager).

Authorize.net Installation

Arts Management Systems provides the Authorize.net module to support credit card authorization. The installation is done for you on site by Arts Management training staff on any Theatre Manager Workstation.

Authorize.net implements either user id and password authentication over https connections to provide compliance with PCI DSS 4.1

Installation is quite straightforward. You would contact Arts Management to arrange the process of creating a Merchant Account for you. Once set up, funds gets authorized as 'Card Not Present' and then deposited right to your own bank upon settlement from Theatre Manager. This account information that you are provided is all you need to set up in the merchant setup window below to provide secure credit card authorization.

Authorize.net needs an account setup for authorization and one for online viewing of the account data. You can set up multiple accounts for online access the data so some people can view data and others have more access to transactions and history.

  1. Authorize.net - uses the Merchant Portal via a web browser to "view the transactions" that have occurred. This account setup might need to be used during the EOD deposit process to verify transactions if you have more than 1000 authorizations between each End of Day.
  2. Merchant User ID and Password - uses Authorize.net to allow authorizations to occur and be settled but not be viewed. This information is what needs to be entered into Theatre Manager's Merchant account to allow authorizations to occur.

The user ids and passwords for both of the above are different and should not be interchanged or confused with each other. Follow the appropriate setup steps for each.

After following the setup for both accounts, make sure to:

Gateway Account

The User ID and Password setup is arranged by Arts Management from Authorize.net and is entered into the Setup --> System Tables --> Merchant Accounts window as below:

Software Type

The following values are set on the software type tab per the diagram below:

  • Set the server software to be Authorize.net
  • The merchant provider will automatically be set for you
  • The merchant number is for use on ticket faces and for contacting Authorize.net support.

Connection Info

The following entries are set on the Connection Info tab per the diagram below:

  • User/Server id - provided through Authorize.net. The user id remains constant for the life of the account and is generally an MD5 version of your main account UserID
  • Password - the password is auto generated for you. You can change it via the online interface to generate a new 'secret' key. If you do that, you can expire your old password right away or allow both old and new to co-exist for up to 24 hours.
  • Primary URL - is always secure.authorize.net/gateway/transact.dll and is used for authorization only
  • Secondary URL - is always api.authorize.net/xml/v1/request.api and is used during the settlement process.
  • Port - is always 443

Employee and Card Setup

On the Merchant Setup window (see account setup), the final bit of setup is to determine which employees and which payment methods are associated with this merchant account.
  • To assign employees to this merchant account, click on the 'Employee' tab and find the employees to assign. In a multi merchant setup situation, drag only those employees that will use this merchant account as the default.

    While some employees may have permission to use multiple merchant accounts, viewing their name here is the default merchant account assigned to them for charging cards. If the employee wants to use another merchant account, they will need to select it on the payment window.

  • Click on the 'card' tab to select which credit card payment methods are associated with this merchant account.

    If you need to have multiple merchant accounts and both are to take Visa (for example), you will need two Visa payment methods and assign one of them to each merchant account.

If you are switching from PC Charge to another merchant services provider software, you can open both merchant accounts and drag the employees from one window to the other. You can do the same for the credit card payment methods - to make the switch easy and fast.

Any future dated 'post dated payments' associated with the card you drag to another merchant provider will automatically be re-assigned to authorize on the new merchant provider card network.

Testing Authorize.net

After setting up the Authorize.net in the Merchant Account setup, you will need to test that it works. The best way to do this is:
  • Find yourself in the database or create a new patron that is yourself
  • Create a new order and attempt to by a ticket
  • On the payment window, select the credit card you want to use and do a test authorization
  • If you get an authorization with a message indicating AVS match and/or CVV2 match, then the setup is correct
  • Log in to your Online Merchant Account account and view the batch to see that your transaction is there
  • In Theatre Manager, void the credit card payment and then confirm in the Online Merchant Account that the charge is marked as void
    • Trouble Shooting

      If you get an authorization response that looks like it is HTML or XML and indicates that it was not authorized, then your user id/password is probably wrong (please verify it).

      If is still doesn't work after verifying it, log in to the Online Merchant Account and

      • click on 'Account' button at the top.
      • Click on the MD5 hash at the middle of the screen
      • Get a new MD5 hash for your account and put it into the setup screen under the password
      • Try authorize a card again

      If an error occurs during the initial part of settlement, you may not have the 'Transaction Details API' enabled. If this occurs, log in to the Online Merchant account and then

      • click on 'Account' button at the top.
      • Click on the 'Transaction Details API' link
      • Click 'Enable Transaction Details API' button if it is not already enabled

      If issues persist, contact Arts Management and let us know of the issue so that we can help get it corrected.

Allowing refunds through Theatre Manager with Authorize.net

In order to process refunds in a separate batch from the original transaction (which is how most refunds occur), clients will need to download Authorize.net's Extended Credit Capabilities form:

http://www.authorize.net/files/ecc.pdf

Once the form is filled out and faxed back to Authorize.net, clients will be able to process refunds through Theatre Manager within hours.

Note: This is only for processing refunds in a separate batch, after the End of Day deposit has been done for the original charge. In cases where the card is to be refunded before settlement, users should instead Void and Delete the payment in Theatre Manager. Then the tickets can be refunded to clear the order balance that will be created when the payment is voided. There is no additional setup required through Authorize.net in order to process voids. For more information about voiding charges in Theatre Manager, click here.

It is also important to note that the ECC form will allow users to run a refund in any amount to a card without matching up the refund amount to the original charge. Because of this, there are a couple of important considerations:

  • Clients may want to limit who can do refunds in Theatre Manager through their employee access settings.
  • Clients may also be cautious with whom the Virtual Gateway login and password is shared as users could run refunds directly from within that interface.

Enabling Transaction Details API in order to settle during End of Day

There is a setting inside the Authorize.net Virtual Terminal that will need to be enabled in order for Theatre Manager users to settle batches using the End of Day Wizard.
  1. Log into your Authorize.net account
  2. Select the Account button at the top right of the toolbar
  3. Choose Settings from the Menu at the left
  4. Select the Transaction Details API option under Security Settings
  5. You will be prompted to enter your secret question/answer that you set up when you created your account. Then click the Enable Transaction Details API button
  6. You will be taken back to the main Settings screen. To check that the settings have taken effect, go back to Transaction Details API
  7. When enabled, your screen shows you an option to Disable as below (do not do this).
  8. You will now be able to settle through the Theatre Manager End of Day Wizard. For more information about the Wizard, click here.

Setting the Sweep Time for Settlement

As explained here, Authorize.net sweeps (or settles) all transactions once a day to the client's bank account. This Sweep Time, or Transaction Cut-Off Time, is set directly in the Settings for the client's Authorize.net account.
  1. Sign in to the Authorize.net interface
  2. Choose the Virtual Terminal option at the left

  3. Choose the Transaction Cut-Off Time option under Business Settings.

  4. You'll see the current sweep or settlement time in the middle of the page (3:00 PM PDT in the example). Change the time using the drop down choices at the bottom of the page and click Submit. Our recommendation is to set this time sometime between 12AM and 4AM local time.

Moneris Installation

Moneris eSelectplus Payment Gateway

Contact your Moneris support representative to have your account setup. Their eSelectplus is the product/account type to use.

You will also want to have Moneris add-on CVV verification to your account at the time of account set-up. Theatre Manager uses the CVV code on a credit card for security and for your (and your patrons') security.

The information that Theatre Manager requires from your Moneris setup will be:

  • Merchant Account Number: xxxxxxxxxx
  • Store ID: xxxxxx
  • API Token/Password: xxxxxxxxxx
  • Primary URL for LIVE authorizations: www3.moneris.com/gateway2/servlet/MpgRequest
  • Port #: 443
  • ECR Terminal ID: 66xxxxxx

The merchant account number, Store ID and ECR Terminal ID will be sent to you in a document from Moneris. That document will also contain instructions for you to log in to the eSelectplus gateway to activate your account. Once you do that, you can obtain the API Token that will be required by the Theatre Manager merchant account setup.

To Test the Gateway:

You can use specific values for testing when setting up the gateway to ensure the connection is valid.

These values are open for general testing from all sources - so you may see more than just your test transactions in the virtual gateway.

The following values will enable you to enter the test environment for the gateway:

  • Merchant Account Number: 700000208782
  • Store ID: store1
  • API Token/Password: yesguy
  • Primary URL for TEST authorizations: esqa.moneris.com/gateway2/servlet/MpgRequest
  • Port #: 443
  • ECR Terminal ID: 66002173

Activate the Moneris Account And Obtain the API Token

To activate your eSelectplus account and get the API Token:

  • Log into www.eselectplus.ca
  • Click Activate My Store
  • You'll be asked to verify the information sent to you in the document from Moneris (merchant account number, Store ID)
  • You'll then be asked to create a Username and temporary password. The Username will need to be something memorable that can be shared among folks in the office who will have access to the Moneris Virtual Terminal online. The temporary password is a one-use password that will be changed upon the first log-in.
  • Future log-ins will require the Username, Store ID, and permanent password that you will set up using the one-use password. Make sure that information is stored somewhere safe in your office and shared among the appropriate staff. Arts Management will not have access to that information if it is lost.
  • Once logged into the account online, you should plainly see the API Token. Copy and paste that into a document to store/send to Arts Management along with the info sent you by Moneris so that we may assist setting up the merchant account in Theatre Manager.
  • If you do not see the API Token, in the Moneris Virtual Terminal go to Admin > Store Settings and the API Token will be displayed at the top of the page

Note:The API Token above has been removed for security. Where the gray square appears, a combination of upper-case and lower-case letters and numbers will comprise your store's API Token.

Changing the eSelectplus Account to Manual Settlement

By default, your eSelectplus account will be set to manually settle each night between 10 and 11PM Eastern time.

To alter this setting:

  • Log into the eSelectplus Virtual Terminal
  • Go to Admin > Store Settings
  • Scroll down the page until you see the Batch Close selections
  • Change the radio button to the Manually Close option:

Setting Up the Theatre Manager Merchant Account for Moneris Accounts

Once the Moneris account has been activated and all the information from this list has been obtained, the Merchant Account in Theatre Manager can be set up. Click here for detailed information on creating a merchant account in Theatre Manager.

The Merchant Number from the document sent by Moneris to the client goes in the Software Type Tab.

Store ID, API Token and ECR Terminal ID from the Moneris document and from the online account (API Token) go on the Connection Info Tab. The Primary URL and Port should be populated for you. If not, make sure they match the above image.

On the Authorization Tab, be sure to uncheck Send address/zip box. Moneris does not use AVS by default (it's an account add-on). If a test charge results in a "no permissions for avs_info error," unchecking this box will address the error.

The Employees and Cards Tabs are populated the same as described here.

Regenerate the API Token

This process should only be undertaken in consultation with both Moneris Support and Arts Management Support. The API Token must match the Theatre Manager merchant account setup in order for credit card processing to work.

Moneris Support may advise you to re-generate the API Token for your store in certain circumstances or for security reasons. If you are advised to do so, please contact support@artsman.com for instructions on changes within the Theatre Manager merchant account.

USB Credit Card Swipes

Theatre Manager supports using USB credit card swipes - which effectively are a replacement for keyboard input. The user swipes a credit card into the USB reader which translates it into keyboard input - exactly as if you typed the data.

Installation is easy - just plug it into your computer.

It works by reading the card information, including the track II information into Theatre Manager. Theatre Manager encrypts the credit card. It forwards the track II information to the credit card company and then promptly forgets about it - Track II data is never retained in Theatre Manager per PCI DSS requirements. A number of credit card companies use Track II information as proof that the cardholder is present and may adjust discount rates. Note also that they adjust rates for full address verification, CVV2 verification and other factors - making it equivalent to Track II authorization.

Paymentech Orbital is only 'card not present'. That means Track II information is never send to them, even if the credit card is swiped using a USB reader. The card #, plus address and CVV2 are more important and will provide competitive discount rates. In this case, a USB swipe becomes only an efficiency tool for data entry rather than a need for proving card present.

Any computer that has a USB credit card reader attached to cannot be allowed to connect to the internet with direct access for browsing.

The reason for this protection is that the 'bad guys' have created viruses that are keystroke loggers. If your machine is infected, it will send every keystroke to the 'bad guys' and this is one easy way for them to compromise all credit card information.

Schedule C/D Compliance - Self Assessment Questionnaire

The Self Assessment Questionnaire (SAQ) is a self-validation tool for merchants who, because of transaction volume or other criteria, are not required to do on-site assessments for PCI DSS compliance. The SAQ includes a series of yes-or-no questions for compliance. If an answer is no, the organization must state the future remediation date and associated actions. In order to align more closely with merchants and their compliance validation process, the SAQ was revised and now allows for flexibility based on the complexity of a particular merchant’s or service provider’s business situation (see chart below). The SAQ validation type does not correlate to the merchant classification or risk level. Source: PCI 1.2 quick reference guide

The PCI council has established 4 levels for merchant compliance; schedules 'A', 'B','C' or 'D'. You can use the table below to determine the level that applies to your organization below.

Theatre Manager can easily achieve schedule 'C' or 'D' compliance. Schedule 'A' and 'B' are far more difficult to achieve because of the definitions that the PCI council provide - essentially you must do paper processing of credit card and or use older, dial-up only, stand-alone terminals. Any merchant with walk up ticket sales of any volume and/or the faster stand alone internet terminals automatically default to Schedule 'C' as the minimum possible level based on the PCI definition.

Because of the inherent nature of the ticketing business has a combination of walk up, phone and/or internet sales, Theatre Manager (or any other ticketing system for that matter - hosted or non-hosted) needs to ensure that a vendor has their choice of Schedule 'C' or 'D' compliance - since the others are not possible and are intended to help small volume mom and pop corner stores be compliant through manual processing.

  • Schedule "C": means that Theatre Manager will store the credit cards in 3DES format and then render the cards useless by shredding them during batch settlement in the end of day process after which they are no longer required for voids. If you do not want credit card information onsite, please select this option along with Paymentech Orbital or Authorize.net as the merchant services provider.
  • Schedule "D": means that you wish to store some or all credit card data in 3DES encrypted format for a period of time. Possible uses are for recurring credit card transaction for monthly donations. If you chose this option, you can also chose how long to store data for previously authorized cards. After this 'Retention Period', all credit cards are shredded doing a deposit (end of day process) unless still required for a future post dated payment, or it has been specifically marked as retain permanently under the patron record.

  • Schedule "A": means that credit card information is never touched, stored or processed within an organization. This is not possible for any organization with walk up ticket sales that might include payment by credit card.
  • Schedule "B": applies to two types of merchants. Those who do not use electronic processing and write credit card slips by hand could apply to this level. Also, those that use stand alone DIAL UP terminals to process credit cards could also apply. DIAL UP means that the standalone POS terminal is not connected to a processor until an authorization is required. Any merchant with fast authorization through internet connectivity cannot apply for Schedule 'B' compliance - even with stand alone terminals.

Shredding Credit Cards

Theatre Manager can implement either Schedule "C" or "D" for the SAQ - the choice is yours. You can define a retention period for credit card information in Theatre Manager on n the System Preferences on the PCI Security Tab screen before it is 'shredded' per PCI DSS standard 3.1

Notes:

  • A shredded card means that it will be stored in the database as '#### **** **** ####'. This renders the PAN useless for all purposes. However, given the first 4 and last 4 digits of any card, you can still search for the patron.
  • Schedule "D" compliance with about 120 days of retention is sufficient for most venues, especially if you are using post dated payments or may have to deal with refunds for cancelled events.
  • Paymentech Orbital is the recommended mode of authorizing credit cards because it is one less instance of storing card information onsite. Using Paymentech and schedule "C" setting effectively means that cards will be onsite for the duration of the transactions.
  • Using PCCharge and schedule "C" setting effectively means that cards will be onsite for the duration of the day.

Reencrypting Credit Cards

Credit cards stored in a database must be encrypted using a key that is distinct to the venue per PCI DSS standard 3.6. This must occur:
  • Immediately after the initial implementation and data conversion has taken place
  • on a minimum of an annual basis. If the procedure is not invoked manually, it will be done automatically during any upgrade.
  • if there is any suspected security breach at the organization

To change the cryptography of credit card information at any time:

  • Log in as Master User
  • Go to the System Preferences->Security Tab
  • Click 'Change Card Encryption key' button at the bottom left

You will see a dialog similar to the one below that asks you to confirm the step and the reasons why the step is required. Click 'Yes' to continue.

Some notes about this process:

  • Theatre Manager will generate a completely random a 40 character key to use as half of the encryption key process that will be unique to the venue and re-encrypt all cards in the database.
  • This encryption key will not be known to the user and will not be known to Arts Management
  • You can still use theatre manager while this process occurs to sell tickets and take credit cards.
  • This process should be performed at least annually.
    • A venue will be reminded to do it after 350 days
    • If it is not done, within the required time frame, then it will automatically occur during any upgrade that occurs 350 days since the last time the venue's encryption key was changed
  • It should be performed at any time you suspect a security breach to any part of your network (make sure you also address whatever the security breach might have been).

Apache Server

For PCI compliance, the Apache web server must be installed in a DMZ and separated from the rest of the network so that card holder data would never be stored in the DMZ.

This can be accomplished in a number of ways and can be done with one or two routers. This depends on the features in the router and ability to program it. The actual installation of Apache is described for Macintosh and Windows. While unsupported, it is possible to do it on Linux if you have the skill set to build apache and compile our module yourself.

Generally, the best approach is to have a single router that is capable of supporting a machine in a DMZ and creating rules that isolates the Apache web server in a vlan separate from the other machines on the network, with rules that specify the traffic that is allowed:

If possible, try and keep the apache machine on the same subnet as the other machine, even if it is in a different vlan in the router setup. This supports bringing new machines on as web listeners at a moments notice far easier because internally, they are all on the same sub net.

The second option is to have physically separate routers - which means the Apache server will have a different subnet range than the web listeners in the Office Network. It means that you will need to do some extra work:

The diagram below shows the differences between the two options.

Web Listener Settings in Company Preferences

You need to tell Theatre Manager web listeners where to find the apache server. You do this in company preferences >> Apache Server tab.

This is done once on initial setup. However if you change your internal IP subnets, you will need to make changes within Theatre Manager to reflect the new IP addresses.

There are two ways to set up the apache server. Using either a single DMZ or dual routers.

If the apache server is on the same subnet (in a DMZ) as the web listeners, then all you do is make this one setting and it will handle multiple listeners. If you implement dual routers, then you will need to make NAT entries in the firewall if you wish to use multiple routers.

Multiple Listeners

In the Theatre Manager Apache build that is provided, there is a loadable module (mod_tm.so) that is used as the broker to distribute requests from the customer to one or more internal web listeners. The design is such that it is horizontally scaleable. If you only want one listener, the module handles that. If you have a big onsale day, then you can have more. The apache module looks for busy and/or failure of any web listener and redirects traffic as appropriate. If you shut down all web listeners, the Apache module directs traffic to a 'web site down' web page that you can customize.

In general, the average venue has two listeners in case one computer fails. While unusual, computers do die so two reduces a point of failure. Since the price of a mac mini or a PC is low, the cost of expansion is minimal. (The little bit extra cost for Macs is worth it for unix underpinnings and, no virus, etc).

Very large on sales days or very large volume venues may want more than two listeners. For example, a venue turned on 7 listeners on the day they put their summer concert season on sale to handle $1.2M in sales - using average machines around the office - and turned them off the next day.

In the diagram below, extra listeners are simply started on any machine in the Theatre Manager Lan by going to the 'Patron Sales' menu and picking Web Sales Module->Web Sales Listener

Setting up a Second Web Listener

If you are running a Mac as a web listener, you can setup two web listeners to work on one machine, effectively doubling the capacity of your web sales. Instead of using only one machine for one web listener, you can use one machine as TWO web listeners. This requires setting up a second user on the Mac, and running one web listener under each user.

If you are running OS Lion on your Mac, there are two considerations:

  • "Fast User Switching" has somewhat limited success, with most Google user sites indicating that it does not work. Fast User Switching is a key component of creating multiple Web Listeners on the same machine, therefore you may encounter difficulty under Lion. Our experimentation here has shown that it is possible, however, and have at least one site using it successfully.
  • The Library folder in Lion is now hidden. You can unhide it easily, however, as outlined in this web page.

General Installation Steps

For Web Listener 1

Step Purpose
Step 1 Alter the Port Forwarding Range for Web Sales on the router.

Typically, the Web Listener "listens" for all traffic on port 5111. This means that all traffic coming from the Apache server will be funneled through port 5111 to the Web Listener. Port 5111 is the traditional port if you only have a single Web Listener.

If you plan to have multiple listeners, or even single machines functioning as multiple listeners, you need to open more ports than just 5111. This will require increasing the range to include Ports 5111, 5112, 5113, 5114, etc. depending on the number of listeners need.

If you need assistance opening the ports, please contact your IT department.

Step 2 Update Theatre Manger preferences file (plist).
  1. Go to your hard drive, Users>>Your User>>Library>>theatremanager.plist
  2. Open the file using a text authoring tool such as BBEdit or TextWrangler.
  3. Add an entry for WebPort "5112"
  4. Save the file

For Web Listener 2

Step Purpose
Step 3 Create a second login account on your Mac.
  1. Click on the "Apple" icon in the upper left corner of your Mac
  2. Choose "System Preferences"
  3. Under the "System" category, choose "Accounts"
  4. If required, click the "lock" icon in the lower right and enter the Administrator's password for this machine to unlock this window
  5. Click the "+" sign in the lower left corner
  6. Add a new User, giving a name and password. The second user can be a "Standard User"
  7. Click the "Create Account" button
Step 4 Duplicate the existing copy of TM on the machine so there are 2 copies of TM (copy 1 and copy 2)
  1. Go to your hard drive, Applications>>TheatreManager and duplicate it (you may either RIGHT click on it and choose Duplicate, or highlight it, and hit Command+D)
  • You will now have TheatreManager, and TheatreManager copy
  • Rename the copy to be TheatreManager2. Subsequent copies can be TheatreManager3, TheatreManager4....
  • This copy is for the second Mac user.
Step 5 Create a shortcut on the second user account desktop for TheatreManager2.
  1. Switch to the second user by selecting it in the upper right corner of your Mac finder.

  2. Add a shortcut to TheatreManager2 on the desktop of the second user. Make sure it is TheatreManager2 and not the original Theatre Manager application. You must use the second Theatre Manager application. (Hint: if there are any shortcuts to Theatre Manager other than the TheatreManager2 application, delete them.
Step 6 Set preferences for the second user.
  1. Use the same steps as in Step 2 above to update the Theatre Manager Preferences file (plist) for the second user. Make the WebPort entry for Port 5113
  2. Each individual user account must have its own port specified. If you run multiple Macs each with multiple users, then they each must have their own unique specified port.
    • For the original Web Listener using Theatre Manager, assign WebPort 5112
    • For TheatreManager2 (Web Listener2), assign WebPort 5113
    • For TheatreManager3 (Web Listener3), assign WebPort 5114, etc.
Step 7 Enable Fast User Switching on the Mac System Prefs under Login Prefs to switch between user 1 and user 2. For more information on Fast User Switching, click here.
Step 8 Other configuration considerations.
  • Multiple Web Listener Employees should NOT be created. The original Employee can be logged into the database as many times as needed.
  • Once this configuration is complete and you can access the second user, Theatre Manager can be started and you can login as the Web Listener Employee. If the configuration is accurate the Web Listener will start.
  • Running multiple listeners on the same machine will require more RAM. Check the hardware requirements for a single listener, and multiply the RAM for the number of Web Listeners you plan to operate on that machine. For example, if you plan to have 2 Web Listeners running on one machine, and the recommended RAM for a single Web Listener is 2 GB, then your machine should be equipped with 4 GB of RAM.
  • Mac Apache Server

    Theatre Manager does not use the Apple version of Apache. It is often behind in versions and is configured specifically for how Apple Corp. likes things. Instead, Theatre Manager uses a vanilla version of Apache taken directly from the apache.org web site and compiled by us. This way, we can keep up with the latest patches as per PCI compliance and help you meet any compliance scan.

    In this example, the assumption is made the IP range of anything between the two firewalls will be 192.168.1.x. Please check with the local IT Administrator to confirm.

    Notes:

    • The instructions assume you have not started the built in apache web server for OS-X. If you are running Apples built in web server, go to the System Preferences->File Sharing and stop the built in web services.
    • This installer is intended only for OS-X 10.5.0 and greater on intel macs.
    • Make sure you turn off airport and other energy saving preferences or time wasting applications in this link.
    • Upgrading Apache from an earlier version is the similar to installing it. The following additional steps are required:
      • Stop all web listeners
      • Navigate to the /Library/Apache2 folder
      • Make a copy of the 'htdocs' and 'conf' folders on your desktop
      • Perform all the install instructions below
      • At the end of the installation of the new version, compare your htdocs folder with the new reference standard web pages and adjust as neccessary
      • replace the conf folder installed into /Library/Apache2 with the conf folder you saved on your desktop
      • Start Apache and your web listeners

    General Installation Steps

    Step Purpose
    Step 1

    apacheDownload the latest installer using TMApacheSetup.zip.

    It should automatically be placed into the software download folder and, depending on your settings, it may extract automatically. If it does not, then double click on the TMApacheSetup.zip file and it should create an executable 'TMApacheSetup.app' file like the image to the right.

    When downloading any update for Theatre Manager, please make sure your personal firewall is turned on (PCI requirement 1.4)

    Step 2 Double click on the TMApacheSetup to start the install. If you are asked if you want to run this file because it was downloaded from the internet, please do so.
    Step 3 You will be asked to authenticate the installer. Please type the user name of a person with administrative rights to this machine along with the password.

    Step 4 When you see the splash screen, please click continue.

    Step 5 Click continue on the license page. Feel free to read it if you wish.

    Step 6 When the confirmation appears indicating that you have read the licence, please click 'Agree'

    Step 7 You are now ready to install Apache on the mac. Click the Install button

      The progress bar will monitor the installation process.

    Step 8 When the end of the install occurs, click the 'quit' button.

    Testing and Configuration Steps

    Step 9 To begin the process of configuring Apache:

    • Go to the Apple menu
    • Open the system preferences
    • and click on the 'TM Apache' icon
    NOTE: if you see an old icon with a blue feather labeled 'apache' in the control panels in addition to the new one, please right click on it and delete it.

    Step 10 If the Apache preference pane does not open to the 'Status', tab, click the status tab.

    1. Click on the 'Start' button. You may be asked to enter the password of a user with administrative rights.
    2. The 'status' should change to 'Running' in the middle of the screen. If it does not, then click the 'Start' button one more time and the status should change to 'Running'. It is fairly common to have to start the server twice.

    Step 11 Test the server to see if it starts out of the box
    1. Start a web browser like Safari
    2. Type 'http://localhost/apacheindex.html
    3. The page should respond with 'It Works!' as per the picture on the right. If it does not respond like this, or it spins forever, then possible problems are:
      • You did not stop the build in OSX Apache web server
      • You need to open Ports 80 (and 443) on this machine
      • You need to restart the computer.

    Step 12

    We are now ready to configure the server for security and behaviour related items

    1. Click on the 'Configuration' tab of the Apache2 System Preference pane.
    2. Click on the 'Edit' button at the top right to edit the main Apache configuration file. You want to be very careful editing this because an invalid config file will prevent Apache from starting up.
    3. A window will pop up showing the 'httpd.conf' file.
    4. Scroll to the very bottom of the file and look for the line that says

      SetEnv TM_LISTENER_MASK'

      This allows you to describe which machines can talk to the listener.

      • the default is to allow 192.168.0.255 which means any machine behind the second firewall. If your subnet IP ranges are not the same, please change as appropriate
      • It also includes an entry for 127.0.0.1 so that the apache will listen for a web listener running on itself.
      • If you have multiple subnet's in your network, you can add as many as you wish, separated by commas.
      • If all machines on the subnet could act as web listeners, then leave the last segment of the ip address as .255 If you do this, then the servers can by and dynamic IP addresses. This is the preferred approach.
      • If you want to specify specific machines that can act as Theatre Manager web listeners, then enter a string of ip addresses for the specific machines. If this is the case, we recommend that the machines be at static dip addresses.

    5. There are two other environment variables you may wish to set:
      • SetEnv TM_WAIT_TIME is used to indicate how long Apache should wait trying to contact any web listener before sending back the page called 'TMSysBusyListeners.html. Think of this as how long you want a user to wait before they get sent to the 'we are busy' page so that they can try again. We recommend that this value be no more than 10.
      • SetEnv TM_PROCESS_TIME is used to tell Apache how long it should wait for a web listener to respond with the page requested by the user before it declares the web listener hung. Most requests take under a second. Credit card Authorization requests might take 2 or 3 seconds (Orbital) or 3 to 10 seconds (PC Charge), so a long time like 45 seconds is reasonable. Do not make it shorter than the credit card authorization time as you will get cards authorized and TM will think that they are not. If Apache detects that a web listener is hung, it send back the page 'TMsysErrorListeners.html'
    6. Save the Changes to the httpd.conf file and close it.

    Step 13

    We are now ready to configure the httpd-ssl file.

    1. Click on the 'Configuration' tab of the Apache2 System Preference pane.
    2. Click on the 'Edit' button for the SSL Configuration at the middle right to edit the SSL configuration file. You want to be very careful editing this because an invalid config file will prevent Apache from starting up.
    3. A window will pop up showing the 'httpd-ssl.conf' file.
    4. in that file, you will see the servername and email address near the top of the file.
    5. Set the servername (for example, tickets.yourvenue.org) to the ticketing domain name for your apache server.
    6. Set the email address for the primary contact person for web activity.
    Step 14 Restart Apache2

    • Click on the 'Status' tab of the system preference
    • Click 'Start' if the server was not running
    • Click 'Restart' if the server was running and just needs rertarted to obtain the latest configuration changes.

    When the status says 'running' you can go on to the next step. If it is not running check the changes you made to find the issue.

    Step 15

    If the restart of the server worked, then we need to test the apache server one more time

    1. Start a web browser like Safari
    2. Type 'http://localhost/TheatreManager/1/login&event=0
    3. You should see a page like the one on the right.

    If so, then it means that the apache module and configuration are correct. If not, it means that you may need to remove the

    /library/Apache2

    folder and start the process from the top.

     

    Step 16 Refer to any PCI consideration for installing Apache for late breaking security patches
    Step 17 Make sure to turn off airport, ensure there is a monitor, and deal with other power saving features.

    Windows Apache Server

    For the purposes of this example, assume that the IP range of the Theatre Manager network is 192.168.1.x and the IP address of the Apache server in the DMZ is 192.168.1.5. Please check with the local IT Administrator to confirm.

    Notes:

    • Note that the instructions assume that IIS is not installed, or that it is turned off, or that it is operating on different ports from 80 and 443.
    • This installer is intended for Windows 2000, 2003, 2008, XP, Vista or Windows 7.
    • Upgrading Apache from an earlier version is similar to installing it. The following additional steps are required
      • Stop all web listeners
      • Navigate to the C:\Program Files\Apache Software Foundation\2.2 folder
      • Make a copy of the 'htdocs' and 'conf' folders on your desktop
      • Perform all the install instructions below
      • At the end of the installation of the new version, compare your htdocs folder with the new reference standard web pages and adjust as neccessary
      • Replace the conf folder installed into c:\Program Files\Apache Software Foundation\2.2 with the conf folder you saved on your desktop
      • Start Apache and your web listeners

    General Installation Steps

    Step Purpose
    Step 1

    Download the latest installer using TMApacheSetup.exe and save it to the desktop

    When downloading any update for Theatre Manager, please make sure your personal firewall is turned on (PCI requirement 1.4)

    Step 2 Double click on the TMApacheSetup to start the install. If you are asked if you want to run this file because it was downloaded from the internet, please do so.
    Step 3 Click Next

    Step 4 Click Next

    Step 5 Select where you want to install the 'Installer' to.

    This part of the install is not actually installing Apache (yet). It is only placing the install files on the computer. Once they files are there, then the actual Apache installer will run.

    We recommend that you accept C:/BoxOffice as the install location because that is where we put the PostGres install files as well.

    Click Next

    Step 6 After all the files have been put in the correct location on the hard drive, you will be asked if you want to start the Apache installer at that time.

    If you wish to, click 'yes'

    If you wish to do this later, you can go to C:/BoxOffice and run the 'ApacheInstaller' link

    You will also be give the option of installing the FileZilla FTP server at the same time. This is used to let Theatre e-blasts automatically post jpegs to the apache server so that they will be visible for users. If you also want to install this, click 'Yes'. If you want to do it later, you can go to C:/BoxOffice and run the 'FileZilla installer' link

    Step 7 If you clicked 'Yes' above, you are now ready to begin the install process for Apache on the PC. Click the 'Next' button

    Step 8 On the license screen, click 'I accept the terms in the licence agreement' then click Next

    Step 9 Click Next

    Step 10 Apache needs a minimum amount of configuration. In the examples, you may just need to replace 'myserver.org' with your main domain name for your venue.

    please enter:

    • Network Domain is the name of your web site up at your ISP.
    • Server Name is the name of this server. We recommend 'tickets.myserver.org'.
    • Administrators email address.
    • If you want to change and of these later, you can do so by editing the httpd.conf file. It is easier to get them right at this time.

    Step 11 Click 'Typical' if it is not selected and then Click 'Next'

    Step 12 Select the destination.

    Please accept the defaults and click 'Next'.

    Step 13 Click 'Install'

    Apache will intall and register itself with the operating system

    Step 14 Click 'Finish'.

    If you opted to also install FileZilla, please follow the directions here and come back to continue with the rest of the Apache install.

    Final Customization Steps

    Step 15 There are some manual steps to configuring Apache on the PC

    Open up a view to the C:\BoxOffice folder where the installers were placed

    Open up a second view to the C:\Program Files\Apache Software Foundation\Apache2.2 - or wherever you installed Apache. On a 64 bit operating system like 2003 server 64 bit, this could be C:\Program Files x(86)\Apache Software Foundation\Apache2.2

    Files to move are:

    • copy the 'data' folder in it's entirety from C:\BoxOffice into the Apache2.2 folder
    • copy the 'htdocs' folder in it's entirety from C:\BoxOffice into the apache2.2 folder. You should be asked if you want to replace the existing files. Click yes.
    • open the 'Modules' folder and copy the mod_tm.so file to from C:\BoxOffice into the Apache2.2\modules folder.
    Step 16 Test the server to see if it starts out of the box. At the lower right corner of the computer, there should be an icon that looks like a pencil (its really a feather) that is red and has a green triangle in it. If it is there, you are ready to skip to the next step and test the apache browser.

    If the icon has a 'red' square in it, then click on the icon and you'll see and 'Apache 2.2 menu popup and then slide to the right and 'start' the server. If that does not work, please contact tech support as it means there is a configuration issue someplace.

    Step 17 If Apache is running, then the next step is to test the browser before making any changes to the config file.
    1. Start a web browser like Internet Explorer
    2. Type 'http://localhost/apacheindex.html
    3. The page should respond with 'It Works!' as per the picture below. If it does not respond like this, or it spins forever, then possible problems are:
      • You did not stop the IIS server
      • You need to open Ports 80 (and 443) on this machine
      • Some other service is using ports 80 and/or 443 and they need to be disabled.
      • You need to restart the computer.

    Step 18 We are now ready to configure the server for security and behaviour related items. We'll do this by copying some data from the sample httpd.conf file to the apache httpd.conf file.

    NOTE: DO NOT REPLACE THE HTTPD.CONF FILE otherwise it will not work. You must copy/paste the configuration as follows

    1. Open up the conf directory in C:\BoxOffice
    2. right click on httpd and Edit the file with 'wordpad'
    3. Highlight all the text in this file and copy it

    now in the httpd file in the conf directory in the Apache2.2

    • open the conf directory in the Apache2.2 folder
    • edit the httpd file
    • scroll to the very bottom
    • paste all the code you copied above into the end of this file

    Step 19 Scroll back up in the conf file that you just pasted the code into (the one in the Apache2.2 directory, not the one in C:\BoxOffice). Look for a series of #LoadModule commands. It will look like the picture below. Near the end of them, about 8 lines up, there is a line that says

    #LoadModule ssl_module modules/mod_ssl.so

    remove the '#' from the beginning of that line.

    Save the file

     

    Scroll down in the conf file (the one in the Apache2.2 directory, not the one in C:\BoxOffice). About 1/3 of the way through the document there is a line that says:

    #ServerName tickets.mytheatre.org:80

    remove the '#' from the beginning of that line.

    Save the file

     

    Scroll down in the conf file (the one in the Apache2.2 directory, not the one in C:\BoxOffice). About 3/4 of the way through the document the EnableMMAP information will appear. If this machine is running a 32 bit operating system make the following changes:


    EnableMMAP off
    EnableSendfile off
    Win32DisableAcceptEx

    Save the file

     

    Scroll down in the conf file (the one in the Apache2.2 directory, not the one in C:\BoxOffice). Just above the copied text for Theatre Manager there are lines that says:

    # Secure (SSL/TLS) connections
    #Include conf/extra/httpd-ssl.conf

    remove the '#' from the beginning of the Include conf/extra/httpd-ssl.conf line.

    Save the file

    Step 20 Scroll back to the bottom of the httpd file that you are editing.
    • Look for the line that says 'SetEnv TM_LISTENER_MASK'. This allows you to describe which machines can talk to the listener.
      • the default is to allow 192.168.0.255 which means any machine behind the second firewall. If your subnet IP ranges are not the same, please change as appropriate
      • It also includes an entry for 127.0.0.1 so that the apache will listen for a web listener running on itself.
      • If you have multiple subnet's in your network, you can add as many as you wish, separated by commas.
      • If all machines on the subnet could act as web listeners, then leave the last segment of the ip address as .255 If you do this, then the servers can by and dynamic IP addresses. This is the preferred approach.
      • If you want to specify specific machines that can act as Theatre Manager web listeners, then enter a string of ip addresses for the specific machines. If this is the case, we recommend that the machines be at static dip addresses.
    • There are two other environment variables you may wish to set:
      • SetEnv TM_WAIT_TIME is used to indicate how long Apache should wait trying to contact any web listener before sending back the page called 'TMSysBusyListeners.html. Think of this as how long you want a user to wait before they get sent to the 'we are busy' page so that they can try again. We recommend not changing it from the 10 seconds default.
      • SetEnv TM_PROCESS_TIME is used to tell Apache how long it should wait for a web listener to respond with the page requested by the user before it declares the web listener hung. Most requests take under a second. Credit card Authorization requests might take 3 to 10 seconds, so a long time like 45 seconds is reasonable. Do not make it shorter than the credit card authorization time as you will get cards authorized and TM will think that they are not. If Apache detects that a web listener is hung, it send back the page 'TMsysErrorListeners.html'
    • Save any changes made
    Step 21 It's now time to configure http-ssl.conf file. We'll do this by copying some data from the sample httpd-ss.conf file to the apache httpd-ssl.conf file.

    NOTE: DO NOT REPLACE THE HTTPD-SSL.CONF FILE otherwise it will not work. You must copy/paste the configuration as follows

    1. Open up the conf directory in C:\BoxOffice
    2. right click on httpd-ssl and Edit the file with 'wordpad'
    3. Highlight all the text in this file and copy it

    now in the httpd-ssl file in the extra directory in the Apache2.2/conf

    • open the extra directory in the Apache2.2/conf folder
    • edit the httpd-ssl file
    • scroll down the page till you find the SSL Cipher Suite lines
    • highlight the four lines for the SSL Cipher Suite
    • paste all the code you copied above over the current SSL Cipher Suite
    • save the file

    Now copy both the server.crt and server.key files from the C:\BoxOffice\conf folder and paste them into the Apache2.2/conf folder

    Step 22 Click on the Apache monitor icon in the lower right tray and you'll see and 'Apache 2.2 menu popup and then slide to the right and 'Restart' the server. If that causes the green triangle to go to a red square, please contact tech support as it means there is a configuration issue someplace.

    Optionally, go back through the changes that were made above to the httpd.conf file and see if you can spot the mistake.

    Step 23 If the restart of the server worked, then we need to test the apache server one more time
    1. Start a web browser like Internet Explorer
    2. Type 'http://localhost/TheatreManager/1/login&event=0
    3. You should see a page like the one on the right.

    If so, then it means that the apache module and configuration are correct. If not, it means that you may need to remove the

    C:\program Files\Apache Software Foundation

    directory and start the process from the top.

    Step 24 Refer to any PCI consideration for installing Apache for late breaking security patches

    winnt_acceptx messages in the error log

    for the vast majority of web sites using apache, everything runs just fine. If you find apache crashing (especially after installing some virus software on the windows apache) and you look at your apache error log and see messages similar to below:

    [warn] The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed

    then please find and edit the httpd.conf file as per below.

    For clarity, the lines should look like the following without any comments

    EnableMMAP off
    EnableSendfile off
    Win32DisableAcceptEx

    and make sure to stop, restart apache and test a connection to it.

    Linux Apache (Debian)

    Installing the Apache server using the Debian distribution is not officially supported by our team but it has been done successfully and works.

    Installing the module

    The following is a general set of steps to put the module in place. It is assumed that the reader has extensive linux knowledge. This assumes that you have either 32 bit or 64 bit apache 2.2 installed. This has been tested with 2.2.15.

    • download the binary file that contains mod_tm.so and tm.conf and unzip
    • Select the appropriate version of the mod_tm.so file from one of the folders in the archive depending if you are using 32 bit or 64 bit apache
    • copy the file in the previous step to /usr/lib/httpd/modules and make sure the permissions are ok. e.g. owner root:root, mode 755
    • The mod_tm module needs a "data" directory in ServerRoot, on Debian this is in /etc/apache2/data. As you don't normally want to write data into /etc the Debian way of dealing with this would be to create an /etc/apache2/data symlink pointing to somewhere more appropriate, /var/www/data, for example. So:
      • mkdir the "data" directory
      • set permissions, owner apache:apache and mode 750
      • and then create a symlink in /etc/apache2 pointing there.
    • The normal Debian way of accomodating module configuration needs is not to edit the main httpd.conf file directly but to drop a module-specific config file in /etc/apache2/conf. Put the included tm.conf file there and set permissions should be root:root, mode 644. You may also want to disable other module config files if they may interfere with TM - any file ending in ".conf" in that directory will be included in the apache configuration - so simply renaming a config file something.conf to something.conf.bak is enough to stop it being included. (Better yet remove unnecessary modules from the system using rpm or yum.)
    • Debian puts web pages in /var/www/html so download the web pages and replace the content of the htdocs directory with the downloaded pages.
    • Test the listener as per below
    • when working, add in mod_ssl and the ssl certificates to make sure it works with https.

    Testing the module

    Step 1

    Restart and test the apache server by

    1. Starting a web browser like Firefox
    2. Type 'http://localhost/TheatreManager/1/login&event=0
    3. You should see a page like the one above

    If so, then it means that the apache module and configuration are correct. You should also see at least files created in the 'data' directory that contain the state of the active listeners.

    If not, it means that you may need to look at the apache logs to determine what the issue is and/or redo the process from the start.

    Step 2 Refer to any PCI consideration for installing Apache for late breaking security patches

    Linux Apache (redhat)

    Installing the Apache server using the Red Hat distribution is not officially supported by our team but it has been done successfully and works.

    Installing the module

    The following is a general set of steps to put the module in place. It is assumed that the reader has extensive linux knowledge. This assumes that you have 32 bit apache 2.2 installed. This has been tested with 2.2.15.

    • download the binary file that contains mod_tm.so and tm.conf and unzip
    • copy the file in the previous step to /usr/lib/httpd/modules and make sure the permissions are ok. e.g. owner root:root, mode 755
    • The mod_tm module needs a "data" directory in ServerRoot, on RedHat this is in /etc/httpd. As you don't normally want to write data into /etc the RedHat way of dealing with this would be to create an /etc/httpd/data symlink pointing to somewhere more appropriate, /var/www/data, for example. So:
      • mkdir the "data" directory
      • set permissions, owner apache:apache and mode 750
      • and then create a symlink in /etc/httpd pointing there.
    • The normal RedHat way of accomodating module configuration needs is not to edit the main httpd.conf file directly but to drop a module-specific config file in /etc/httpd/conf.d. Put the included tm.conf file there and set permissions should be root:root, mode 644. You may also want to disable other module config files if they may interfere with TM - any file ending in ".conf" in that directory will be included in the apache configuration - so simply renaming a config file something.conf to something.conf.bak is enough to stop it being included. (Better yet remove unnecessary modules from the system using rpm or yum.)
    • RedHat puts web pages in /var/www/html so download the web pages and replace the content of the htdocs directory with the downloaded pages.
    • Test the listener as per below
    • when working, add in mod_ssl and the ssl certificates to make sure it works with https.

    Testing the module

    Step 1

    Restart and test the apache server by

    1. Starting a web browser like Firefox
    2. Type 'http://localhost/TheatreManager/1/login&event=0
    3. You should see a page like the one above

    If so, then it means that the apache module and configuration are correct. You should also see at least files created in the 'data' directory that contain the state of the active listeners.

    If not, it means that you may need to look at the apache logs to determine what the issue is and/or redo the process from the start.

    Step 2 Refer to any PCI consideration for installing Apache for late breaking security patches

    Upgrading the Apache mod_tm.so plug in

     
    The 1.4.2 version of the Apache Module is known to cause Apache to restart resulting in Theatre Manager's web listener crashing. This issue can be addressed by upgrading the version of the Apache Module to 1.4.5 or higher, or downgrading to version 1.2.9.

    Which to choose:

    • Version 1.2.9 will always work and uses less resources, but does not show the web stats. It is recommended for PC apache servers at this time if you observe Apache increasing the amount of memory the longer it runs.
    • Version 1.4.5 captures usage stats but may take more memory under some circumstances on windows machine.

    Steps to install the module:

    1. On the Web Listener machine, click the Stop button at the top of the web sales window.
       
    2. On the Apache machine, download the latest Apache Module file from the link below.
       
      Macintosh - 1.4.5 or Windows - 1.2.9 or Debian Linux - 1.4.4 or Redhat Linux - 1.4.4
    3. Stop Apache.
       
      For detailed steps on how to stop Apache for Mac click here.
      For detailed steps on how to stop Apache for Windows click here.
       
    4. Unzip the tmApacheModule145.zip or the tmApacheModule129.zip file that you downloaded.
       
    5. Open the unzipped folder.
       
    6. Double click on the operating system folder that matches the operating system of the Apache machine.
       
    7. Right click on the mod_tm.so file.
       
    8. Select Copy.
       
    9. Open the Modules folder.
       
      Mac: Macintosh HD\Library\Apache2\Modules
      PC: C:\Program Files\Apache Software Fondation\Apache2.2\Modules
       
    10. Right click on the white space in the Modules folder.
       
    11. Click Paste.
       
    12. When asked to replace the existing file click Replace or OK.
       
    13. Start Apache
       
    14. On the Web Listener machine, click the Start button at the top of the web sales window.
       

    FTP Access for Apache (optional)

    In Version 9.00 of Theatre Manager, clients can create form letters for eblasts containing images easier than before. When editing an eblast, any imbedded pictures are automatically placed on the FTP set prior to the eblast going out.

    To set it up, you will need to:

    • set up a special 'account' that has FTP access to the htdocs folder on the Apache server for image hosting
    • ensure the account has read/write access to the eblastimages folder
    • put those account settings into Company Preferences so that Theatre Manager knows how to put the pictures on the 'eblastimages' folder

    How it works

    A Theatre Manager user create the form letter using drag-and-drop for images. Theatre Manager recognizes all pictures in the form letter, places them on the Apache server and sends out the form letter email with the pictures as links rather than storing multiple copies of an image in the database.

    At no time does the patron have FTP access to the apache server. Likewise, the internal user should not have FTP access beyond sending pictures to the Apache Server. Since the 'account' settings are in company preferences, most Theatre Manager users should not be aware other than this 'just happens' in the background.

    Some set up is required before the new feature will function. The following pages include step-by-step instructions for setting up FTP access to the htdocs folder on the Apache server and for setting up Company Preferences inside Theatre Manager with that access.

    FTP sharing of 'eblastimages'

    Before you can utilize Theatre Manager's What-You-See-Is-What-You-Get (WYSIWYG) eblast capabilities inside Form Letters, you will need to set up FTP access to the Apache Server htdocs folder.

    Read more about the functionality in the release notes for 9.00.

    Select the instructions for the appropriate platform below.

    you are making your selection based on the type of machine (Mac or PC) that is running Apache and contains your htdocs folder (not your personal workstation).

    Mac FTP access

    How to set up a shared FTP folder for use with Theatre Manager and e-blast images on a Mac Apache Server.

    You will first have to set up a new, non-admin account on the Apache server itself. To do so:

    1. While signed in as an Administrator on the Apache server (not in Theatre Manager), go to System Preferences and choose Accounts.
    2. Click the + button below Login Options to create a new user account.
    3. In the New account window that opens, choose Standard as the type of account from the drop down at the top, then give the user a descriptive name and password that you'll remember and click "Create Account"
    4. Right-click (or control-click) on the new account in the Account list to bring up the Advanced Options context menu.
    5. Change the Home directory to: /Library/Apache2/htdocs and then click OK
    6. Next you'll need to turn on Sharing on the machine. Go to System Preferences again and select Sharing.
    7. Select the File Sharing checkbox on the left. Use the + sign to add htdocs to the list of shared folders (and other shared folders can be removed using the - sign). With the 'htdocs' shared folder selected, add the account (i.e. testblast) you just created to the list of users giving it 'Read & Write' privileges (everyone else can be read only).
    8. Select the Options button near the center of the screen. In the window that opens, in addition to the default options, select "Share files and folders using FTP" then click Done. Only 'Share file and folders using FTP' is required for email blasts and depending upon shared folder requirements within your organization, you may be able de-select the defaulted 'Share files and folders using AFP' option.

      If you are running OS Lion the option for Share Files and Folders Using FTP will not appear in the list. Check the option for Share Files and Folders Using AFP. To initiate file sharing for OS Lion open Terminal and type the following command:

      sudo launchctl load -w /System/Library/LaunchDaemons/ftp.plist

    9. Once you have updated your web pages as indicated in the release notes for 8.25.00, you will need to enable permissions on the htdocs, 1 and eblastimages folders. All three of those are in Library/Apache2
    10. Right-click (or control-click) on the htdocs folder and choose "Get Info"
    11. Under "Sharing & Permissions" at the bottom of the folder options window, click the + button to add the new account (i.e. testblast) you just created to the list of users with permissions related to that folder. Set the privileges to 'Read & Write' for that user (and for Admin), and 'Read Only' for the 'everyone' user group.
    12. Repeat Steps 9 and 10 for the 1 and eblastimages folders inside htdocs
    13. Finally, you can move to configuring Company Preferences Template Page FTP Access.

    Windows FTP (FileZilla)

    Filezilla is an FTP server that is shareware and is included with Theatre Manager Apache server so that a Theatre Manager user doing an eblast has a methodology to transfer pictures directly from Theatre Manager form letter document and to place it onto the Apache server.

    Each user does not need to know the user id and password. Theatre Manager moves the files automatically based on settings in Company Preferences.

    Step Purpose
    Step 1 Click 'I Agree' to the licence window after reading it (if you wish).

    Step 2 Ciick 'Next'

    Step 3 Click 'Next'

    Step 4 Click 'Next'

    Step 5 Click 'Install'

    Step 6 Click 'Close'

    Step 7 FileZilla server is already started. A window appears asking if you want to start the interface to the FileZilla server so that you can set up users and a path name to the 'eblastimages' folder for each outlet.

    Click 'OK'

    Step 8 This is the interface to FileZilla

    Configuring Filezilla

    Once you have installed Filezilla, you will need to add a user and shared folder (the same that you will set up in Theatre Manager's Company Preferences in this later step).
    Step Purpose
    Step 1 In the Filezilla Server Interface, click Edit and select Users

    Step 2 Click the Add button button under the Users box on the right of the Users setup. Enter a name for the user and click OK.

    Step 3 Check the box and set a password for the user in the Account Settings box in the top center of the window.

    Step 4 Select the Shared Folders option in the navigation tree on the left of the window.

    Step 5 Click Add to browse for your "htdocs" folder that contains your web pages. If you followed the apache installation instructions here, it should be at C:\Program Files\Apache Software Foundation\2.2\htdocs and then click OK.

    Give full access to all eight checkboxes to the user (Read, Write, Delete and Append access to Files, Create, Delete, List and + Subdirs to Directories).

    Step 6 Click OK at the bottom left to complete the process of adding the user and shared folder.

    After configuring Filezilla, you will need to add the user and password you created to Theatre Manager's Company Preferences following these instructions.

    Firewall Changes for FTP

    In order to allow Theatre Manager to add images to the 'eBlastImages' folder, you may need to adjust the Windows Firewall.

    At a minimum, you will need to open TCP port 21 and that may be enough.

    For some versions of Microsoft Windows (eg Windows 7), you may also need to add the FileZilla program to the list of applications in the firewall set up that are allowed to have outside access.

    Both of these changes are done by accessing Start->Control Panels -> Windows Firewall

    FTP Settings in Company Preferences

    After you have followed these instructions for setting up a shared FTP folder on either your Mac or PC Apache server, you'll need to configure the appropriate area of Theatre Manager's Company (or Outlet) Preferences.
    1. Go to Setup > Company Preferences
    2. Select the Apache tab
    3. Under Template Page Management, enter the URL of the shared FTP folder. This can be found on a Mac by looking at the Shared folder settings under System Preferences > Sharing and highlighting the File Sharing checkbox.
    4. Then you'll need to fill in the Template Page FTP Access information with the username and password for the account you created on your machine in these first steps.
    5. Click the Test FTP Button to test whether you have set things up correctly. There are two ways to tell. The first is that you will see the following message at the bottom of the Company Preferences window just under the Test FTP Button:
    6. The second way to check that everything is working properly is to look in your htdocs>1>eblastimages folder for a file named "imagetest.txt" that was placed there when you clicked the Test FTP Button:

    Edit the Hosts file

    After Apache is set up, the firewall adjusted to open the necessary ports and the web listeners running, you should be able to access your ticketing web site via the URL you used to create the SSL certificate.

    Try:

    • accessing the web site from a location outside the office to confirm it works
    • accessing the ticketing web site from one or more computers inside the office to confirm it works

    Troubleshooting access inside the office

    If you are having issues connecting to your ticketing web site while inside the office and are receiving timeouts, this is often resolved by editing the hosts file on each machine or adding an internal DNS entry to point to your ticketing web site.

    Mac's are not usually subjected to this issue. PC's inside the office frequently are because they do not always seem to be able to resolve the DNS that goes outside the firewall and back in, so you have to edit the hosts file to tell the PC how to find the web site.

    Apache PCI Compliance Settings

    Periodically, we learn of new issues that may prevent a PCI scan from completing at a venue. These will be listed here as things you may need to do in response to emerging issues. Please be sure to implement all of them.

    The date in front of the web pages below indicate approximately when the fix was released.

    Periodically, you may need to upgrade Apache to the latest version to simply eliminate some PCI scan messages (see links below). We attempt to incorporate each advisory in the latest installs where possible.

    2010-01 Improve Cipher Suite security

    Edit the extra/httpd-ssl.conf file and look for the line of code that pertains to SSLCihperSuite. Then make changes as below. You will end up commenting the existing line and adding two lines in bold.

    note: this change is included in the latest install of apache. Older sites will need to make this change.

    #
    # SSL Cipher Suite:
    # List the ciphers that the client is permitted to negotiate.
    # See the mod_ssl documentation for a complete list.
    # Updated the following Apache Core Features for PCI Compliance reasons
    # Refer to: http://httpd.apache.org/docs/2.0/mod/mod_ssl.html#sslprotocol
    # Refer to: http://httpd.apache.org/docs/2.0/ssl/ssl_howto.html
    # Synopsis : The remote service supports the use of medium strength SSL ciphers.
    # Description : The remote host supports the use of SSL ciphers that offer medium
    # strength encryption, which we currently regard as those with key lengths
    # at least 56 bits and less than 112 bits.
    # Solution: Reconfigure the affected application if possible to avoid use of medium
    # strength ciphers.
    #SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
    SSLProtocol -all +TLSv1 +SSLv3
    SSLCipherSuite HIGH:!aNULL:+SHA1:+MD5:+HIGH

    2010-01 Prevent Trace and directory listings

    If you are doing compliance scans and using windows as an Apache Server, then you may want to update to the Apache 2.2.15 (or later) if your scans are failing.

    Edit the httpd.conf file and add changes as below at the end of the file. They address some recent items that PCI security scans now look for.

    # ---------------------- to tighten security in browser ----------
    # Updated the following Apache Core Features for PCI Compliance reasons
    # Disable the TRACE/TRACK command
    # refer to: http://httpd.apache.org/docs/1.3/mod/core.html#traceenable
    TraceEnable Off

    # To enforce or deny complete folder listing
    # refer to: http://httpd.apache.org/docs/1.3/mod/mod_autoindex.html#indexignore
    IndexIgnore *

      2010-04 .DS_STORE files flagged as issues

      If you navigate the Apache htdocs folder using a Macintosh, it will leave hidden files with the name '.DS_STORE' in the directories. Those files are used by the OSX file system to remember how the window was opened and what view they should be in - a fairly convenient feature.

      The PCI guardians have determined that they do not like any hidden files in the htdocs directory as they view it as a possible attack vector - and if a PCI compliance scan finds these, it will flag you as non-compliant. The response is:

      • OSX Apache: We have created a script for you that you can run daily using cronnix that will clean out these files automatically. You will find this in the /Users/Shared directory called 'TMApachePCIScan.php'.

        Use Cronnix to create a daily job on your apache machine to run this script. It is installed as part of the Apache installer into your Applications folder'. The setup is similar to below.

      • Windows Apache: use find files to find all ".DS_STORE" files on your machine and delete them. The installation process will do this for you automatically, by they may come back if your web designer edits them.

      2010-11 FileEtag

      If you are getting messages about FileEtag in your compliance scan, you may need to add the following to your httpd.conf file. This is provided with the latest TM installers.

      Edit the httpd.conf file and add changes as below at the end of the file. They address some recent items that PCI security scans now look for.

      # To remove Inode information from ETag
      FileETag MTime Size

      2011-01 Open SSL 1.0.0d on Windows

      We have been hearing that recent Security Metrics PCI scans have identified a vulnerability in OpenSSL version 0.9.8. There is a new version of OpenSSL 1.0.0d that should be installed on MS Windows Apache server. Normally this comes as part of Apache and is installed automatically but Apache Software Foundation has not released a version as of yet.

      The remedy is to download and install an another flavor of Apache and upgrade that version of Apache to use OpenSSL 1.0.0.d or higher from Apache Haus

      NOTE: Apache 2.2.21 and OpenSSL 1.0.0d are the most recent versions available as of updating this web page on Oct 17, 2011. The respective organizations who maintain the installers for Apache and OpenSSL may release new updates at any time. It is your organizations responsibility to check that they are installing the most recent version at the time of update.

      Your options are:

      • Wait until Apache Software Foundation releases a version with OpenSSL 1.0.0d or higher
      • Install the version of Apache as outlined below
      • Have Arts Management install the version of Apache as outlined below
      • Leave things as they are for a while, knowing that a PCI test 'may' continue to indicate that the OpenSSL needs to be upgraded. After you have evaluated the risk assessment from the PCI report, you can choose to address it at sometime in the future - or - accept the risk and not upgrade at this time.

      There is a bit of work to do to perform this and takes approximately 1 hour worth of time. Web sales will need to be taken offline for approximately 5 minutes during the process -- meaning you can do this upgrade during a time when there is minimal web sales activity.

      • On the computer running as the Apache server, download:
      • The basic steps to follow are:
        • If required, install the Microsoft Visual C++ 2008 Redistributable Package and Service Packs
        • Extract the httpd-2.2.21-ssl-x86.zip files
        • Extract the openssl-1.0.0d-update-sni-x86.zip files
        • Review the two "readme_first.html" files located with each of the respective extracted folders
        • Move the httpd-2.2.21-ssl-x86.zip extracted files and place in the root c:\ level and called c:\Apache22
        • Move the openssl-1.0.0d-update-sni-x86.zip extracted files and replace the respective files in the c:\Apache22 folder
        • Delete all files in the c:\Apache22\htdocs folder
        • From the existing copy of Apache in the c:\Program Files\Apache Software Foundation\Apache2.2 folder, copy over to the c:\Apache2.2 folder:
          • \data (the entire folder)
          • \modules\tm_mod.so
          • \htdocs (the entire folder)
          • \conf\server.crt and place into the \conf\ssl folder
          • \conf\server.key and place into the \conf\ssl folder
          • \conf\server.csr (this file may not exist) and place into the \conf\ssl folder
          • \conf\ca-bundle.crt (this file may not exist) and place into the \conf\ssl folder
        • Update (DO NOT COPY) c:\Apache22\conf\httpd.conf with the required Theatre Manager information from c:\Program Files\Apache Software Foundation\Apache2.2\httpd.conf
        • Update (DO NOT COPY) c:\Apache22\conf\extra\httpd-ssl.conf with the required Theatre Manager information from c:\Program Files\Apache Software Foundation\Apache2.2\extra\httpd-ssl.conf
        • Review the httpd.conf and httpd-ssl.conf files for any additional PCI update/requirements that may need to be added or adjusted as per Theatre Manager's release notes and Theatre Manager's Apache setup configuration guide
        • Stop Theatre Manager's Web Listener(s)
        • De-install the existing application of Apache2.2 via Windows "Add/Remove Programs"
        • Install c:\Apache22 as a service
        • Go into Windows Services Window and start the Apache service
        • Start Theatre Manager's Web Listener(s)
        • Update Windows Startup folder to have it automatically start Apache Monitor upon login
        • Delete the c:\Program Files\Apache Software Foundation folder
        • Update FileZilla User settings for Theatre Manager's eblast home folder to be c:\Apache22\htdocs

        Then try your PCI scan again. We understand from the PCI council that you have approximately 30 days from identification of the problem at your venue to resolution. Select a slow day to do the upgrade as it should only take approximately 1+/- hours to complete. (as this may be your first and perhaps only time doing it, we would recommend that you allocate 2+/- hours just in case)

        If you wish to have Arts Management perform the above upgrades to your copy of Apache, please let us know and we will schedule a date/time with you. It typically takes approximately 1+/- hours to complete and is deemed a billable service.

        Some of the gotcha's you may encounter along the way are:

        • On the Apache Server, you must first install the Visual C++ 2008 Redistributable Packages
        • If you have a x64 bit machine, you still must install the x86 Visual C++ 2008 Redistributable Packages
        • If you have a x64 bit machine, you still must install the x86 version of Apache2.2
        • When editing the /conf/extra/httpd-ssl.conf file, you must also update the ServerName and ServerAdmin parameters
        • The placement of the SSL certificate location is different and is located in the c:\Apache22\conf\ssl folder
        • When attempting to install Apache as a service, if you receive "unauthorized access errors", go back and start the Command console again by Right-clicking on it and selecting "Run as Administrator"
        • When attempting to install Apache as a service, if you receive "side-by-side errors", go verify if you have installed the Visual 2008 C++ Redistributable Packages

        We have tried the following OpenSSL links, however they did not prove to be successful when using the OpenSSL 1.0.0.d upgrade with the standard installation of Apache 2.2.17

      2011-11 OpenSSL < version 1.0.0e on OSX

      This assumes that your PCI scan is failing on your OSX apache server verison 2.2.17 or later. Normally Apple updates operating system components but in the case of OpenSSL, it is compiled right into the Apache server.

      The latest version of our apache installers for OSX include openssl 1.0.0e and all you need do is upgrade to the latest version of Apache.

      Updating Apache From a Prior Version

      PCI compliance indicates that you need to update system components after they are released and/or if you fail a PCI compliance scan.

      If you wish to do this yourself, the steps are, in general:

      Macintosh Apache Server

      • Find the apache install directory. It is in /Library/Apache2
      • Save the entire contents of the htdocs folder by zipping it up, labelling it and putting it on the desktop
      • Save the entire contents of the conf folder by zipping it up, labelling it and putting it on the desktop
      • Stop the apache server by going to the control panel and stopping the server.
      • Go to the /Library directory and delete the Apache2 folder or move it to the desktop for safe keeping. IT MUST NOT EXIST in the /Library folder.
      • Download and install the latest version of Apache as per the install instructions
      • After the install has been tested and works, empty the 'htdocs' folder in /Library/Apache2 and replace it with the saved copy on the desktop
      • Re-install the SSL certificate by copying server.crt and server.key from the backup of the conf folder into the new /library/apache2/conf folder
      • If everything works, move the apache folder that was saved on the desktop earlier into the trash.

      Windows

        • Find the apache install directory. It is in C:\Program Files\Apache Software Foundation\2.2 directory
        • Save the entire contents of the htdocs folder by zipping it up, labelling it and putting it on the desktop
        • Save the entire contents of the conf folder by zipping it up, labelling it and putting it on the desktop
        • Go to startup->Control Panels->Add/Remove Programs and Remove the existing installation of Apache. You MUST do it this way to remove the services.
        • Download and install the latest version of Apache as per the install instructions
        • After the install has been tested and works, empty the 'htdocs' folder in C:\Program Files\Apache Software Foundation\2.2 and replace it with the saved copy on the desktop
        • Re-install the SSL certificate by copying server.crt and server.key from the backup of the conf folder into the new C:\Program Files\Apache Software Foundation\2.2\conf folder
        • If everything works, move the apache folder that was saved on the desktop earlier into the trash.

      OWASP and Theatre Manager

      The Open Web Application Security Project (OWASP) is a 501c3 not-for-profit worldwide charitable organization focused on improving the security of application software. Their mission is to make application security visible, so that people and organizations can make informed decisions about true application security risks. Everyone is free to participate in OWASP and all of the materials are available under a free and open software license.

      The OWASP Top 10 for 2010 is interesting reading for application developers, web site builders and end users. The internet has many good features, but it is not a safe place if you are not aware.

      Each year, the Arts Management team reviews the top 10 and, for those that are applicable, ensures that the web sales module provides a defence against the top 10 per PCI standard 5.1. Responses are posted here. Merchants should also be aware of these.

      2010 Top 10 list

        Description Thestre Manager Implementation
      A1 SQL Injection OWASP 's preferred option is to use a safe API which avoids the use of the interpreter entirely or provides a parameterized interface.

      In Theatre Manager, all web pages access the web listener using an API and each parameter is scrubbed on the way to the web listener for specific values.

      A2 Cross-Site Scripting (XSS) OWASP 's preferred option is to properly escape all untrusted data based on the HTML context (body, attribute, JavaScript, CSS, or URL) that the data will be placed into.

      Theatre Manager looks for any attempt to put javascript and other characters into a form and simply removes them. We have determined that there is no valid need to have words like <script> in a enterable fields like name or address.

      A3 Broken Authentication and Session Management Theatre Manager uses cookies for session managment. All data in the cookie is 3DES encrypted, along with a date and time.

      If the web listener notices that the cookie comes back and is an earlier time than expected, then it discards the request.

      There are no session ID's allowed in the URL.

      A4 Insecure Direct Object References Theatre Manage does not allow direct access to any object in the database through the user of an API. Users cannot retrieve data in an unauothorized way.
      A5 Cross-Site Request Forgery (CSRF) Theatre Manager does not allow access to the database except via API. It also forces a timeout for inactivity.

      At worst, a hacker taking the time and effort to put an API call into a jpeg and tricking a person buying tickets into sending that to your Web Listener might find a seat or add a ticket to a shopping cart. The key is that the impact, should it even happen, is low.

      A6 Security Misconfiguration (NEW) The primary prevention to this is PCI security scans and upgrading of Theatre Manager components on a regular basis and following any implementation notes.
      A7 Insecure Cryptographic Storage Theatre Manager handles encryption of the key card information and reommends shredding of unused data after a period of time.

      The majority of this OWASP item refers to storage, backups and a venue's internal processes.

      A8 Failure to Restrict URL Access This does not apply to Theatre Manager's web lsiteners due to the API's used to control access to the system. Accessing the limited number of web pages in the htdocs directory in a direct manner does nothing unless they are processed by a web listener. Further, all requests are send through a specialized Apache module that adds additional tokens not known visible in the browser and re-routes the URL and does some NAT translation of its own.
      A9 Insufficient Transport Layer Protection Theatre Manager web listener suggests using SSL for all traffic - which mean turning on port 443 to the apache server.

      Ensuring the SSL certificate is current is a responsibility of the monthly PCI scan process.

      A10 Unvalidated Redirects and Forwards (NEW) Theatre Manager does not use re-directs in any web page.

      SSL Certificate

      The goal of the SSL is to validate that the internet address of the Apache server is validated and secure. The existence of the SSL certificate on the apache server causes the 'lock' on the patrons web browser to turn on and encrypts all communication between the patron and your office.

      Before you can get an SSL certificate, you will need a static address for your router and a 'nice' domain name like 'tickets.yourvenue.org' that points to your firewall. Both of these are supplied by your webhosting company. The steps you will need to follow to set up an SSL and get web pages working are in the following sections.

      Static IP for Your Router

      Before you can get an SSL certificate, you will need a static address for your router and a 'nice' domain name like 'tickets.yourvenue.org' that points to your firewall.

      The static IP must be obtained first and is supplied by your ISP. It will be set up in your firewall/router so that it never changes and means that customers will always be able to find you on the internet.

      These generally cost about $10 to $20 monthly in addition to your connection fees, unless you have a business internet package - in which case you probably get one included.

      If you have a static IP and do not recall it, then open up a browser and type 'whatsmyip.org'. This asks a web site to tell you what the IP address of the outside of your router is. Alternately, you can enter the config mode for your router to determine the static IP address.

      External DNS

      You will need to ask your ISP (or sometimes the people that host your external web site) to set up a DNS record to point to your static IP address if you do not have one.

      You can think of this as a 'nice' name by which customers can find you, or if they see it in the URL area of the browser, they will be confident that they are connecting to the right web site.

      Call up your ISP (or web site hosting company) and ask them to create a DNS record for 'tickets.myvenue.com' (where myvenue is replaced by your main web site name). As an example, if your main web site is www.artsman.com, then you would like your ISP to create a DNS record for tickets.artsman.com.

      Possible DNS names that you may prefer from a marketing perspective are:
      • tickets.myvenue.org
      • boxoffice.myvenue.org
      • sales.myvenue.org
      • tm.myvenue.org
      • secure.myvenue.org
      • and if you have a mail server or other services already in your organization, we could use that as well.

      Once the DNS record has been created and is propagated to the internet (this usually happens in a few hours but can take as long as 24 hours), the next step is to purchase and install the SSL certificate.

      Buying the actual SSL Certificate

      Hard Way - Self Purchased SSL

      If you purchase your own SSL certificate from another source, you will need to install it yourself following the instructions provided to you during the purchase process and make sure it works. If you have any questions about your Self Purchased SSL certificate, contact the company from whom you purchased it for any and all assistance.

      Easy Way - Buy your SSL from Arts Management Systems

      Arts Management Systems uses 256 bit encrypted premium certificates from GeoTrust and if you wish to purchase one, please contact the sales office at (403) 536-1214. We will install any SSL certificate purchased from us and install a secure SSL logo on the checkout page of Theatre Manager.

      When you buy an SSL from Arts Management Systems, information that we will require from you in order to customize the SSL to your venue are:

      • company name (do not abbreviate, provide the full legal company name)
      • primary contact's first and last name
      • primary contact's title
      • primary contact's email address
      • primary contact's direct phone number
      • venue's legal Address, City, full State/Province name (do not abbreviate the state or province name)
      • external DNS that you set up such as tickets.myvenue.org
      • the operating system that Apache is running on (OSX, Linux, or Windows)
      • we will require an authorized administrator's email address to send the verification to and approve the request. This needs to be an email address you have the ability to check for the incoming emails. Please make sure that the email account has been set up and is available before you provide us the email account to use, or the approval email will not be delivered. With an invalid or non-working email account, the SSL certificate will not be processed. The options for the email address are below: (Select ONE of the following)
        • admin @ myvenue.org
        • administrator @ myvenue.org
        • hostmaster @ myvenue.org
        • root @ myvenue.org
        • webmaster @ myvenue.org
        • postmaster @ myvenue.org
      We will generate the SSL based on the information provided and you will receive 3 emails:
      1. An email indicating that an SSL creation request has been started.
      2. An email requiring you to confirm the information at the specified email address above. Please confirm the email (by clicking on the acceptance link within that email) and accept the SSL request.
      3. After you have confirmed email #2's acceptance link and the SSL has been processed by GeoTrust, the 3rd final email containing the actual SSL certificate information will be sent to you. Please note that this final email may arrive anywhere from 10 minutes to 12 hours after email #2 was accepted depending upon the next processing cycle by GeoTrust.
      After we have received the SSL certificate information, we will make the SSL certificate files and put it into the Apache server for you in the 'Conf' folder and verify that it works. During this final process, we will require remote access to your Apache Server and to a Web Listener to test the SSL certificate configuration with Theatre Manager.

      Open Ports 80 and 443 and Test

      Open ports 80 and 443 in the firewall and point them to the static IP address of the Apache Web Server.

      Once the firewall has been opened and the SSL certificate installed:

      1. Open up a browser
      2. Type 'https://tickets.myvenue.org'
      3. It should display a web page in the browser and turn on the lock on the browser.

      This page shows safari with the lock on the upper right turned on

      This page shows firefox with the lock on the lower right turned on

      Please check for it on your browser as appropriate.

      TroubleShooting a Web Listener

      Troubleshooting generally depends on the behaviour of the DNS within the firewall and the operating system you use. Most Mac's will easily find 'tickets.yourvenue.org' by navigating through the firewall properly. Windows machines sometimes need a helping hand.

      The best approach is to put an entry within your internal DNS server to point 'tickets.myserver.org' directly to the internal address of the apache server.

      If that is not possible, you may have to make an entry in the hosts file of each web listener that points to the apache server if the DNS does not propagate in the internal network. If the Web Listeners start up and are able to find the 'tickets.myvenue.org', you will not need this step. If they do startup but they seem to be ignored by apache very quickly, then you will need this step.

      The hosts file is located and edited as follows

      Windows c:/windows/system32/drivers/etc/hosts (or where the windows system32 directory is located)

      Navigate to this using the file system and edit it with WordPad and place an entry at the end for 'tickets.myvenue.org' that looks like the following. Replace 192.168.1.xx with the address of the machine that is the Apache Web Server that is within the DMZ

      OSX /etc/hosts

      To edit this file on the mac, open up 'Terminal'

      type cd /etc

      type sudo vi hosts

      type the administrator password to the machine

      A file should open similar to below. use the arrow keys to scroll down and edit it to look like below. Replace 192.168.1.xx with the address of the machine that is the Apache Web Server that is within the DMZ.

      type 'I'

      This will put you in edit mode

      Type the text as required to add the line to the end. When the changes are made hit the 'ESC' key.

      Hold the SHIFT key down and type Q

      Type WQ

      Adjusting Security Settings

      There are some settings in Theatre Manager that a venue must examine during installation and may need to be changed for PCI standard 8.5 compliance.

      If you are upgrading from a demo version of TM, some of these settings were optional to facilitate the purposes of a demo and need implemented for a production system.

      Minimum Password Settings for All Users

      For PCI compliance, a user MUST:
      • be required to enter a password to access Theatre Manager -and-
      • have their own user id and password to track access within the database -and-
      • ALSO have a unique logon to access the computer prior to accessing Theatre Manager that is PCI/DSS compliant.

      Ensure that the minimum recommended settings are met and increase the security as you see fit. If the minimum recommended settings change, Theatre Manager will automatically update the current settings to any more current minimum during any upgrade.

      The steps to increase security strength are:

      • Log in as Master User (this System Administrator account is only person with access to System Preferences)
      • go to 'Setup->System Preferences'
      • click on the 'Security' Tab. The minimum recommended settings are below.
      • Click on the 'Use PCI Card Industry Standards' to reset all password settings to the minimum acceptable standards.
      • Make any adjustments you wish to the policies such as requiring longer passwords, or increasing the minimum number of unique passwords before a repeat password can be used.
      • Close the window to save the changes.

      Changing User ID's

      (optional step)

      If you wish to implement login by user id in addition to password, the change all the user id's in the system to a scheme that is suited to your network security needs. Since you will be logging in with a User Id and Password, it can be a good idea to make user names more difficult to determine.

      To change user names and password settings, repeat the following steps for all users EXCEPT the Master User:

      • go to Setup->Users & Access->Employee List
      • Click the 'search' icon (the magnifying glass) or hit enter to see a list of users
      • Double click on the name in the list to change
      • Click on the 'Access' Tab
      • Click on the 'Access Id' field and change that to something suitable for the employee
      • Make sure the Logon Level selection is either 'No Access' if they are not allowed to use the system -or- 'Normal' if they are allowed to access the system.
      • If the user can log in, click the 'Set Password' button and assign them an initial random password (or have the user type in their own). It is not necessary to know or record each users password - in fact we recommend that you do not write those down. If a user forgets their password, you can always re-assign a new one here.
      • If user's access to parts of the system is similar to another users, you can use the 'Copy Access' button to make them like each other. You may wish to create a template for some of the important job functions that make copying easier.

      Verify Credit Card Access

      You must at least visit the 'Functions' tab and make sure that any of the privileges that say 'Credit Card' in the second column are all unchecked to start with. Then enable those that you wish the user to have. Creating any new normal user will default to a 'deny-all' setting per PCI DSS 7.2

      All existing users can be easily reset to the 'deny-all' at one button click (see below)

      Click on the 'Data' and 'Functions' tab and make any changes to the employee's access that you wish. To reset this employee to the standard 'deny-all' access to credit cards, click the lock on the toolbar. Two you may consider overriding relatively safely are:
      • 'Allow empty CID even if required for credit card payments'. If this is unchecked, the user must ask the customer for a CID/CVV2 number on the back of the credit card if it is required for the credit card type or by the processor. If your service provider does not accept or check CVV2 data, you may need to check this. You may also want to check this for at least one of the box office supervisory personnel who can then provide an operator over-ride to any other user if need be.
      • 'Able to Search for Patron using a card number'. This should be checked for a finance position or a box office supervisor so that a patron can be found when all we are given is the credit card number - such as in the case of charge backs. When searching for a patron by credit card, only the first 4 and last 4 digits in the care are required for a search.

      You can do reset all employees with non-administrative access at one time by selecting them all on the list of employees and clicking the 'PCI' button.

      Change the Master User Password

      There should only be one 'Master User' account.

      Per PCI requirements, this password for this account must be changed at the initial installation of Theatre Manager by the venue so that it is something unique to the venue.

      No user of Theatre Manager is required to have these privileges in order to use the system - except to create another user account. If any user is set as a Master User for the duration of the installation process, those privileges should be revoked per PCI compliance.

      • Find any user with Master User access using Setup->Employees and Access->Employee List
      • Click on the 'Access' tab
      • Make sure that the 'Logon Level' is 'Master User' for only one administrative account. Change all others to normal users.
      • Click 'Set Password' and give this special user a unique password. You will be asked to confirm the current password before you are allowed to change the password.
      • You may want to log out of theatre manager and then log back in as the special 'Master User' account before continuing - just to make sure you have the user id and password set.
      • This is one user id and password combination that you do wish to record on a paper and put in a sealed envelope in your safe with instructions to open under emergency only.

      Editing/Upgrading Web Pages

      A release of Theatre Manager may require that some of the web pages be changed or added to the htdocs folder. Theatre Manager is designed so that the web pages are fully functional 'out of the box' (with a couple exceptions noted below). In many cases, only the style sheets need changed in order to create a custom look and feel for your venue.

      The intent with Theatre Manager web sales is that a venue can customize the pages in any way they wish since they are generally only HTML based pages that can easily be edited with a WYSIWIG editor like Adobe Dreamweaver as long as the basic <form> submission are not altered, or are replaced by the equivalent API call using javascript.

      The release notes for Theatre Manager will provide a list (and file) indicating which web pages have changed, and if possible, what the general intent of the change was. To implement these changes, you need to:

      This can be done by hand or you can use automated tools to help identify exactly what has changed. We recommend using some automated tools.

      Useful HTML editing tools

      Any page can be changed if you wish.

      While you are testing your web site, or your customers are using web sales, you may see text on a page that you think could be worded more suitably for your venue. The best way to find the page to change is to do a multi-file text search to find a portion of the text.

      You would search within all the files in the HTDOCS folder on the Apache server. Good options for multi-file text searching are:

      We recommend Dreamweaver as it is a probably the easiest HTML editing tool. It can be purchased for about $25.00 for non-profits through www.techsoup.com. Notepad++ is free. TextWrangler is also free from the makers of BBedit. BBedit costs about $40 and is a programmer type tool - but we really like it.

      Comparing HTML Pages with BBedit/TextWrangler

      On a Macintosh, you can use a tool like BBedit or Text Wrangler 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)

      You can do it either on a subset of pages provided with each upgrade to identify the key differences, our you can compare your entire htdocs folder on the Apache server with the most recent htdocs folder supplied by Arts Management. In either case, the general approach is:

      • Make a copy of your current htdocs folder on your apache server and copy it to your computer. This is so you edit the web pages and test them in a test environment
      • Obtain the full set of web pages, or the subset that is part of the current release. 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 or TextWrangler (or similar file comparison tool) to compare all files in a folder

        Start BBedit or TextWrangler and then go to Search->Find Differences. In the find differences window that opens, put the names of the old and new htdocs folders as per the picture below and click Compare.

      • Decide which changes should be merged into your web pages. 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.

      • If there are new files, copy them into the right place
      • Test the web pages before moving them into the live web site
      • Upgrade Theatre Manager to match the version of the web pages
      • Start the web listeners
      • Do a final test purchase using the live web pages

      Comparing HTML Pages with WinMerge

      On a Windows PC, you can use a tool like WinMerge to compare two sets of web pages and move changes from one page to another.

      You can do this either using a subset of pages provided with each upgrade to identify the key differences, our you can compare your entire htdocs folder on the Apache server with the most recent htdocs folder supplied by Arts Management. In either case, the general approach is:

      • Make a copy of your current htdocs folder on your apache server and copy it to your computer. This is so you edit the web pages and test them in a test environment.
      • Obtain the full set of web pages, or the subset that is part of the current release. 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 WinMerge (or similar file comparison tool) to compare all files in a folder

        Start WinMerge and pick the File->Open menu. You will be asked to pick the folder for the left side (pick the old htdocs directory) and the folder for the right side (pick the new htdocs directory).

      • In the list window that opens up, it tells you which files are on only one folder and which files have a difference. Double click on a file with a difference and a second window opens with a visual indicator of where the difference is. Click on the difference to see it (see top window in the picture below).

        Decide which changes should be merged into your web pages. This shows you the actual differences in the files highlighted in orange. Repeat this decision making for all files that are different.

      • If there are new files, copy them into the right place.
      • Test the web pages before moving them into the live web site.
      • Upgrade Theatre Manager to match the version of the web pages.
      • Start the web listeners.
      • Do a final test purchase using the live web pages.

      Redirecting a link to a specific page in the Web Listener

      It is straightforward to link your main web site to a specific page within the Theatre Manager web listeners if you construct a link using the following syntax:

      http:// tickets. yourserver. com [/TheatreManager/1/login[&action=0|number][&lang=XX][&tmsource=YYY]]

      where the meaning of the parts of the above syntax is:

      • http:// tickets. yourserver. com is the direct link to the Theatre Manager web server. It is the only part that is mandatory.
      • /TheatreManager/1/login - if supplied, is used by the apache server to direct the user to the theatre manager web listeners and begin the sales process. The '1' is replaced by your outlet number in a multi-outlet site. In most cases, it is '1' corresponding to the '1' folder within the standard 'htdocs' web page structure.
      • &action=0|number - 'action=' is replaced by one of the specific words as shown in the sections that follow (eg action might be 'event' or 'pass' or 'donation'). If you use 0 as the parameter, the user will be able to start at the selection process for 'action'. If you use a specific number as the parameter, then the user will be placed directly at the start of the sales process for the 'action'. For ticket sales web page access, there are some other options as described below.
      • &lang=XX - if you build a multi language web site, you can direct the user to begin using a language you specify. &lang=EN is the default. There must be a WebPagesXX folder for each language you want to support
      • &tmsource=yyy - which is an additional parameter that can be used to detect the web site referrer and attach it to a shopping cart. The idea with this is that you might tie the source to an eblast, another web site, your own site, some tourism source, etc. The value 'yyy' is attached to a shopping cart and once a value is in the cart, it cannot be changed. This means that the first source (or referrer) is used. Note: the source can also be set using a cookie if you want instead of a command line argument.

      The following are specific examples of links that can be added to your main website:

      Standard Access to Web Sales

      The general starting place for all sales might be a link like like the one that follows which is placed on your main web site:

      Click here to purchase tickets (all available events) - https://tickets.myserver.com which actually lands on the index.html page. The index.html page is usually set up to redirect the user automatically to the list of events. The same can be accomplished by directly coding a link with login&event=0 similar to

      https://tickets.myserver.com/TheatreManager/1/login&event=0.

      Starting at the Login Window

      To force the patron to go to the logon widow:

      Click here to log in https://tickets.myserver.com/TheatreManager/1/login

      Purchasing Tickets to a specific Event

      If you wish to have links beside each event that you advertise on your web site:

      Click here to purchase tickets to Event #1 - https://tickets.myserver.com/TheatreManager/1/login&event=297
      Click here to purchase tickets to Event #2 - https://tickets.myserver.com/TheatreManager/1/login&event=298
      Click here to purchase tickets to Event #3 - https://tickets.myserver.com/TheatreManager/1/login&event=294
      Click here to purchase tickets to Event #4 - https://tickets.myserver.com/TheatreManager/1/login&event=295
      Click here to purchase tickets to Event #5 - https://tickets.myserver.com/TheatreManager/1/login&event=296

      where the event value is defined by Theatre Manager as the unique event number for each of the different events you have. The event number is found by:

      • going to Setup > Events
      • clicking the Search icon to populate the Event List
      • The far left column of the Event List shows the event number for each item in the list:

      Purchasing Tickets to a specific Genre for an Event

      If you wish to have links for genre's of events you can use a link like the following - please note that you must specify &event=0 with the &genre=yyy parameter. These are the same ones that are defined for ticket trove and cannot be changed by the venue. You can find the values for yyy in the 'event genre' code table.

      Click here to purchase tickets to a specific genre. https://tickets.myserver.com/TheatreManager/1/login&event=0&genre=200

      Purchasing Tickets to a Performance

      If you have an event that only has a single performance, you can go directly to selling that performance (bypassing the event selection) by:

      Click here to purchase tickets to GalaDinner - https://tickets.myserver.com/TheatreManager/1/login&performance=1568

      where the 'performance' value is defined by Theatre Manager as the unique performance number.

      To find the performance number:

      • go to Setup > Events
      • click the Search icon to populate the Event List
      • Double-click an Event to select it
      • In the Event Setup Window that will open, click on the Performance Tab to see the list of Performances for that Event
      • The far left column, labeled Perf #, shows the unique performance number for each performance of the Event:

      Purchasing Tickets to a Venue

      If you have a venue description that has different type of events, you can go directly to selling any performance in that venue by:

      Click here to purchase tickets for this venue - https://tickets.myserver.com/TheatreManager/1/login&venue=1

      where the 'venue' value is defined by Theatre Manager as the unique venue map number.

      To find the venue map number:

      • go to Setup > Venue Maps
      • In the Venue Maps List, the far left column is labeled Map #:

      Purchasing Tickets to a Subscription

      If you have a subscription and want to go there directly, you can have: Click here to purchase subscriptions - https://tickets.myserver.com/TheatreManager/1/login&subscription=1

      where the 'subscription' value is defined by Theatre Manager as the unique subscription number for that subscription package.

      To find the subscription number:

      • go to Patron Sales > Season Reservations > Setup Season Packages
      • Populate the Season Package list by clicking the Search icon.
      • The subscription number for each package is in the far left column labeled Seq #:

      Purchasing Tickets to a Specific List of Events

      If you have a specific list of events, or date range of events, you can create a customized search Click here to purchase tickets to Event - https://tickets.myserver.com/TheatreManager/1/login&event=0&search=XXXXXX

      where the XXXXXX is a valid sql search of Theatre Manager's database to retrieve events for sale. Do NOT place quotes around the entire search parameter that you are creating. For example:

      • P_SEQ IN (x,y,z,...) where x, y, z are valid P_SEQ (event) numbers - find these 3 specific events
      • PB_SEQ IN (x,y,z,...) where x, y, z are valid PB_SEQ (performance) numbers - find these 3 specific performances.
      • TM_SEQ=a where a is a valid TM_SEQ (venue) number - find all performances in venue 'a'
      • TM_SEQ IN (a,b,c) where a, b and c are valid TM_SEQ (venue) numbers - find all performances in venues 'a', 'b', and 'c'
      • P_SEQ IN(x,y) or TM_SEQ=a this will give you the 2 events 'x' and 'y', along with ANY performance in venue 'a'
      • PB_PERFORM_DATE>=date '2008-09-15' and PB_PERFORM_DATE<= date '2008-10-31' This will give you all performances between Sep 15 2008 and Oct 31 2008

        Refer to comments within htdocs/1/WebPages/TMTickets.html for more examples of searching for performances within the Ticketing Page.

        See the relevant sections above on where to find event, performance and venue numbers within Theatre Manager.

      Purchasing a Donation

      This will take you right to the donation page to allow the patron to select which campaign they want to donate towards

      Click here to make a donation - https://tickets.myserver.com/TheatreManager/1/login&donation=xx Where "xx" represents the Seq # associated with the Donation Campaign that will appear as the default in the drop-down menu on the web page. To find the Seq # for the Donation Campaign:

      • go to Setup > System Tables > Donation Campaigns
      • Right-click on the Donation Campaigns List and select Preferences > Change Columns
      • In the Manage Column Display Window, locate Seq #, select it by checking its box, and drag it to the place in the list you'd like it to appear or use the green up and down arrows to move it
      • Once the location is set, click Update Columns for the change to take effect
      • Click the Search icon in the Campaign List Window to see the Donation Campaigns and reference the Seq # for each

      Purchasing a Gift Certificate or Pass

      This will take you to the pass/Gift Certificate/merchandise page.

      Click here to purchase a gift certificate - https://tickets.myserver.com/TheatreManager/1/login&pass

      Going Directly to the Mail List page

      This will take you to the mail list page.

      Click here to purchase subscribe or be removed from a mail list -https://tickets.myserver.com/TheatreManager/1/login&maillist

      Keep in mind, with this link, the user MUST log in first before their mail list options will appear.

      Which Web Page to edit and HTDOCS Structure

      The following sections provide information on:
      • how to find the web page that you want to edit
      • the structure of the htdocs directory
      • the general outline of the content of a web page
      • and the meaning of some internal variables found on most web pages

      Finding the web page to Edit

      There are a number of web pages so the trick can be how to find the one to edit if you want to customize one. There are a couple of techniques to use:

      Multi File Search

      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.

      File Names

      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:

      • TMTemplates - contains all the row definitions for any html file that includes a table. We've tried to name them according to what they do. For example: rowticketevent is for rows in the TMticket web page.
      • TMGifs - contains all images and style sheets
      • TMMaps - contains all files that show the maps during the sales processes
      • TMVenues -contain all files that describe what a venue is
      • TMEvent - contains all files that describe what the event is about
      • TMPass - contains all files that describe the purpose of a pass/gift certificate/membership
      • TMSubscripition - contains descriptions about season packages
      • TMCampaign - contain descriptions about donation campaigns
      • TMFee - contain descriptions about ticket fees

      General Web Page Content

      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.

      Hidden Text/Comments

      There are several types of texts within the code of each page that use the comment tags (i.e. <!-- BLANK -->).

      The Disclaimer
      <!-- comment: Created by: Arts Management Systems Limited - Calgary Alberta Canada (403) 536-1214 http://www.artsman.com This web page integrates with Theatre Manager to support online ticket sales and donations and provide a single intregrated database for online and inhouse sales for arts and entertainment venues. If you see this and want to use for your own venue, please check us out at http://www.artsman.com Alter this source code as you see fit to suit your needs, but if you do, Arts Management Systems is not responsible for supporting or debugging errors that may occur -->
      This string must be kept in each page. Removing this string will remove responsibility for supporting or debugging errors.
      Sets of <include> tags throughout the pages. For example:

      <!--#include virtual="TMtemplates/tmnavButtons.html" -->

      These tags allow you to include the code from an outside file into any given page. In this case, the <include> tag is set in each page to insert the navigation buttons contained within the tmnavButtons.html file.

      Although the <include> tag looks like a comment tag, it is read in by the page.

      Each page will include the TMtemplates/tmnavButtons.html page listed above as well as the TMtemplates/pleaseWaitMessage.html and the TMtemplates/tmFooter.html.
      The TMtemplates/pleaseWaitMessage.html displays warning messages regarding actions taken on the pages. The TMtemplates/tmFooter.html will pull the footer information directly from Theatre Manager.
      There are also two other pages in the TMtemplates folders that are called using the <include> tag: tmContact.html and tmContactHours.html.
      these pages contain the venue's contact information with the latter also containing the hours of operation. These pages are included on any webpage that would display the venue's contact information, such as on the TMsys404 page.

      Messages

      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.

      Javascript

      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.

      Variable Theatre Manager Fields

      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 X when viewed as source code, will identify what the string is linked to.

      <FORM ACTION="<field>F_HTML_FIREWALL</field>online" METHOD=POST>
      This string is linked to the F_HTML_FIREWALL, which is the URL found in Web Server URL field of Setup >> Company Preferences under the Apache tab.

      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="<field>F_HTML_IMAGE_SERVER</field>">
      This string is linked to the F_HTML_IMAGE_SERVER, which indicates the location of the images to be referenced within the pages. The string adds to the F_HTML_FIREWALL listed above. When the source code for the pages is viewed it appears as:

      <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.

      <field>F_HTML_PAGE_MESSAGE</field>
      This string is the page message sent by Theatre Manager to update any information relative to the current web page.
      <field>F_HTML_MONTH_LIST</field>
      <field>F_HTML_YEAR_LIST</field>
      <field>F_HTML_EVENT_LIST</field>
      <field>F_HTML_PERFORMANCE_LIST</field>
      These strings extract information relative to the month, year, event, etc. of the current information for the web page.

      Click here for Internal Variable Theatre Manager Fields.

      Button Names

      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.

      <input name="btnGetEventRange" type=submit value="Update Performance List">
      The names of each button name="btnGetEventRange" must be kept as they were when the pages were provided. The values of the buttons value="Update Performance List" may be changed as needed.

      Click here for information about Navigation Buttons.

      Cascading Style Sheets

      The style sheets are used with the Web Pages are: stylePages.css and styleButtons.css. They are linked to each page with strings.

      rel="stylesheet" href="TMgifs/styleButtons.css" type="text/css">
      k rel="stylesheet" href="TMgifs/stylePages.css" type="text/css">
      ePages.css contains the font and background styles for the text of the site.
      eButtons.css contains the font, background and border styles for the form buttons in the site. This style sheet works in conjunction with a javascript function to create the customizable rollover effects.

      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.

      Key Internal Variable Fields

      Within the code for each page are strings that appear within ## ## when the source code is viewed without a connection to the database. These fields are internal Theatre Manager fields, and should never be altered.

      These are the different types of internal Variable Theatre Manager 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_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_EMAIL_ADDRESS - The current logged in user's Email Address
      F_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_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.

      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_ADDRESS1 - Patron's primary Address Line 1
      C_ADDRESS2 - Patron's primary Address Line 2
      C_ALT_EMAIL_ADDR - Spouse's email address
      C_CITY - Patron's City
      C_COMPANY - Patron's Company
      C_EMAIL_ADDR - Patron's email address
      C_FAX_PHONE - Patron's Fax
      C_FIRST_NAME - Patron's First Name
      C_FIRST_NAME2 - Spouse's First Name
      C_HOME_PHONE - Patron's Home phone
      C_INITIAL - Patrons Middle Initial
      C_INITIAL2 - Spouse's Middle Initial
      C_LAST_NAME - Patron's Last Name
      C_LAST_NAME2 - Spouse's Last Name
      C_PASSWORD - Patron's Password
      C_POSTAL_CODE - Patron's Postal Code
      C_PROVINCE - Patron's province
      C_SEQ - Patron number
      C_WEB_LAST_LOGON - Patron's date of last login
      C_WEB_PREFER_HTML_LIST -
      C_WORK_PHONE - Patron's work phone
      C_WORK_PHONE2 - Spouse's work phone


      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

      Standard 'htdocs' Web Page Structure

      The following pages are contained directly within the htdocs folder most commonly located on the Apache server on a PC at:

      C:\Program Files\Apache Software Foundation\Apache 2.2

      and on a Mac at:

      Library\Apache2

      It is worth noting that at minimum, the pages linked here will need edits in order to bring web sales online.

      The "1" Folder

      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.

      Each company must have its own web listener.

      The pages beyond this folder mark the true beginning of the custom look of a client's online store.

      eblastimages Folder

      Description:

      • The folder that stores images from a form letter for use with eblasts sent from within the program. Images are sent via FTP from the database to this folder on the Apache machine. For information on how to set up FTP access to your htdocs and eblastimages folder, click here.

      Location:

      htdocs/1

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      • Not Applicable

      TMsysBusyListeners.html

      Description:

      • This page is referenced by Apache when the web listeners are too busy with requests to respond with the desired page in the online sale.
      • The page counts down and attempts to access the online sales site again once it reaches zero. page.
      • If the patron does not wish to wait for the page to finish counting down they can click a link that will reload the page they were previously accessing.
      • This page can be avoided by starting Theatre Manager on a machine within the network and logging is at the web listener. This will start another listener to respond to requests the existing Web Listener(s) are too busy to handle.

      Location:

      htdocs/1

      Able to Call Page(s):

      • Will reload the last page visited within the online ticketing site.

      Called By Page(s):

      • The httpd.conf file within Apache

      Page(s) Referenced:

      TMsysBusyListenersNorefresh.html

      Description:

      • This page is referenced by Apache when the web listeners are too busy with requests to respond with the desired page in the online sale.
      • The patron can click a link that will call the page referenced in the index.html page.
      • This page can be used as an alternative to the TMsysBusyListener.html page. It is recommended this page be renamed to TMsysBusyListener.html and the existing page with the same name be renamed. This will avoid having to edit the httpd.conf file.
      • This page can be avoided by starting Theatre Manager on a machine within the network and logging is at the web listener. This will start another listener to respond to requests the existing Web Listener(s) are too busy to handle.

      Location:

      htdocs/1

      Able to Call Page(s):

      Called By Page(s):

      • The httpd.conf file within Apache

      Page(s) Referenced:

      TMsysErrorListeners.html

      Description:

      • This page is displayed when a response takes longer then indicated acceptable in the httd.conf file of Apache.
      • A longer then recommended response time could be caused by several things. Ultimately a request was sent to the Web Listener and a response was not made within the allocate time frame.
      • Contains a reference line at the bottom of the page that should be edited to include the companies ticketing domain.
      • This page can be avoided by ensuring communication between the Web Listener and Apache has not been blocked/interrupted or by restoring the default web page for any pages recently changed.

      Location:

      htdocs/1

      Able to Call Page(s):

      Called By Page(s):

      • The httpd.conf file within Apache

      TMsysNoListeners.html

       

      Description:

      • This page is displayed when Apache and the Web Listener had been communicating and there are now no active Web Listeners or Apache can not communicate with the Web Listener over the network.
      • Contains a reference line at the bottom of the page that should point to the companies main web page once edited.
      • If the online sales is scheduled to be down for a period of time due to network issues this page should be edited to reflect the information the patron will see during the outage.For example: Our online ticketing is currently unavailable, please contact the box office for assistance.
      • This page can be avoided by logging in to Theatre Manager as a web listener within the network or by correcting any network issues that may be preventing communication between Apache and the Web Listener.

      Location:

      htdocs/1

      Able to Call Page(s):

      • The companies main web page when configured correctly.

      Called By Page(s):

      • The httpd.conf file within Apache

      WebPagesEN Folder

      The parent folder containing the bulk of the html pages that make up the online store. The "EN" used in the example assumes English language pages.

      MultiLanguage Considerations

      Clients who wish to have multilingual pages will need to do four things:

      • You will need to duplicate the WebPagesEN folder for each language you want to support and change the ending to be a two character language code. For example, WebPagesFR for French or WebPagesES for Spanish, WebPagesDE for German (we suggest using the ISO two character language code).
      • Translate all the web pages within the new WebPagesXX folder as required
      • edit the TMTemplates/tmnavLanguages.html to add a language and a flag to the navigation for each language you with to support.
      • In company preferences on the WebListener tab, add in the language codes that you want TheatreManager to look for in the htdocs folder. That means you can put the languages in place using the WebPagesXX folder, but TM will not recognize them until you edit the company preferences.
      • Where appropriate, on the main corporate web site, you might wish to edit the links to direct to a specific page by adding the &lang=XX to the direct links.

      After a patron picks their language, the next time they log in, Theatre Manager will recall and use their personal language preference.

      TMattendance.html

       

      Description:

      • This page is designed to check patrons in and out of the venue through a web browser as opposed to directly through Theatre Manager or by hand held scanner.
      • The Used status of the ticket is updated within the Patron's record in Theatre Manager.
      • An example of how this page functions can be found by clicking here.

      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):

      • Not Applicable

      Called By Page(s):

      • Not Applicable

      Page(s) Referenced:

      TMattendancePalm.html

      Description:

      • Contains two links designed to communicate with the Theatre Manager database for testing the web interface of the checkin and checkout process.
      • This page determines if a connectivity issue is between the hand held scanners or the network.
      • The page will need to be edited to reflect the internal IP address of the apache machine.
      • It will also need to be edited to reflect Performance sequence number(s) and Ticket number(s) that are currently setup within the database. The numbers currently listed within the page were selected from the Demo Database for Theatre Manager.
      • If the page fails after the edits are complete it indicates an issue within the network communication that will need to be addressed prior to troubleshooting hand held scanner related issues.
      • If the page is successful in it's communication and the hand held scanners do not connect it means the issue lies with the scanners and either their connectivity to the network or their setup.

      Questions and Answers:

      Q:
      A:
      ____________________________________________________________

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      • Not Applicable

      tmCampaign Folder

      The tmCampain folder contains the detail pages for donation campaigns sold within the online sales. The Default page is used only when a custom pages is not available for the campaign. It pulls the note information directly from the campaign within Theatre Manager.

      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.

      tmCampaign1.html

       

      Description:

      • This page provides a description of the donation campaign.
      • The campaign name is pulled from the External Name of the campaign from within Theatre Manager.
      • The default page pulls the description information directly from the Notes tab for the Donation Campaign setup inside Theatre Manager.
      • The title of the page includes a number that references the campaign sequence number from within Theatre Manager.
      • This is a custom page that can be edited to reflect the details of this specific campaign.

      Location:

      htdocs/1/WebPagesEN/tmCampaign

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      tmCampaign2.html

       

      Description:

      • This page provides a description of the donation campaign.
      • The campaign name is pulled from the External Name of the campaign from within Theatre Manager.
      • The default page pulls the description information directly from the Notes tab for the Donation Campaign setup inside Theatre Manager.
      • The title of the page includes a number that references the campaign sequence number from within Theatre Manager.
      • This is a custom page that can be edited to reflect the details of this specific campaign.

      Location:

      htdocs/1/WebPagesEN/tmCampaign

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      tmCampaignDefault.html

       

      Description:

      • This page provides a description of the donation campaign.
      • The campaign name is pulled from the External Name of the campaign from within Theatre Manager.
      • The default page pulls the description information directly from the Notes tab for the Donation Campaign setup inside Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/tmCampaign

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMcart.html

       

      Description:

      • Lists all items currently within the patrons online shopping cart. This includes any fees or coupons associated with the purchase.
      • This page is presented after each new tickets, subscription, donation or member type is added to an order.
      • If the item is checked in Setup >> Company Preferences of Theatre Manager, the option to have tickets Mailed will appear within this window.
      • If the item is checked in Setup >> Company Preferences of Theatre Manager, the patron is asked if they would like to add a donation to their ticket purchase.
      • If the item is checked in Setup >> Company Preferences of Theatre Manager, the option to enter a coupon appears.

      Questions and Answers:

      Q:
      A:
      ____________________________________________________________

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMcheckout.html

       

      Description:

      • This page is the final page before payment for the Order it processed.
      • The page is secured under the SSL.
      • If you have not purchased an SSL with Arts Management Systems you may wish to comment out the Geotrust Security Certificate information on the page.
      • The ticket handling information at the top of the page may need to be altered to more accurately reflect the policies of the organization.
      • If the item is checked in Setup >> Company Preferences of Theatre Manager and it has not be previously selected, the button to have tickets Mailed will appear within this window.
      • The Payment Method, Card Number, Name as it Appears, CID, Card Expiry Date fields are all mandatory fields for credit card processing.
      • If the How Did You Hear field may be set as a mandatory field within the Theatre Manager database it will also need to be entered before processing a payment.
      • If their are no Payment Method listed in the drop down click here.
      • To learn how to create options for multiple currency payment methods click here.

      Questions and Answers:

      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):

      • TMcart.html
      • Any page listing the navigation buttons after the patron has logged into the online sales.

      Page(s) Referenced:

      TMcheckoutCardError.html

       

      Description:

      • This page is displayed when the connection between apache and the web listener is interrupted during the processing of a payment.
      • The contact information within this page is pulled directly from the Company tab in Setup >> Company Preferences of Theatre Manager.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • maps.google.com
      • The companies web site as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager.

      Called By Page(s):

      Page(s) Referenced:

      TMcheckoutConfirmation.html

       

      Description:

      • This is the confirmation page listing a break down of the items within the Patron's Order.
      • This page allows the patron to print a copy of their purchase much like a receipt. Theatre Manager will also email the patron a confirmation receipt as a part of the purchase process.
      • Many of the fields within this page are pulled directly from Theatre Manager based on the patrons purchase.
      • If the Print At Home Tickets option is checked in the Web Options tab of Setup >> System Tables in Theatre Manager a third button will appear toward the top of this window. The button reads Print Tickets and is designed to print out a paper copy of tickets (complete with bar code) to be presented at the venue for admittance.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMcheckoutInvoiceEmail.html

       

      Description:

      • This is the email confirmation page listing a break down of the items within the Patron's Order.
      • This page is emailed after each payment is complete as a receipt of the purchase.
      • Many of the fields within this page are pulled directly from Theatre Manager based on the patrons purchase.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      • Not Appicable

      Page(s) Referenced:

      TMcheckoutNoItems.html

       

      Description:

      • This page is presented when a patron attempts to process an empty cart.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMcheckoutNoPayment.html

       

      Description:

      • This page is presented when the total value of the items added to the web sales cart is zero. No payment is required for the Order.
      • When the Confirm Order for Processing button is clicked the Order is completed in Theatre Manager.
      • An option of where to send tickets after purchase may or may not be available (depending on the version of TM)

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMcheckoutProcessing.html

       

      Description:

      • The final confirmation page before the payment is processed against the patrons credit card.
      • This age will automatically refresh when the payment is finished processing within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      tmContent Folder

      The tmContent folder provides reference pages that are currently a part of the tmnavSide.html page. They are examples of information an organization may choose to include when using frames in the online sales.

      contentBoard.html

       

      Description:

      • A sample page for Board of Directors information.

      Location:

      htdocs/1/WebPagesEN/tmContent

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      contentClass.html

       

      Description:

      • A sample list of upcoming Courses or Classes the organization is offering.
      • The course description information is hard coded onto the page.
      • The Enroll in Class buttons are coded to reference the course in the TMtickets.html using the Event # from within Theatre Manager for the course.

      Location:

      htdocs/1/WebPagesEN/tmContent

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      contentContact.html

       

      Description:

      • Contact information for the Organization.
      • The Company information is pulled directly from the Setup >> Company Preferences tab of Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/tmContent

      Able to Call Page(s):

      • maps.google.com
      • The companies web site as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager.

      Called By Page(s):

      Page(s) Referenced:

      contentDonation.html

       

      Description:

      • A sample page describing the organizations donation campaigns.
      • The donation description information is hard coded onto the page.

      Location:

      htdocs/1/WebPagesEN/tmContent

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      contentEvents.html

       

      Description:

      • A sample page describing the organizations upcoming special events.
      • The event description information is hard coded onto the page.
      • The link behind the event title references the tmEvent1.html where the number 1 is replaced with the Event # from within Theatre Manager.
      • The Click Here to Purchase Tickets link and the Purchase Tickets buttons both reference the TMtickets.html page where the Event # has been added to the button to present just the performances for this event. See the Redirecting a link to a specific page in the Web Listener page for more information on creating links within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/tmContent

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      contentHistory.html

       

      Description:

      • A sample page of History information for an organization.

      Location:

      htdocs/1/WebPagesEN/tmContent

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      contentMailList.html

       

      Description:

      • A sample page describing the options to subscribe to Mail Lists.
      • The mail list description information is hard coded onto the page.
      • The Click Here to Subscribe to Mail List link and the Subscribe to Mail List button both reference the TMmaillist.html page

      Location:

      htdocs/1/WebPagesEN/tmContent

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      contentPass.html

       

      Description:

      • A sample page describing the Pass Type items available for sale.
      • The pass description information is hard coded onto the page.
      • The Click Here to Purchase a Pass link and the Purchase Pass button both reference the TMpass.html page

      Location:

      htdocs/1/WebPagesEN/tmContent

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      contentSeason.html

       

      Description:

      • A sample page of the upcoming season for the organizations.
      • The event description information is hard coded onto the page.
      • The link behind the event title references the tmEvent1.html where the number 1 is replaced with the Event # from within Theatre Manager. The Event # has been added to the link to present just the performances for this event. See the Redirecting a link to a specific page in the Web Listener page for more information on creating links within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/tmContent

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      contentSeason2002.html

       

      Description:

      • A sample page of a past seasons individual performances.
      • The event description information is hard coded onto the page.
      • The link behind the event title references the tmEvent1.html where the number 1 is replaced with the Event # from within Theatre Manager. The Event # has been added to the link to present just the performances for this event. See the Redirecting a link to a specific page in the Web Listener page for more information on creating links within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/tmContent

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      contentSeason2003.html

       

      Description:

      • A sample page of a past seasons individual performances.
      • The event description information is hard coded onto the page.
      • The link behind the event title references the tmEvent1.html where the number 1 is replaced with the Event # from within Theatre Manager. The Event # has been added to the link to present just the performances for this event. See the Redirecting a link to a specific page in the Web Listener page for more information on creating links within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/tmContent

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      contentStaff.html

       

      Description:

      • A sample page of Staff information for the organization.

      Location:

      htdocs/1/WebPagesEN/tmContent

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      contentVolunteer.html

       

      Description:

      • A sample page for Volunteer information.
      • The company name and telephone number are pulled from Setup >> Company Preferences within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/tmContent

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      TMcoupon.html

       

      Description:

      • When an invalid coupon code is entered this page is displayed offering the patron an opportunity to reenter the code.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      tmCustom Folder

      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.

      tmCampaign Folder (Custom)

      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.

      tmContent Folder (Custom)

      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.

      tmEvent Folder Custom

      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.

      tmFee Folder (Custom)

      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.

      tmMaps Folder (Custom)

      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.

      tmPass Folder (Custom)

      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.

      tmScripts Folder (Custom)

      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.

      tmSubscription Folder (Custom)

      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.

      TMtemplates Folder (Custom)

      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.

      tmVenue Folder (Custom)

      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.

      TMdonation.html

       

      Description:

      • The page for entering Donation purchases.
      • This page can be linked on the main web page using the steps as outlined in the ReadeMe About Configuring Index.html.txt page. Links can be to the generic Donation page or to specific campaigns.
      • The mandatory fields within this pages are Donation Campaign and Donation Amount.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMdonationmonthly.html

       

      Description:

      • This page allows patrons to setup a donate using a post dated payment schedule.
      • The manditory fields are Donation Campaign, Total Donation Amount, Donation Frequency, Start Date and End Date.
      • Theatre Manager will create a Donation for the amount indicated in the Total Donation Amount field. It will then setup multiply payments for the Donation based on the Donation Frequency in combination with the Start/End Date.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      • Not Applicable

      Page(s) Referenced:

      TMError.txt

       

      Description:

      • The TMError.txt page feeds the messages located at the top of many pages.
      • The TMError.txt page is referenced as F_HTML_PAGE_MESSAGE.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      tmEvent Folder

      The tmEvent folder contains the detail pages for event sold within the online sales. The Default page is used only when a custom pages is not available for the event. It pulls information such as the date range of the run, the venue, performance notes and the map layout directly from the event within Theatre Manager.

      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.

      tmEvent1.html

       

      Description:

      • This page provides a description of the over all event and it's details.
      • The title of the page includes a number that references the event sequence number from within Theatre Manager.
      • This is a custom page that can be edited to reflect the details of this specific event.
      • The event name is pulled from the external name of the event from within Theatre Manager.
      • The run start and end date are pulled from the performance tab within the event setup of Theatre Manager.
      • The venue and it's address are pulled from the map the event was built on within Theatre Manager.
      • The run time, description information and image are directly from the marketing tab of the event from within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/tmEvent

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      tmEventDefault.html

       

      Description:

      • This page provides a description of the over all event and it's details.
      • The event name is pulled from the external name of the event from within Theatre Manager.
      • The run start and end date are pulled from the performance tab within the event setup of Theatre Manager.
      • The venue and it's address are pulled from the map the event was built on within Theatre Manager.
      • The run time, description information and image are directly from the marketing tab of the event from within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/tmEvent

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      tmFee Folder

      The tmFee folder contains the detail pages of fees charged for online sales. The Default page is used only when a custom pages is not available for the fee. It pulls the note information directly from the fee within Theatre Manager and contains contact information for the box office.

      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.

      tmBoxOfficePolicy.html

       

      Description:

      • A list of box office policies as they apply to the organization.
      • This page should be edited to accurately reflect the policies of the organization.

      Location:

      htdocs/1/WebPagesEN/tmFee

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      tmFeeDefault.html

       

      Description:

      • This is the default web page called for online fees.
      • The name of the fee and the description are pulled from the Fee Type from within Theatre Manager.
      • Any fee created for online sales will present this page with the fee title is clicked on. This excludes mailing fees and order fees as they have their own default pages.

      Location:

      htdocs/1/WebPagesEN/tmFee

      Able to Call Page(s):

      • maps.google.com
      • The companies web site as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager.

      Called By Page(s):

      Page(s) Referenced:

      tmMailFee.html

       

      Description:

      • This is the web page called for online mailing fees.
      • The name of the fee and the description are hard coded into the web page.

      Location:

      htdocs/1/WebPagesEN/tmFee

      Able to Call Page(s):

      • maps.google.com
      • The companies web site as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager.

      Called By Page(s):

      Page(s) Referenced:

      tmMailFeeDefault.html

       

      Description:

      • This is the default web page called for online mailing fees.
      • The name of the fee and the description are hard coded into the web page.

      Location:

      htdocs/1/WebPagesEN/tmFee

      Able to Call Page(s):

      • maps.google.com
      • The companies web site as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager.

      Called By Page(s):

      Page(s) Referenced:

      tmOrderFee.html

       

      Description:

      • This is the web page called for online order fees.
      • The page pulls the name of the fee from within Theatre Manager.
      • The description of the fee is hard coded in the web page.

      Location:

      htdocs/1/WebPagesEN/tmFee

      Able to Call Page(s):

      • maps.google.com
      • The companies web site as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager.

      Called By Page(s):

      Page(s) Referenced:

      tmOrderFeeDefault.html

       

      Description:

      • This is the default web page called for online order fees.
      • The page pulls the name of the fee from within Theatre Manager.
      • The description of the fee is hard coded in the web page.
      • If the existing online order fee were duplicated within Theatre Manager and a custom fee page not created, this would be the page pulled to describe the fee.

      Location:

      htdocs/1/WebPagesEN/tmFee

      Able to Call Page(s):

      • maps.google.com
      • The companies web site as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager.

      Called By Page(s):

      Page(s) Referenced:

      TMfutureTickets.html

       

      Description:

      • Presents a list of tickets to future events purchased online.
      • Patrons can review their upcoming events or print off the details if they choose.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMfutureTicketsPrint.html

       

      Description:

      • Presents and prints a page listing tickets to future events.
      • This page is printer friendly in that it does not contain the default banner or buttons and is largely black and white.
      • When the "Print at home tickets" box is checked in Setup > Company Preferences > Web Options Tab, this page is the ticket that patrons can print with the bar code for admission to events. If the box is not checked, then the bar code will not present. For more information on the Web Options Tab, click here.
      • The buttons which call this page (when activated in Web Options) are located on TMfutureTickets.html and TMcheckoutConfirmation.html.

      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 to img src="tmGifs/sponsorLogo.jpg". 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.
      ____________________________________________________________

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      tmGifs Folder

      This folder contains the images and style sheets referenced by the web sales. Additional images can be added to the folder and references as needed. Images that are uploaded from Form Letters within Theatre Manager can be found in the eblastimages folder.

      background.gif

       

       

      Description:

      • This image is references as the background of the invoice emailed to patrons upon the completion of a sale.

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      backgroundBottom.gif

       

       

      Description:

      • This image is called as a part of the .backgroundBottom reference in the default style sheets.

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      backgroundSide.gif

       

       

      Description:

      • This image is called as a part of the .backgroundSide reference in the default style sheets.

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      bg_main.gif

       

       

      Description:

      • Can be added to the style sheets as the background image.

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      • Currently Not Applicable

      Page(s) Referenced:

      • Not Applicable

      cvv2.gif

       

       

      Description:

      • This image contains examples of the location for the CVV, CVV2 or CID number on a credit card.
      • The purpose of this image is to assist patrons during the purchase process in locating the number to complete their online sale.
      • CVV, CVV2 or CID numbers are not stored within the Theatre Manager database.

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      handicapped.gif

       

       

      Description:

      • This is an image of the handicap stencil.
      • The image is used to draw attention to important information for patron requiring accessibility information.

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      Language Flag gifs

       

       

      Description:

      • There are several different Language Flags in the tmGifs folder.
      • If a desired flag is current not available, additional images can be added to the folder.
      • The images are used, in conjunction with buttons, to navigate back and forth between the multilingual WebPages folders.
      • An organization would need to translate the WebPages folder to the desired languages before implementing this feature.
      • Please see the WebPagesEN folder for additional information on setting up multilingual pages.

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      nav_space.gif

       

       

      Description:

      • This image represents a line.

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      • Currently Not Applicable

      Page(s) Referenced:

      • Not Applicable

      pageHeader.gif

       

       

      Description:

      • This image is the default online sales page header.
      • It's pulled by the stylePages.css onto almost every page within the online sales.
      • This image is often replaced with a page header that more accurately resembles the organizations main web pages.

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      spacer.gif

       

       

      Description:

      • This image represents a blank space.
      • It is most often used to place a space between images on a page. An example would be the flags on the Language Flags Gif page.

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      • Currently Not Applicable.

      Page(s) Referenced:

      • Not Applicable

      step1.gif

       

       

      Description:

      • This image is used to indicate a first step.
      • The images is designed to draw notice to fields that require the patrons attention.

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      step2.gif

       

       

      Description:

      • This image is used to indicate a second step.
      • The images is designed to draw notice to fields that require the patrons attention.

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      step3.gif

       

       

      Description:

      • This image is used to indicate the third step.
      • The images is designed to draw notice to fields that require the patrons attention.

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      step4.gif

       

       

      Description:

      • This image is used to indicate the fourth step.
      • The images is designed to draw notice to fields that require the patrons attention.

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      stop.html

       

       

      Description:

      • This image represents a stop sign.
      • The image is used to draw attention to important information that should be read prior to navigating away from the current page.

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      styleButtons.css

       

       

      Description:

      • This stylesheet contains the styles that are used for the buttons on the various web pages within the Web Sales Module that have buttons.
      • Stylesheets (also called Cascading Style Sheets hence "css") are used to change the look of web pages. By having them you can set text, buttons, hyperlinks and so forth to different colors, size, etc. They are called in with a <link rel="stylesheet" href="" type="text/css"> where within the double quotes would be the path of the stylesheet.
      • The different styles are called from source code an changes to the text, hyperlinks, etc of a web page can be made simply by editing the stylesheet instead of manually changing each page individually.
      • The look of the buttons can be changed by editing the fields within the style sheet. For example, if you don't like the light blue halo around the navigation buttons across the top of the page you can change the colour by editing the board color in the .button style.
      • .button - a button style. This is for majority of the buttons within the web pages.

      • .buttonover - a button style. This is for majority of the buttons within the web pages when a mouse hovers over them.

      • .new - a button style. This is used for select buttons with the web pages. It's often associated with buttons within the page.

      • .newover - a button style. This is for buttons referenced by .new when a mouse hovers over the button.

      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');

      To comment out information within the style sheet add a /* at the beginning of the text and */ at the end of the text.


      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):

      • Not Applicable

      Called By Page(s):

      • All pages within the online sales containing a button.

      Page(s) Referenced:

      stylePages.css

      Description:

      • Stylesheets (also called Cascading Style Sheets hence "css") are used to change the look of web pages. They can set text, buttons, hyperlinks and so forth to different colors, size, etc. The usefulness is that they are called in with a <link rel="stylesheet" href="" type="text/css"> where within the double quotes would be the path of the stylesheet. The different styles are called using source code and you can change the text, hyperlinks, etc of a web page simply by editing the stylesheet instead of manually changing each page individually.
      • This stylesheet contains the design for all pages within the Web Sales module. The styles in this css page changes the properties of text and hyperlinks to different font sizes, colors, etc.
      • You can change how items look by changing the fields within this page. For example, if you don't like a text color simple change the color field within the appropriate style.
      • To comment out information within the style sheet add a /* at the beginning of the text and */ at the end of the text.
      • The references below containing the word Print belong to web pages where the page name ends in the word Print. These pages are designed to be printer friendly versions of the original page. The references are also used when any page is printed. Some organizations customize their web pages with colours schemes that are not printer friendly. These references allows for a colour combination that will be visible when pages is printed.

      •  

      • .background - Indicates the colour, image and attributes to be used for the background in most web pages within the online sales.

      • .backgroundPrint - The colour to be used as the background for print pages from within the web sales.
      • .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.
      • .backgroundSidePrint - The colour of the side panels, when printed, while using frames within the web pages.
      • .limitedprofilelogin - Allows for the over all customization of the TMpatronLimitedProfile.html page.
      • .limitedprofileentry - The customization of the entry fields within the TMpatronLimitedProfile.html page.
      • .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.

      • .mainPrint - The text colour for print pages from within the web sales.
      • .title - The header of the page that often appears at the top of the browser window.

      • .titlePrint - Header for print pages from within the web sales.
      • a.navlink - Attributes for the navigation links within the tmnavSide.html pages. It is also used in the TMattendancePalm.htmlpage.

      • a.navlinkPrint - The attributes of a.navlink when printed.

      • a.navlink:hover - The result of a mouse moving over a hyperlink in the tmnavSide.html page.
      • a.navlinkPrint:hover - The attributes of a.navlink:hover when a mouse is on top of it at the time the page is printed.
      • .message - The text pulled from the TMError.txt page. This text is found across the top of the web page.

      • .messagePrint - The attributes of .message when printed.

      • .waitmessage - This message appears on web pages where it make take a moment for the request to return with information from the database.

      • a.link - An <A HREF> style for links within the web pages.

      • a.linkPrint - The attributes of a.link when printed.

      • a.link:hover - The result of a mouse moving over the a.link hyperlink in the web pages.
      • a.linkPrint:hover - The attributes of a.link:hover when a mouse is on top of it at the time the page is printed.
      • .playinfo - The text within the season or ticket sales process that describes the performance details.

      • .playinfoPrint - The attributes of a.playinfo when printed.

      • .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.
      • .backgroundBottomPrint - The colour of the bottom panels, when printed, while using frames within the web pages.
      • .tablerowheader - Descriptive information within the tables of the web pages.

      • .tablerowheaderprint - The attributes of .tablerowheader when printed.

      • .tablerowdetail - Active information within the tables of the web pages.

      • .tablerowdetailprint - The attributes of .tablerowdetail when printed.

      • .calendarheader - For Future Implementation.
      • .calendarcellheadercurrentmonth - For Future Implementation.
      • .calendcellheadercurrentdate - For Future Implementation.
      • .calendarcellheaderothermonth - For Future Implementation.
      • .calendarcellheaderotherdate - For Future Implementation.
      • table.inner - For Future Implementation.
      • table.outer - For Future Implementation.
      • table.calendar - For Future Implementation.
      • table.calendar a.link - For Future Implementation.
      • table.calendar a.link:hover - For Future Implementation.
      • .calendar2 - For Future Implementation.
      • table.calendar tr - For Future Implementation.
      • table.calendar td - For Future Implementation.
      • table.calendarother - For Future Implementation.
      • table.calendarother a.link - For Future Implementation.
      • table.calendarother a.link:hover - For Future Implementation.
      • table.calendarother tr - For Future Implementation.
      • table.calendarother td - For Future Implementation.
      • table.datenumber - For Future Implementation.
      • table.datenumber tr - For Future Implementation.
      • table.datenumber td - For Future Implementation.
      • table.datenumber td#green - For Future Implementation.
      • table.datenumberother - For Future Implementation.
      • table.datenumberother tr - For Future Implementation.
      • table.datenumberother td - For Future Implementation.
      • table.datenumberother td#noborder - For Future Implementation.

      Test1

      Description:

      • Stylesheets (also called Cascading Style Sheets hence "css") are used to change the look of web pages. They can set text, buttons, hyperlinks and so forth to different colors, size, etc. The usefulness is that they are called in with a <link rel="stylesheet" href="" type="text/css"> where within the double quotes would be the path of the stylesheet. The different styles are called using source code and you can change the text, hyperlinks, etc of a web page simply by editing the stylesheet instead of manually changing each page individually.
      • This stylesheet contains the design for all pages within the Web Sales module. The styles in this css page changes the properties of text and hyperlinks to different font sizes, colors, etc.
      • You can change how items look by changing the fields within this page. For example, if you don't like a text color simple change the color field within the appropriate style.
      • To comment out information within the style sheet add a /* at the beginning of the text and */ at the end of the text.
      • The references below containing the word Print belong to web pages where the page name ends in the word Print. These pages are designed to be printer friendly versions of the original page. The references are also used when any page is printed. Some organizations customize their web pages with colours schemes that are not printer friendly. These references allows for a colour combination that will be visible when pages is printed.

        .background Indicates the colour, image and attributes to be used for the background in most web pages within the online sales.
        .backgroundPrint The colour to be used as the background for print pages from within the web sales.
        .backgroundSide The colour used for the tmnavSide.html page. When using frames, this attribute can be edited to meet the design requirements for the side panels.
        .backgroundSidePrint The colour of the side panels, when printed, while using frames within the web pages.
        .limitedprofilelogin Allows for the over all customization of the TMpatronLimitedProfile.html page.
        .limitedprofileentry The customization of the entry fields within the TMpatronLimitedProfile.html page
        .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.
        .mainPrint The text colour for print pages from within the web sales.
        .title The header of the page that often appears at the top of the browser window.
        .titlePrint Header for print pages from within the web sales.
        a.navlink Attributes for the navigation links within the tmnavSide.html pages. It is also used in the TMattendancePalm.html page
        a.navlinkPrint The attributes of a.navlink when printed.
         a.navlink:hover The result of a mouse moving over a hyperlink in the tmnavSide.html page.
        a.navlinkPrint:hover The attributes of a.navlink:hover when a mouse is on top of it at the time the page is printed.
        .message The text pulled from the TMError.txt page. This text is found across the top of the web page.
        .messagePrint The attributes of .message when printed.
        .waitmessage This message appears on web pages where it make take a moment for the request to return with information from the database.
        a.link An <A HREF> style for links within the web pages.
        a.linkPrint The attributes of a.link when printed.
        a.link:hover The result of a mouse moving over the a.link hyperlink in the web pages.
        a.linkPrint:hover The attributes of a.link:hover when a mouse is on top of it at the time the page is printed.
        .playinfo The text within the season or ticket sales process that describes the performance details.
        .playinfoPrint The attributes of a.playinfo when printed.
        .backgroundBottom The colour used for the tmnavBottom.html page. When using frames, this attribute can be edited to meet the design requirements for the bottom panels.
        .backgroundBottomPrint The colour of the bottom panels, when printed, while using frames within the web pages.
        .tablerowheader Descriptive information within the tables of the web pages.
        .tablerowheaderprint The attributes of .tablerowheader when printed.
        .tablerowdetail Active information within the tables of the web pages.
        .tablerowdetailprint The attributes of .tablerowdetail when printed.
        .calendarheader Future Implementation.
        .calendarcellheadercurrentmonth Future Implementation.
        .calendcellheadercurrentdate Future Implementation.
        .calendarcellheaderothermonth Future Implementation.
        .calendarcellheaderotherdate Future Implementation.
        table.inner Future Implementation.
        table.outer Future Implementation.
        table.calendar Future Implementation.
        table.calendar a.link Future Implementation.
        table.calendar a.link:hover Future Implementation.
        .calendar2 Future Implementation.
        table.calendar tr Future Implementation.
        table.calendar td Future Implementation.
        table.calendarother Future Implementation.
        table.calendarother a.link Future Implementation.
        table.calendarother a.link:hover Future Implementation.
        table.calendarother tr Future Implementation.
        table.calendarother td Future Implementation.
        table.datenumber Future Implementation.
        table.datenumber tr Future Implementation.
        table.datenumber td Future Implementation.
        table.datenumber td#green Future Implementation.
        table.datenumberother Future Implementation.
        table.datenumberother tr Future Implementation.
        table.datenumberother td Future Implementation.
        table.datenumberother td#noborder Future Implementation.

       

      Location:
      • WebPagesEN/tmGifs/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      • All web pages within the online sales.

      Page(s) Referenced:

      tickettrove.jpg

       

       

      Description:

      • This image is the Arts Management Systems TicketTrove application logo.

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      tmCompanyLogo.gif

       

       

      Description:

      • This image is of the Arts Management Systems company logo.

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      tmName.gif

       

       

      Description:

      • This image contains the words "Theatre Manager".
      • It's designed to be used in conjunction with the tmPoweredBy.gif.
      • The Letter of Confirmation agreement states "As part of the license, you agree to place on a static web page on your main site, the phrase "Powered By Theatre Manager" and that the phrase be linked back to the ArtsMan home page at http://www.artsman.com.".

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      tmPoweredBy.gif

       

       

      Description:

      • This image contains the words "powered by".
      • It's designed to be used in conjunction with the tmName.gif.
      • The Letter of Confirmation agreement states "As part of the license, you agree to place on a static web page on your main site, the phrase "Powered By Theatre Manager" and that the phrase be linked back to the ArtsMan home page at http://www.artsman.com.".

      Location:

      htdocs/1/WebPagesEN/tmGifs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      TMhome.html

       

      Description:

      • This is the introduction page to the online sales. It's the first page patrons see after the login to the online sales.
      • This page is designed to convey any relevant information the patrons purchasing online.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      tmindex.html

       

      Description:

      • This page integrates frames with the online web sales.
      • The Index.html page needs to be edited in order to reference the online sales using frames.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      TMlogin.html

       

      Description:

      • This page allows patrons to login to the online sales in order to complete a transaction within Theatre Manager.
      • By logging in to the online sales Theatre Manager can attache the patrons purchase to their patron record within the database.
      • This is the initial page for online sales when Allow Anonymous Login is not selected in the Web Options tab of Setup >> Company Preferences within Theatre Manager.
      • The Browse Anonymously button will only appear when Allow Anonymous Login is selected in the Web Options tab of Setup >> Company Preferences within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMloginSelectPatron.html

       

      Description:

      • Allows the patron the option to choose which member in the household this ticket order should belong to.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMlogoff.html

       

      Description:

      • The page presenting when a patron click the logout button in Theatre Manager.
      • This page acts as a confirmation the patron has been logged out of the online sales.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMlogoffOpenCart.html

       

      Description:

      • This page acts as a warning to a patron logging out of the online sales when they currently have items within their online shopping cart.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      • Any page containing the navigation buttons but only when the patron attempts to log out and their online cart has unreleased items.

      Page(s) Referenced:

      TMmaillist.html

       

      Description:

      • Allows patrons who have logged into the online sales to subscribe and unsubscripe to their desired mail lists.
      • Only those Mail Lists that have the "Allow Patrons to subscribe/unsubscribe via the internet" box checked within the Mail List setup will be available in the lists.
      • The Patron can select a Mail Lists from the Subscribe to a Mail List column and use the "Subscribe to selected Mail List" button to move their name onto the Mail List within the Theatre Manager database.
      • The patron can select a Mail List in the Unsubscribe from a Mail List column and click the "Remove from selected Mail List" button to remove their name from the Mail list with the Theatre Manager database.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      • contentMailList.html
      • Any page containing the navigation buttons after the Patron has logged into the online sales.

      Page(s) Referenced:

      TMmaillistDisallow.html

       

      Description:

      • This page is presented when a secondary member of a household attempts to remove a Mail List that is set to only select primary members of the household in the Theatre Manager database.
      • The Patron needs to login to the online sales as the primary patron in the household in order to remove the Mail List.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMmaillistQuickAdd.html

       

       

      Description:

      • Populates a list with check boxes of Mail Lists for the patron to indicate those they wish to sign up for.
      • If the patron is not signed in to the online sale, fields will be available for the patrons first name, last name and email address.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      TMmaillistUnverifiedEmail.html

       

      Description:

      • The confirmation page that appears after a patron adds themselves to a Mail List using the Quick Add feature.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMmaillistVerify.html

       

      Description:

      • This page is displayed when the Confirm This Email Address link from the TMmaillistUnverifiedEmail.html page is clicked and the patron has not entered an email address.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      tmMaps Folder

      The tmMaps folder contains the pages accessed when purchasing tickets. The default pages are only when a custom page is not available.

      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.

      TMsubscriptionMapDefault.html

       

      Description:

      • This page allows the patron to choose the subscription details they would prefer for Reserved seating events.
      • Step 1 is a drop down of seating sections pulled from the Best Seat Settings tab from within the Map in Theatre Manager. Depending on the seat configuration of your venue (in particular dinner theatre seating), your Seat Name file may have been setup for a two-pass approach to Best Available seating. For more information on the two-pass system click here.
      • Step 2 allows the patron to choose the number of subscriptions they wish to purchase. The quantity is limited to the number of tickets allowed to be sold per Order within Theatre Manager.
      • Step 3 indicates the day of the week the patron wishes to attend. This drop down is populated when there is more then one performance date within the season package.
      • Step 4 confirms the options as they are indicated about and takes the patron to the TMsubscriptionPriceMapDefault.html page.

      Location:

      htdocs/1/WebPagesEN/tmMaps

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMsubscriptionMapDefaultf.html

       

      Description:

      • For Future Implementation
      • This page allows the patron to choose the subscription details they would prefer for Festival Seating/General Admission events.
      • Step 1 allows the patron to choose the number of subscriptions they wish to purchase. The quantity is limited to the number of tickets allowed to be sold per Order within Theatre Manager.
      • Step 2 indicates the day of the week the patron wishes to attend. This drop down is populated when there is more then one performance date within the season package.
      • Step 3 confirms the options as they are indicated about and takes the patron to the TMsubscriptionPriceMapDefault.html page.

      Location:

      htdocs/1/WebPagesEN/tmMaps

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMsubscriptionPriceMapDefault.html

       

      Description:

      • Allows the patron to review the best available seating option within the section they choose from the TMsubscriptionMapDefault.html page. The best available seats are indicated in the Seat Names tab of the Map within Theatre Manager. The Best Avail Area and Best Seat # columns determine the order of the seats. Depending on the seat configuration of your venue (in particular dinner theatre seating), your Seat Name file may have been setup for a two-pass approach to Best Available seating. For more information on the two-pass system click here.
      • The drop down next to the seat location allows the patron to choose the appropriate price for the seat. The pricing options in the list are pulled from the event within Theatre Manager. Only prices that are indicated as Season pricing will be available in the drop down.
      • The patron can click the Next Best Available button and they will be presented with the next option for available seats within the section.

      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:

      TMsubscriptionsMapDefaultf.html

       

      Description:

      • For Future Implementation

      Location:

      htdocs/1/WebPagesEN/tmMaps

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMsubscriptionsPriceMapDefault.html

       

      Description:

      • WEB PAGE CURRENTLY UNDER CONSTRUCTION

      Location:

      htdocs/1/WebPagesEN/tmMaps

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMticketsPrice_MapDefault.html

       

      Description:

      • Displays the best available seating option within the section the patron chose from the TMticketsSection_MapDefault.html page. The best available seats are indicated in the Seat Names tab of the Map within Theatre Manager. The Best Avail Area and Best Seat # columns determine the order of the seats. Depending on the seat configuration of your venue (in particular dinner theatre seating), your Seat Name file may have been setup for a two-pass approach to Best Available seating. For more information on the two-pass system click here.
      • The patron can click the Next Best Available button and they will be presented with the next option for available seats within the section.
      • The drop down next to the seat location allows the patron to choose the appropriate price for the seat. The pricing options in the list are pulled from the event within Theatre Manager. Only prices available online will be displayed in the drop down. Season Subscription online pricing does not appear in the drop down.

      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 htdocs. 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 htdocs through the base reference.
      ____________________________________________________________

      Location:

      htdocs/1/WebPagesEN/tmMaps

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMticketsSection_MapDefault.html

       

      Description:

      • This pages is specific to reserved seating performances.
      • The patron can choose the ticket options they would prefer to add to their cart.
      • The event title, date and time are pulled from Theatre Manager based on the selection from the previous window.
      • Step 1 is a drop down of seating sections pulled from the Best Seat Settings tab from within the Map in Theatre Manager.
      • Step 2 allows the patron to indicate the number of tickets they wish to purchase. The quantity is limited to the number of tickets allowed to be sold per Order within Theatre Manager.
      • Step 3 searches the database for the preferences from the above steps. It loads the TMticketsPrice_MapDefault.html page.
      • The map is pulled directly from the Theatre Manager database. The page can be duplicated and the word Default changed to the map number from within Theatre Manager. The page can then be edited to display an image specific to the venue.
      • Web sales produces seats using the Best Seat settings within each venue map. For more information on the Best Seat settings, click here. Depending on the seat configuration of your venue (in particular dinner theatre seating), your Seat Name file may have been setup for a two-pass approach to Best Available seating. For more information on the two-pass system click here.

      Location:

      htdocs/1/WebPagesEN/tmMaps

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMticketsSection_MapDefaultc.html

       

      Description:

      • This pages is specific to Courses. Note the c at the end of the page name.
      • The patron can choose the ticket options they would prefer to add to their cart.
      • The event title, date and time are pulled from Theatre Manager based on the selection from the previous window.
      • Step 1 allows the patron to choose the number of admissions to the course they wish to purchase. The quantity is limited to the number of tickets allowed to be sold per Order within Theatre Manager.
      • Step 2 searches the database for the preferences from the above steps. It loads the TMticketsPrice_MapDefault.html page.
      • For details on how to setup a course click here.

      Location:

      htdocs/1/WebPagesEN/tmMaps

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMticketsSection_MapDefaultf.html

       

      Description:

      • This pages is specific to Festival Seating/General Admission seating performances. Note the f at the end of the page name.
      • The patron can choose the ticket options they would prefer to add to their cart.
      • The event title, date and time are pulled from Theatre Manager based on the selection from the previous window.
      • Step 1 allows the patron to indicate the number of tickets they wish to purchase. The quantity is limited to the number of tickets allowed to be sold per Order within Theatre Manager.
      • Step 2 searches the database for the preferences from the above steps. It loads the TMticketsPrice_MapDefault.html page.
      • The map is pulled directly from the Theatre Manager database. The page can be duplicated and the word Default changed to the map number from within Theatre Manager. The page can then be edited to display an image specific to the venue.

      Location:

      htdocs/1/WebPagesEN/tmMaps

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      tmnavBottom.html

       

      Description:

      • The footer page attached to tmindex.html.
      • The page pulls images from the tmGifs folder. The page can be edited to meet the organizations needs.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      tmnavMain.html

       

      Description:

      • This is the main body of the page when using tmindex.html.
      • As links or buttons are clicked within the frames the information in this page is replaced with the page referenced by the link or button.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      tmnavTop.html

       

      Description:

      • The header page attached to tmindex.html.
      • The page pulls the pageHeader.gif. The page can be edited to meed the organizations needs.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      TMoldCartDetailsPrint.html

       

      Description:

      • A printer friendly copy of the Old Cart Detail page.
      • The page will present as a preview behind the machines default printer page setup.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      TMoldCartHeaders.html

       

      Description:

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      tmPass Folder

      The tmPass folder contains the detail pages for passes, gift certificates, memberships or other sales items within the online sales. The Default page is used only when a custom pages is not available for the pass type.

      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.

      tmPass1.html

       

      Description:

      • Provides a description of the pass type with a sequence number of 1.
      • This is an example of how to create a custom pass page.

      Location:

      htdocs/1/WebPagesEN/tmPass

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      tmPassDefault.html

       

      Description:

      • Provides a description of the pass selected.
      • The description is hard coded into the page.

      Location:

      htdocs/1/WebPagesEN/tmPass

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMpass.html

       

      Description:

      • The TMpass.html page lists all items currently available for sale in Member Type area of Theatre Manager.
      • This page is accessed by the button that is titles Gift Certificate in the default web pages.
      • Often the button and this area of Theatre Manager are renamed to something like Pass, Gift Certificate, Sales Items or another option chosen by the organization.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMpassAskAmount.html

       

      Description:

      • This page is designed to enter the details of the Membership/Pass/Gift Certificate being purchased.
      • Member Type are created in Setup >> System Tables Member Types of Theatre Manager.
      • Depending on the setup of the Member Type, the value of the item may need to be entered in this window.
      • Information entered in the Personalized Notes field will appear in the Notes tab of the Membership Detail window within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMpasswordChange.html

       

      Description:

      • This page allows a patron to change their existing online password to a new password.
      • When an email address is entered into Theatre Manager the application generates a random password for the patron. The first time the patron attempts to login to the online sales using the Password they will be redirected to this page. The Patron can then set their password to something they choose.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMpasswordChangeEmail.html

       

      Description:

      • This email is automatically sent when a patron changes their password using the TMpasswordChange.html page.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • maps.google.com
      • The companies web site as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager.
      • The ticketing site as referenced in index.html

      Called By Page(s):

      Page(s) Referenced:

      TMpasswordEmptyEmail.html

       

      Description:

      • This email is sent to a patron when their email address is selected in their patron window and the Send Password button is clicked from within Theatre Manager.
      • The most common reason for this email to be sent would be the patrons email address is not the primary email for their patron record but rather a secondary email. Secondary email addresses cannot be used to login to the online sales module therefore Theatre Manager does not assign a password to them.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • maps.google.com
      • The companies web site as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager.

      Called By Page(s):

      • Not Applicable.

      Page(s) Referenced:

      TMpasswordForgot.html

       

      Description:

      • The patron enters their email address in this page and their online password will be emailed to the address entered.
      • If the email address does not currently exist in the database the patron will be prompted to create a new online account.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMpasswordForgotEmail.html

       

      Description:

      • The email that is sent when a patrons click the Email Me My Password button in the TMpasswordForgot.html
      • The Password is populated using the online sales password for the email address within the Theatre Manager database.
      • If the patron has never logged into the online sales but their email address appears in Theatre Manager this will be a randomly generated password. The patron will be prompted to change the password the first time they login. .

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      • Not Applicable

      Page(s) Referenced:

      TMpasswordResetChange.html

       

      Description:

      • This page allows patrons to change their passwords.
      • If this is the first time a patron has logged into Theatre Manager using a password generated within the database they will be directed to this page. The patron is encouraged to change their password to something easier to remember then the Theatre Manager generated password.
      • The new password must be at least 7 characters long
      • The new password cannot contain special characters such as exclamation marks or ampersands.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMpasswordResetEmail.html

       

      Description:

      • The email that is sent when a patrons click the Save New Email button in the TMpasswordResetChange.html
      • The Password is populated using the online sales password for the email address within the Theatre Manager database.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      • Not Applicable

      Page(s) Referenced:

      TMpatronLimitedProfile.html

       

      Description:

      • Allows for patrons to login to the online sales without creating a full patron profile.
      • This option is currently available for Safari and the latest release of Firefox.
      • This page will only accessible is a patron is not logged in and click the checkout button at the top of the online sales window. This option is only available when the Enable Partial Patron On Web checkout box is checked under the Web Options tab in Setup >> System Tables within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMpatronNew.html

       

      Description:

      • This pages creates an account in the Theatre Manager database for the patron.
      • The mandatory fields are set within the Theatre Manager database in Setup >> System Preferences under the Mandatory Data tab.
      • All fields indicated within this window access specific database fields within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMpatronNewEmail.html

       

      Description:

      • This page is sent in the form of an email every time a new Patron Account is setup in the TMpatronNew.html page.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • maps.google.com
      • The companies web site as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager.
      • The ticketing site as referenced in index.html

      Called By Page(s):

      Page(s) Referenced:

      TMpatronUpdateEmail.html

       

      Description:

      • This email is automatically sent when a patron changes their patron record using the TMpatonUpdate.html page.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      • Not Applicable

      Page(s) Referenced:

      tmScripts Folder

      buttonRollover.html

      Description:

      • Changed the look of a button in the online sales web page when a mouse is hovered over it.
      • Accesses the styleButtons.css to change the attributes of the button.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      dropDownMenuFunction.html

      Description:

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      navSideRollover.html

      Description:

      • Changed the look of a link in the online sales web page when a mouse is hovered over it.
      • Accesses the stylePages.css to change the attributes of the link..

      Location:

      htdocs/1/WebPagesEN/tmScripts

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      showhidediv.html

      Description:

      Location:

      htdocs/1/WebPagesEN/tmScripts

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not applicable

      tmSubscription Folder

      The tmSubscription folder contains the detail pages for subscription packages sold within the online sales. The Default page is used only when a custom pages is not available for the season. It pulls the note information directly from the season setup within Theatre Manager.

      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.

      tmSubscriptionDefault.html

       

      Description:

      • This page displays the description and note information from the season package. This information is pulled directly from the Theatre Manager database.
      • Customized pages can be created for season packages by duplicating this page and changing the word Default at the end of the title to the season package sequence number from within Theatre Manager. The season package number is located in the Seq # column under Patron Sales >> Season Reservations >> Setup Season Packages.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMsubscriptions.html

       

      Description:

      • Lists the Season Packages that are available to purchace.
      • Packages are made available for sale in the Patron Sales >> Season Reservations >> Setup Season Package by opening the desired page with Theatre Manager.
      • Packages available to the patron depend on availability and the patrons season package history.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      • Any page containing the navigation buttons.

      Page(s) Referenced:

      TMsubscriptionsRenew.html

       

      Description:

      • The Renewal page for season subscription packages.
      • If a patron has a package for the selected season already in their patron record they will be presented with this page.
      • This option is only available for season packages where the Renew Online option is selected in the Patron Sales >> Season Reservations >> Setup Season Package by opening the desired page with Theatre Manager.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMsys404.html

       

      Description:

      • This page is displayed when a patron attempts to access a page that does not exist. This can often be caused by bookmarking a page within the online sales as the titles of the pages are static.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • maps.google.com
      • The companies web site as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager.

      Called By Page(s):

      • Not Applicable.

      Page(s) Referenced:

      TMsysBackupInProgress.html

       

      Description:

      • This page is displayed when Theatre Manager is paused for a backup.
      • Most backups are run while the system is in use rather then paused.
      • For more information on how to backup the database click here.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • maps.google.com
      • The company web site as it appears in the Setup >> Company Preferences of Theatre Manager.

      Called By Page(s):

      • Not Applicable

      Page(s) Referenced:

      TMsysCookiesDisabled.html

       

      Description:

      • This page is displayed when a patron has disabled cookies on their internet browser.
      • Cookies from the online sales are encrypted and contain only sufficient information to assist the ticket buying process.
      • The cookie expires in 24 hours and is removed from the web browser at that time.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMsysInvalidCall.html

       

      Description:

      • The page the patron is attempting to access does not exist.
      • This can be caused by the patron bookmarking a page or attempting to access a page incorrectly referenced on the organizations main web site.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • maps.google.com
      • The companies web site as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager.

      Called By Page(s):

      • Not Applicable

      Page(s) Referenced:

      TMsysInvalidCallDirect.html

       

      Description:

      • This page indicates the patron attempted to access a page they do not have privileges to access.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • maps.google.com
      • tmindex.html
      • The companies web site as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager.

      Called By Page(s):

      • Not Applicable

      Page(s) Referenced:

      TMsysInvalidCallNoAccess.html

       

      Description:

      • The page the patron is attempting to access does not exist.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • maps.google.com
      • The companies web site as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager.

      Called By Page(s):

      • Not Applicable

      Page(s) Referenced:

      TMsysInvalidFunction.html

       

      Description:

      • This page is displayed when a patron uses the browser navigation buttons or clicks a button within the online sales multiple times.
      • Patrons are asked to refrain from using the back button in the TMhome.html page.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • maps.google.com
      • The companies web site as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager.

      Called By Page(s):

      • Not Applicable

      Page(s) Referenced:

      TMsysWebSalesDisabled.html

       

      Description:

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • maps.google.com
      • The companies web site as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager.

      Called By Page(s):

      • Not Applicable

      Page(s) Referenced:

      TMtemplates Folder

      cellPerfDetailCalCurrent.html

      Description:

      • Pulls the current months performance dates directly from Theatre Manager for the volunteer calendar.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      cellPerfDetailCalOther.html

      Description:

      • Pulls the prior and future months performance dates directly from Theatre Manager for the volunteer calendar.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      cellPerfDetailCalTextProperty.html

      Description:

      • Pulls the performance time and title from Theatre Manager for the volunteer calendar.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      cellPerfDetailCalTitleProperty.html

      Description:

      • Pulls the performance notes and sales notes for a performance from Theatre Manager for the volunteer calendar.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      cellVolDetailCalCurrent.html

      Description:

      • Pulls the date and activity the volunteer will be performing from Theatre Manager for the volunteer calendar.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      cellVolDetailCalOther.html

      Description:

      • Pulls the historical date and activities the volunteer is scheduled to perform from Theatre Manager for the volunteer calendar.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      constantALLEVENTS.txt

       

       

      Description:

      • The default text for the event drop down at the top of the TMtickets.html page.
      • Allows for the customization of the text and accommodates change of language

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      constantALLGENRES.txt

       

       

      Description:

      • The default text for the genre drop down at the top of the TMtickets.html page.
      • Allows for the customization of the text and accommodates change of language.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      constantALLVENUES.txt

       

       

      Description:

      • The default text for the venue drop down at the top of the TMtickets.html page.
      • Allows for the customization of the text and accommodates change of language

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      constantALLYEARS.txt

       

       

      Description:

      • The default text for the year drop down.
      • Allows for the customization of the text to accommodate change of language.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      constantMONTHS.txt

       

       

      Description:

      • The default text for month drop downs.
      • Allows for the customization of the text to accommodate change of language

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      constantNEWPATRON.txt

       

       

      Description:

      • The default text for adding a new patron in the left column of the TMpatronUpdate.html page.
      • Allows for the customization of the text and accommodates change of language

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      constantPATRONCONTACTEXISTING.txt

       

       

      Description:

      • The default text for contact information within the TMpatronUpdate.html page.
      • The contact type is coded into Theatre Manager. The sequence numbers are listed within this page and should not be altered.
      • The location options are based on the default selection for Patron Location within Setup >> System Tables >> Code Tables of Theatre Manager.
      • In this page the number 2 appears twice. It the value is undefined in the Theatre Manager database the online sales will leave the text in this location blank.
      • Allows for the customization of the text and accommodates change of language

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      constantPATRONCONTACTNEW.txt

       

       

      Description:

      • The default text for contact information within the TMpatronNew.html page.
      • The contact type is coded into Theatre Manager. The sequence numbers are listed within this page and should not be altered.
      • The location options are based on the default selection for Patron Location within Setup >> System Tables >> Code Tables of Theatre Manager.
      • In this page the number 2 appears twice. It the value is undefined in the Theatre Manager database the online sales will leave the text in this location blank.
      • Allows for the customization of the text and accommodates change of language

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      constantYESNO.txt

       

       

      Description:

      • The default text for the anonymous and corporate drop down at the top of the TMdonation.html page.
      • Allows for the customization of the text and accommodates change of language

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      NextEventEmpty.html

       

       

      Description:

      • Displays an empty field in place of the date where there isn't a performance on that date or the performance for that date is not listed as available for sale online.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      NextEventNormal.html

       

       

      Description:

      • Displays the performance information on the performance date within the calendar.
      • This information is pulled directly from the Theatre Manager database.
      • Only performances indicated as available for sale via the web under the Performance tab of Setup >> Events in the Theatre Manager database will appear.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      NextVolEmpty.html

       

       

      Description:

      • Displays an empty field under a date where there is no scheduled volunteer activity for that day.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      NextVolNormal.html

       

       

      Description:

      • Displays the volunteer information on the calendar for the date when the volunteer is scheduled to perform an activity.
      • The volunteer activity is pulled directly from the Theatre Manager database.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      palmCheckin.html

       

      Description:

      • This pages is sent as a response to hand held scanners during the Check In process.
      • The page provides the status of the admission, the beep associated with the status and the reason for the message.
      • The scanner needs to be set to the check in option prior to scanning tickets.
      • If the ticket status is set to Not Used within Theatre Manager scanning the ticket will change the status and indicate the ticket is a "GO" for admission.
      • If the ticket status is set to Used within Theatre Manager the result will be the "STOP" screen. This is due to a ticket previously being scanned as checked in but not being scanned as checked out. Thus the status is still Used within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      • This page is called by a hand held scanner.

      Page(s) Referenced:

      • Not Applicable

      palmCheckout.html

       

      Description:

      • This pages is sent as a response to hand held scanners during the check out process.
      • The page provides the status of the admission, the beep associated with the status and the reason for the message.
      • The scanner needs to be set to the check out option prior to scanning tickets.
      • If the ticket status is set to Used within Theatre Manager scanning the ticket will change the status and indicate the ticket is a "GO" for check out.
      • If the ticket status is set to Not Used within Theatre Manager the result will be the "STOP" screen. This is caused by a ticket that has not previously been scanned into the venue. Thus the status is still Not Used within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      • This page is called by a hand held scanner.

      Page(s) Referenced:

      • Not Applicable

      palmTime.html

       

      Description:

      • This page displays the current date and time for the web listener it reaches.
      • The page is designed for testing to ensure Apache and at least one web listener are up and running.
      • Arts Management Systems uses a tool called InterMapperwhen testing client sites where online sales are experiencing frequent outages. InterMapper is set to request the palmTime.html page. When the page is not available, a message is sent by email to the indicated recipients.
      • If another tool is used for monitoring online sales, it is recommended that this be the page it checks for activity. This will ensure tools, such as google analytics, do not present false statistics for online activity due to monitoring.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      • Not Applicable.

      Page(s) Referenced:

      • Not Applicable.

      pleaseWaitMessage.html

       

       

      Description:

      • Acts as a place saver for the pleaseWaitMessgeFuction.html message.
      • Each page containing the pleaseWaitMessage.html reference also contains a reference to the pleaseWaitMessageFunction.html. When a button within the page references the OnClick-process() function the Please Wait message is pulled from the script within the pleaseWaitMessgeFuction.html page. The text is displayed on the page in the location of the pleaseWaitMessage.html place saver.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      PrevEventEmpty.html

       

      Description:

      • Displays an empty field in place of the date where there isn't a performance on that date or the performance for that date is not listed as available for sale online.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      PrevEventNormal.html

       

       

      Description:

      • Displays the performance information on the performance date within the calendar.
      • This information is pulled directly from the Theatre Manager database.
      • Only performances indicated as available for sale via the web under the Performance tab of Setup >> Events in the Theatre Manager database will appear.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      PrevVolEmpty.html

       

      Description:

      • Displays an empty field under a date where there is no scheduled volunteer activity for that day.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      PrevVolNormal.html

       

       

      Description:

      • Displays the volunteer information on the calendar for the date when the volunteer is scheduled to perform an activity.
      • The volunteer activity is pulled directly from the Theatre Manager database.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      TMoldCartDetailsPrint.html

      Description:

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      rowCartCoupon.html

       

       

      Description:

      • Displays the details of the Coupon Code applied to the cart within the online sales.
      • The coupon code is setup in Theatre Manager under Setup >> System Tables >> Coupons and Pre-Access Codes. For more information on setting up coupon codes click here.
      • A coupon code can be entered in the TMcart.html or TMtickets.html page.
      • Once the code is added it will appear in the TMcart.html page.
      • The details of the coupon are pulled directly from Theatre Manager.
      • To remove a coupon check the box to the far right of the coupon in the cart and click the Remove button at the bottom of the window. The patron can add the coupon to the cart again if desired while available redemption exist.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      rowCartCourse.html

       

       

      Description:

      • Displays the quantity and price of the course when more then one admission to the course is purchased in the online sales.
      • The information is pulled directly from Theatre Manager.
      • If only one admission to the course is purchased this line will not appear.
      • For details on how to setup a course click here.
      • To alter the price of a course admission or remove a course when too many are added to the cart the entire course purchase must be removed. Check the box to the far right of the first registration for the course and click the Remove button at the bottom of the window. The course can then be purchased again selecting the desired price and or quantity.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      rowCartCourseNewGroup.html

       

       

      Description:

      • Displays the course details, quantity, course location and price added to the online cart.
      • The information is pulled directly from Theatre Manager.
      • For details on how to setup a course click here.
      • To alter the price of a course admission or remove a course when too many are added to the cart the entire course purchase must be removed. Check the box to the far right of the first registration for the course and click the Remove button at the bottom of the window. The course can then be purchased again selecting the desired price and or quantity.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      rowCartDonation.html

       

       

      Description:

      • Displays the details of the Donation(s) added to the cart within the online sales.
      • Donations can be added to a cart on the TMcart.html or TMdonation.html page.
      • For steps on how to enable a donation campaign for online sales click here.
      • To remove a donation check the box to the far right of the donation in the cart and click the Remove button at the bottom of the window.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      rowCartFestival.html

       

       

      Description:

      • Displays the quantity and price of a festival seating or general admission ticket when more then one admission to the performance is purchased in the online sales.
      • The information is pulled directly from Theatre Manager.
      • If only one admission to the performance is purchased this line will not appear.
      • For details on how to setup a new festival seating performance click here.
      • To change the price of a festival seating ticket or remove a ticket when too many are added to the cart the entire performance purchase must be removed. Check the box to the far right of the first ticket for the performance and click the Remove button at the bottom of the window. The patron can purchase tickets for the performance again selecting the desired price or quantity.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      rowCartFestivalNewGroup.html

       

       

      Description:

      • Displays the performance details, quantity, performance location, seating location and price of the festival seating or general admission ticket added to the online cart.
      • The information is pulled directly from Theatre Manager.
      • For details on how to setup a new festival seating or general admission performance click here.
      • To change the price of a festival seating ticket or remove a ticket when too many are added to the cart the entire performance purchase must be removed. Check the box to the far right of the first ticket for the performance and click the Remove button at the bottom of the window. The patron can purchase tickets for the performance again selecting the desired price or quantity.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      rowCartMailFee.html

       

       

      Description:

      • Displays the details of the Mailing Fee added to the cart within the online sales.
      • It's recommended the fee be turned off with Theatre Manager rather then removed from the source code in the event the fee may be used in the future.
      • A Mailing Fee can be turned off and on using the Mail To Patron option under the Web Options tab in Setup >> Company Preferences in Theatre Manager. Uncheck the box to remove the Mail Me My Tickets button from the online sales.
      • The value of the Mailing Fee is determined by the fee selected in the Mail Fee box under the Web Options tab of Setup >> Company Preferences with Theatre Manager.
      • The TMcart.html and TMcheckout.html pages both allow the patron to request the items in their cart to be mailed.
      • To remove the mail fee check the box to the far right of the fee in the cart and click the Remove button at the bottom of the window. The order will no longer be flagged with a patron wants tickets mailed status within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      rowCartOrderCouponFee.html

       

      Description:

      • Displays the name and value of the fee associated with a Coupon. This fee is only added to the Order when the subsequent Coupon is added to the cart.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowCartOrderFee.html

       

       

      Description:

      • Displays the details of the Internet Order Fee added to the cart within the online sales.
      • This Fee can be edited by double clicking on the Order Internet fee in Setup >> System Tables >> Fee Tables.
      • Often the external description for the fee is titled Convenience Fee. The name of the fee can be altered by editing the External Name field in the setup of the fee within Theatre Manager.
      • The fee is automatically added to the order based on the fee setup. Removing the Check from the Automatically Add To Order box within Theatre Manager will remove the fee from online sales.
      • The value of the fee can be altered under the Calculation tab of the fee setup within Theatre Manager. There are options to charge a per ticket fee, per order fee and to add tax to the fee within the setup.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      rowCartPass.html

       

       

      Description:

      • Displays the details of the Pass(s), Gift Certificates(s) or Membership(s) added to the cart within the online sales.
      • A Pass in the Theatre Manager database is called a Member Type by default. Often an organization will change the default name to pass, gift certificate, gc or other such options.
      • Member types can be added to a cart from the TMpass.html page.
      • For steps on how to enable a member type for online sales click here.
      • To remove a member type check the box to the far right of the type in the cart and click the Remove button at the bottom of the window.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      rowCartReserve.html

       

       

      Description:

      • Displays the quantity and price of the reserved seating ticket when more then one admission to the reserved performance is purchased in the online sales.
      • The information is pulled directly from Theatre Manager.
      • If only one admission to the performance is purchased this line will not appear.
      • For details on how to setup a new reserved seating performance click here.
      • To change the price of a reserved seating ticket, change the seating location or remove a ticket when too many are added to the cart the entire performance purchase must be removed. Check the box to the far right of the first ticket for the performance and click the Remove button at the bottom of the window. The patron can purchase tickets again for the performance selecting the desired section, quantity and price.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      rowCartReserveNewGroup.html

       

       

      Description:

      • Displays the performance details, quantity, performance location, seating location and price of a reserved seating ticket added to the online cart.
      • The information is pulled directly from Theatre Manager.
      • For details on how to setup a new reserved seating performance click here.
      • To change the price of a reserved seating ticket, change the seating location or remove a ticket when too many are added to the cart the entire performance purchase must be removed. Check the box to the far right of the first ticket for the performance and click the Remove button at the bottom of the window. The patron can purchase tickets again for the performance selecting the desired section, quantity and price.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      rowCartSub.html

       

       

      Description:

      • Displays the details of the performance, price and seating location within the season package in the online cart.
      • The information is pulled directly from Theatre Manager.
      • For details on how to setup a season subscription package click here.
      • To change the price of a subscription package, change the seating location or remove a ticket when too many are added to the package the entire package must be removed. Check the box to the far right of the first line of the ticket for the package and click the Remove button at the bottom of the window. The patron can purchase the package again selecting the desired section, quantity and price.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      rowCartSubNewGroup.html

       

       

      Description:

      • Displays the details of the season package, the first performance, the seat price and the seating location added to the online cart.
      • The information is pulled directly from Theatre Manager.
      • For details on how to setup a season subscription package click here.
      • To change the price of a subscription package, change the seating location or remove a ticket when too many are added to the package the entire package must be removed. Check the box to the far right of the first line of the ticket for the package and click the Remove button at the bottom of the window. The patron can purchase the package again selecting the desired section, quantity and price.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      rowCheckoutCoupon.html

       

      Description:

      • Displays the name of the fee and it's value in the checkout confirmation when it's been added to an online sale.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowCheckoutCourse.html

       

      Description:

      • Displays the name and location of the course as well as the price in the checkout confirmation when it's been added to an online sale.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowCheckoutDonation.html

       

      Description:

      • Displays the name of the donation campaign, the publication name and value of the donation in the checkout confirmation when it's been added to an online sale.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowCheckoutFestival.html

       

      Description:

      • Displays the name, location and price of a festival seating performance in the checkout confirmation when it's been added to an online sale.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowCheckoutMailFee.html

       

      Description:

      • Displays the mailing fee and it's value in the checkout confirmation when it's been added to an online sale.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowCheckoutOrderCouponFee.html

       

      Description:

      • Displays the name of the fee and it's value in the checkout confirmation when it's been added to an online sale.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowCheckoutOrderFee.html

       

      Description:

      • Displays the name name and value of an order fee when it's been added to an online sale.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowCheckoutPass.html

       

      Description:

      • Displays the name and value of the member type/pass in the checkout confirmation when it's been added to an online sale.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowCheckoutReserve.html

       

      Description:

      • Displays the name, location, seat and price of a reserved seating performance in the checkout confirmation when it's been added to an online sale.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowCheckoutSub.html

       

      Description:

      • Displays the name of the subscription, seating location and price in the checkout confirmation when it's been added to an online sale.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowCheckoutSubNewGroup.html

       

      Description:

      • Displays the name of the subscription, seating location, venue and price in the checkout confirmation when it's been added to an online sale.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowFutureTicketCourse.html

       

      Description:

      • Displays the course detail including the promotion, price, order number and date/time purchased for future courses. This information is pulled of the Theatre Manager database.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowFutureTicketFestival.html

       

      Description:

      • Displays the detail for festival seating tickets including the promotion, price, order number and date/time purchased for future courses. This information is pulled of the Theatre Manager database.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowFutureTicketHeader.html

       

      Description:

      • Displays the date, time, name of the event and the location for future courses, general admission or reserved seating events. This information is pulled of the Theatre Manager database.
      • If the Print At Home option is turned on in Company Preferences and for the Performance a Print Tickets button will also appear. This allows patron to print their ticket for admission to the Performance.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowFutureTicketPrintCourse.html

       

      Description:

      • Displays the course detail including the promotion, price, order number and date/time purchased for future courses. This information is pulled of the Theatre Manager database.
      • If the Print At Home option is turned on in Company Preferences and for the Course a bar code will appear before the course tect. This allows patron to print this page and present it as admission to the Course.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowFutureTicketPrintFestival.html

       

      Description:

      • Displays the detail for festival seating tickets including the promotion, price, order number and date/time purchased for future courses. This information is pulled of the Theatre Manager database.
      • If the Print At Home option is turned on in Company Preferences and for the Performance a bar code will appear before the text Festival Seating. This allows patron to print this page and present it as admission to the Performance.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowFutureTicketPrintHeader.html

       

      Description:

      • Displays the date, time, name of the event and the location for future courses, general admission or reserved seating events. This information is pulled of the Theatre Manager database.
      • Also contains the column headers for the bar code, seating location, price, order and purchase date displayed on the TMfutureTicketsPrint.html page.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowFutureTicketPrintReserved.html

       

      Description:

      • Displays the detail for reserved seating tickets including the section/row/seat, promotion, price, order number and date/time purchased for future courses. This information is pulled of the Theatre Manager database.
      • If the Print At Home option is turned on in Company Preferences and for the Performance a bar code will appear before the seating location. This allows patron to print this page and present it as admission to the Performance.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowFutureTicketReserved.html

       

      Description:

      • Displays the detail for reserved seating tickets including the section/row/seat, promotion, price, order number and date/time purchased for future courses. This information is pulled of the Theatre Manager database.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowOldCartCoupon.html

       

      Description:

      • Displays the coupon details for coupon added to a historical cart within the online sales.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowOldCartCourse.html

       

      Description:

      • Displays the course detail of a course added to a historical cart within the online sales.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      rowOldCartDonation.html

       

      Description:

      • Displays the donation details for donations added to a historical cart within the online sales.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      rowOldCartFestival.html

       

      Description:

      • Displays the detail for festival seating tickets including the promotion, price, order number and date/time purchased for future courses. This information is pulled of the Theatre Manager database.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowOldCartHeader.html

       

      Description:

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowOldCartMailFee.html

       

      Description:

      • Displays the details of the mail fee added to a historical online cart.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowOldCartOrderCouponFee.html

       

      Description:

      • Displays the details of the fee associated with a coupon from a history online cart.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowOldCartOrderFee.html

       

      Description:

      • Displays the name of the fee added to a historical cart within the online sales.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowOldCartPass.html

       

      Description:

      • Displays the member type or pass details for pass added to a historical cart within the online sales.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowOldCartPrintCoupon.html

       

      Description:

      • Displays the coupon details for coupon added to a historical cart within the online sales.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowOldCartPrintCourse.html

       

      Description:

      • Displays the course detail of a course added to a historical cart within the online sales.
      • If the Print At Home option is turned on in Company Preferences and for the Course a bar code will appear before the text Course. This allows patron to print this page and present it as admission to the Course.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowOldCartPrintDonation.html

       

      Description:

      • Displays the donation details for donations added to a historical cart within the online sales.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowOldCartPrintFestival.html

       

      Description:

      • Displays the detail for festival seating tickets including the promotion, price, order number and date/time purchased for future courses. This information is pulled of the Theatre Manager database.
      • If the Print At Home option is turned on in Company Preferences and for the Performance a bar code will appear before the text Festival Seating. This allows patron to print this page and present it as admission to the Performance.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowOldCartPrintOrderCouponFee.html

       

      Description:

      • Displays the details of the fee associated with a coupon from a history online cart.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowOldCartPrintOrderFee.html

       

      Description:

      • Displays the name of the fee added to a historical cart within the online sales.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowOldCartPrintPass.html

       

      Description:

      • Displays the member type or pass details for pass added to a historical cart within the online sales.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowOldCartPrintReserve.html

       

      Description:

      • Displays the detail for reserved seating tickets including the section/row/seat, promotion, price, order number and date/time purchased for future courses. This information is pulled of the Theatre Manager database.
      • If the Print At Home option is turned on in Company Preferences and for the Performance a bar code will appear before the text Festival Seating. This allows patron to print this page and present it as admission to the Performance.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowOldCartPrintSub.html

       

      Description:

      • Displays the details of a subscription ticket added to a historical cart within the online sales.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowOldCartReserve.html

       

      Description:

      • Displays the detail for reserved seating tickets including the section/row/seat, promotion, price, order number and date/time purchased for future courses. This information is pulled of the Theatre Manager database.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowOldCartSub.html

       

      Description:

      • Displays the details of a subscription ticket added to a historical cart within the online sales.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowPatronAddress.html

       

       

      Description:

      • Displays address lines, City, Province/State, Postal/Zip Code and a Country drop down fields to enter patrons address information. This information is added to the Theatre Manager database.
      • Asterisk next to fields indicate mandatory data that must be entered for the Theatre Manager database.

      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):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      rowPatronContact.html

       

       

      Description:

      • Displays contact fields for entering a patrons fax number, phone number or web site into the Theatre Manager database.

      Questions and Answers:

      Q:
      A:
      ____________________________________________________________

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      rowPatronEmail.html

       

       

      Description:

      • Displays a field for entering the patrons email address.
      • If the patron is inserting their email address into the database to create a new record fields for entering their password also appears.

      Questions and Answers:

      Q:
      A:
      ____________________________________________________________

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      rowPatronEmailLimitedProfile.html

       

       

      Description:

      • Displays a field where a patron can enter their email address for a limited profile.
      • If the patron is not logged in to the online sales a password field will also appear to create a limited profile account in the Theatre Manager database.

      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):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowPerfDetailCal.html

       

      Description:

      • Displays the Performance details in a calendar view.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowPerfHeaderCal.html

       

      Description:

      • Displays the month at the top of the calendar and the days of the week for each column within the calendar.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowSubBookedFestival.html

       

       

      Description:

      • Displays the details of a festival seating ticket for the season package.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowSubBookedHeader.html

       

      Description:

      • Displays the details of a season packages purchased for the first time this year.
      • In contains the name and information for the package as well as the status of the package.
      • This page pulls the details of the package from the Theatre Manager database and references additional pages for the seat information.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      rowSubBookedReserved.html

       

      Description:

      • Displays the details of a reserved seating ticket for the season package.
      • When multiple seats are booked a line will appear for each seat within the package.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowSubNewDetail.html

       

      Description:

      • Displays the name of the season package and the venue it takes place in. This information is pulled from the season package setup within Theatre Manager.

      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:

      • Not Applicable.

      rowSubNewHeader.html

       

      Description:

      • Displays the column heads for new season subscriptions and the button to purchase a new subscription.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      rowSubNewNone.html

       

      Description:

      • Displays a message when there are no new subscriptions available for sale online.

      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):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowSubNoSeat.html

       

      Description:

      • Displays text indicating there are no season subscription seats available in the desired seating section. This can happen when all seats in the section are sold/held or when there is no online pricing available for the seats.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowSubRenewAnonymous.html

       

      Description:

      • The text explaining why a patron cannot see their existing subscriptions when they are not currently logged into the online sales.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      rowSubRenewFestival.html

       

       

      Description:

      • Displays the details of a festival seating ticket for a renewed season package.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowSubRenewHeader.html

       

       

      Description:

      • Displays the details of a season packages renewed for the coming year.
      • In contains the name and information for the package as well as the status of the package.
      • This page pulls the details of the package from the Theatre Manager database and references additional pages for the seat information.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      rowSubRenewReserved.html

       

       

      Description:

      • Displays the details of a reserved seating tickets for a renewed season package.
      • When multiple seats are booked a line will appear for each seat within the package.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowSubReserve.html

       

      Description:

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      rowTicketCourse.html

       

      Description:

      • Displays "Course" and lists the available online pricing options. This information is pulled from within the Theatre Manager database.
      • The pricing available online is determined by the price and promotion setup within the course in Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowTicketEvent.html

       

       

      Description:

      • Displays the details the Performance from within the Theatre Manager database.
      • 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.
        ____________________________________________________________

        Location:

        htdocs/1/WebPagesEN/TMtemplates/

        Able to Call Page(s):

        Called By Page(s):

        Page(s) Referenced:

        • Not Applicable

      rowTicketEventExport.html

       

      Description:

      • Do Not Alter This Page.
      • This pages is used in conjunction with the TicketTrove mobile device application. The application will soon be available for iPhone and iPad interfaces.
      • The information within the page is pulled directly from Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowTicketEventExportCustom.html

       

      Description:

      • Pull Event information for Performance available for sale online directly from Theatre Manager.
      • This page can be customized to pull the desired Event information for external viewing in the TMticketsExportCustom.html page.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowTicketFestival.html

       

       

      Description:

      • Displays the description for a festival seating ticket and lists the available online pricing options. This information is pulled from within the Theatre Manager database.
      • The term Festival Seating can be altered in Setup >> Company Preferences under the Appearance tab within Theatre Manager.
      • The pricing available online is determined by the price and promotion setup within the event in Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      rowTicketNoSeat.html

       

      Description:

      • Displays text indicating there are no seats available in the desired seating section. This can happen when all seats in the section are sold/held or when there is no online pricing available for the seats.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowTicketPageList.html

       

       

      Description:

      • Provides numeric page numbers in hyperlink form at the bottom of the TMtickets.html page for navigating to additional pages of performances not visible on the current page.
      • The number of performances listed on the page is directly related to Max Events settings under the Web Options tab in Setup >> Company Preferences of Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowTicketReserve.html

       

       

      Description:

      • Displays the section, row, seat number, sales notes and lists the available online pricing options. This information is pulled from within the Theatre Manager database.
      • The name of the seat (section, row, seat number) as well as the sales notes are pulled directly from the Map for the venue within the online sales.
      • The pricing available online is determined by the price and promotion setup within the event in Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      rowVolDetailCal.html

       

      Description:

      • A volunteers scheduled activities are pulled from within the Theatre Manager database to populate the calendar view on the TMvolunteer.html page.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowVolHeaderCal.html

       

      Description:

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowVolHistoryDetail.html

       

      Description:

      • A volunteers scheduled activities are pulled from within the Theatre Manager database to populate the list view on the TMvolunteer.html page.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      rowVolHistoryHeader.html

       

      Description:

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      setACTIVITY_LIST.html

       

       

      Description:

      • Displays the personnel/volunteer activity the patron is scheduled to performed.
      • If the patron is not currently scheduled to perform an activity there will be nothing to list.
      • To access the personnel module open the desired patrons record and click the Personnel button at the top of the window within Theatre Manager. To learn more about scheduling an activity for a patron after the Personnel window is open click here.
      • Please note the word Personnel may have been customized within Theater Manager. Often it is replace with Volunteer.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setACTIVITY_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** under the Activity column when there patron is not scheduled for an activity within Theatre Manager.
      • To avoid this message the patron can be scheduled for a position in the Personnel/Volunteer module within Theatre Manager. To access this module open the patrons record within Theatre Manager and click the Personnel button at the top of the window. Steps on how to schedule an activity for a patron can be found by clicking here.
      • Please note the word Personnel may have been customized within Theater Manager. Often it is replaced with Volunteer.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setCAMPAIGN_LIST.html

       

       

      Description:

      • The drop down list of donation campaigns available for online sales as indicated within Theatre Manager.
      • To add campaigns to the list click Setup >> System Tables >> Donation Campaigns inside Theatre Manager. Double click on the desired campaign and select the Edits tab. Check the box for Accepted on the Internet. Close the window to save the changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setCAMPAIGN_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the Donation Campaign drop down when there is no donation campaigns indicated as available online within Theatre Manager.
      • To avoid this message go to Setup >> System Tables >> Donation Campaigns. Double click on the desired campaign and select the Edits tab. Check the box for Accepted on the Internet. Close the window to save the changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setCCMONTH_LIST.html

       

       

      Description:

      • Presents a list of Months in the credit card expiry month drop down that the patron can choose from in order to enter the expiry date of their credit card for payment.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setCCMONTH_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the credit card expiry month field when there is are no active merchant accounts within Theatre Manager.
      • The merchant account must be available for online sales in order to process credit cards. Go to Setup >> System Tables >> Merchant Accounts. Double click on the merchant account to open it. Check the box for Enable Card Use By The Web Listener. Close the window to save the changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setCOUNTRY_LIST.html

       

       

      Description:

      • Displays a list of Countries from within the database.
      • The options in the list can be edited in the Theatre Manager database by going to Setup >> System Tables >> Code Tables and selecting Country in the left column. Double click on any of the listings to make changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setCOUNTRY_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the Country drop down when there is no online Countries within Theatre Manager.
      • The most common reason for this messages is there are not Country options available online. To avoid this message go to Setup >> System Tables >> Code Tables. Select Country in the left column and double click on the desired Country in the right column. Check the box for Available At Internet. Close the window to save the changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setEMAIL_LOCATION_LIST.html

       

       

      Description:

      • Displays the name of the email location based on the data from the patron record within Theatre Manager.
      • The location can only be changed in the patron contact card from within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      setEMAIL_LOCATION_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the email location drop down when there are no locations type marked as available for sale online within Theatre Manager.
      • This drop down allows for patrons to select the location of their email address.
      • To avoid this message click Setup >> System Tables >> Code Tables within Theatre Manager. Select Paton Location from the left column. Double click on the type that should be available online. Check the box for Available at Website. Close the window to save the changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      setEVENT_LIST.html

       

       

      Description:

      • Presents the future Events in a drop down list based on their available for sale via the web status within Theatre Manager.
      • Events made active by the use of a Pre-Access Code will not appear in the drop down.
      • This drop down allows for patrons to search by event title to locate their desired performance.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setEVENT_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the event drop down when there are no performances marked as available for sale online within Theatre Manager.
      • To avoid this message click the Events icon at the top of the window in Theatre Manager. Open an Event and select the Performance tab. Select one performance and check the box at the top of the window for Allow Selling Via The Internet. Close the window to save the changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setFAX_LOCATION_LIST.html

       

       

      Description:

      • Displays the name of the fax location based on the data from the patron record within Theatre Manager.
      • The location can only be changed in the patron contact card from within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      setFAX_LOCATION_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the fax number location drop down when there are no locations type marked as available for sale online within Theatre Manager.
      • This drop down allows for patrons to select the location of their fax number.
      • To avoid this message click Setup >> System Tables >> Code Tables within Theatre Manager. Select Paton Location from the left column. Double click on the type that should be available online. Check the box for Available at Website. Close the window to save the changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      setGENRE_LIST.html

       

       

      Description:

      • Displays a drop down of Genre's for the performances available for sale within the online sales. The options in the drop down are populated based on the genre selected in the Marketing tab of the Event within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setGENRE_LISTempty.html

       

       

      Description:

      • Displays All Genres when there are no performances listed or genres have not been indicated for the performances listed in the online sales the drop down will state All Genres.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setHOUSEHOLD_PATRON_LIST.html

       

       

      Description:

      • Displays a list of names associated with the email address on the TMpatronUpdate.html page.
      • This list of names is pulled directly from the Theatre Manager database. It is a list of names from the household that use the same email address. Only patrons within the same household can share an email address.
      • The patron can choose the name of the record they wish to update within Theatre Manager. Clicking the Update Account button at the bottom of the window will updated the database.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setHOUSEHOLD_PATRON_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** when the patron access the
      • TMpatronUpdate.html and is not logged in.
      • To avoid this message the patron can log into the online sales.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setHOUSEHOLD_PATRON_SELECTION_LIST.html

       

       

      Description:

      • Displays a list of names associated with the email address on the TMCart.html page.
      • This list of names is pulled directly from the Theatre Manager database. It is a list of names from the household that use the same email address. Only patrons within the same household can share an email address.
      • The patron can choose the name of the patron they wish to assign the course to within Theatre Manager.
      • This drop down will only appear if there is more then one member of the household within Theatre Manager.
      • If the patron would like to assign a course to another person they will need to add that patron to their household. This is done by clicking Account at the top of the window, choose the New Patron option in the list on the left and add the patron information to their household.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setHOUSEHOLD_PATRON_SELECTION_LISTempty.html

       

       

      Description:

      • Displays the text **will be selected after logging in** in the Attendee drop down when the patron is not currently signed in to online sales.
      • To avoid this message the patron can login to online sales before adding a course to their online cart or they can sign in after adding the course and return to the cart.
      • If the patron would like to assign a course to another person they will need to add that patron to their household. This is done by logging into the online sales, clicking Account at the top of the window, choose the New Patron option in the list on the left and add the patron information to their household.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setLOGIN_PATRON_LIST.html

       

       

      Description:

      • Displays a list of names associated with the email address entered at the time of login.
      • This list of names is pulled directly from the Theatre Manager database. It is a list of names from the household that use the same email address. Only patrons within the same household can share an email address.
      • The patron must choose a name from the list and this will be the record the cart is added to within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setMERCHANT_LIST.html

       

       

      Description:

      • Displays the payment methods available for completing the order when there is more then one currency.
      • This option requires a second merchant account to be created under Setup >> System Tables >> Merchant Types within Theatre Manager. For details on how to create a merchant account click here.
      • The Enable Card Use By The Web Listener box should be checked under the Software Type of the Merchant Account.
      • In the setup of the new merchant account select the Currency tab. Select the desired country from the Currency Country drop down and enter a G/L Account to allocate the difference from the exchange rate.
      • The Exchange Rate should be entered under Setup >> System Tables >> Currency Exchange within Theatre Manager. For more information on setting up a Currency Exchange rate click here.
      • Select the Cards tab and add the credit cards that should be processed using this currency rate. If a card can be used for more then one rate a second payment method should be setup for the card type. For more information on setting up payment methods click here.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setMERCHANT_LISTempty.html

       

       

      Description:

      • Hides the option to select a currency.
      • To avoid a single currency a second merchant account needs to be setup in Setup >> System Tables >> Merchant Accounts within Theatre Manager. The Currency Country field under the Currency tab needs to be set to something other then the same Country as the existing merchant account.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setMONTH_LIST.html

       

       

      Description:

      • Presents the twelve months of the year in a drop down list.
      • This allows for patrons to search by month to find their desired date faster.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setMONTH_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the month drop down when there are no performances marked as available for sale online within Theatre Manager.
      • To avoid this message click the Events icon at the top of the window in Theatre Manager. Open an Event and select the Performance tab. Select one performance and check the box at the top of the window for Allow Selling Via The Internet. Close the window to save the changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setPASS_LIST.html

       

       

      Description:

      • Presents the memberships or passes in a drop down list based on their available for sale via the web status within Theatre Manager.
      • This drop down allows for patrons to select the member type they wish to purchase.
      • Member types are made available for sale by checking the Via The Internet box under the Edits tab of Setup >> System Tables >> Member Types within Theatre Manager.
      • Many organizations choose to rename Memberships to Passes, Gift Certificates, or Other Sales Items. The name of this area within Theatre Manager is at the discretion of the organization.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setPASS_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the event drop down when there are no member types marked as available for sale online within Theatre Manager.
      • This drop down allows for patrons to select the pass type they wish to purchase.
      • To avoid this message click Setup >> System Tables >> Member Types within Theatre Manager. Open a member type that should be offered online. Select the Edits tab and check the box for Via The Internet under the Allow Membership To Be Purchased. Close the window to save the changes.
      • Many organizations choose to rename Memberships to Passes, Gift Certificates, or Other Sales Items. The name of this area within Theatre Manager is at the discretion of the organization.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setPAYMENT_LIST.html

       

       

      Description:

      • Presents the payment methods in a drop down list based on their settings within Theatre Manager.
      • This drop down allows for patrons to select the credit card type they wish to use in order to complete their purchase.
      • To make a payment method available online go to Setup >> System Tables >> Code Tables. Select Payment Methods in the left column and double click on the desired method. Check the Available At Internet box and close the window to save changes.
      • Only credit card payment methods can be made available online at this time.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setPAYMENT_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the payment drop down when there are no payment methods available for online within Theatre Manager.
      • This drop down allows for patrons to select the credit card type they wish to use in order to complete their purchase.
      • This message can appear if there are no payment methods enabled for online sales. To correct this go to Setup >> System Tables >> Code Tables. Select the Payment Methods in the left column. Double click on the payment method and check the box for Available At Internet. Close the window to save the changes.
      • The merchant account for the payment method must also be available for online sales. Go to Setup >> System Tables >> Merchant Accounts. Double click on the merchant account to open it. Check the box for Enable Card Use By The Web Listener. Close the window to save the changes.
      • If the payment methods previously appeared but suddenly do not it's possible an End of Day may need to be run in Theatre Manager or that PC Charge (a credit card processing option) is currently not available.
      • Only credit card payment methods can be made available online at this time.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setPHONE_LOCATION_LIST.html

       

       

      Description:

      • Displays the name of the phone location based on the data from the patron record within Theatre Manager.
      • The location can only be changed in the patron contact card from within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      setPHONE_LOCATION_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the phone number location drop down when there are no locations type marked as available for sale online within Theatre Manager.
      • This drop down allows for patrons to select the location of their phone number.
      • To avoid this message click Setup >> System Tables >> Code Tables within Theatre Manager. Select Paton Location from the left column. Double click on the type that should be available online. Check the box for Available at Website. Close the window to save the changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      setPROMOTIONSSUB_LIST.html

       

       

      Description:

      • Provides a drop down of available season pricing for the displayed seats.
      • The availability of a price depends on the setup of the pricing structure for an event and sales promotion.
      • The desired price needs to be available for use within the performance that are a part of the package. This is adjusted by opening the event, selecting the Pricing tab, single clicking on the performance in the left column, double clicking on the price code and placing a check mark in the Allow Price Code To Be Used box within Theatre Manager.
      • At least one season promotion enabled for online sales needs to be active for the performance in the package. In Theatre Manager open the Event, select the Promotions tab and change the Promotions Shown drop down in the lower right corner to All. Locate the desired season sales promotion, select it and click the Allow Use button at the bottom of the window.
      • At least one of the price points that are active for the season performances can not be listed in the Excludes Price Code field of sales promotion. The Excludes Price Code field is found in the Description tab of the promotion. The promotion can be found in Setup >> System Tables >> Sales Promotions within Theatre Manager.
      • The Season Promotion must be a Season Ticket Type for G/L Posting under the Description tab of Setup >> System Tables >> Sales Promotions within Theatre Manager.
      • The Season Promotion needs to be available for online sales. The Via The Internet box needs to be checked in the Edits tab of the promotion found in Setup >> System Tables >> Sales Promotions within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setPROMOTIONSSUB_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the price drop down when there are is no available season pricing for a package within Theatre Manager.
      • This drop down allows for patrons to select price at which they will purchase their tickets.
      • To prevent this message the desired price needs to be available for use within the performances that are a part of the package. This is adjusted by opening the event, selecting the Pricing tab, single clicking on the performance in the left column, double clicking on the price code and placing a check mark in the Allow Price Code To Be Used box within Theatre Manager.
      • To prevent this message at least one season promotion enabled for online sales needs to be active for the performance in the package. In Theatre Manager open the Event, select the Promotions tab and change the Promotions Shown drop down in the lower right corner to All. Locate the desired season sales promotion, select it and click the Allow Use button at the bottom of the window.
      • To prevent this message at least one of the price points that are active for the season performances can not be listed in the Excludes Price Code field of sales promotion. The Excludes Price Code field is found in the Description tab of the promotion. The promotion can be found in Setup >> System Tables >> Sales Promotions within Theatre Manager.
      • To prevent this message the Season Promotion must be a Season Ticket Type for G/L Posting under the Description tab of Setup >> System Tables >> Sales Promotions within Theatre Manager.
      • To prevent this message the Season Promotion needs to be available for online sales. The Via The Internet box needs to be checked in the Edits tab of the promotion found in Setup >> System Tables >> Sales Promotions within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setPROMOTIONS_LIST.html

       

       

      Description:

      • Provides a drop down of available pricing for the displayed seats.
      • The availability of a price depends on the setup of the pricing structure for an event and the sales promotion.
      • The desired price needs to be available for use within the performance. This is adjusted by opening the event, selecting the Pricing tab, single clicking on the performance in the left column, double clicking on the price code and placing a check mark in the Allow Price Code To Be Used box within Theatre Manager.
      • At least one promotion enabled for online sales needs to be active for the performance. In Theatre Manager open the Event, select the Promotions tab and change the Promotions Shown drop down in the lower right corner to All. Locate the desired Internet sales promotion, select it and click the Allow Use button at the bottom of the window.
      • At least one of the price points that are active for the performance can not be listed in the Excludes Price Code field of sales promotion. The Excludes Price Code field is found in the Description tab of the promotion. The promotion can be found in Setup >> System Tables >> Sales Promotions within Theatre Manager.
      • The Sales Promotion needs to be available for online sales. The Via The Internet box needs to be checked in the Edits tab of the promotion found in Setup >> System Tables >> Sales Promotions within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setPROMOTIONS_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the price drop down when there is no available online pricing for the performance within Theatre Manager.
      • This drop down allows for patrons to select price at which they will purchase their tickets.
      • The availability of a price depends on the setup of the pricing structure for an event and sales promotion.
      • To prevent this message the desired price needs to be available for use within the performance. This is adjusted by opening the event, selecting the Pricing tab, single clicking on the performance in the left column, double clicking on the price code and placing a check mark in the Allow Price Code To Be Used box within Theatre Manager.
      • To prevent this message at least one promotion enabled for online sales needs to be active for the performance. In Theatre Manager open the Event, select the Promotions tab and change the Promotions Shown drop down in the lower right corner to All. Locate the desired Internet sales promotion, select it and click the Allow Use button at the bottom of the window.
      • To prevent this message at least one of the price points that are active for the performance can not be listed in the Excludes Price Code field of sales promotion. The Excludes Price Code field is found in the Description tab of the promotion. The promotion can be found in Setup >> System Tables >> Sales Promotions within Theatre Manager.
      • To prevent this message the Sales Promotion needs to be available for online sales. The Via The Internet box needs to be checked in the Edits tab of the promotion found in Setup >> System Tables >> Sales Promotions within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setPROVINCE_LIST.html

       

       

      Description:

      • Displays a list of Provinces or States available online depending on the Country the patron chooses in the drop down window.
      • The options in the list can be edited in the Theatre Manager database by going to Setup >> System Tables >> Code Tables and selecting Province in the left column. Double click on any of the listings to make changes.
      • Please note the word province may be changed to State within the Theatre Manager database.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setPROVINCE_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the Province/State drop down when there is no online Provinces/States within Theatre Manager.
      • The most common reason for this messages is there are not provinces for the region available online. To avoid this message go to Setup >> System Tables >> Code Tables. Select Provinces in the left column and double click on the desired province in the right column. Check the box for Available At Internet. Close the window to save the changes.
      • Please note the word province may be changed to State within the Theatre Manager database.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setREASON_TO_BUY_LIST.html

       

       

      Description:

      • Presents a drop down of options for the patron to choose from indicating how they heard about the performances they purchased. This information is used for marketing purposes.
      • Additional options can be added to the Theatre Manager database by going to Setup >> System Tables >> Code Tables, clicking Order Reason to Buy in the left column and using the New button at the top of the window.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setREASON_TO_BUY_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the how did you hear list when there is no available online reasons within Theatre Manager.
      • To avoid this message go to Setup >> System Tables >> Code Tables and select Order Reason To Buy in the left column within Theatre Manager. Double click on one of the option in the right column and check the box for Available At Internet. Close the window to save the changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setSALUTATION_LIST.html

       

       

      Description:

      • Displays the a drop down box of the available online salutations from within Theatre Manager.
      • Only those salutations that have been indicated as Available At Internet within their setup in Theatre Manager will be displayed.
      • To change the visibility of a status online go to Setup >> System Tables >> Code Tables within Theatre Manager. Select Patron Salutations in the left column. Double click on a salutation in the right column that should be available online. Alter the check box for Available At Internet accordingly. Close the window to save the changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setSALUTATION_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the salutation drop down when there is no available salutations within Theatre Manager.
      • To prevent this message go to Setup >> System Tables >> Code Tables within Theatre Manager. Select Patron Salutations in the left column. Double click on a salutation in the right column that should be available online. Check the box for Available At Internet. Close the window to save the changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setSUBSCRIBE_LIST.html

       

       

      Description:

      • Displays a list of available mail lists the patron can subscribe to online.
      • To add a mail list the Allow Patron To Subscribe/Unsubscribe Via The Internet box needs to be checked for the list within Theatre Manager. To access this option click the Mail List button at the top of the window in Theatre Manager. Double click on the desired mail list and select the Description tab. Check the Allow Patron To Subscribe/Unsubscribe Via The Internet box. Close the window to save the changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setSUBSCRIBE_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** when there are no available mail lists for the patron to subscribe to.
      • This can be caused by the lack of available mail lists online or if the patron has subscribed to all available mail lists.
      • To add a mail list the Allow Patron To Subscribe/Unsubscribe Via The Internet box needs to be checked for the list within Theatre Manager. To access this option click the Mail List button at the top of the window in Theatre Manager. Double click on the desired mail list and select the Description tab. Check the Allow Patron To Subscribe/Unsubscribe Via The Internet box. Close the window to save the changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setSUBS_SERIES_LIST.html

       

       

      Description:

      • Presents a list of available series options to choose from in a drop down format.
      • Some organizations have more then one performance within their season package. Each performance is indicated by a series code. This allows Theatre Manager to book the patron into the same night for each event within the season package.
      • Only performances marked as Season Control Performance within the Control House in Theatre Manager will appear in the drop down.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setSUBS_SERIES_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the series drop down when there is no season control performances within the control house in Theatre Manager.
      • Some organizations have more then one performance within their season package. Each performance is indicated by a series code. This allows Theatre Manager to book the patron into the same night for each event within the season package.
      • To avoid this messaged ensure at least on performance has the Season Control Performance box checked within it's setup. This is accessed by clicking the Event button at the top of Theatre Manager, double clicking on the event and selecting the Performance tab.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setTICKET_QTY_LIST.html

       

      Description:

      • Displays a drop down of the quantity of tickets the patron can purchase for the Performance.
      • This number is determined by the number of tickets in the patrons current cart, the system default per order and the performance per order limit.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setTICKET_QTY_LISTempty.html

       

       

      Description:

      • Displays the text **Maximum tickets per order has been reached** in the quantity drop down when the maximum tickets per order has been met.
      • If the maximum quantity of tickets is being meet too soon it's possible to increase the number of tickets per order in the Maximum Tickets field of the Web tab in Setup >> System Preferences within Theatre Manager.
      • The event purchase limit can also impact the maximum tickets a patron can purchase. This limit can be adjusted in the Patron Purchase Limit field located in the Event tab. To access this event click the Events tab at the top of the window and double click on the event to open it within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setUNSUBSCRIBE_LIST.html

       

       

      Description:

      • Displays a list of mail lists the patron can unsubscribe from.
      • This list is populated based on the mail lists the patron has previously subscribed to.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setUNSUBSCRIBE_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** when there are no available mail lists for the patron to unsubscribe from.
      • This can be caused by the lack of available mail lists online or if the patron has not subscribed to any of the available mail lists.
      • To add a mail list the Allow Patron To Subscribe/Unsubscribe Via The Internet box needs to be checked for the list within Theatre Manager. To access this option click the Mail List button at the top of the window in Theatre Manager. Double click on the desired mail list and select the Description tab. Check the Allow Patron To Subscribe/Unsubscribe Via The Internet box. Close the window to save the changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setVENUE_LIST.html

       

       

      Description:

      • Presents a list of Venues, where upcoming events will take place, in a drop down list. The venue is a part of the event setup and the list is based on the events available for sale via the web status within Theatre Manager.
      • This drop down allows for patrons to search for their desired performance by venue.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setVENUE_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the venue drop down when there are no performances marked as available for sale online within Theatre Manager.
      • To avoid this message click the Events icon at the top of the window in Theatre Manager. Open an Event and select the Performance tab. Select one performance and check the box at the top of the window for Allow Selling Via The Internet. Close the window to save the changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setWEBSITE_LOCATION_LIST.html

       

       

      Description:

      • Displays the name of the website location based on the data from the patron record within Theatre Manager.
      • The location can only be changed in the patron contact card from within Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      setWEBSITE_LOCATION_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the website location drop down when there are no locations type marked as available for sale online within Theatre Manager.
      • This drop down allows for patrons to select the location type for their website.
      • To avoid this message click Setup >> System Tables >> Code Tables within Theatre Manager. Select Paton Location from the left column. Double click on the type that should be available online. Check the box for Available at Website. Close the window to save the changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates

      Able to Call Page(s):

      • Not Applicable.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable.

      setYEAR_LIST.html

       

       

      Description:

      • In the calendar view this presents the year(s) in a drop down based on the Season Year for the performances marked as available for sale online within Theatre Manager.
      • For credit card processing the year is programed to display the current year and ten years in advance of the current date.
      • This drop down allows for patrons to search by year to find their desired date faster.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      setYEAR_LISTempty.html

       

       

      Description:

      • Displays the text **Nothing available to select** in the year drop down when there are no performances marked as available for sale online within Theatre Manager.
      • To avoid this message click the Events icon at the top of the window in Theatre Manager. Open an Event and select the Performance tab. Select one performance and check the box at the top of the window for Allow Selling Via The Internet. Close the window to save the changes.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      tmContact.html

       

       

      Description:

      • Pulls the company name, address, telephone number, fax, web site and email address as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager
      • The Google Map link draws on the address for Company tab of Setup >> Company Preferences within Theatre Manager
      • The main web site address is pulled from the Company tab of Setup >> Company Preferences within Theatre Manager

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • maps.google.com
      • The companies web site as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      tmContactHours.html

       

       

      Description:

      • Pulls the company name, address, telephone number, fax, web site and email address as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager
      • The hours of operation are hard coded into this page and may need to be edited to reflect the accurate information for the organization

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • maps.google.com
      • The companies web site as it appears in the Company tab of Setup >> Company Preferences within Theatre Manager.

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      tmFooter.html

      Description:

      • Pulls the Footer details from the Web Listener tab found in Setup >> Company Preferences of Theatre Manager

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      tmLoginForm.html

       

       

      Description:

      • Displays the mandatory fields from the database and their names, need to login to a limited user profile for online sales
      • The mandatory fields are located in the Allow Limited Profile Patrons On section of the Mandatory

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      tmMailListQuickAddInsert.html

       

       

      Description:

      • Populates a list of Mail Lists with check boxes for the patron to indicate the Mail Lists they wish to sign up for.
      • The list can be customized using the Mail List Sequence number from within Theatre Manager
      • Allows for the ability to add subscribing and unsubscribing to a Mail List to any online page

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      tmnavButtons.html

       

      Description:

      • This pages is designed to pull the buttons listed at the top of most pages within the online sales.
      • The name seen on the button can be altered by editing the text within the double quotes. For example changing the work Gift Certificate in value="Gift Certificates" to be Passes or Memberships.
      • It's recommended buttons are commented out rather then deleted in the event they are needed at a later date.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      tmnavLanguages.html

      Description:

      • The language flags only appear when multiple languages are setup. This included uncommenting the lines within this page and adding details under the Web Listener tab of Setup >> Company Preference within Theatre Manager.
      • A line can be added to this file for each desired language.
      • The Language codes for &lang=XX where XX must have a WebPagesXX folder and be found in Theatre Manager under Setup >> Company Preferences in the Web Listener tab.
      • Currently this reference is tied to the tmnavButtons.html page and will appear to the left of the buttons at the top of the window when the references is not commented out.
      • Sample Flag images can be found in the tmGifs folder for referencing.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      Page(s) Referenced:

      • Not Applicable

      tmtermsandconditions.html

       

      Description:

      • An optional page for terms and conditions the patron must agree to prior to purchasing tickets.
      • This page is only displayed when the Acknowledge Terms box is checked under Setup >> Company Preferences in the Web Options tab of Theatre Manager.

      Location:

      htdocs/1/WebPagesEN/TMtemplates/

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMtickets.html


       

      Description:

      • This is traditionally the first pages patrons see when accessing the online sales process. It's the default reference in the page
      • This page contains a list of all performances that have been made available for sale via the web within Theatre Manager.
      • Additional performances may be added to the list when a presales access coupon is in use.
      • The rowTicketEvent.html template can be edited to change the percentage and font colour in the Availability column.
      • To edit the column widths both this page and the rowTicketEvent.html page need to be updated. The later will ensure the contact of the page displays correctly.

      Questions and Answers:
      Q: How can the Availability options column be changed?
      A: The text in the Availability column is located in the rowTicketsEvent.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:

      TMticketsExport.html

       

       

      Description:

      • Do Not Alter This Page.
      • This pages is used in conjunction with the TicketTrove mobile device application. The application is currently available for iPhone and iPad interfaces.

      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):

      • Not Applicable.

      Called By Page(s):

      • Not Applicable.

      Page(s) Referenced:

      TMticketsExportCustom.html

       

      Description:

      • Provides a list of Events in a drupal like CMS/front end style in an XML format.
      • This information can be viewed through the web rather then needing direct access to Theatre Manager.
      • The page will provide details of the Event that can be used as an import to other application or for creating customized links on an organizations main website.
      • Viewing the source code of the page will display the field reference details.
      • Only Performances that are indicates as available for sale online will be visible.
      • The rowTicketEventExportCustom.html page can be altered to display the desired Event information for this page.

      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):

      • Not Applicable.

      Called By Page(s):

      • Not Applicable.

      Page(s) Referenced:

      TMticketsMaxPurchased.html

       

      Description:

      • The online sales has a defined maximum number of tickets that can be purchases per order, per event and per performance. When any of these limits have been reached this page is displayed.
      • The Maximum Tickets in an Order is set under the Web tab in Setup >> System Preferences within Theatre Manager.
      • The Patron Purchase Limit for an event is indicated in the Event tab of Setup >> Events within Theatre Manager.
      • The Web Purchase Limit for a performance setting can be found by clicking Setup >> Events, selecting the Performance tab, double clicking in the desired performances and selecting the Web Settings tab.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMticketsSoldOut.html

       

      Description:

      • Tickets for an event area available to purchase online until the event is sold out, it is manually removed from online sales or the performance has reached the minutes prior to start remove time.
      • If a performance sells out while a patron is in the middle of the sales process they will receive this page. However, if the performance is already sold out prior to their attempt to purchase tickets it will be indicated in the Availability column of the TMtickets.html page.
      • The Remove Minutes Before It Starts is set under the Web tab in Setup >> System Preferences within Theatre Manager.
      • The Stop Sales in Advance for an event is indicated in the Event tab of Setup >> Events within Theatre Manager.
      • The Stop Sales in Advance for a performance setting can be found by clicking Setup >> Events, selecting the Performance tab, double clicking in the desired performances and selecting the Web Settings tab.

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      tmVenue Folder

      The tmVenue folder contains the pages for locations tickets are sold to within the online sales. The Default page is used only when a custom pages is not available for the venue. It pulls information such as the address, capacity, notes and seating image directly from the Map within Theatre Manager.

      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 map number. The map number is located in the Map # column under Setup >> Theatre Maps in Theatre Manager.

      tmVenueDefault.html

       

      Description:

      • A descriptive page of a Venue tickets are sold for.
      • The Default page pulls the venue information directly from the Map setup with Theatre Manager.
      • This page can be duplicated and the word Default changed to the map number from within Theatre Manager. The page can then be customized for the specific venue.

      Location:

      htdocs/1/WebPagesEN/tmVenue

      Able to Call Page(s):

      Called By Page(s):

      Page(s) Referenced:

      TMvolunteer.html

       

      Description:

      • THIS PAGE IS CURRENTLY UNDER CONSTRUCTION

      Location:

      htdocs/1/WebPagesEN

      Able to Call Page(s):

      • Not Applicable At This Time

      Called By Page(s):

      • Not Applicable At This Time

      Page(s) Referenced:

      Powered By Apache images

      Description:

      The following files in the htdocs folder are all variations on the Powered By Apache logo:

      • apache_pb.gif
      • apache_pb.png
      • apache_pb22_ani.gif
      • apache_pb22.gif
      • apache_pb22.png

      Location:

      htdocs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      • Not Applicable

      apacheindex.html

       

      Description:

      Location:

      htdocs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      • Not Applicable

      favicon.ico

       

      Description:

      • A favicon (short for favorites 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.

      Location:

      htdocs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      • Appears in the address bar next to the title when supported for all pages.

      index.html

      Description:

      • This is the first page accessed when Apache is running.
      • This page redirects to the page listed in the window.location.href reference.
      • The address referenced by the windows.location.href should be altered so localhost replaced by the sub domain for the ticketing site.
      • The title of the online pages when quick referenced is found within the title references of this page.
      • The cached preferences for this page and how long they are stored are also listed on this page.

      Location:

      htdocs

      Able to Call Page(s):

      • The page listed in the window.location.href reference.

      Called By Page(s):

      • This is the first page accessed in Apache when it's running.

      ReadMe About Configuring Index.html.txt

      Description:

      • Contains information on how to accurately edit the index.html file to work in conjunction with Theatre Managers online web pages.
      • Provided details on how to create links from the main web site to various different areas of the online sales. This includes direct links to Donation Campaigns, Gift Certificates, Passes or Season Subscriptions Packages.

      Location:

      htdocs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      • Not Applicable

      robots.txt

      Description:

      • Robots.txt is a text (not html) file you put on your site to tell search robots which pages you would like them not to visit. Robots.txt is by no means mandatory for search engines but generally search engines obey what they are asked not to do. It is important to clarify that robots.txt is not a way from preventing search engines from crawling your site (i.e. it is not a firewall, or a kind of password protection) and the fact that you put a robots.txt file is something like putting a note “Please, do not enter” on an unlocked door – e.g. you cannot prevent thieves from coming in but the good guys will not open to door and enter. That is why we say that if you have really sensitive data, it is too naive to rely on robots.txt to protect it from being indexed and displayed in search results.

      Location:

      htdocs

      Able to Call Page(s):

      • Not Applicable

      Called By Page(s):

      • Not Applicable

      TMsysNoListeners.html

      Description:

      • This page is most commonly referenced when the Apache machine has recently been restarted and there is no communication between Apache and the Web Listener or if a connection between Apache and the Web Listener has never been established.
      • If the Apache machine has been restarted and online sales is scheduled to be down for a period of time this page should be edited to reflect the information the patron will see during the outage. For example: Our online ticketing is currently unavailable, please contact the box office for assistance.
      • Contains a reference line at the bottom of the page that should point to the companies main web page once edited.
      • This page can be avoided by logging in to Theatre Manager as a web listener within the network or by correcting any network issues that may be preventing communication between Apache and the Web Listener.

      Location:

      htdocs

      Able to Call Page(s):

      • The Companies main web site.

      Called By Page(s):

      • The httpd.conf file within Apache.

      Branding web sales to make it look like the main web site

      Theatre Manager comes with a set of web pages that can be dropped in place so you can have web sales running in very short order. These web pages provide all the functionality of the web sales component of Theatre Manager including ticket sales, online donations, gift certificate sales, managing the shopping cart, and much more.

      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:

      1. Use the sample pages and review the sales process. Also see examples of what others have done to show possibilities.
      2. If possible, change only the style sheets as the first step. Then use the pages for a while before making deeper changes.
      3. Make some adjustments to notes within Theatre Manager to sales options, text, notes, maps etc that display on the web. It allows control of a number of changes to remain in the hands of the end user.
      4. As a final step, adjust the text content on a few important web pages. Likely, there should only be changes required for mailing, box office hours and a couple of other pages.

        If you do want to change a page, copy that page into the same location in the WebPagesEN/tmCustom folder and make the changes to the COPY. Theatre Manager will reference the tmCustom folder first and use the page there, if it finds one.

        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 HTDOCS folder of the apache server that is set up when Theatre Manager is first installed. If you need remote access to this folder, you may need to set up an FTP server or File Sharing to the HTDOCS folder, or simply do the work on the apache machine. (Talk to your IT person if you need to set up access via something like Filezilla).

      Types of Pages

      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

      Adjusting Content on Important Web Pages

      We recommend making changes to the style sheets only. However, we do know that some venues like to customize additional text on pages. This is only possible if you change the actual web page itself.

      You are free to edit additional pages if you choose. However, a couple of caveats:

      • Generally, change anything in the page that you want as long as it doesn't affect the function of the page. Save the original page so you can compare it to your changes if something stops working
      • Do not change the names of any field within a <form> tag or an <input> tag
      • Do not adjust any calculation between a <field> and </field> tag without consulting with an Arts Management Systems support person first. These calculations and field names are items merged back into a page from the database before it is sent to the user and in effect, are the guts of the web process
      • try to only edit files if they begins with an upper case TM.... as in TMhome.html.
      • try to avoid changing any file in the 'tmTemplates' folder that starts with 'row' or 'set', or 'cell' or lowercase 'tm'

      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:

      • TMcart.html - to put rules about exchanges and mailing
      • TMhome.html - to add general rules about your venue's key policies
      • TMdonation.html - to add comments about online giving
      • TMlogin.html - to alter any rules or notes that user sees on the login screen
      • TMError.txt - to alter some of the error message text for some error conditions
      • TMtickets.html - to add any last minute details regarding online purchasing before patrons choose their performances
      • tmTemplates/tmContactHours.html - to set rules about when you are open
      • tmTemplates/tmContact.html - to adjust any text around how to contact the venue
      • tmTemplates/tmnavButtons.html - to adjust which buttons are acceptable for the venue at the top of the page

      Changing Style Sheets

      The fastest way to remake the web sales pages is to change a couple of Style Sheets and create a gif/jpeg for a couple of files. This can be done in minutes - and you have a completely new look to the web site without changing anything else.

      The files that you want to change can be found within the HTDOCS folder. Look for a folder with a number on it (for most sites it will be '1' - this represents the outlet in a multi company version of Theatre Manager). Look for a folder called WebPagesEN and inside that, for tmGifs. This will be the base folder for the remainder of this section. The files to change are:

      There are two style sheet files within the tmGifs folder. By altering them, you can change most of the look of Theatre Manager web sales. Specifically, change styleButtons.css to change the look of the buttons at the top of the page and stylePages.css to change the look of the tables, text, error messages, buttons, etc. within each page.

      There are some files like pageHeader.gif. Make replacement files for those that contain your header or how you want the top of each page look. If you prefer a different look for the numbers in steps, or the handicapped logo there are some other .gif files within this folder that you may want to change . Make your image, save the image with the same name as the one in the tmGifs folder (ensure you match the case), replace the existing file in the tmGifs folder, and you will have a new look to your page

      Correcting Crimson Navigation Buttons

      More content here

      Make Changes within Theatre Manager for Web Content

      Over the years, we have found that some changes web designers want to make were the same from venue to venue. We have taken those changes away from the web pages and allowed the end user to do them, without the assistance of a web designer. This makes Theatre Manager part of the 'content management' for the web site.

      The kinds of changes that fall into this category and involve no web design work are:

      • Pagination of the list of events presented to the user
      • Maps showing recommended seats or the seats in the venue
      • Search setup for finding best seating
      • Naming of events, gift certificates, passes, season subscription packages, donation campaigns
      • Naming of sales promotions, price codes and display options for these two fields
      • Naming of mail lists that users can sign up to
      • Allowing people to browse anonymously for tickets - or- required to sign in at the beginning
      • Print at home ticketing
      • Availability of coupon codes on the web
      • Comments and text to describe performances, events, donations, passes, subscriptions, etc
      • Onsale dates for events
      • Time outs for sales in a shopping cart
      • and a number of other business processes

      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.

      Permitted Web Ticket Printing Options

      In Company Preferences (Setup >> Company Preferences >> Web Options tab), there are options to add a Mail Fee to online orders, Print at home tickets, and Hold for Will Call. If you check the box to add a Mail Fee, then you must also select the fee from your fee tables. For more about Fees, click here.

      Specifically, this help page focuses on the three options on the right side of the Web Options tab.

      Logical order of these checkboxes:

      There is a hierarchy to how the permitted web ticketing options work.

      • Condition #1: If the 'Mail to patron' option is checked and made available to the patron on the web and patron selects the option to have their tickets mailed, any other settings anywhere in Theatre Manager are ignored. The following will happen:
        • All tickets in the order will have the date printed field cleared; simply meaning that the tickets have not yet been printed.
        • 'Ticket handling' order will be set as 'Mail to Patron'
      • Condition #2: if 'Mail to patron' is available and the user does not select it on their web order (or cannot select it because you have removed the code from the web page), then one of two things can happen:
        • Condition 2a: If you turn on 'Print at home' for the event, then that is what the patron gets. There is no other option. The web pages print their tickets at home. This is because you (the venue) want the tickets printed at home to save on ticket printing costs or because you need absolute access control to the event. It is a Venue's Marketing/Operations choice to make the customers take their tickets as print at home. This is because print at home will need an infrastructure in place like scanners, special access lines or what have you to deal with print at home.
        • Condition 2b: If 'Print at home' is not available, then the only remaining option is 'Hold at Will Call', by default.

    • Condition #3: If no other option (above) is selected or occurs, the tickets will NOT be marked printed. They will need printing manually at a later date.
    • Further Clarification of the above

      If you do not allow a mail fee in the company preferences, then the 'Mail to Patron' button will not be available online. The default behavior of the pages is to hide the button.

      So, in the case of 'no mail fee allowed', then there are two remaining options in Company Preferences:

      • [ ] Print at home
      • [ ] Hold for will call

      If you check 'Print at home' for tickets, bar codes will be printed for events/performances for later scanning when the patron arrives at the venue - But only for the performances where 'Print at home' is also enabled. This implies that you may chose to let people print bar code on some events and not others.

      If bar codes can be printed for an event, the tickets are marked as printed in Theatre Manager, regardless. Therefore, when you do a batch print of unprinted tickets, the print at home tickets will never be included in the batch print. 'Hold for Will Call' has NO meaning in that context because the customer has already got tickets with bar codes on them.

      If bar codes are not allowed on an event, then those tickets are not marked as printed. That, in essence, defaults into 'hold for willcall' (but only the tickets that had no barcode).

      In the case where 'Mail to patron' is checked, then all other options are ignored, regardless of setting (i.e. "mail me tickets, plus I'll also print the bar code for those tickets" simply doesn't make sense).

      Taking it a step further, if mail to patron is not enabled and print at home is not enabled, then the only choice is 'Hold for Will Call'.

      Sample Web Sites

      The following are examples of what a few our of the hundreds of venues using Theatre Manager have done to the sample web pages. It gives you an idea that the sky can be the limit and a fair degree of personal branding is very possible very quickly.

      Make sure and click on the 'tickets' buttons on these sites.

      Customization Ideas

      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.

       

      Redirecting the Add Code button for Coupons and Pre-Access Codes

      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.


      <tr>
      <td align="right">Presale Access Code</td>
      <td><input name="CH_CODE" type=text id="CH_CODE" value="<field>CH_CODE</field>" size=40 maxlength=40 onBlur="this.value=this.value.toUpperCase()">
      </td>
      <td align="left"><input name="btnCouponAccept" type=submit class="new" onMouseOver="pviiClassNew(this,'newover')" onMouseOut="pviiClassNew(this,'new')" value="Add Code" onClick="process()">
      <input name='param' type='hidden' value ='altbtn=btnTicket'>
      </td>
      </tr>

    • The above represents the Add Code button.
    • To change the destination of the button the value following btn needs to be edited.
    • Change btnTickets to btnCart will direct the button to the TMcart.html page.
    •  

      Adding Anchors to a page

      When adding anchors it's important to comment out the F_HTML_IMAGE_SERVER reference at the top of the page. This means the reference will needed to be added directly to any images within the pages and the style sheet lines in order for them to appear. They would look something like this:

      href="<field>F_HTML_IMAGE_SERVER</field>tmGifs/styleButtons.css"
      href="<field>F_HTML_IMAGE_SERVER</field>tmGifs/stylePages.css"

      The link and reference to an anchor must fall outside of a Table. Additional items can be added to the link such as a class reference to the style sheets that will determine the attributes of the link. The link would look something like:

      <a class="link" href="#gc">Gift Certificates</a>

      The anchor would look something like this:

      <h3 id="gc">Gift Certificates</h3>

       

      Adding a Direct Purchase Button for a Donation

      The lines below are an example of a donation button with a fixed value. Clicking on the button will add a donation to the online cart for the value hidden within the button. The donation campaign is also specified within the button. This code can be added to any page within the online sales. It would most commonly appear within a customized TMdonation.html page or a TMcart.html page.

      <FORM ACTION="<field>F_HTML_FIREWALL</field>online" METHOD=POST>
      <input name="btnDonationAccept" type=submit value="YES! Add $2 for SPAC's Classical Kids Program sponsored by Union College" class="new" onMouseOver="pviiClassNew(this,'newover')" onMouseOut="pviiClassNew(this,'new')" onClick="process()">
      <input type="hidden" id="DD_DC_SEQ" name="DD_DC_SEQ" value="59">
      <input type="hidden" id="DD_AMOUNT_PLEDGE" name="DD_AMOUNT_PLEDGE" value="25">
      </form>

    • The first and last line open and close the form for the button. All information within the form is passed together when the button is clicked.
    • The btnDonationAccept line represents the actual button. The value reference within this line indicates the text that will appear on the button.
    • The line containing DD_DC_SEQ has a value of 59. This number references the sequence number for the donation campaign with Theatre Manager.
    • The DD_AMOUNT_PLEDGE also contains a value reference. In this example the value is equal to 25. This is the dollar value of the donation to be added to the patrons purchase.
    •  

      Adding a Direct Purchase Button for a Member Type

      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.


      <FORM ACTION="<field>F_HTML_FIREWALL</field>online" METHOD=POST>
      <input name="btnReservePass" type=submit value="Purchase Youth Golfer - $100" class="new" onMouseOver="pviiClassNew(this,'newover')" onMouseOut="pviiClassNew(this,'new')" onClick="process()">
      <label for="Membership"><strong> Golfers Name </strong> </label>
      <input type="hidden" name="MT_SEQ" value="23">
      <input type="hidden" name="PS_QUANTITY" value="1">
      <textarea name="M_NOTES" cols="49" rows="1"><field>M_NOTES</field></textarea>
      </form>

    • The first and last line open and close the form for the button. All information within the form is passed together when the button is clicked.
    • The btnReservePass line represents the actual button. The value reference within this line indicates the text that will appear on the button.
    • The label for line contains details regarding the use of the button. In this example the text appears to the right of the button as it falls after the btnReservePass line.
    • The line containing MT_SEQ has a value reference of 23. This value is the member type sequence number from within Theatre Manager.
    • The PS_QUANTITY line contains a value of 1. This is the quantity of memberships to be added to the order.
    • The code above does not contain a dollar value reference. The value is set within Theatre Manager during the setup of the Member Type.
    • The M_NOTES line contains a field designed for the patron to type any additional notes required for the membership. For example, if the membership were to apply to two patron this field could be used to type the second patrons name.
    •  

      Adding a Purchase Option for a Specific Member Type

      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>

    • The code above places the Membership in a table. This allows for the description to appear in the left column and the options to appear in the right column. It also breaks up the title, quantity and message.
    • The section that opens and closes with the select function is a drop down. It allows the patron to choose the quantity of the item they wish to purchase. Each number in the drop down is represented by one of the option value lines.
    • The btnReservePass line represents the actual button. The value reference within this line indicates the text that will appear on the button.
    • The code above does not contain a dollar value reference. The value is set within Theatre Manager during the setup of the Member Type.
    •  

      Adding a Button to Apply a Specific Coupon Code

      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.

      <tr>
      <td>input name="btnCouponAccept" type=submit class="new" id="CH_CODE" onMouseOut="pviiClassNew(this,'new')" value="Special Promotion Button" onClick="process()">
      <td>input type="hidden" id="CH_CODE" name="CH_CODE" value="1234">
      <td>input name='param' type='hidden' value ='altbtn=btnTicket'>
      </td>
      </tr>

    • The text Special Promotion Button would be the wording that appears on the button.
    • In the part of the statement that reads value=1234 replace 1234 with the actual coupon code from within the setup of the Coupon itself. This would be the code the patron traditional would type in order to add the coupon to their cart.
    •  

      Eliminating the Price Code Drop Down

      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&gtF_HTML_PROMOTIONS_LIST.1.SC_SEQ</field&gt:
      <field&gtF_HTML_PROMOTIONS_LIST.1.PC_SEQ</field&gt:
      <field&gtF_HTML_PROMOTIONS_LIST.1.SCD_ORIGINAL_SC_SEQ</field&gt:
      <field&gtF_HTML_PROMOTIONS_LIST.1.SCD_ORIGINAL_PRICE_CODE</field&gt:
      <field&gtF_HTML_PROMOTIONS_LIST.1.SCD_SAVINGS</field&gt"
      <field&gtF_HTML_SELECTED</field&gt&gt
      <field&gtpick(D_WEB_SHOW_PROMOTION,'',con(F_HTML_PROMOTIONS_LIST.1.SC_DESCRIPTION,' '))</field&gt
      <field&gtpick(D_WEB_SHOW_PRICE_CODE,'',con(F_HTML_PROMOTIONS_LIST.1.PC_DESCRIPTION,' '))</field&gt$<field&gtF_HTML_PROMOTIONS_LIST.1.PS_TOTAL_COST</field&gt

    • The above code will print the default ticket price for the performance. This is based on the Default setting at the bottom of the Pricing tab within the event.
    • The line containing D_WEB_SHOW_PROMOTION will print the name of the default sales promotion.
    • The line containing D_WEB_SHOW_PRICE_CODE will display the name of the price code and the value of the ticket.
    •  

      Google Analytics

      Google Analytics is a powerful way of understanding how people come to arrive at your web site and which pages they visit.

      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 U-XXXXX-X number that will replace the value in the sample code.

      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:

      1. Open a Form Letter (existing or create new). If you need instructions, click here.
      2. Right-click in the letter at the footer or wherever you'd like to embed the code to bring up the context window .
      3. Select Insert Data Base Field > Current Addresses > Google Analytics Code.

      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.

      PCI DSS Cross Reference/Index

      This section indicates where to find information about selected PCI DSS requirements in the Theatre Manager installation documentation. The purpose of this section is so that you can look at a PCI requirement and then view where in our implementation documentation this is referenced.

      The PCI Security Council supplies a document to merchants that provides a Prioritized Approach to PCI compliance. This document is quite good because it breaks down the standards into 6 milestones - what to do first, what to do second, etc. according to what will have the biggest impact in safeguarding your customer data.

      Following the document and this index should help you address that most important PCI implementation standards quickly.

      Source: PCI Prioritized Approach

      Build and Maintain a Secure Network

      In the past, theft of financial records required a criminal to physically enter an organization’s business site. Now, many payment card transactions (such as debit in the U.S. and “chip and pin” in Europe) use PIN entry devices and computers connected by networks. By using network security controls, organizations can prevent criminals from virtually accessing payment system networks and stealing cardholder data.

      Requirement 1: Install and maintain a firewall

      Install and maintain a firewall and router configuration to protect cardholder data

      Firewalls are devices that control computer traffic allowed into and out of an organization’s network, and into sensitive areas within its internal network. Routers are hardware or software that connects two or more networks.

      Section PCI Requirement Comments
      1.1 Establish firewall and router configuration standards that formalize testing whenever configurations change; that identify all connections to cardholder data (including wireless); that use various technical settings for each implementation; and stipulate a review of configuration rule sets at least every six months.  
      1.1.1 A formal process for approving and testing all network connections and changes to the firewall and router configurations
       
      1.1.2 Current network diagram with all connections to cardholder data, including any wireless networks
      Refer to Recommended Layout and adapt as neccessary
      1.1.3 Requirements for a firewall at each Internet connection and between any demilitarized zone (DMZ) and the internal network zone  
      1.1.4 Description of groups, roles, and responsibilities for logical management of network components  
      1.1.5 Documentation and business justification for use of all services, protocols, and ports allowed, including documentation of security features implemented for those protocols considered to be insecure  
      1.1.6 Requirement to review firewall and router rule sets at least every six months  
      1.2 Build a firewall configuration that denies all traffic from "untrusted" networks and hosts, except for protocols necessary for the cardholder data environment. Firewall rules
      1.2.1 Restrict inbound and outbound traffic to that which is necessary for the cardholder data environment.
       
      1.2.2 Secure and synchronize router configuration files.
       
      1.2.3 Install perimeter firewalls between any wireless networks and the cardholder data environment, and configure these firewalls to deny or control (if such traffic is necessary for business purposes) any traffic from the wireless environment into the cardholder data environment. refer to venue lan setup
      1.3 Prohibit direct public access between the Internet and any system component in the cardholder data environment.  
      1.3.1 Implement a DMZ to limit inbound and outbound traffic to only protocols that are necessary for the cardholder data environment.  
      1.3.2 Limit inbound Internet traffic to IP addresses within the DMZ.  
      1.3.3 Do not allow any direct routes inbound or outbound for traffic between the Internet and the cardholder data environment.  
      1.3.4 Do not allow internal addresses to pass from the Internet into the DMZ.  
      1.3.5 Restrict outbound traffic from the cardholder data environment to the Internet such that outbound traffic can only access IP addresses within the DMZ.  
      1.3.6 Implement stateful inspection, also known as dynamic packet filtering. (That is, only "established" connections are allowed into the network.)  
      1.3.7 Place the database in an internal network zone, segregated from the DMZ.  
      1.3.8 Implement IP masquerading to prevent internal addresses from being translated and revealed on the Internet, using RFC 1918 address space. Use network address translation (NAT) technologies—for example, port address translation (PAT).  
      1.4 Install personal firewall software on any mobile and/or employee-owned computers with direct connectivity to the Internet that are used to access the organization's network. May be required when Updating TM

      Requirement 2: Change Vendor Passwords

      Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters

      The easiest way for a hacker to access your internal network is to try default passwords or exploits based on default system software settings in your payment card infrastructure. Far too often, merchants do not change default passwords or settings upon deployment. This is akin to leaving your store physically unlocked when you go home for the night. Default passwords and settings for most network devices are widely known. This information, combined with hacker tools that show what devices are on your network can make unauthorized entry a simple task – if you have failed to change the defaults.

      Section PCI Requirement Comments
      2.1 Always change vendor-supplied defaults before installing a system on the network. This includes wireless devices that are connected to the cardholder data environment or are used to transmit cardholder data. change vendor supplied passwords
      2.1.1 For wireless environments connected to the cardholder data environment or transmitting cardholder data, change wireless vendor defaults, including but not limited to default wireless encryption keys, passwords, and SNMP community strings. Ensure wireless device security settings are enabled for strong encryption technology for authentication and transmission. refer to venue lan setup
      2.2 Develop configuration standards for all system components that address all known security vulnerabilities and are consistent with industry-accepted definitions.  
      2.3 Encrypt all non-console administrative access such as browser/Web-based management tools. Theatre manager does not provide web management tools. Use RDC or equivalent internally for remote access management.
      2.2.1 Implement only one primary function per server
       
      2.2.2 Disable all unnecessary and insecure services and protocols (services and protocols not directly needed to perform the device's specified function). refer to Disable SNMP service on Practical Automation Ticket Printers
      2.2.3 Configure system security parameters to prevent misuse  
      2.2.4 Remove all unnecessary functionality, such as scripts, drivers, features, subsystems, file systems, and unnecessary Web servers.  
      2.4 Shared hosting providers must protect each entity's hosted environment and cardholder data (details are in PCI DSS Appendix A: "Additional PCI DSS Requirements for Shared Hosting Providers.")  

      Protect Cardholder Data

      Cardholder data refers to any information printed, processed, transmitted or stored in any form on a payment card. Organizations accepting payment cards are expected to protect cardholder data and to prevent their unauthorized use – whether the data is printed or stored locally, or transmitted over a public network to a remote server or service provider.

      Requirement 3: Protect stored cardholder data

      Protect stored cardholder data

      In general, no cardholder data should ever be stored unless it's necessary to meet the needs of the business. Sensitive data on the magnetic stripe or chip must never be stored. If your organization stores PAN, it is crucial to render it unreadable (see 3.4, and table below for guidelines).

      Section PCI Requirement Comments
      3.1 Limit cardholder data storage and retention time to that required for business, legal, and/or regulatory purposes, as documented in your data retention policy. Theatre Manager offers a shredding capability as well as option of meeting schedule C or D compliance
      3.2 Do not store sensitive authentication data after authorization (even if it is encrypted). See guidelines in table below.  
      3.3 Mask PAN when displayed; the first six and last four digits are the maximum number of digits you may display. Not applicable for authorized people with a legitimate business need to see the full PAN. Does not supersede stricter requirements in place for displays of cardholder data such as on a point-of-sale receipt. Refer to PCI compliance statement on PAN etc.
      3.2.1 Do not store the full contents of any track from the magnetic stripe (located on the back of a card, contained in a chip, or elsewhere). This data is alternatively called full track, track, track 1, track 2, and magnetic-stripe data.
      3.2.2 Do not store the card-verification code or value (three-digit or four- digit number printed on the front or back of a payment card) used to verify card-not-present transactions
      3.2.3 Do not store the personal identification number (PIN) or the encrypted PIN block.
      3.4 Render PAN, at minimum, unreadable anywhere it is stored (including on portable digital media, backup media, in logs) by using any of the following approaches:
      • One-way hashes based on strong cryptography
      • Truncation
      • Index tokens and pads (pads must be securely stored)
      • Strong cryptography with associated key management processes and procedures
       
      3.4.1 If disk encryption is used (rather than file- or column-level database encryption), logical access must be managed independently of native operating system access control mechanisms (for example, by not using local user account databases). Decryption keys must not be tied to user accounts. Theatre Manager does not use Disk Encryption. It uses field level encryption for data.
      3.5 Protect cryptographic keys used for encryption of cardholder data from disclosure and misuse. Theatre Manager handles creation and hiding of keys automatically.
      3.5.1

      Restrict access to cryptographic keys to the fewest number of custodians necessary

      3.5.2 Store cryptographic keys securely in the fewest possible locations and forms
      3.6 Fully document and implement all appropriate key management processes and procedures for cryptographic keys used for encryption of cardholder data.

      refer to re-encryption of credit cards for discussion on keys, generation and re-encryption. An upgrade will automatically perform this process if more than 350 days have elapsed since last re-encrption.

      Split 'knolwedge' of the keys is achieved by bringing together a key generated programatically and another portion generated by the customers interfacing with the key creation screen in system preferences.

      Both keys are required to generate the final encryption key. Arts Management never has knowledge of the customers portion of the key. The customer never knows the value of any key.

      3.6.1 Generation of strong cryptographic keys
      3.6.2 Secure cryptographic key distribution
      3.6.2 Secure cryptographic key storage
      3.6.4 Periodic cryptographic key changes
      • As deemed necessary and recommended by the associated application (for example, re-keying); preferably automatically
      • At least annually
      3.6.5 Retirement or replacement of old or suspected compromised cryptographic keys
      3.6.6 Split knowledge and establishment of dual control of cryptographic keys
      3.6.7 Prevention of unauthorized substitution of cryptographic keys
      3.6.8 Requirement for cryptographic key custodians to sign a form stating that they understand and accept their key-custodian responsibilities Customer should have a form signed by the people/person responsible for key management that they reset the key once a year at a minimum or when suspected compromise occurs. Note it will be changed automatically on you during an upgrade if Theatre Manager detects it hasn't been changed for 350 days.

      Requirement 4: encrypt transmission of cardholder data

      Encrypt transmission of cardholder data across open, public networks

      Cyber criminals may be able to intercept transmissions of cardholder data over open, public networks so it is important to prevent their ability to view these data. Encryption is a technology used to render transmitted data unreadable by any unauthorized person.

      Section PCI Requirement Comments
      4.1

      Use strong cryptography and security protocols such as SSL/TLS or IPSEC 2 to safeguard sensitive cardholder data during transmission over open, public networks.

      See PC Charge and Orbital
      4.1.1 Ensure wireless networks transmitting cardholder data or connected 2 to the cardholder data environment, use industry best practices ( e.g., IEEE 802.11i) to implement strong encryption for authentication and transmission.
      • For new wireless implementations, it is prohibited to implement WEP after March 31, 2009.
      • For current wireless implementations, it is prohibited to use WEP after June 30, 2010.
      refer to venue lan setup
      4.2 Never send unencrypted PANs by end-user messaging technologies (for 2 example, e-mail, instant messaging, chat). see link

      Maintain a vulnerability Management Program

      Vulnerability management is the process of systematically and continuously finding weaknesses in an organization’s payment card infrastructure system. This includes security procedures, system design, implementation, or internal controls that could be exploited to violate system security policy.

      Requirement 5: Use and regularly update anti-virus software

      Use and regularly update anti-virus software or programs

      Many vulnerabilities and malicious viruses enter the network via employees’ e-mail and other online activities. Anti-virus software must be used on all systems affected by malware to protect systems from current and evolving malicious software threats.

      Section PCI Requirement Comments
      5.1

      Deploy anti-virus software on all systems commonly affected by malicious software (particularly personal computers and servers).

      See PostgreSQL Server and Apache Server and Workstations and Web Listeners and Remote Box Office
      5.1.1 Ensure that all anti-virus programs are capable of detecting, removing, and protecting against all known types of malicious software.  
      5.2 Ensure that all anti-virus mechanisms are current, actively running, and capable of generating audit logs.  

      Requirement 6: Develop and maintain secure systems and applications

      Develop and maintain secure systems and applications

      Security vulnerabilities in systems and applications may allow criminals to access PAN and other cardholder data. Many of these vulnerabilities are eliminated by installing vendor-provided security patches, which perform a quick-repair job for a specific piece of programming code. All critical systems must have the most recently released software patches to prevent exploitation. Organizations should apply patches to less-critical systems as soon as possible, based on a risk-based vulnerability management program. Secure coding practices for developing payments applications, change control procedures and other secure software development practices should always be followed.

      Section PCI Requirement Comments
      6.1

      Ensure that all system components and software have the latest vendor- supplied security patches installed. Install critical security patches within one month of release.

       
      6.2 Establish a process to identify newly discovered security vulnerabilities (for example, subscribe to alert services freely available on the Internet). Update configuration standards as required by PCI DSS Requirement 2.2 to address new vulnerability issues.  
      6.3 Develop software applications in accordance with PCI DSS (for example, secure authentication and logging) and based on industry best practices and incorporate information security throughout the software development life cycle. These processes must include the following:  
      6.3.1 Testing of all security patches, and system and software configuration changes before deployment, including but not limited to the following:  
      6.3.1.1 Validation of all input (to prevent cross-site scripting, injection flaws, malicious file execution, etc.)  
      6.3.1.2 Validation of proper error handling  
      6.3.1.3 Validation of secure cryptographic storage  
      6.3.1.4 Validation of secure communications  
      6.3.1.5 Validation of proper role-based access control (RBAC)  
      6.3.2 Separate development/test, and production environments  
      6.3.3 Separation of duties between development/test, and production environments  
      6.3.4 Production data (live PANs) are not used for testing or development  
      6.3.5 Removal of test data and accounts before production systems become active  
      6.3.6 Removal of custom application accounts, usernames, and passwords before applications become active or are released to customers  
      6.3.7 Review of custom code prior to release to production or customers in order to identify any potential coding vulnerability.  
      6.4 Follow change control procedures for all changes to system components. The procedures must include the following:  
      6.4.1 Documentation of impact  
      6.4.2 Management sign-off by appropriate parties  
      6.4.3 Testing of operational functionality  
      6.4.4 Back-out procedures  
      6.5 Develop all Web applications (internal and external, and including Web administrative access to application) based on secure coding guidelines such as the Open Web Application Security Project Guide. Cover prevention of common coding vulnerabilities in software development processes, to include the following:  
      6.5.1 Cross-site scripting (XSS)  
      6.5.2 Injection flaws, particularly SQL injection. Also consider LDAP and Xpath injection flaws as well as other injection flaws.  
      6.5.3 Malicious file execution  
      6.5.4 Insecure direct object references  
      6.5.5 Cross-site request forgery (CSRF)  
      6.5.6 Information leakage and improper error handling  
      6.5.7 Broken authentication and session management  
      6.5.8 Insecure cryptographic storage  
      6.5.9 Insecure communications  
      6.5.10 Failure to restrict URL access  
      6.6 For public-facing Web applications, address new threats and vulnerabilities on an ongoing basis and ensure these applications are protected against known attacks by either of the following methods:
      • Reviewing public-facing Web applications via manual or automated application vulnerability security assessment tools or methods, at least annually and after any changes
      • Installing a Web-application firewall in front of public-facing Web applications
       

      Implement Strong access Control Measures

      Access control allows merchants to permit or deny the use of physical or technical means to access PAN and other cardholder data. Access must be granted on a business need-to-know basis. Physical access control entails the use of locks or restricted access to paper-based cardholder records or system hardware. Logical access control permits or denies use of PIN entry devices, a wireless network, PCs and other devices. It also controls access to digital files containing cardholder data.

      Requirement 7: Restrict access to cardholder data

      Restrict access to cardholder data by business need-to-know

      To ensure critical data can only be accessed by authorized personnel, systems and processes must be in place to limit access based on need-to-know and according to job responsibilities. Need-to-know is when access rights are granted to only the least amount of data and privileges needed to perform a job.

      Section PCI Requirement Comments
      7.1

      Limit access to system components and cardholder data to only those individuals whose job requires such access.

       
      7.1.1 Restriction of access rights to privileged user IDs to least privileges necessary to perform job responsibilities  
      7.1.2 Assignment of privileges is based on individual personnel's job classification and function  
      7.1.3 Requirement for an authorization form signed by management that specifies required privileges  
      7.1.4 Implementation of an automated access control system  
      7.2 Establish an access control system for systems components with multiple users that restricts access based on a user's need-to-know, and is set to "deny all" unless specifically allowed  
      7.2.1

      Coverage of all system components

      Refer to employee settings and function access for credit cards
      7.2.2 Assignment of privileges to individuals based on job classification and function
       
      7.2.3 Default "deny-all" setting  

      Requirement 8: Assign a unique ID to each person

      Assign a unique ID to each person with computer access

      Assigning a unique identification (ID) to each person with access ensures that actions taken on critical data and systems are performed by, and can be traced to, known and authorized users.

      Section PCI Requirement Comments
      8.1 Assign all users a unique user name before allowing them to access system components or cardholder data.  
      8.2 Employ at least one of these to authenticate all users: password or passphrase; or two-factor authentication (e.g., token devices, smart cards, biometrics, public keys).  
      8.3 Implement two-factor authentication for remote access to the network by employees, administrators, and third parties. Use technologies such as remote authentication and dial- in service or terminal access controller access control system with tokens; or virtual private network with individual certificates.  
      8.4 Render all passwords unreadable for all system components both in storage and during transmission using strong cryptography based on approved standards  
      8.5 Ensure proper user authentication and password management for non-consumer users and administrators on all system components. Theatre Manager implements PCI standards. You may need a manual process for other applications or hardware.
      8.5.1 Control addition, deletion, and modification of user IDs, credentials, and other identifier objects
      8.5.2 Verify user identity before performing password resets.
      8.5.3 Set first-time passwords to a unique value for each user and change immediately after the first use.
      8.5.4 Immediately revoke access for any terminated users.
      8.5.5 Remove/disable inactive user accounts at least every 90 days.
      8.5.6 Enable accounts used by vendors for remote maintenance only during the time period needed.
      8.5.7 Communicate password procedures and policies to all users who have access to cardholder data.
      8.5.8 Do not use group, shared, or generic accounts and passwords.
      8.5.9 Change user passwords at least every 90 days.
      8.5.10 Require a minimum password length of at least seven characters.
      8.5.11 Use passwords containing both numeric and alphabetic characters.
      8.5.12 Do not allow an individual to submit a new password that is the same as any of the last four passwords he or she has used.
      8.5.13 Limit repeated access attempts by locking out the user ID after not more than six attempts.
      8.5.14 Set the lockout duration to a minimum of 30 minutes or until administrator enables the user ID.
      8.5.15 If a session has been idle for more than 15 minutes, require the user to re-enter the password to re-activate the terminal
      8.5.16 Authenticate all access to any database containing cardholder data. This includes access by applications, administrators, and all other users.  

      Requirement 9: Restrict physical access to cardholder data

      Restrict physical access to cardholder data

      Any physical access to data or systems that house cardholder data provides the opportunity for persons to access and/or remove devices, data, systems or hardcopies, and should be appropriately restricted.

      Section PCI Requirement Comments
      9.1

      Use appropriate facility entry controls to limit and monitor physical access to systems in the cardholder data environment.

       
      9.1.1 Use video cameras or other access control mechanisms to monitor individual physical access to sensitive areas. Review collected data and correlate with other entries. Store for at least three months, unless otherwise restricted by law.  
      9.1.2 Restrict physical access to publicly accessible network jacks  
      9.1.3 Restrict physical access to wireless access points, gateways, and handheld devices.  
      9.2 Develop procedures to help all personnel easily distinguish between employees and visitors, especially in areas where cardholder data is accessible.  
      9.3 Make sure all visitors are handled as follows:  
      9.3.1 Authorized before entering areas where cardholder data is processed or maintained  
      9.3.2 Given a physical token (for example, a badge or access device) that expires and that identifies the visitors as non-employees
       
      9.3.3 Asked to surrender the physical token before leaving the facility or at the date of expiration  
      9.4 Use a visitor log to maintain a physical audit trail of visitor information and activity. Retain the log for at least three months unless otherwise restricted by law.  
      9.5 Store media back-ups in a secure location, preferably off site.  
      9.6 Physically secure all paper and electronic media that contain cardholder data, including the following:  
      9.7 Maintain strict control over the internal or external distribution of any kind of media that contains cardholder data.  
      9.7.1

      Classify the media so it can be identified as confidential.

       
      9.7.2 Send the media by secured courier or other delivery method that can be accurately tracked.  
      9.8 Ensure that management approves any and all media containing cardholder data moved from a secured area, especially when media is distributed to individuals.  
      9.9 Maintain strict control over the storage and accessibility of media that contains cardholder data.  
      9.9.1 Properly maintain inventory logs of all media and conduct media inventories at least annually.  
      9.10 Destroy media containing cardholder data when it is no longer needed for business or legal reasons.  
      9.10.1 Shred, incinerate, or pulp hardcopy materials so that cardholder data cannot be reconstructed.  
      9.10.2 Render cardholder data on electronic media unrecoverable so that cardholder data cannot be reconstructed.  

      Regularly Monitor and Test Networks

      Physical and wireless networks are the glue connecting all endpoints and servers in the payment infrastructure. Vulnerabilities in network devices and systems present opportunities for criminals to gain unauthorized access to payment card applications and cardholder data. To prevent exploitation, organizations must regularly monitor and test networks to find and fix vulnerabilities.

      Requirement 10: Track and monitor all access to network

      Track and monitor all access to network resources and cardholder data

      Logging mechanisms and the ability to track user activities are critical for effective forensics and vulnerability management. The presence of logs in all environments allows thorough tracking and analysis if something goes wrong. Determining the cause of a compromise is very difficult without system activity logs.

      Section PCI Requirement Comments
      10.1

      Establish a process for linking all access to system components to each individual user – especially access done with administrative privileges.

       
      10.2 Implement automated audit trails for all system components to reconstruct the following events: refer to PCI audit Log settings
      10.2.1 All individual accesses to cardholder data  
      10.2.2 All actions taken by any individual with root or administrative privileges  
      10.2.3 Access to all audit trails  
      10.2.4 Invalid logical access attempts  
      10.2 5 Use of identification and authentication mechanisms  
      10.2.6 Initialization of the audit logs  
      10.2.7 Creation and deletion of system-level objects  
      10.3 Record at least the following audit trail entries for all system components for each event: refer to PCI audit Log settings
      10.3.1 User identification  
      10.3.2 Type of event  
      10.3.3 Date and time  
      10.3.4 Success or failure indication  
      10.3.5 Origination of event  
      10.3.6 Identity or name of affected data, system component, or resource  
      10.4 Synchronize all critical system clocks and times.  
      10.5 Secure audit trails so they cannot be altered  
      10.5.1 Limit viewing of audit trails to those with a job-related need  
      10.5.2 Protect audit trail files from unauthorized modifications.  
      10.5.3 Promptly back up audit trail files to a centralized log server or media that is difficult to alter.  
      10.5.4 Write logs for external-facing technologies onto a log server on the internal LAN.  
      10.5.5

      Use file integrity monitoring or change detection software on logs to ensure that existing log data cannot be changed without generating alerts (although new data being added should not cause an alert).

       
      10.6 Review logs for all system components at least daily. Log reviews must include those servers that perform security functions like intrusion detection system (IDS) and authentication, authorization, and accounting protocol (AAA) servers (for example, RADIUS).  
      10.7 Retain audit trail history for at least one year, with a minimum of three months immediately available for analysis (for example, online, archived, or restorable from backup).  

      Requirement 11: Regularly test security systems and processes

      Regularly test security systems and processes

      Vulnerabilities are being discovered continually by malicious individuals and researchers, and being introduced by new software. System components, processes, and custom software should be tested frequently to ensure security is maintained over time. Testing of security controls is especially important for any environmental changes such as deploying new software or changing system configurations.

      Section PCI Requirement Comments
      11.1

      Test for the presence of wireless access points by using a wireless analyzer at least quarterly, or deploying a wireless IDS/IPS to identify all wireless devices in use.

       
      11.2 Run internal and external network vulnerability scans at least quarterly and after any significant change in the network. ASVs are not required to perform internal scans.  
      11.3 Perform external and internal penetration testing at least once a year and after any significant infrastructure or application upgrade or modification (such as an operating system upgrade, a sub-network added to the environment, or a Web server added to the environment). These penetration tests must include the following:  
      11.3.1 Network-layer penetration tests  
      11.3.2 Application-layer penetration tests  
      11.4 Use intrusion detection systems, and/or intrusion prevention systems to monitor all traffic in the cardholder data environment and alert personnel to suspected compromises. Keep all intrusion detection and prevention engines up to date.  
      11.5 Deploy file integrity monitoring software to alert personnel to unauthorized modification of critical system files, configuration files or content files; and configure the software to perform critical file comparisons at least weekly.  

      Maintain an Information Security Policy

      A strong security policy sets the tone for security affecting an organization’s entire company, and it informs employees of their expected duties related to security. All employees should be aware of the sensitivity of cardholder data and their responsibilities for protecting it.

      Requirement 12: Maintain a policy that addresses information security for employees and contractors

      Maintain a policy that addresses information security for employees and contractors

      As part of Theatre Manager's PA-DSS implementation process, creating a policy guide will be brought to the attention of venues desiring to be PCI compliant

      Section PCI Requirement Comments
      12.1

      Test for the presence of wireless access points by using a wireless analyzer at Establish, publish, maintain, and disseminate a security policy that accomplishes the following:

       
      12.1.1 Addresses all PCI DSS requirements  
      12.1.2 Includes an annual process that identifies threats, and vulnerabilities, and results in a formal risk assessment  
      12.1.3 Includes a review at least once a year and updates when the environment changes  
      12.2 Develop daily operational security procedures that are consistent with requirements in this specification (for example, user account maintenance procedures, and log review procedures).  
      12.3 Develop usage policies for critical employee-facing technologies (for example, remote access technologies, wireless technologies, removable electronic media, laptops, personal data/digital assistants (PDAs), email usage and internet usage) to define proper use of these technologies for all employees and contractors. Ensure these usage policies require the following:  
      12.3.1 Explicit management approval  
      12.3.2 Authentication for use of the technology  
      12.3.3 A list of all such devices and personnel with access  
      12.3.4 Labeling of devices with owner, contact information, and purpose  
      12.3.5 Acceptable uses of the technology  
      12.3.6 Acceptable network locations for the technologies  
      12.3.7 List of company-approved products  
      12.3.8 Automatic disconnect of sessions for remote access technologies after a specific period of inactivity  
      12.3.9 Activation of remote access technologies for vendors only when needed by vendors, with immediate deactivation after use Team Viewer
      12.3.10 When accessing cardholder data via remote access technologies, prohibit copy, move, and storage of cardholder data onto local hard drives and removable electronic media.  
      12.4 Ensure that the security policy and procedures clearly define information security responsibilities for all employees and contractors.  
      12.5 Assign to an individual or team the following information security management responsibilities:  
      12.5.1 Establish, document, and distribute security policies and procedures.  
      12.5.2
      Monitor and analyze security alerts and information, and distribute to appropriate personnel.
       
      12.5.3 Establish, document, and distribute security incident response and escalation procedures to ensure timely and effective handling of all situations.  
      12.5.4 Administer user accounts, including additions, deletions, and modifications  
      12.5.5 Monitor and control all access to data.  
      12.6 Implement a formal security awareness program to make all employees aware of the importance of cardholder data security.  
      12.6.1 Educate employees upon hire and at least annually.  
      12.6.2 Require employees to acknowledge at least annually that they have read and understood the company's security policy and procedures.  
      12.7 Screen potential employees (see definition of employees above) prior to hire to minimize the risk of attacks from internal sources.  
      12.8 If cardholder data is shared with service providers, maintain and implement policies and procedures to manage service providers, to include the following:  
      12.8.1 Maintain a list of service providers.  
      12.8.2 Maintain a written agreement that includes an acknowledgement that the service providers are responsible for the security of cardholder data the service providers possess.  
      12.8.3 Ensure there is an established process for engaging service providers including proper due diligence prior to engagement.  
      12.8.4 Maintain a program to monitor service providers' PCI DSS compliance status.  
      12.9 Implement an incident response plan. Be prepared to respond immediately to a system breach.  
      12.9.1 Create the incident response plan to be implemented in the event of system breach. Ensure the plan addresses the following, at a minimum:
      • Roles, responsibilities and communication and contact strategies in the event of a compromise including notification of the payment brands, at a minimum
      • Specific incident response procedures
      • Business recovery and continuity procedures
      • Data backup processes
      • Analysis of legal requirements for reporting compromises
      • Coverage and responses of all critical system components
      • Reference or inclusion of incident response procedures from the payment brands
       
      12.9.2 Test the plan at least annually.  
      12.9.3 Designate specific personnel to be available on a 24/7 basis to respond to alerts.  
      12.9.4 Provide appropriate training to staff with security breach response responsibilities.  
      12.9.5 Include alerts from intrusion detection, intrusion prevention, and file integrity monitoring systems.  
      12.9.6 Develop process to modify and evolve the incident response plan according to lessons learned and to incorporate industry developments.  

      Javascript

      The Web Pages that are used by the Web Sales Module contain javascript that performs different functions. There are 3 javascripts that are used and each one is called into the page by the tags. All 3 javascript functions reside in their own page within the tmScripts folder. Below is a description of all three javascripts.

      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 tag for each cell you wish to rollover.

      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

      Navigation Buttons

      Each page contains form input buttons as navigation. Buttons are used in the Web Pages not only to move between different sections of Web Sales, such as Ticketing and Donations, but are also used to communicate data to and from the Theatre Manager database, so that the content on each page is current and constantly linked back to the database. The commands that provide connectibility between the database and the Web Pages are contained within each button's <input> tag. Those Buttons Commands are listed below.

      There are two groups of buttons:

      1. Menu Navigation Buttons
      2. Data Input Buttons
      Menu Navigation 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 Cascading Style Sheets to make them fit whatever concept your site incorporates, such as

      These buttons are assigned classes (default to the button and buttonover classes) from the styleButtons.css style sheet, and can use javascript to create a rollover effect.

      Data Input 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 in the TMtickets.html page, which would send a command to Theatre Manager and open a new page based on the show that you clicked it for, allowing you to select seats for that performance.

      The Data Input Buttons default to the 'new' and 'newover' classes in styleButtons.css.

      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.

      • btnLogin
      • btnLoginAccount
      • btnLoginFromDetail

      • btnHome
      • btnHistoricalCart
      • btnHistoricalCartDetail

      • btnAccount
      • btnAccountRequest
      • btnAccountAdd
      • btnAccountUpdate

      • btnPassword
      • btnPasswordCancel
      • btnPasswordAccept
      • btnPasswordRequest
      • btnPasswordSend

      • btnMailList
      • btnMailListAdd
      • btnMailListRemove

      • btnTicket
      • btnGetEventRange - Deprecated. use btnGetEventList instead. This button uses btnGetEventList anyway
      • btnGetEventAll - Deprecated. use btnGetEventList instead. This button uses btnGetEventList anyway
      • btnGetEventList
      • btnSelectEvent
      • btnBestAvailCancel
      • btnBestAvail
      • btnReserveCancel
      • btnReserveTicket

      • btnPass
      • btnReservePass
      • btnPassAmountCancel
      • btnPassAmountAccept

      • btnDonation
      • btnDonationAccept

      • btnCart
      • btnCartRemoveItem
      • btnMailFeeAdd

      • btnCheckout
      • btnCheckoutAccept

      • btnLogout
      • btnLogoutCancelOrder