Releases are cumulative. If you skip one, installing the next release will provide all the changes of the previous one. There is no need to install them in order... just the most recent.
Click on the printer friendly link at the bottom if you want to print out all release notes, or go to the specific page and click printer friendly version.
The Version Number is comprised of 3 parts. Using the example below of 10.07.371:
Key features and improvements since version 7:
Version 8.00Version 8 is a significant upgrade with over 50 new features. Many changes relate to 'under the hood' performance along with enhancements to various parts of Theatre Manager based on feedback from users. From the users perspective, version 8 looks and functions the same as version 7. There are additional buttons in various places to extend functionality. Users familiar with version 7 should not need training on version 8. Version 8 will be installed by the Arts Man Support team using remote access. It is free to all venues who have a current active support agreement. Upgrades will occur during normal support hours on dark days. For those on after hours support, evening upgrade time slots may be arranged. April 2009 |
Key changes:
There are mandatory web change for this version and a new Apache Loadable module must be installed. For this version, it will be done by Arts Management Support team. |
Before upgrade |
|
---|---|
After Upgrade |
|
Optional Steps |
|
Time Required |
|
Version 8 consists of many hundreds of little changes through out Theatre Manager. Some are major and are listed below. Most were under the hood tweaks for performance and added convenience in a number of areas. They are too numerous to mention them all, so this document focuses on the key ones.
Some code in Theatre Manager has been moved from the application into the server using more stored procedures. That generally improves performance of applications and this is true in Theatre Manager. We did this in a number of areas to try to take out seconds, or even milliseconds of time and improve response. The table below shows some sample improvements that we have experienced on our test suite of machines. Venues that are currently using version 8 have told us that it seems faster, so, anecdotally, the improvement is noticeable.
The improvement that each venue achieves is dependant entirely on the postgres server machine and is affected by things like: memory, striping of hard drives and speed (number of CPU's). Sample performance improvements are listed below (note that they are not cumulative, just indicative of areas where we focused on performance):
Window or function | After | Improvement |
email blasts | Does one ping at the start of the process (and each time there is an interruption longer than a minute). We also adjusted memory management | about 3 times faster on small batches. Much faster on large batches of emails. The standard test suite now allows 4000-5000 emails to be sent per hour from the merge process |
record inserts | revised the methodology of generating new keys | 10-15% improvement inserting new records in all aspects of Theatre Manager |
Open Sales window | Optimized the reading of records | window opens about 10% faster |
selling individual tickets | There is a minor change to selling one ticket by clicking on it and then clicking on another | small, not generally appreciable |
selling block of tickets | when selecting multiple tickets and booking at one time, the process goes much faster. | selling between 10 and 80 tickets at one time - speed improvement was as much as 3 times faster. Example selling 83 tickets took 30 seconds. It now takes less than 10 seconds. |
Selling any ticket | server contention and record locking has been optimized | any number of users may now sell large blocks of tickets simultaneously without any record locking happening. We have noticed that each ticket workstation in a large venue now receives the same response time from the server (on average) |
End of Day Posting | Some work that used to be done during end of day to post to daily statistics is now done during the ticket sale | even though the ticket sale is 3 times faster, this change also improved end of day posting by a factor of 2 to 2.5 times. Posting 280 transactions is about 2 time faster. |
Refunding tickets | refunding tickets and creation of transactions is now about 1.5 times faster | |
Entering donations | the allocation of payments and creation of transactions was optimized | entering a new donation is about 2 times faster. |
Finding Patrons and other records | The actual performance of finding records has not changed. We optimized this display of the records on the work stations. | displaying a moderate number of patron, orders, shopping carts and such is as much as 10 times faster. Retrieving them from the database takes the same amount of time - the display is much faster because work is now done on the server. |
Postgres optimizations | a number of indexes were removed from fields that are heavily updated to take advantage of a feature in postgres version 8.3 | In general, this optimization results in about a 30% improvement in record I/O a the server on a properly tuned system. |
There were changes to the general behavior of Theatre Manager in response to requests we had from people. Many of these are subtle such as:
There were a few minor changes to the patron window to add some functions requested by users.
On the patron window where the email addresses and phone numbers are displayed, you can now:
There is an optional field for each patron that we called an 'external search field'. If enabled, you can specify a key that can be used to find the patron. Suggested uses for this field might be a student/faculty number or a number that relates a Theatre Manager patron to an external system.
There is a new feature on the address list and patron card detail window that allows you to:
The ticket and order window now has a legend on it indicating if the order contains reservation only tickets, as well as if you owe money to the patron or the patron owes money to you. Ticket window now displays order notes.
From the ticket window, you can now select some of the tickets and then 'print a map' showing a picture of the seats where the patron is sitting.
There are a number of minor changes on this window:
Theatre now supports redemption of coupon codes on the web. There are three pre-conditions to accepting them:
There is a new apache server version 2.2.11 that will be installed. There are some slight revisions that must be made to your existing web pages to support the new apache module. Your existing version 7 web pages will be converted by the support team unless you have made massive modifications to them (most venues have not).
Key changes to the web component:
Operating system | Generic Location | Typical Path name |
OS-X | HOME | ~/Library/Preferences/TheatreManager/TheatreManager.plist note: ~ refers to each users preferences, or /User/MyUser/Library/Preferences/TheatreManager |
Win 2000 and XP | USERPROFILE | C:\Documents and Settings\MyUser\Application Data\TheatreManager\TheatreManager.txt |
Vista | LOCALAPPDATA | C:\Users\MyUser\AppData\Local\TheatreManager\TheatreManager.txt |
Version 8.04This version is a maintenance release for most venues with little changed here and there to improve the user experience. It added one main new feature for tracking attendance in each class for a course and printing attendance lists. May 26, 2009 |
Key changes:
There are no mandatory web change for this version. |
Before upgrade |
|
---|---|
After Upgrade |
|
Optional Steps |
|
Time Required |
|
Version 8 consists of many hundreds of little changes through out Theatre Manager. Version 8.04 contains further improvements to this version upon request of venues.
Version 8.08.04 of Theatre Manager was released today with links to the new online help system.
We've been wanting to use new web based technology for a long time and we have setup a drupal web site at http://www.theatremanagerhelp.com so that you may view the theatre manager help at any time and print off small booklets of web pages from the web site - or review the help as you need it.
Clicking on the '?' in Theatre Manager (V8.08.04 or later) will take you to the main help page. We plan on updating links for context sensitive help on an ongoing basis.
All the help pages originally came from version 6 and many of them have been converted to reflect screen shots from version 8. You may encounter some pages that are out of date. Please forgive us for those as we update them. Our goal is to make this a one stop resource for most help and update the pages as you ask us questions. Look to the pages to change in minor ways each day.
Version 8.08.04 also:
We recommend this update be installed at all venues currently using version 8 immediately.
Version 8.08.08 contains an important change to detect if an end user has cookies enabled in their browser. We discovered that TM was detecting if cookies were enabled (or not), but was not displaying an appropriate message to users as they proceeded through the web sales system. This has been enhanced so that once the patron hits the first web page, if they proceed to an area that requires cookies, they will be alerted when cookies are not enabled. That should improve their browsing experience.
Version 8.08.08 also:
We recommend this update be installed at all venues currently using version 8.
Version 8.09 contains ongoing minor enhancements to address small issues reported by customers. The changes in this version are:
We recommend this update be installed at all venues currently using version 8.
We have discovered a small issue where opening any window could address the wrong memory and possibly cause a crash. It is an obscure happenstance - it will only occur if you repeatedly open certain windows and opening a window may delay the actual crash until a long time afterwards, possibly an hour or so later.
This particular bug appears to affect Macintosh users mostly.
If you upgrade to this version of Theatre Manager, you will need to walk around and install it on all computers. Please be sure to check for updates using the 'Windows' menu to get this version.
The time required to upgrade varies on the number of transactions, orders, payment and e-mail blast records. If the database contains many of those, the upgrade might take an hour or more from version 8.09.
If you want to implement the 'presales' coupon feature, you can make one change to the TMtickets.html web page that streamlines the process for presales codes. Please download the latest copy of the TMtickets page and compare your TMtickets.html with the new one. There is a bit of code that needs added to the page that starts with
<field>pick(F_PRESALES_ALLOWED,'<!-- comment: based on setting in company preferences')</field>
and ends with
<field>pick(F_PRESALES_ALLOWED,'-->')</field>
The following changes have been made to Theatre Manager since version 8.09
We have built a product right into Theatre Manager for remote support called 'TeamViewer'. From our testing, is zero configuration and secure - and it is right on the Theatre Manager menu bar. If you are talking to support and want to show them what you are seeing, you can invite our support staff to view your screen while you are on the phone. This can be used from any computer within your organization. If you elect to use this feature, you have to provide your randomly generated access code for to the support team, otherwise they cannot connect to your machine. We are very excited about including this support tool right into Theatre Manager.
We will be using this feature for remote training and support in the future, so we urge all users to upgrade
Future address changes - you can now specify that address and phone information may change at any time in the future. This can be a one-time change, or address flipping between summer and winter addresses, or any number of address changes throughout the year.
This feature includes:
You can now set up courses with multiple class days (such as summer camps) and track attendance at each day of the session. There is an attendance report and a report card feature to accompany this new capability.
Coupon codes now support the notion of 'Presales', or early access to tickets for events to select groups of individuals - where those same performances are not available to the general public. It is implemented through coupons - and if the coupon code is entered, then more events will appear in the list that a patron can select from. A further enhancement to coupon codes is that you can now email blast a mail list - and only allow people on the mail list to have early access, or use a discounted coupon. This prevents patrons from handing coupon codes around or posting them on the internet.
Passes now allow you to specify the number of tickets to redeem from any one pass. This allows you to:
This new feature supports GC's or Passes that can be used by a corporation or family such as scholarships, or event passes that may be assigned to one person and used by another.
Employee's and Patrons are now merged - this is a significant (but subtle) change. In the past, the employee record was separate from the patron record and if employees bought tickets, you would need to enter them as a patron as well. Now, you set up a employee in the patron record. Then you assign the patron 'employee' permissions. You will see, on the patron list, a little 'star' beside those people who are current employees. Existing employees in the database will have a new record created for them in the patron file, so you will have to merge the employee and the patron together that have the same name.
Enabling at least one MasterUser Account at Login - We added some features to prevent the master user from dissappearing from the database. These include:
This also works on the end of day wizard copy of the receivables list and adjusts the various calculations to show balancing status
The print process now only considers printable documents and the email process now only considers those that are marked as email.
If one of those are encountered, TM will warn the user. If it is the A/R account, TM will display a dialog that warns the user about potential end of day balancing issues if they are not careful with that they are doing.
See full notes about Version 8.13 or read on for a summary.
Users of version 7 may download version 7.36.42 from:
http://www2.artsman.com/Software/Version7/TMSetup.exe (PC)
http://www2.artsman.com/Software/Version7/TMSetup.zip (mac)
The time required to upgrade varies on the number of patrons in the database with email addresses. If the database contains many of those, the upgrade might take half hour from version 8.13.
This is a walk around install.
The following changes have been made to Theatre Manager since version 8.13
If you want to implement the 'limited profile patron' feature, you will need to download and compare some web page files. Please download the web page updates and compare your web pages with the template files in this mini archive.
The new files are below and should just be moved into the appropriate place in the htdocs folder:
There is a key revision to enable tax calculation on a per performance basis in the Event window
A significant new feature has been added to Theatre Manager called 'limited profile patron'. We heard that some venues may not always want capture name and address information on every patron during a web sale. This feature allows you to accept a web sale and specify which data is mandatory before allowing the patron check out. It can range from as little as name/email to the same full requirements as the box office.
If implemented, this feature is designed to allow a patron to buy tickets, provide only sufficient information to get them their tickets, and checkout. If they buy again, they would need to provide the same information. For example: if all tickets are print at home or held till willcall, you only need patron name. If you still want to mail tickets, you will need to make address mandatory.
If the 'limited profile patrons' feature is enabled in System Preferences, the following will apply:
Limited Profile Patrons also allows quick sign up to any number of mail lists by providing only name and email info without signing in.
There is a convenient quick-add feature that simply creates a patron by swiping their credit card. We think this might be used during the admittance process for Auctions. The process works as follows:
A field was added to the database to track the date and time that last backup that was done. A message will be displayed to the user whenever backups are deemed not to have run recently based on a setting in System Preferences that can range from 1 day to 7 days.
The backup script must be updated with a couple of commands to use this feature as it simply tells the database after the backup is completed.
See the full notes about Version 8.15 or read on for a summary.
The time required to upgrade depends on the number of volunteer history records. If the database contains many of those, the upgrade might take 5 minutes from version 8.15.
The following changes have been made to Theatre Manager since version 8.15
We are also implementing a new system for tracking and assigning support requests internally. As of Thursday morning, you will get a response back to any email sent to support @ artsman . com assigning a tracking number to it. Each follow-on discussion with support will refer to that number so that both you and ArtsMan can have a complete thread on each subject.
Please bear with us as we implement - we've been using the tool for 6 months internally and like it. But we know that change means steps forward and sideways.
See the full notes about Version 8.16 or read on for a summary.
This version is recommended for all version 8 users.
The time required to upgrade depends on the number of payment records. If the database contains many of those, the upgrade might take 5 minutes from version 8.16.
The following changes have been made to Theatre Manager since version 8.16
The time required to upgrade depends on the number of volunteer history records. If the database contains many of those, the upgrade might take 5 minutes or more from version 8.17.
The following changes have been made to Theatre Manager since version 8.17
The time required to upgrade depends on the number of ticket and shopping cart records. If the database contains many of those, the upgrade might take 20 minutes or more from version 8.20.
This is a walk around install
The following changes have been made to Theatre Manager since version 8.20
There is a significant new feature in the patron window (and the ticket review tab in the sales process) that allows you to purchase the ticket normally and then 'Gift' or 'Assign' the ticket to another patron who may be in the household, or, it could be anybody in the database.
The purpose of this feature is to enhance many aspects of the sales process. It means you could purchase season tickets under one patron and assign them to each of the other families that are coming. It could also be used for classes where the parent buys and the child get assigned the tickets, rather than buying under the child's name.
The interface for this feature is done and you can use it now - all you need do is right click on the ticket to assign it (or remove the gift). In subsequent releases, the reporting, ticket printing and web capabilities will be enhanced to support the feature. This also means that selling courses online will allow a parent to purchase and assign the class to children so that the class roster is perfect.
Other Changes:
The upgrade time from version 8.21 is very short.
This is a walk around install
The following changes have been made to Theatre Manager since version 8.21
This version of TM is approved by Paymentech to support their Orbital credit card platform. Orbital is a web based authorization process where TM sends special commands to a special web page based on merchant authentication. Connection to the web page can only be done with secure communication. It also provides a web interface for seeing your credit cards in your batch.
This is a fairly significant option that some venues may like to implement, but there are pro's and con's to using the gateway. The highlights of using this credit card gateway are:
We have added the core capability for XML export to BANNER (used at a number of Universities) in addition to flat file export. If this is of interest to you, you will need to discuss this with the development team to see if it can apply to you..
The upgrade time from version 8.22 varies depending on the number of patrons in the database - it may take a little time.
There are MANDATORY web page changes that must be made before upgrading. If you do not do this, your web sales will not run until the web pages are updated as per the instructions at the bottom of this page
This is a walk around install
The following changes have been made to Theatre Manager since version 8.22
A few venues have asked for the capability of allowing patrons to buy using various languages and this version provides that capability. There are some things that each venue must do in this upgrade to web pages, regardless if they wish this feature or not. Specifically:
Events that are set up as courses may now be sold online. This has introduced a small change to the sales process for courses online that some venues may find useful. These are:
The PCI certification is an evolving process, changing and getting stronger as the years roll on. We have made some changes here that you may need to be aware of.
This version of Theatre Manager is in limited release at this current time - and will become the default version of Theatre Manager in a month or so
Make a copy of the WebPages folder and name it WebPagesEN. Do this and make ALL changes below in the WebPagesEN folder before upgrading Theatre Manager to version 8.23.00. Please download the web page updates and compare the web pages in the WebPagesEN folder with with the template files in this mini archive. If you have not made any changes from prior versions, you may need to get the full set of standard web pages and compare them.
Note: on PC Apache servers, please find all files called '.ds_store' and delete those for PCI compliance.
Files in the main WebPagesEN directory | |
TMattendance.html | replace entire file |
TMcart.html | include dropDownMenuFunction at top of page and add an ID to the FORM tag |
TMcheckout.html | include dropDownMenuFunction at top of page and add an ID to the FORM tag. Change code for F_HTML_MERCHANT_LIST (compaer old page to new) |
TMlogin.html | compare old page to new - turn 'autocomplete=off' on password fields |
TMloginSelectPatron.html | compare old page to new - turn 'autocomplete=off' on password fields |
TMpasswordChange.html | compare old page to new - turn 'autocomplete=off' on password fields |
TMpasswordResetChange.html | compare old page to new - turn 'autocomplete=off' on password fields |
TMpatronNew.html | compare old page to new |
TMpatronUpdate.html | compare old page to new |
tmError.txt | additional error message number 10153 |
tmFee Directory | |
tmOrderFee.html | compare old page to new |
tmOrderFeeDefault.html | compare old page to new |
tmGifs | |
langxx.gif | add all files starting with lang to your tmGif folder |
tmMaps | |
TMticketsSection_MapDefaultc.html | new file used for description of courses |
tmScripts | |
dropDownMenuFunction.html | new file used for change of course attendee and chnaging of merchant on checkout |
tmTemplates | |
rowPatronEmail.html | compare old page to new. Variable called F_HTML_ALLOW_PASSWORD_CHANGE |
rowPatronEmailLimitedProfile.html | compare old page to new |
setMERCHANT_LIST.html | replace page |
tmnavButtons.html | (optional) add the code for <!--#include virtual="tmTemplates/tmnavLanguages.html" --> inside the form if you want to do multi language |
tmLoginForm.html | replace file |
setCCMONTH_LIST.html | new file |
setCCMONTH_LISTempty.html | new file |
setHOUSEHOLD_PATRON_LIST.html | new file |
setHOUSEHOLD_PATRON_LISTempty.html | new file |
setHOUSEHOLD_PATRON_SELECTION_LIST.html | new file |
setHOUSEHOLD_PATRON_SELECTION_LISTempty.html | new file |
tmnavLanguages.html | new file - update for the languages you want to support |
rowCartCourse.html | new file |
rowCartCourseNewGroup.html | new file |
rowCheckoutCourse.html | new file |
rowFutureTicketCourse.html | new file |
rowFutureTicketPrintCourse.html | new file |
rowOldCartCourse.html | new file |
rowOldCartPrintCourse.html | new file |
constantALLEVENTS.txt | new file - edit if using multi language |
constantALLVENUES.txt | new file - edit if using multi language |
constantALLYEARS.txt | new file - edit if using multi language |
constantMONTHS.txt | new file - edit if using multi language |
constantYESNO.txt | new file - edit if using multi language |
constantNEWPATRON.txt | new file - edit if using multi language |
See the full notes about Version 8.23 or read on for a summary.
Also note that there are 38 web page changes must be made prior to installing this version to avoid some web pages not working. Most are new pages and about 6 are important changes to existing pages. Please do not install this version without doing the web page changes first.
The upgrade time from version 8.23 should be relatively short.
There are 3 MANDATORY web page changes that must be done when upgrading. If you do not do this, new patrons may not be able to add themselves on the web
If you are at 8.23.00, this should self deploy, otherwise it is walk around.
The following changes have been made to Theatre Manager since version 8.23
This version of Theatre Manager is in limited release at this current time - and will become the default version of Theatre Manager in a month or so
Make a copy of the WebPages folder and name it WebPagesEN. Do this and make ALL changes below in the WebPagesEN folder before upgrading Theatre Manager to version 8.24.00. Please download the web page updates and compare the web pages in the WebPagesEN folder with with the template files in this mini archive. If you have not made any changes from prior versions, you may need to get the full set of standard web pages and compare them.
Note: on PC Apache servers, please find all files called '.ds_store' and delete those for PCI compliance.
Files in the main WebPagesEN directory | |
TMpatronUpdate.html | compare old page to new |
tmError.txt | additional error message number 10154 |
tmTemplates | |
rowPatronEmail.html | compare old page to new. Fixes a mistake that prevented new patrons adding themselves in version 8.23.02 or later. |
Apparently, Harris Theatre in Chicago (they are NOT a Theatre Manager customer) is being sued because their credit card receipts printed the expiry date and their insurance settled out of court - even though no actual damages occurred to the customer. The article talks about how some lawyers have used this same law to target restaurants and other consumer outlets.
This is a US specific law is called FACTA - the Fair and Accurate Credit Transactions Act of 2003 (non-authoritative link for more info) which has a subsection repeated below. There does not appear to be a similar Canadian counterpart.
Credit card receipts that include full account numbers and expiration dates are a gold mine for identity thieves. FACTA says credit and debit card receipts may not include more than the last five digits of the card number. Nor may the card's expiration date be printed on the cardholder's receipt. However, this does not apply to receipts for which the sole means of recording a credit or debt card number is by handwriting or by an imprint or copy of the card.
During Theatre Manager training, we always recommend against printing credit card receipts because we do not feel that the ticket business requires separate receipts - and that the ticket is your receipt. If that is your practice, there are probably few historical ramifications. However, we do recommend following the recommended action below immediately.
There is enough in my searching of the internet that leads me to believe that this possible threat to your venue is credible (even if it is a sad statement on the legal system). We strongly encourage you to make your own investigation on the matter if you need more information.
Regardless, we suggest that you edit all your 'payment' ticket faces. Look for any lines that have the field called PAY_CARD_EXPIRY and remove that line from the ticket face immediately.
Also, on your web page confirmations, look for the same field and remove that. We will remove from our standard pages and information will be in the next release notes.
Note: Version 8.25 will automatically remove this field from all ticket faces and due to be released early next week. You may wish to have and advanced read of the release notes.
See the full notes about Version 8.24 or read on for a summary.
Version 8.24 is primarily a bug fix release that addresses a number of issues found and change requests to the recent enhancements for facility management, Paymentech Orbital, online course sales, and online management of household patrons.
We recommend that those using versions 8.10 and later upgrade when possible to obtain the bug fixes.
Those at 8.09 and earlier should also upgrade - but at their leisure in order to obtain the new functionality.
There are 3 web page updates for this version that correct earlier functionality.
Version 9 is a major release for PCI PA/DSS 1.2 compliance and UTF8 converison. All components of Theatre Manager need to be updated to meet the new PCI requirements and we have tried to aggregate everything into one large upgrade step for the year to optimize work effort. If you would like to contract ArtsMan to do this for you, please read about the upgrade options.
Specifically you will need to:
Please refer to the 8.xx-9.00 upgrade steps and allow 4-6 hours for the upgrade from version 8 as all components have changed to latest versions for PCI compliance.
Point releases are minor version fixes and small enhancements to any particular version.
The following changes have been made to Theatre Manager since version 8.24
this checkbox must be set before the last payment is taken and the order window closed otherwise credit card receipts will not print. |
There is a significant underlying change to donation management in this release. A new field has been implemented called 'Receipt Not Required' that is applicable to each donation. If it is set, no receipt can be printed
If the end user's Outlook client is set to send emails as RTF or HTML (in some versions), the response sent back by Outlook is in a Winmail.dat file which we do not yet read. You will be able to still go in with your Outlook (or other) client and view the message by hand and update your Theatre Manager information. |
On PC Apache servers, please find all files called '.ds_store' and delete those for PCI compliance. |
Files in the main htdocs directory | |
TMsysNoListeners.html | this is a new file. It is activated if there are no listeners for any outlet active and/or if the user attempts to get a listing of the /TheatreManager directory. use it to redirect the user to the correct outlet. |
Files in the each outlet directory (1) | |
TMsysBusyListeners.html | compare old page to new |
TMsysErrorListeners.html | compare old page to new |
TMsysNoListeners.html | compare old page to new - this is similar to but not the same page as in the main htdocs directory. It indicates that a specific outlet has no listeners running. |
eblastimages | this is a new directory that will contain all jpegs used for eblasts and for pictures used in the 'event' marketing tab. Please make sure that the FTP user in 'Company Preferences' has full read/write access to this folder, and all other users have read access |
Files in the main WebPagesEN directory | |
TMpatronUpdate.html | compare old page to new. Changes are to better handle multiple patrons in the household. |
TMpatronNew.html | compare old page to new. Changes are to better handle patrons trying to add themselves twice. |
TMpatronNewEmail.html | minor changes to add company name to the email |
TMpatronUpdateEmail.html | minor changes to add company name to the email |
TMCheckoutConfirmation.html | Remove the credit card expiry date from the confirmation per FACTA. Also provide capability ot printing receipt, printing ticket bar codes in controlled manner. |
TMCheckoutInvoiceEmail.html | Remove the credit card expiry date from the email per FACTA |
tmTemplates | |
rowPatronEmail.html | compare old page to new, specifically remove HTML email preferences CCL_PREFER_HTML |
rowPatronEmailLimitedProfile.html | compare old page to new, specifically remove HTML email preferences as above |
rowCheckoutDonation.html | removed the bar code column. This was done for esthetics, performance improvements and to direct the user to askingfor a specially formatted bar code page that contains only ticket information. This and similar changes are optional, but recommended |
rowCheckoutFestival.html | removed the bar code column |
rowCheckoutMailFee.html | removed the bar code column |
rowCheckoutOrderFee.html | removed the bar code column |
rowCheckoutPass.html | removed the bar code column |
rowCheckoutReserve.html | removed the bar code column |
rowCheckoutSub.html | removed the bar code column |
rowCheckoutSubNewGroup.html | removed the bar code column |
rowCheckoutCoupon.html | removed the bar code column |
rowCheckoutCourse.html | removed the bar code column |
rowCheckoutOrderCouponFee.html | removed the bar code column |
rowFutureTicketHeader.html | revised to to remove an extraneous </script> tag |
rowPatronAddress.html | markers to identify mandatory fields |
constantPATRONCONTACTEXISTING.txt | new file |
constantPATRONCONTACTNEW.txt | new file |
setPROMOTIONSUB_LIST.html | used to present alternate options for price/promotion/price code for subscriptions. Example. Regular tickets might show price, subscripitons mught just show promotions as in 'Subscription' |
setPROMOTIONSUB_LISTempty.html | used to present alternate option for 'no subscripitons available' if Theatre Manager cannot find a price. |
tmFooter.html | New file containing google analytics code and addition of possible footer for each web page (see version 9.01) |
tmCampaign | |
tmCampaign1.html | compare old page to new, minor changes |
tmCampaign2.html | compare old page to new, minor changes |
tmCampaignDefault.html | compare old page to new, minor changes |
tmEvent | |
tmEventDefault.html | revistions to show an picture placed into the 'events' window on the marketing tab. This allows you to put pictures into the default 'about this event' page within Theatre Manager and not touch the web pages. |
tmEvent1.html | same as above |
tmMaps | |
TMSubscriptionMapDefaultf.html | compare old page to new, minor changes. |
Please send a note to support@artsman.com to get the links for theatre manager before starting the upgrade if you are attempting the process yourself as we will need schedule the upgrade support (we can't do everybody in one day).
The steps to upgrade generally involve:
You will need a Macintosh intel machine to do the work on (all downloads are free). It assumes that you have:
If you have not done the above successfully, the next steps in the process will not work.
If you do not have at least one Macintosh at your venue, there is no available Windows equivalent to this process yet. You will need to FTP your database and we will return it in UTF8 encoding for you.
where YourDatabaseName is the name of the database that you log into each day. This will backup the database to a file in the /Users/Shared/Backup folder called YourDatabaseNameV9.sql. You may need to supply the postgres user password if you do not have 'trust' set for the server IP address in the pg_hba.conf file.
Depending on the size of your database, this step could take as long as 4 hours. The pg_dump shows obvious activity. The 'Recode' step may look hung, but it is not.
If the 'Recode' completed successfully, it will display some instructions at the end of it similar to the following screenshot.
/library/PostgreSQL/8.4/bin/createdb VenueDatabaseNew -U postgres -E UTF8 -O TheatreManager
/library/PostgreSQL/8.4/bin/psql -U postgres -v -d VenueDatabaseNew -f /Users/Shared/Backups/VenueDatabasev9new.sql
The simple answer is no. Your Theatre Manager will continue to work, regardless of the upgrade.
However - in order to become PCI compliant, you must upgrade to Theatre Manager Version 9 AND Upgrade to Paymentech Orbital or one of the other direct processors for improved credit card authorization.
For those who are already PCI compliant, you can continue to use Theatre Manager version 8 until December 2010 when you need to upgrade to Theatre Manager Version 9 AND switch to one of the direct processors to achieve PCI 1.2 compliance.
There are several components to the installation process. Please refer to the 8.xx-9.00 upgrade steps for the complete installation instructions. The process takes about a day and should be performed by proficient IT personnel as it will require changes to:
If you choose to self-install, and then require support assistance, the regular hourly billable rate of $100 per hour will be applicable. Please note that support for a self installation is not covered under the After Hours Emergency Support contract. Please plan your time accordingly to ensure that if you do have questions, Arts Management support will be available to assist you. |
If you choose to have Arts Management perform this work for you, you will need to send a request to our sales office. They can be reached at sales@artsman.com or (888) 536-5244, ext. 2 from 8:00 AM - 5:00 PM MST. They will process the request and then forward the request to the Support team for scheduling. Because of the high demand for conversions, your scheduled date may be as much as 4 months away. Please plan accordingly.
The actual upgrade process takes about one business day, during which time your offices will not be able to use Theatre Manager (even to "look things up"), and web sales (if applicable) will be offline during the upgrade process.
Finally, all upgrades are cumulative. For example, if you are upgrading from verison 8.1 to 8.16, read all the release notes for each version in-between and follow all steps for each version
When downloading any update for Theatre Manager, please make sure your personal firewall is turned on per PCI requirement 1.4 |
You can visit http://www.theatremanagerhelp.com for our updated Version 9 help. If you have not already subscribed to our RSS feed, please take this opportunity to subscribe by visiting the RSS link (click the icon) in the upper right corner of the main http://www.theatremanagerhelp.com page.
Release Notes
Read the release notes to see if there is anything special that impacts your organization in Version 9. This is a long list of enhancements from the version previously being used.
Installing Theatre Manager on Each Workstation(s)
Please see the following online help page for steps on installing the Theatre Manager application on a work station:
http://www.theatremanagerhelp.com/installing-theatre-manager/install-theatre-manager
Starting Theatre Manager After Upgrading
The following window will appear.
Passwords
Version 9 of Theatre Manager is designed to meet the latest PCI Compliance. One of the features within this version is stronger security for Employee Passwords. If you have not previously used PCI Compliant passwords each Employee will need to enter their old password all in CAPITAL letters. When they click the login button they will be prompted to change their password to a format that meets compliance. The requirements for compliant passwords are listed in the image below. For more information on PCI Password Requirements click here.
Employees Disappear From the Login Window After Incorrect Password Attempts
After six attempts at entering an incorrect password Theatre Manager will remove the Employee from the login window per PCI requirements. Theatre Manager resigns the employee to protect the database and all you need do is follow these steps to reinstate the employee.
Theatre Manager List of Employees does not appear
In some rare cases following the installation of Theatre Manager the application opens but does not display an employee list to login. The common characteristics of this situation are a blank gray screen containing File, Edit, Help options in the upper left of the window and nothing more. If you encounter this issue please follow these steps.
Employee Access
Some employee settings have been changed due to PCI Compliance. One of note is the Accounting >> Create Bank Deposits for Current Payments Received - Authorized Credit Cards Only option. This is found in the Functions tab of the Employee Access Data window. By default, all Employees who do not have Master User access will have this option unchecked. If you have Employees who run the End of Day Wizard and are not Master Users you will need to check this option for those Employees.
Power Saving Settings for Apache Running on a Mac
To increase stability for Apache running on a Mac you will need to adjust some of the settings for the machine. Click here to learn more about the settings.
The upgrade time from version 9.00 should be relatively short.
There are NO mandatory web page changes that must be done when upgrading. One of the changes we made was to easily enable google analytics to be deployed in web pages footers. You may wish to review page changes for that purpose during the version 8 to 9 upgrade.
This is a WALKAROUND install that contains CRITICAL fixes for web security that should be installed immediately.
The key enhancements in this version are the introduction of:
Point releases are minor version fixes and small enhancements to any particular version.
The following changes have been made to Theatre Manager since version 9.00
Please download the web page updates and compare the web pages - but only if you want to implement google analytics page tracking. If this is the case, about 80% of the pages will need changing as below.
</BODY>
</HTML>
<!--#include virtual="TMtemplates/tmFooter.html" -->
</BODY>
</HTML>
There is a new page in TMtemplates called 'tmFooter.html' that you will need to put in place.
The key enhancements in this version are the introduction of:
A final note for everybody. Theatre Manager underwent PA DSS 1.2 compliance audit on June 10 & 11 and we have received word that Security Metrics has finished testing and will submit Theatre Manager to the PCI council as an approved application. We are awaiting confirmation from PCI of acceptance.
The upgrade time from version 9.0x should be relatively short.
There are one mandatory web page change that should be done during the upgrade process to support our testing of a forthcoming iPhone app under development. Other changes are optional.
This is a WALKAROUND install.
The key enhancements in this version are the introduction of:
Point releases are minor version fixes and small enhancements to any particular version.
The following changes have been made to Theatre Manager since version 9.01
Please download the web page updates and compare the web pages.
Files in the main htdocs directory | |
TMSysNoListeners.html | Compare and make changes |
Files in the each outlet directory (1) | |
TMCart.html | revisions for coupon and where to send the user if a coupon is entered. |
TMcheckoutCardError.html | compare to original |
TMcheckoutConfirmation.html | compare to original | TMCoupon.html | compare to original as it has revisions to redirect user based on kind of coupon entered. |
Files in the main templates directory | |
RowTicketEventExport.html | mandatory revisions to support forthcoming iPhone applicaiton. |
The upgrade time from version 9.0x should be relatively short.
This is a WALKAROUND install if upgrading from version 9.00 and 9.01. It will self deploy if upgrading from version 9.02.
There is on new feature that has been added to allow you to plot your patrons on a map using google. Only about 100 distinct points are supported by google's static map function but it lets you see where distributions of people lie. The picture at the tight is from patrons on Poplar street in Memphis. The data was geo-encoded using google's geo-encoding api.
This data can be accessed from the patron list or a patron mail list using the context menus.
Almost everything else in this version is primarily a minor usability enhancement release and a collection of minor bug fixes. It is recommended for all venues using version 9. The following changes have been made to Theatre Manager since version 9.02
There are no mandatory web page changes or additional tasks that a venue need do after installation that are specific to this version. There were some minor wording changes in some web pages that do not need to be made if you are satisfied with your current pages. Please read prior release notes if upgrading from earlier versions to see if there are tasks for earlier versions.
Point releases are minor version fixes and small enhancements to any particular version.
Please download the web page updates and compare the web pages.
Files in the each outlet directory (1) | |
TMcheckoutConfirmation.html | Cosmetic wording changes |
TMmailListUnverifiedEmail.html | Cosmetic gramatical change to the text that says venue will not disclose any information. Changes were made in a couple of words to make the meaning clear. |
TMpasswordChangedEmail.html | Cosmetic grammatical change, see above. |
TMpasswordEmptyEmail.html | Cosmetic grammatical change, see above. |
TMpasswordForgotEmail.html | Cosmetic grammatical change, see above. |
TMpasswordResetEmail.html | Cosmetic grammatical change, see above. |
TMpatronNewEmail.html | Cosmetic grammatical change, see above. |
TMpatronUpdateEmail.html | Cosmetic grammatical change, see above. |
Files in the main templates directory | |
rowFutureTicketPrintCourse.html | small code change to display bar code only if the setting for the event is to print tickets. If tickets are not to be printed for the event (and bar codes are allowed online), then no bar code will be printed for this ticket. |
rowFutureTicketPrintFestival.html | same as above |
rowFutureTicketPrintReserved.html | same as above |
rowOldCartPrintCourse.html | same as above |
rowOldCartPrintFestival.html | same as above |
rowOldCartPrintReserve.html | same as above |
rowOldCartPrintSub.html | same as above |
tmnavButtons.html | changed the default coding to not show multi- language by default. |
A new feature has been added to allow you to spatially plot your patrons on a map using google. Google's static map API supports about 100 distinct points on one map. This lets you see where distributions of people lie. The picture at the right is from patrons on Poplar street in Memphis. The data was geo-encoded using Google's geo-encoding api.
This data can be accessed from the patron list or a patron mail list using the context menus.
There are two key bug fixes to support web sales.
Almost everything else in this version are usability enhancement release and a collection of minor bug fixes.
It is recommended that this release be installed ASAP for all venues currently using version 9.
The upgrade time from version 9.0x might be 15-40 minutes (only an estimate) for an average site, it could be longer if you have lots of historical data and transactions. This is a WALKAROUND install
Almost everything else in this version is primarily a minor usability enhancement release and a collection of minor bug fixes. It is recommended for all venues using version 9. The following changes have been made to Theatre Manager since version 9.04
Point releases are minor version fixes and small enhancements to any particular version.
Please download the web page updates and compare the web pages.
Files in the each outlet directory (1) | |
TMcheckout.html | Added a new feature where you can require purchasers to confirm that they have read your terms and conditions before checking out |
TMticketsExport.html | Changed to describe the meaning and use of the page- but probably no functional changes to the page |
TMticketsExportCustom.html | New page to take the place of the TMticketsExport.html for those venues using an export to a drupal site. This page is accessed from your drupal site using
http: // tickets . yourvenue . org/TheatreManager/1/exportevents |
tmError.txt | new error message (10155) that contains text required for confirming terms and conditions. |
Files in the main templates directory | |
rowTicketEventExport.html | This must be set to the standard contents of this page - in order to take advantage of an upcoming feature (not announced yet, but nearly finished development) |
rowTicketEventExportCustom.html | New Page - starts with the same contents as rowTicketEventExport.html, however if you have used the event export to drupal site, then make this page have the contents of your current rowTicketEventExport.html |
tmtermsandconditions.html | New Page - contains the terms and conditions of ticket sales (or web sales) on your venue if you wish patrons to confirm prior to the sale proceeding. You MUST edit this page to set up the base href for your venue. |
Files in the tmScripts directory | |
pleaseWaitMessageFunction.html | added a function for popup window opening - which is currently only used for terms and condtions |
Version 9.05 has been released for all current users of Version 9. Please refer to the full notes about version 9.05.
This version also brings the initial implementation of estimating, invoicing, billing and posting to the G/L for the sales/booking of rooms, resources, and staff. During our day long internal staff training session, it became quite apparent just how comprehensive and useful this module would be to many venues.
As always, there are other changes contained in the release notes, bug fixes, minor usability enhancements in response to what people ask for. There is one new web feature you've asked for which is to support acknowledgement of 'reading conditions of sale' prior to checkout.
This is a walk-around install.
It contains some significant functional enhancements, performance enhancements, brand new features and a collection of bug fixes. It also contains some features that are pertinent to a pending iPhone/iPad application. We recommend that all venues using version 9 upgrade at their convenience.
The upgrade time from version 9.0x might be about an hour (estimate only) for an average site. It could be longer if you have lots of historical data and transactions. Upgrading this verison requires, at a minimum:
The following changes have been made to Theatre Manager since version 9.05
Point releases are minor version fixes and small enhancements to any particular version.
Also, the future post dated payment has to be deposited before the receipt will print (this has always been the case). So, if you have a number of a future payments and are electing to do 'when fully paid', then the last/final payment must flow through the end of day prior to the receipt being able to print. p> It also means if payments flow across a year boundary, then you will need to use a different option for that receipt - you will need to just use 'annual' receipt and print it at the end of the year (eg early january) for the prior year. (9.07.09)
Please download the latest web page updates and compare the web pages to your existing pages.
In the 3rd Column are 3 flags.
Error handling pages in each outlet directory (1) | ||
TMSysBusyListeners.html | Changed the behaviour of the 'waiting room' page to return to the patrons shopping cart. This condition is caused when there is an abnormally high load on the system and taking patrons to the shopping cart will affirm that any part tickets are still present in the cart. | O |
Files in the each outlet directory (1/WebPagesXX) | ||
TMcart.html | Adjusted the column width to show the lines in the cart more clearly if the ADA field is implemented in the other web pages. | O |
TMcheckout.html | Added a pick statement to show the current mailing status for the order if the user has added a mail fee (in place of the add mail fee button). Note this also applied if the 'add mail fee' adds a zero cost fee to indicate that the order is to be mailed. | O |
TMcheckoutNoPayment.html | Added a pick statement to show the current mailing status for the order if the user has added a mail fee - but yet there is no payment required because of a coupon discount or mailing is free. Note this also applied if the 'add mail fee' adds a zero cost fee to indicate that the order is to be mailed. |
O |
TMoldCartDetailsPrint.html | Adjusted the table width to be 700 pixels so that the user cannot make it wider and then print at the wider setting. This should help force bar codes to print on a page. Only change if you print at home and are finding a lot of people where the bar codes are not easily readable. ALso add the bar code column heading if printing at home so that columns on a printed cart line up and adjusted the colspan on the footer from 3 to 4. Only required if doing print at home. |
O |
TMfutureTicketsPrint.html | Adjusted the table width to be 700 pixels so that the user cannot make it wider and then print at the wider setting. This should help force bar codes to print on a page. Only change if you print at home and are finding a lot of people where the bar codes are not easily readable. |
O |
tmError.txt | 3 new error messages (10156,10157, 10158) to handle a couple of new conditions that the web listener verifies in shopping carts. If you do not add them, TM will use the built-in message text which is the same as the mesages. | O |
Files in the tmMaps directory | ||
TMsubscriptionPriceMapDefault.html | Changed colspan of a table header and footer from 4 to 5. Only needs to be changed if you wish to implement the seat description feature for ADA | O |
TMsubscriptionsPriceMapDefault.html | Changed colspan of a table header and footer from 4 to 5. Only needs to be changed if you wish to implement the seat description feature for ADA | O |
TMticketsPrice_MapDefault.html | Changed colspan of a table header and footer from 4 to 5. Only needs to be changed if you wish to implement the seat description feature for ADA | O |
Files in the main templates directory | ||
rowCartCoupon.html | Adjusted text of the savings to also include the link to describe the order fee used to reduce the reduce the price of the order when the coupon was applied. eg, 'Free Mailing' could now include a link to what that means | O |
rowCartDonation.html | Compare - Minor Change | O |
rowCartCourseNewGroup.html | Bolded the date of performance on the display for clarity | O |
rowCartFestivalNewGroup.html | Bolded the date of performance on the display for clarity | O |
rowCartMailFee.html | Added feature to display the current mailnig status once a mail fee is added such as 'print at home' , 'to be mailed' , 'pick up at wilcall' | O |
rowCartReserve.html | Added new MS_NOTE_USE_FLAG and MS_SEAT_NOTE to simplify ADA implementation | M |
rowCartReserveNewGroup.html | Added new MS_NOTE_USE_FLAG and MS_SEAT_NOTE to simplify ADA implementation. Also bolded the date of performance on the display for clarity. | M |
rowCartSub.html | Added new MS_NOTE_USE_FLAG and MS_SEAT_NOTE to simplify ADA implementation. Also bolded the date of performance on the display for clarity. | M |
rowCartSubNewGroup.html | Added new MS_NOTE_USE_FLAG and MS_SEAT_NOTE to simplify ADA implementation. Also bolded the date of performance on the display for clarity. | M |
rowCheckoutCoupon.html | Adjusted text of the savings to also include the link to describe the order fee used to reduce the reduce the price of the order when the coupon was applied. eg, 'Free Mailing' could now include a link to what that means | O |
rowCheckoutCourse.html | Bolded the date of performance on the display for clarity | O |
rowCheckoutFestival.html | Bolded the date of performance on the display for clarity | O |
rowCheckoutReserve.html | Added new MS_NOTE_USE_FLAG and MS_SEAT_NOTE to simplify ADA implementation. Also bolded the date of performance on the display for clarity. | M |
rowCheckoutSub.html | Added new MS_NOTE_USE_FLAG and MS_SEAT_NOTE to simplify ADA implementation. Also bolded the date of performance on the display for clarity. | M |
rowCheckoutSubNewGroup.html | Added new MS_NOTE_USE_FLAG and MS_SEAT_NOTE to simplify ADA implementation. Also bolded the date of performance on the display for clarity. | M |
rowFutureTicketHeader.html | Changed the colspan in the table heading for a slightly better display of the future tickets purchased. It may help if the 'row' lines for future tickets appear squished. | O |
rowFutureTicketPrintCourse.html | Updated to use the 'print at home flag' for at a performance level rather than the global 'print at home' flag. Implementing this allows the per performance enable/disable of bar code feature to be used. | O |
rowFutureTicketPrintFestival.html | Updated to use the 'print at home flag' for at a performance level rather than the global 'print at home' flag. Implementing this allows the per performance enable/disable of bar code feature to be used. | O |
rowFutureTicketPrintHeader.html | Adjusted the table width to be 700 pixels so that the user cannot make it wider and then print at the wider setting. This should help force bar codes to print on a page. Only change if you print at home and are finding a lot of people where the bar codes are not easily readable. | O |
rowFutureTicketPrintReserved.html | Added new MS_NOTE_USE_FLAG and MS_SEAT_NOTE to simplify ADA implementation. Updated to use the 'print at home flag' for at a performance level rather than the global 'print at home' flag. Implementing this allows the per performance enable/disable of bar code feature to be used. | M |
rowFutureTicketReserved.html | Added new MS_NOTE_USE_FLAG and MS_SEAT_NOTE to simplify ADA implementation. | M |
rowOldCartCourse.html | Bolded the date of performance on the display for clarity | O |
rowOldCartFestival.html | Bolded the date of performance on the display for clarity | O |
rowOldCartCoupon.html | New Page - must be put in place | R |
rowOldCartPrintCoupon.html | New Page - must be put in place | R |
rowOldCartPrintCourse.html | Added new MS_NOTE_USE_FLAG and MS_SEAT_NOTE to simplify ADA implementation. Updated to use the 'print at home flag' for at a performance level rather than the global 'print at home' flag. Implementing this allows the per performance enable/disable of bar code feature to be used. | M |
rowOldCartPrintDonation.html | ||
rowOldCartPrintFestival.html | Updated to use the 'print at home flag' for at a performance level rather than the global 'print at home' flag. Implementing this allows the per performance enable/disable of bar code feature to be used. Changed alignment of the row to be 'align=top' so that bar codes and text align better | O |
rowOldCartPrintOrderCouponFee.html | compare - minor change | O |
rowOldCartPrintOrderFee.html | compare - minor change | O |
rowOldCartPrintPass.html | compare - minor change | O |
rowOldCartPrintReserve.html | Added new MS_NOTE_USE_FLAG and MS_SEAT_NOTE to simplify ADA implementation. Updated to use the 'print at home flag' for at a performance level rather than the global 'print at home' flag. Implementing this allows the per performance enable/disable of bar code feature to be used. Changed alignment of the row to be 'align=top' so that bar codes and text align better | M |
rowOldCartPrintSub.html | Added new MS_NOTE_USE_FLAG and MS_SEAT_NOTE to simplify ADA implementation. Updated to use the 'print at home flag' for at a performance level rather than the global 'print at home' flag. Implementing this allows the per performance enable/disable of bar code feature to be used. Changed alignment of the row to be 'align=top' so that bar codes and text align better | M |
rowOldCartReserve.html | Added new MS_NOTE_USE_FLAG and MS_SEAT_NOTE to simplify ADA implementation. Also bolded the date of performance on the display for clarity. | M |
rowOldCartSub.html | Added new MS_NOTE_USE_FLAG and MS_SEAT_NOTE to simplify ADA implementation. Also bolded the date of performance on the display for clarity. | M |
rowSubReserve.html | Added new MS_NOTE_USE_FLAG and MS_SEAT_NOTE to simplify ADA implementation. | M |
rowTicketCourse.html | Chanced the columnspan setting from 3 to 4. Only change if you implement the ADA column in tmTicketPrice_MapDefault.html | O |
rowTicketFestival.html | Chanced the columnspan setting from 3 to 4. Only change if you implement the ADA column in tmTicketPrice_MapDefault.html | O |
rowTicketReserve.html | Added new MS_NOTE_USE_FLAG and MS_SEAT_NOTE to simplify ADA implementation. If you add this, you must also change tmTicketPrice_MapDefault.html and the order rowticketxxxxxx.hrml | M |
TMoldCartDetailsPrint.html | Adjusted the table width to be 700 pixels so that the user cannot make it wider and then print at the wider setting. This should help force bar codes to print on a page. Only change if you print at home and are finding a lot of people where the bar codes are not easily readable. | O |
tmtermsandconditions.html | revised http to https. Added better template text to handle possible ADA term | M |
We attempt to provide a major feature update twice a year and this release is one of those - with significant functional enhancements, performance enhancements, brand new features and a collection of bug fixes. For this release, the key changes fall into 7 categories, although there is a lot of under the hood changes.
There are 7 major areas with feature enhancement
The upgrade time from version 9.07 is a few minutes. Upgrading this version requires, at a minimum:
The following changes have been made to Theatre Manager since version 9.07
Point releases are minor version fixes and small enhancements to any particular version.
As of 9.08.05, you can also access this feature by selecting a seat and then right-clicking on it to access the context menu per the example. (9.08.05)
A new feature has been added under the 'patron sales' menu to allow you you find orders directly. You could use this to see what orders were added on a specific day, created by a specific employee, changed on a date, order notes contain information, etc. (9.08.05)
Specifying a genre for an event is required. We also suggest entering the external sales notes so that a description of your event appears in the iPhone app.
The upgrade time from version 9.08 is short. Upgrading this version requires, at a minimum:
The following changes have been made to Theatre Manager since version 9.08
Point releases are minor version fixes and small enhancements to any particular version.
Note: at this time, the colours on the map are black and white. We will be introducing colouring options later this year.
While only really affecting Moneris authorization, this option CVV2/CID feature is now common to all merchant services.
The upgrade time from version 9.08 or 9.09 is short. Upgrading this version requires, at a minimum:
The following changes have been made to Theatre Manager since version 9.09
Point releases are minor version fixes and small enhancements to any particular version.
http://itunes.apple.com/us/app/ticket-trove/id417854093?mt=8&ign-mpt=uo%3D4
There are no changes to web pages for this version If you wish the latest references pages, please download the web page updates and compare the web pages to your existing pages.
This release is a minor release.
This key list of accumulated changes since 9.07 are:
To determine what version of postgres you are on, examine the login window. The version of Theatre Manager is in the lower LEFT corner of the log in window, while the version of postgres is in the lower RIGHT corner of the window.
The upgrade time from version 9.08 or later is short. Upgrading this version requires, at a minimum:
The following changes have been made to Theatre Manager since version 9.10
Point releases are minor version fixes and small enhancements to any particular version.
Examples where this might be useful are:
Please download the latest web page updates and compare the web pages to your existing pages. (If you have already implemented the 'tmCustom' folder, you can simply replace the pages below). The following itemizes the changes made to web pages:
In the 3rd Column are 3 flags.
Files in the each outlet directory (1/WebPagesXX) | ||
tmTickets.html | There is one change to tmTickets.html that adds the link to TicketTrove if you wish to make it available to your patrons. If you make the change, we also advise setting up information in Theatre Manager to highlight your venue or events in a way you'd prefer. | O |
tmCustom | The other change you may wish to make for this set of web pages is to move only the pages you've customized to the separate folder tmCustom folder -- to make future changes much easier for you. Please refer to the standard web pages to get the directory structure of this new folder | O |
TMattendance.html | This web page can be used to scan tickets with a tethered bar code reader via the web listeners. If you wish to use this feature, you must replace the existing file with this one. | O |
TMsubscriptionsRenew.html | Correct a field on the web page to show the correct subscription series that the patron is renewing. Also, add support for renewing subscriptions in the state 'new-not yet booked' so that patrons can now checkout and pay for new subscriptions set up by the box office via the web listener. | O |
Files in the main templates directory | ||
rowSubRenewHeader.html | Added support to allowing patrons to renew a subscriptions online where it was set up in the box office as 'new-not yet booked' so that patrons can then check themselves out. The intent is to keep new subscription statistic tracking separate from renewing subscriptions (TM always did this) and allow this new subscription to be paid for online. | O |
This key list of changes are:
The upgrade time from version 9.0x might be about an hour (estimate only) for an average site. It could be longer if you have lots of historical data and transactions. Upgrading this version requires, at a minimum:
The following changes have been made to Theatre Manager since version 9.11
Point releases are minor version fixes and small enhancements to any particular version.
We have put in place the mechanism to track the source/referrer of the shopping cart source from the conversation last week around the board room table. In this sample screen, we've shown 4 carts with 'first time buyer' and 'TimeUnion' as sources for two of the purchases.
Setting them up is easy. You can set up links using by either:
A new feature has been added for reserved seating web pages to allow a customer to find seats in a venue - but not necessarily have them be together. This can be useful for group sales or when a venue is selling out. It can also help users if the seat map is displaying the used seats (masked out) as per the picture. Implementing the feature means adding the web page changes indicated below. (9.12.08)
How does TM decide to find the seats if the user indicates that the seats do not necessarily need to be together?
A new tab has been added to the Company Preferences window to allow some data retention settings. The items on the:
A performance testing function was added to the 'Web Listener' tab called Check Ticket Sales Times. This can be used from multiple workstations to test how long it might take to sell out a performance while you are watching it by clicking on a sales map on another machine. It does not use the web listener - It simply uses the find best seats and book functions in TM against a dummy order to see how long before a venue is sold out. If you use multiple machines to test the same event, it may give an idea of how well your listener and web server are performing under load. If you make changes to the postgres server parameters or change the server, you may be able to judge the effects in a controlled test. (9.12.05)
Please download the latest web page updates and compare the web pages to your existing pages. (If you have already implemented the 'tmCustom' folder, you can simply replace the pages below). The following itemizes the changes made to web pages:
In the 3rd Column are 3 flags.
Files in the each outlet directory (1/WebPagesXX) | ||
TMtickets.html | Added capability for search by genre and an icon link for ticket trove. If implemented, the other 3 genre files become mandatory. | O |
tmError.txt | 3 new error messages to deal with
|
O |
Files in tmMaps | ||
TMticketsSection_MapDefault.html | Added an option for the patron so that they can specify if their seats need to be together or not (meaning pairs where possible). This uses the F_TOGETHER variable in the form. | M |
Files in the main templates directory | ||
constantALLGENRES.txt | New File - place in this directory. If genre search is implemented, you may want to change the word 'Genre' if it is not suitable for your web site. | O |
setGENRE_LIST.html | New file - place in this directory | O |
setGENRE_LISTempty.html | New file - place in this directory | O |
Files in the tmGifs directory(1/WebPagesXX) | ||
tickettrove.jpg | new file Copy the ticket trove icon to this directory | O |
This key list of changes are:
Version 9.15 has some significant features and preparing database for the new fields may take some time for an average site (depending on total ticket sales). Upgrading this version requires, at a minimum:
The following changes have been made to Theatre Manager since version 9.12
Point releases are minor version fixes and small enhancements to any particular version.
The most significant change is the separation of theatre maps into 'Venues' and 'Pricing Maps'. Prior to version 9.15, a theatre map contained both the address data and a pricing map. It meant a new zone set up in a venue required a new theatre map which had some side effects on facility management.
Separating this information means that venues now reflect the true list of venues that are used -- and you can have as many pricing maps as you wish within the venue. Facility Management now shows tasks in the venue on the calendar (and not the pricing map) which is far more convenient.
The screen below shows what a venue now looks like. It has the name, address and icons for ticket trove (like before). The pricing maps at the right are new. You can edit them by double clicking (or create new ones)
The pricing map is shown below and contains the seat count, graphic map, seat names and best seat settings. The subtle difference is that a venue can contain multiple pricing maps which has some future potential:
The order window has been changed so that the words on the left side of the window which are used to navigate to various parts of an order (like tickets, fees, payments, etc), has been enhanced with icons. This change is based on observation and feedback to try to make it even easier to navigate the sales process.
Other changes are:
This is a vey subtle change to the operation of Theatre Manager. Much of using TM consists of filling lists with information - such as searching for patrons or loading up the tickets in the ticket list on the patron detail. We've made this faster in the past by offloading some computation to the postgresql server.
In version 9.15, we've taken this a step further. Many machines these days have two or more CPU's. The trend to multi core machines means that a computer is largely idle unless we take advantage of the other cores - which we did.
The effect, from a user perspective, is threefold and not immediately obvious:
Other changes are:
Please download the latest web page updates and compare the web pages to your existing pages. (If you have already implemented the 'tmCustom' folder, you can simply replace the pages below and verify your customizations).
The vast majority of the changes replace any pricing map field with its corresponding venue field. For example TM_ADDRESS1 should be replaced with VE_ADDRESS1 everywhere. However, to avoid the need to change pages immediately, we have replicated venue and pricing map address data within Theatre Manager so that the page changes can happen at a later date -- if desired. Meaning that existing web sites should work as long as the 3 'required' pages are implemented.
The second major change is enhancing the 'print at home' feature - only make changes if you wish this feature.
The following itemizes the changes made to web pages:
In the 3rd Column are 3 flags.
Files in the each outlet directory (1/WebPagesXX) | ||
TMpatronLimitedProfile.html | Revised html for radio buttons for do not mail so that you can now click on the text to alter the radio buttons. The user doesn't need to be as accurate clicking on the web pages. Adjusted the page layout to take into account a Windows Internet Explorer incompatibility. Enhanced the page layout for more clearer options for what the patron can do. This page change is only Mandatory for those sites that offer the Limited Patron Profiles option during the checkout process. | M |
TMpatronNew.html | Added a reference in the top toolbar containing "Login Information" to make a note that the asterisk refers to required fields on the page. Centered the entire table on the screen (it was left justified to the left of the screen). Enhanced the page coding so that only missing fields are now reported to the user and changed the stylesheet for missing fields. |
O |
TMpatronUpdate.html | Mandatory change to the page to ensure that adding a new household member works with revised submit function. Also revised html for radio buttons for do not mail so that you can now click on the text to alter the radio buttons. The user doesn't need to be as accurate clicking on the web pages. Added a reference in the top toolbar containing "Login Information" to make a note that the asterisk refers to required fields on the page. Centered the entire table on the screen (it was left justified to the left of the screen).
Enhanced the page coding so that only missing fields are now reported to the user and changed the stylesheet for missing fields. |
M |
TMsubscriptionsRenew.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. Revised html for radio buttons for do not mail so that you can now click on the text to alter the radio buttons. The user doesn't need to be as accurate clicking on the web pages. | O |
TMcheckout.html | Major revisions for print at home selection. One change involved moving most of the customised mailing rules into an include file called tmTemplates/tmTicketHandling.html. Moving things there may make this window changed less often. Suggest completely replace this page. | R |
TMcheckoutNoPayment.html | Change the SCH_PRINT_AT_HOME variable name to SCH_TIX_PRINT_STATUS | R |
TMCheckoutConfirmation.html | Revisions to show the 'print tickets' button when user selects e-ticket delivery. | R |
TMcheckoutProcessing.html | Add a status line to show/remind the user of the print at home/eticket delivery option they chose before they actually submit | O |
TMpatronNew.html | Revised html for radio buttons for do not mail so that you can now click on the text to alter the radio buttons. user doesn't need to be as accurate clicking on the web pages. | O |
TMfutureTickets.html | Added code around the 'print all future tickets' button so that it only appears if print at home is allowed. Regardless if button is visible, user can only print tickets that allow print at home. | O |
TMError.txt | Add error message 10162 that describes a condition where two people have the same email address and are not in the same household. Since they can't log in - it informs the patron that they need to contact the box office regarding their email address. Add error messages 10163 and 10164 that inform the user about how they changed their ticket distribution status. Add Error message regarding packages for sale | O |
Files in the WebPagesXX/TMtemplates directory | ||
rowCartCoupon.html | Remove a comma from the link that was making incorrect URL's so that clicking on the URL would indicate that the link was broken. Fixing this means that patron browsing the web could now click the description of the discount fee created by using the coupon and see a description of what it means. Additional cosmetic changes. | R |
rowCartOrderCouponFee.html | Added this file in the TM directory. It was not used prior to version 9.15 and is required to display coupon in the shopping cart correctly when there is a one time discount applied -- and allow the patron the ability to remove the coupon from the cart. | R |
rowSubReserve.html | Added this file in the TM directory. It was not used prior to version 9.15 and is required to sell tickets for subscriptions -- and allow customization of the subscription ticket seat offering to be different than the normal reserved ticket display. | R |
rowCheckoutOrderCouponFee.html | Replace this file in the TM directory. It has not been used prior to version 9.15 and has been updated to match the visual display in the checkout invoice as it is shown within the online shopping cart. | O |
rowPatronAddress.html | Added "span class=missingfield" to the Country popup field to have the required field asterisk appear in the colour red. Currently it was appearing in the colour black where as all other asterisks on the page were in the colour red.
Enhanced the page coding so that only missing fields are now reported to the user and changed the stylesheet for missing fields. |
O |
rowPatronEmail.html | When adding a new online account, it will default to 'Email Address' but when editing the account it will display the kind of email address it is (home, work, other, etc.) rather then saying 'Email Address' for each Email address the patron has assigned to their account. Also updated it show an asterisk beside the Email and Password fields to make it part of the required fields when entering or editing the patron account.
Enhanced the page coding so that only missing fields are now reported to the user and changed the stylesheet for missing fields. |
O |
rowPatronEmailLimitedProfile.html | Enhanced the page coding so that only missing fields are now reported to the user and changed the stylesheet for missing fields. This page is only used by sites that offer Limited Patron Profiles option during the Checkout process. | O |
rowPatronContact.html | Enhanced the page coding so that only missing fields are now reported to the user and changed the stylesheet for missing fields. | O |
rowCartCourseNewGroup.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. Updated the submit form() function. | R |
rowCartFestivalNewGroup.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. | O |
rowCartMailFee.html | Changed SCH_PRINT_AT_HOME to SCH_TIX_PRINT_STATUS | R |
rowCartCourse.html | added a parameter to the submit button to match the new function. | M |
rowCartFestivalNewGroup.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. | O |
rowCheckoutCourse.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. | O |
rowCheckoutFestival.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. | O |
rowCheckoutReserve.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. | O |
rowFutureTicketHeader.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. Replace D_PRINT_AT_HOME with PB_PRINT_AT_HOME |
R |
rowFutureTicketPrintHeader.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. Revised header to print the Time of the performance in large type so that it is obvious. Replace D_PRINT_AT_HOME with PB_PRINT_AT_HOME | R |
rowOldCartCoupon.html | Cosmetic changes. | O |
rowOldCartCourse.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. Replaced D_FESTIVAL_DESC with D_COURSE_DESC | O |
rowOldCartFestival.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. | O |
rowOldCartPrintCourse.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. Replace D_FESTICAL_DESC with D_COURSE_DESC | O |
rowOldCartPrintFestival.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. | O |
rowOldCartPrintReserve.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. | O |
rowOldCartReserve.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. | O |
rowSubBookedHeader.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. | O |
rowSubNewDetail.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. | O |
rowSubRenewHeader.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. | O |
rowTicketEvent.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. For the Date Column, set the width from 80 to be 140 to match the setting in the WebPagesEN/tmTickets.html page. This will now allow the date to show all on a single line. | O |
SetMerchant_List.html | Change the currency from the country to the currency code to satisfy moneris | O |
setVenue_List.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. | O |
rowTicketEventExport.html | Renamed a number of fields from TM_ to VE_ along with the XML. Replace this file in entirety. If you are using it to extract information from TM for another site, then you will need to adjust the code elsewhere to match the field names, or leave the XML tags the same. | M |
tmnavButtons.html | changed btnTicket to btnGetEventList to optimize the caching that the web listener now does for this web page. It makes this button the same as the "search' button on the tmTickets.html page | M |
tmTicketHandling.html | NEW PAGE - Localized all code for selecting E-ticket, Print at home, and hold at will call on the web pages. Required if TMCheckout is changed | M |
tmtermsandconditions.html | revised so that it no longer needs to have customized web links in it for the base href. The page is now processed by Theatre Manager | O |
rowTicketEventExportCustom.html | Renamed a number of fields from TM_ to VE_ along with the XML. Replace this file in entirety. If you are using it to extract information from TM for another site, then you will need to adjust the code elsewhere to match the field names, or leave the XML tags the same. | M |
Files in the WebPagesXX/tmScripts directory | ||
dropDownMenuFunction.html | Replace entire file - added third parameter to help the submit button functions on the checkout window. | R |
PleaseWaitMessageFunction.html | Replace entire file - revised code for opening and closing popup windows. | R |
Files in the WebPagesXX/tmEvent directory | ||
tmEventDefault.html | Renamed the following fields: TM_MAP_NAME to VE_NAME, TM_ADDRESS1 to VE_ADDRESS1, TM_ADDRESS2 to VE_ADDRESS2 Added VE_CITY, VE_PROVINCE, VE_POSTAL_CODE to the description of the location of the venue. Revised code so that it is easier to identify the form within the web page for coders. |
O |
tmEvent*.html | if you have customized TMEventDefault.html to be specific to other events, you may wish to make the same name changes as above. | O |
Files in the WebPagesXX/tmSubscription directory | ||
tmSubscriptionDefault.html | Renamed the following fields: TM_MAP_NAME to VE_NAME, TM_ADDRESS1 to VE_ADDRESS1, TM_ADDRESS2 to VE_ADDRESS2, TM_VENUE_NOTES to VE_NOTES, TM_SEQ to VE_SEQ, TM_WORK_PHONE to VE_WORK_PHONE, TM_FAX_PHONE to VE_FAX_PHONE, and added hidden field for SG_SEQ Added VE_CITY, VE_PROVINCE, VE_POSTAL_CODE to the description of the location of the venue. Also moved the location of the <form> elements to make it clearer in the code. The effect of the change is so that the buy subscription now button will take the user right to the subscription selection window instead of going to the list of subscriptions - the context is more immediate and one less web click for the patron. |
M |
Files in the WebPagesXX/tmMaps directory | ||
TMsubscriptionMapDefault.html | Cosmetic changes |
O |
TMsubscriptionPriceMapDefault.html | Cosmetic changes | O |
TMticketsPrice_MapDefault.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. Also replace TM_ADDRESS1 with VE_ADDRESS1, TM_ADRESS2 with VE_ADDRESS2 | O |
TMticketsSection_MapDefault.html | Replace TM_MAP_NAME with VE_NAME if you want to use the overall venue name instead of the new pricing map name on web pages. Also replace TM_ADDRESS1 with VE_ADDRESS1, TM_ADRESS2 with VE_ADDRESS2 Revised html for radio buttons for do not mail so that you can now click on the text to alter the radio buttons. user doesn't need to be as accurate clicking on the web pages. |
O |
TMticketsSection_MapDefaultc.html | Added VE_NAME, VE_ADDRESS1, VE_ADDRESS2 so that any course offering window is consistent with reserved and general admission and shows the address of the venue | M |
TMticketsSection_MapDefaultf.html | Added VE_NAME, VE_ADDRESS1, VE_ADDRESS2 so that any course offering window is consistent with reserved and general admission and shows the address of the venue. | M |
Files in the WebPagesXX/tmVenue directory | ||
tmVenueDefault.html | Renamed the following fields: TM_MAP_NAME to VE_NAME, TM_ADDRESS1 to VE_ADDRESS1, TM_ADDRESS2 to VE_ADDRESS2, TM_VENUE_NOTES to VE_NOTES, TM_SEQ to VE_SEQ, TM_WORK_PHONE to VE_WORK_PHONE, TM_FAX_PHONE to VE_FAX_PHONE Revisions to form component to make it easier for web programmers to use. |
O |
Files in the WebPagesXX/tmCampaign directory | ||
tmCampaignDefault.html | Revised layout to be similar to other default display pages. |
O |
Files in the WebPagesXX/tmPass directory | ||
tmPassDefault.html | Revised layout to be similar to other default display pages. |
O |
Files in the WebPagesXX/tmGifs directory | ||
stylepages.css | Added a new style sheet item called 'missingfields' and defaulted it to be the same as 'message' style but with the 'main' font size. | O |
Files in the WebPagesXX/tmPackages directory | ||
tmPackagesDefault.html | Added package header file to enable sale of multiple general admission events on one page. | O |
The key list of changes are:
and more... (as always).
It contains a performance, functional, and database enhancements AND a mandatory postgres update if you want to use this version. Since it is not mandatory to upgrade to this version ASAP, please only update at a convenient time when you have reviewed all new features and able to make changes to the web pages.
Upgrading to version 9.16 requires, at a minimum:
The following changes have been made to Theatre Manager since version 9.15
Point releases are minor version fixes and small enhancements to any particular version.
meaning - the card has not truly been authorized yet, but the customer does not have any tickets, so if a card cannot be authorized in end of day, you still have time to cancel the order.
This change was made because donations can be audited and require an ability to trace back to the source. Subscriptions are different from single tickets for obvious reasons. Passes and Gift certificates have varying business practices for storing and using the passes which need more information.
This can be done while sales are occurring and takes moments. The example to the left shows how Theatre Manager controls which venues and pricing maps can be used when changing the entire event. The second example shows how you can select pricing maps within the venue if you are only changing one specific performance.
There are a few rules that will be enforced when switching venues or pricing maps such as the new venue or pricing map must:
Please download the latest web page updates and compare the web pages to your existing pages. (If you have already implemented the 'tmCustom' folder, you can simply replace the pages below and verify your customizations).
The vast majority of the changes are to add easy support for the new asyncronous google analytics web page changes. If you are already at version 9.15.06 or later, you may already have all these page changes, so there would be nothing to do.
The following itemizes the changes made to web pages:
In the 3rd Column are 3 flags.
New web pages: only one of the following is required to go from version 9.15.05 to a later version and only if your venue is using limited profile patron checkout. All page changes can be made if you are running 9.15.05 or earlier and it won't break anything. Note: You must rename the folder 'eblastImages' to 'eblastimages' (i.e. make all items lower case) to resolve issues with servers and/or browsers that work with case sensitive URL's and file names. |
||
tmTemplates/constantPatronContactLIMITED.txt | if using limited profile patron checkout as it limits the data required and shows the 'mandatory' fields properly. | M |
tmTemplates/tmLoginLimitedPatron.html | part of breaking apart TMpatronlimitedProfile for clarity | O |
tmScripts/googleheader.html | an include file was added to a fair number of pages before the </head> to support the new async google analytics approach. If you are not using the async google analytics code, you do not need to worry about these changes | O |
tmFees/tmPrivacyPolicy.html | is a new page containing privacy policy and is directed at limited profile patrons -- so that it might encourage those people to sign in and create an account. | O |
ticketsStats.html | This is in the 'htdocs' root folder and shows stats for internal use in a refreshing page. IT is set, by default to 3 seconds and will need to have the venue ticketing URL updated in this web pages. It is for management purposes only and not part of the web sales process. | O |
Existing web page changes that should can be used in either version 9.15 ot 9.16 or later and should be forward and backward compatible. |
||
changes in webPagesEN | ||
TMError.txt | add a message for partial patron login , so that if they try to log in after getting their notification of purchase, but have not provided a password, then this message is designed to let them know they must supply one. | O |
TMPasswordChange.html | add googleheader.html include file and add small feature of not requiring old password on changing password for secondary email addresses that might arrive because of partial patron | O |
tmAttendance.html | add googleheader.html include file | O |
TMcart.html | add googleheader.html include file | O |
TMCheckoutCardError.html | add googleheader.html include file | O |
TMCheckoutConfirmation.html | add googleheader.html include file | O |
TMcheckoutNoItems.html | add googleheader.html include file | O |
TMcheckoutNoPayment.html | add googleheader.html include file | O |
TMcheckoutProcessing.html | add googleheader.html include file | O |
TMcoupon.html | add googleheader.html include file | O |
TMDonation.html | add googleheader.html include file | O |
TMDonationMonthly.html | add googleheader.html include file | O |
TMFutureTickets.html | add googleheader.html include file | O |
TMFutureTicketsPrint.html | add googleheader.html include file | O |
TMHome.html | add googleheader.html include file | O |
TMLogin.html | add googleheader.html include file | O |
TMLoginSelectPatron.html | add googleheader.html include file | O |
TMLogoff.html | add googleheader.html include file | O |
TMLogoffOpenCart.html | add googleheader.html include file | O |
TMmailList.html | add googleheader.html include file | O |
TMmailListDisallow.html | add googleheader.html include file | O |
TMmailListQuickAdd.html | add googleheader.html include file | O |
TMmailListVerify.html | add googleheader.html include file | O |
TMOldCartDetails.html | add googleheader.html include file | O |
TMOldCartDetailsPrint.html | add googleheader.html include file | O |
TMOldCartHeaders.html | add googleheader.html include file | O |
TMPackageDefault.html | add googleheader.html include file | O |
TMPass.html | add googleheader.html include file | O |
TMPassAskAmount.html | add googleheader.html include file | O |
TMPasswordForgot.html | add googleheader.html include file | O |
TMPassResetChange.html | add googleheader.html include file | O |
tmSubscriptions.html | add googleheader.html include file | O |
tmSubscriptionsRenew.html | add googleheader.html include file | O |
TMsys404.html | add googleheader.html include file | O |
TMsysBackupInProgress.html | add googleheader.html include file | O |
TMsysCookiesDisabled.html | add googleheader.html include file | O |
TMsysInvalidCall.html | add googleheader.html include file | O |
TMsysInvalidCallDirect.html | add googleheader.html include file | O |
TMsysInvalidCallNoAccess.html | add googleheader.html include file | O |
TMsysInvalidFunction.html | add googleheader.html include file | O |
TMsysWebSalesDisabled.html | add googleheader.html include file | O |
TMtickets.html | add googleheader.html include file | O |
TMticketsCalendar.html | add googleheader.html include file | O |
TMticketsMaxPurchased.html | add googleheader.html include file | O |
TMticketsSoldOut.html | add googleheader.html include file | O |
TMvolcalendar.html | add googleheader.html include file | O |
TMvolunteer.html | add googleheader.html include file | O |
TMMaps Folder | ||
TMticketsPrice_MapDefault.html | add googleheader.html include file | O |
TMticketsSecton_MapDefault.html | add googleheader.html include file | O |
TMticketsSecton_MapDefaultc.html | add googleheader.html include file | O |
TMticketsSecton_MapDefaultf.html | add googleheader.html include file | O |
tmSubscriptionMapDefault.html | add googleheader.html include file. Add feature to support changing the series code and seeing which seats are available on a control house as the performance code is changed on the window. | O |
tmSubscriptionMapDefaultf.html | add googleheader.html include file | O |
tmSubscriptionPriceMapDefault.html | add googleheader.html include file | O |
tmSubscriptionsPriceMapDefault.html | add googleheader.html include file | O |
TMpatronlimitedProfile.html | restructured and rewritten to have FORM buttons for selecting choice of login or partial patron. if using partial patron, should use new pages | O |
TMpatronUpdate.html | add googleheader.html include file. Add F_HTML_REQUIRED_xx. Add privacy policy page link | M |
TMpatronNew.html | add googleheader.html include file. Add F_HTML_REQUIRED_xx. Add privacy policy page link | M |
TMVenue folder changes | ||
tmVenueDefault.html | add googleheader.html include file | O |
tmSubscription Folder changes | ||
tmSubscriptionDefault.html | add googleheader.html include file | O |
tmPass folder changes | ||
tmPassDefault.html | add googleheader.html include file | O |
tmCampaign Folder changes | ||
tmCampaignDefault.html | add googleheader.html include file | O |
tmTemplates Folder changes | ||
tmtermsandconditions.html | add googleheader.html include file and link to privacy policy | O |
setMerchantList.html | remove cause of error that is within a comment | O |
rowPatronAddress.html | display behaviour - change for limited patron required fields and F_HTML_REQUIRED_xx |
M |
rowPatronContact.html | display behaviour - change for limited patron required fields and F_HTML_REQUIRED_x | M |
rowPatronEmail.html | display behaviour - change for limited patron required fields and F_HTML_REQUIRED_x | M |
rowPatronEmailLimtedProfile.html | display behaviour - change for limited patron required fields and F_HTML_REQUIRED_x | M |
tmLoginForm.html | restructured to make partial patron pages clearer. only needs changed if TMpatronLimitedProfile is changed | M |
Upgrading to version 9.17 requires, at a minimum:
The following changes have been made to Theatre Manager since version 9.16
Point releases are minor version fixes and small enhancements to any particular version.
There are no changes to web pages for this version. Make sure to read the release notes for prior versions in case those updates apply to you.
Upgrading to version 9.18 requires, at a minimum:
The following changes have been made to Theatre Manager since version 9.17
Point releases are minor version fixes and small enhancements to any particular version.
Please download the latest web page updates and compare the web pages to your existing pages. (If you have already implemented the 'tmCustom' folder, you can simply replace the pages below). The following itemizes the changes made to web pages:
In the 3rd Column are 3 flags.
Files in the each outlet directory (1/WebPagesXX) | ||
TMvolunteerActivity.html | New file - place in this directory | O |
TMloginSelectPatron.html | Added a feature to make it easier for people in a household sharing an email address to select the household patron and log in. | O |
tmError.txt | 9 new error messages to deal with from 10176 to 10184 All error messages have had the $$ substitution replaced with some key names in {}. Prior verisons of TM only allowed on substitution. With the new {} syntax, the error messages can be re-arranged and do more substitutions from values set in company preferences. As an example, a message can now look like the {seats} you wanted in the {venue} could not be found, please select another {performance}. or reworded like: Select a different {performance}. This {venue} has no {seats} available for the {event} This should make customization for langauge and venue specifics much easier. |
O |
Files in the main templates directory | ||
rowVolHistoryDetail.html | Revised to show future volunteer activities on web pages | O |
rowVolHistoryHeader.html | Revised to show future volunteer activities on web pages | O |
constantALLACTIVITIES.html | New file - place in this directory | O |
rowCheckoutCourse.html | replace the word Course with <field>D_COURSE_DESC</field> to substitute from company preferences | |
Files in the tmFees directory(1/WebPagesXX) | ||
tmPrivacyPolicy.html | Fixed spelling error for 'decide' | O |
Upgrading to version 9.19 requires, at a minimum:
The following changes have been made to Theatre Manager since version 9.18
Point releases are minor version fixes and small enhancements to any particular version.
When using this search option, patrons will be shown that have a series of at least 12 contiguous digits in various fields in fields where we have most often observed users typing card information in the past. Searching for 12 contiguous digits might find things like 4500 000 000 000 or 5200 0000 0000 0000. It doesn't matter if there are one or more spaces between the numbers or not. Data that will not be found are phone numbers like 518-444-5555 or conditions where numbers are separated by something other than spaces.
Searching may take a short while. Tests on a very large database (400,000 patrons) with a lot of other data on a fast server yielded a total of 131 possible patrons within 8 seconds. Your mileage may vary.
Fields that are searched are:
Please download the latest web page updates and compare the web pages to your existing pages. (If you have already implemented the 'tmCustom' folder, you can simply replace the pages below). The following itemizes the changes made to web pages:
In the 3rd Column are 3 flags.
Files in the each outlet directory (1/WebPagesXX) | ||
Files in the main templates directory | ||
rowFutureTicketHeader.html | Fixed spelling error from 'aligh' to 'align' | O |
Files in the tmMaps directory(1/WebPagesXX/tmMaps) | ||
TMticketsPrice_MapDefault.html | Fixed spelling error from 'aligh' to 'align' | O |
TMsubscriptionPriceMapDefault.html | Fixed spelling error from 'aligh' to 'align' | O |
TMsubscriptionsPriceMapDefault.html | Fixed spelling error from 'aligh' to 'align' | O |
Upgrading to version 9.20 requires, at a minimum:
The following changes have been made to Theatre Manager since version 9.19
Point releases are minor version fixes and small enhancements to any particular version.
There is a significant change to how the eblast and letter merge process works. This is in preparation for our next generation Web Server processes. In the past emailing was generally done as a single merge and email step. Now, in all cases, emails and letters are added to the database first and then the web listeners will send them. As before, you can select the 'email now' and 'email later' options.
The differences in the behaviour you could see are:
Other changes involving word processing are:
Please download the latest web page updates and compare the web pages to your existing pages. (If you have already implemented the 'tmCustom' folder, you can simply replace the pages below).
These page changes are effective as of 9.20.02 and allow print at home tickets to appears on one page (see sample ticket below). This feature was added because we have heard that patrons want individual tickets for each attendee and venues told us they wanted to include advertizing and make the tickets look more like a traditional ticket. If you do implement this feature, make sure to create your own ticketAd.png file and place it in tmGifs folder (as below).
The following itemizes the changes made to web pages:
In the 3rd Column are 3 flags.
Files in the each outlet directory (1/WebPagesXX) | ||
TMfutureTicketsPrint.html | there are a few changes in this file and we recommend replacing it.
|
O |
Files in tmGifs directory | ||
stylePages.css | Added two global settings for the @media style type to indicate how to display print-at-home tickets on a web page and to tell the browser to paginate them when printing. Added two new style sheets called 'tablerowticketprint' and 'ticketlineprint' that are the fonts used in the ticket sample. |
O |
ticketAd.png | A sample image representing advertizing to put at the bottom of each print at home ticket. Replace this PNG file with something appropriate to your venue that you would like to see printed with each ticket. | O |
Files in the main templates directory | ||
rowFutureTicketPrintCourse.html | revised the complete look of the print at home ticket so that it looks like a ticket for courses - replace this file | O |
rowFutureTicketPrintFestival.html | revised the complete look of the print at home ticket so that it looks like a ticket for general admission events- replace this file | O |
rowFutureTicketPrintReserved.html | revised the complete look of the print at home ticket so that it looks like a ticket for reserved seating events- replace this file | O |
rowFutureTicketPrintHeader.html | simplified this file as the formatting was moved into the 3 files above to consolidate the look of a ticket in the respective files - replace this file. | O |
rowCartCourse.html | Remove duplicated conditional line to show the attendee. This change is mandatory if using the second generation Theatre Manager Server (9.20.07) | M |
rowCartDonation.html | Revise how repeated payments are shown for a donation. This change is mandatory if using the second generation Theatre Manager Server (9.20.07) | M |
Upgrading to version 9.21 requires, at a minimum:
Point releases are minor version fixes and small enhancements to any particular version.
The second generation web servers will eventually replace the current web listeners to provide faster service. A number of venues already have the initial release as of version 9.20. This release of Theatre Manager also has an update to the second generation server that does the following additional functions (instead of having the classic listeners do them)
Please download the latest web page updates and compare the web pages to your existing pages. (If you have already implemented the 'tmCustom' folder, you can simply replace the pages below).
The following itemizes the changes made to web pages:
In the 3rd Column are 3 flags.
Files in the main WebPagesEN directory | ||
TMcheckoutConfirmation.html | Replaced two id= tags with value= tags on SCH_SEQ and C_SEQ for viewing the historical cart detail from the checkout confirmation screen. Also changed the Print Tickets from a submit to a type of button. | R |
Files in the TMtemplates directory | ||
rowFutureTicketPrintCourse.html | Replaced the html code for ' ' to be ' ' so that it works with the second generation server. Also fixed a missing < on a </field> tag. | R |
rowFutureTicketPrintFestival.html | Replaced the html code for ' ' to be ' ' so that it works with the second generation server. Also fixed a missing < on a </field> tag. | R |
rowFutureTicketPrintReserved.html | Replaced the html code for ' ' to be ' ' so that it works with the second generation server. | R |
rowCartDonation.html | Added a missing </field> tag to correct issue with displaying data. | R |
rowOldCartMailFee.html | Remove the extraneous <td> </td> in the last column so that all rows in historical carts have the same number of columns. This just fixes a minor display issue. | O |
Files in the tmPackages directory | ||
tmPackageDefault.html | Fixed the value field for the PKG_SEQ hidden input field. This must be fixed if you want to use the package of event list for selling general admission tickets and have it go back to the package window if the customer selects no quantities. | R |
Files in the tmMaps directory | ||
TMticketsPrice_MapDefault.html | Revised code around 'Next Best Seats' so that the button shows properly if you are using the second generation server. If the cnage is not made, you will see a little cosmetic code on the window. | R |
TMsubscriptionPriceMapDefault.html | same as above | R |
TMsubscriptionsPriceMapDefault.html | same as above | R |
Upgrading to version 9.22 requires, at a minimum:
The following changes have been made to Theatre Manager since version 9.21
Point releases are minor version fixes and small enhancements to any particular version.
There are ongoing changes and performance enhancements for the new TM server:
There are some minor enhancements to the classic web listener. These will continue to occurs as needed until the second generation server handles all services.
Please download the latest web page updates and compare the web pages to your existing pages. (If you have already implemented the 'tmCustom' folder, you can simply replace the pages below). Note that there are over 100 pages that have changed -- none of them mandatory. We have just consolidated the stylesheets into one include file to make it easier for people to add their own stylesheets in a single include
The following itemizes the changes made to web pages:
In the 3rd Column are 3 flags.
Files in the TMscripts directory | ||
styles.html | This file contains the links for the stylePages.css and styleButtons.css. This means you can add your own style sheets to the one file and include it in all other pages. This is designed to consolidate style sheets in one file. | R |
disclaimer.html | This file contains Arts Management disclaimer for the web pages and is now included in each html page via an include file rather than being in each web page. This is more of a tidy up and simplify reading the pages when viewing them. | R |
Files in the TMgifs directory | ||
normalize.css | This is an open source style sheet that is designed to normalize differences between various web browsers and make it easier to work with variations in the browsers. | R |
Files in the TMtemplates directory | ||
constantALLPRICECODES.txt | text to indicate a search for 'all price codes' if none are provided. This is a new feature and the file must be in place for the second generation web server. | R |
constantALLSECTIONS.txt | text to indicate a search for 'all sections' if none are provided. This is a new feature and the file must be in place for the second generation web server. | R |
setBEST_AREA_SEARCH_LIST.html | Allows specification of the fields to go into the best seat search window. This is a new feature and the file must be in place for the second generation web server. | R |
setBEST_AREA_SEARCH_LISTempty.html | The specification of the text shown to the user if the best seat search list in a pricing map is empty. This is a new feature and the file must be in place for the second generation web server. | R |
setBEST_PRICE_CODE_SEARCH_LIST.html | Allows specification of the fields to go into the price code search window. This is a new feature and the file must be in place for the second generation web server. You can specify the price, the price code, or add constants to the prices. | R |
setBEST_PRICE_CODE_SEARCH_LISTempty.html | The specification of the text shown to the user if the price code search list in a pricing map is empty. This is a new feature and the file must be in place for the second generation web server. | R |
The key list of changes since Version 9.15 are:
As a note to all, we are in the process of having Theatre Manager audited to the PCI 2.0 standard as part of the 3 year cycle for PCI compliance.
Upgrading to version 9.23 requires, at a minimum:
The following changes have been made to Theatre Manager since version 9.22
Point releases are minor version fixes and small enhancements to any particular version.
Please download the latest web page updates and compare the web pages to your existing pages. (If you have already implemented the 'tmCustom' folder, you can simply replace the pages below). The Page changes below make print-at-home from the confirmation email and reprinting tickets from an old cart to be the same.
The following itemizes the changes made to web pages:
In the 3rd Column are 3 flags.
Files in the WebPagesEN directory | ||
TMoldCartDetailsPrint.html | Removed the column for the bar code of tickets. | O |
TMcheckoutInvoiceEmail.html | Wording change around information to the patron regarding ability to reprint tickets at home by logging in. | O |
TMoldCartDetails.html | Added a button to reprint tickets that are 'print-at-home' within the order. This will use the same approach as the one ticket per page implemented in prior versions. | O |
TMlogoff.html | Added the 'include' for the navigation buttons to the page. There was no reason that they should be left off the page, so this is a convenience change that makes the header pictures in place on more screens and makes the web experience look smoother. | O |
TMPatronNew.html | Added the 'include' for the navigation buttons to the page. Same as above | O |
TMcart.html | Add button at bottom of cart called 'continue shopping' in case people do not use ticket button at the top of the navigation bar | O |
Files in the TMtemplates directory | ||
rowOldCartPrintCoupon.html | Remove the first column in the table on the printable version of the cart where the bar code used to go. The functionality is replaced in TMOldCartDetails.html via the Reprint Tickets button. | O |
rowOldCartPrintCourse.html | same as above | O |
rowOldCartPrintDonation.html | same as above | O |
rowOldCartPrintFestival.html | same as above | O |
rowOldCartPrintOrderCouponFee.html | same as above | O |
rowOldCartPrintOrderFee.html | same as above | O |
rowOldCartPrintPass.html | same as above | O |
rowOldCartPrintReserve.html | same as above | O |
rowOldCartPrintSub.html | same as above | O |
rowCartCourseNewGroup.html | add performance notes to the cart so that it is the same as the event list | O |
rowCartFestivalNewGroup.html | add performance notes to the cart so that it is the same as the event list | O |
rowCartReserveNewGroup.html | add performance notes to the cart so that it is the same as the event list | O |
setVENUE_LIST.html | replace TM_SEQ with VE_SEQ for consistency of naming fields. At this time, either will work. | O |
Files in the conf/extra directory
These changes below can be made by comparing the 3 config files. Alternatively, if you are at an older version of apache, it may just be better to do an apache upgrade. |
||
httpd-mod_tm.conf | The second generation listener has been enhanced to do multiple retries to connect to a classic server it if determines that it received a wait page. normally this does not happen until you hit periods of high load. The following changes to the mod_tm conf file are placed after the
SetEnv TM_ERROR_PAGE TMsysErrorListeners.html The changed below in the conf/extra/httpd-mod_tm.conf file causes the second generation listener to re-try (20 times) contacting the classic listener multiple times should it encounter a wait page. Effectively, this almost guarantees that a request to the classic listener that gets through the second generation listener will be serviced - vastly reducing the waiting page on high load situations. note: best approach is to just copy the lines below and paste them in or do a file compare, then restart the apache server.
NOTE: on windows that may mean you need to edit the httpd.conf file and uncomment the LoadModule line for mod_headers.so if you are not reinstalling apache from scratch.
|
O |
httpd-balance.conf | Rewrote the forwarding for PCI compliance and enforce switch over to https before the first request ever gets to any listener.
This change requires comparing your old and new httpd-balance.conf and simplifying the mod balancer for port 80 to the 1 line rewrite rule. |
M |
httpd.conf | Uncomment the line
#LoadModule headers_module module/mod_headers.so This change required to enable the multiple retry on the classic listener (only mandatory if you change httpd-mod_tm.conf). |
O |
Upgrading to version 9.24 requires, at a minimum:
The following changes have been made to Theatre Manager since version 9.23
Point releases are minor version fixes and small enhancements to any particular version.
There are no web page changes between this version and the last. However, if you with to get the latest web pages and compare the web pages to your existing pages, you are most welcome to for confirmation.
Upgrading to version 9.25 requires, at a minimum:
The second generation web listener services have been available and in use for a year and the performance improvements have been very satisfying. Based on customer use and support feedback, this version of Theatre Manager is the first to require using second generation listener. Please do not upgrade to this version unless:
|
We highly recommend that Postgres version 9.3.3 be installed. (This version of Theatre Manager accepts various Postgres 9.x). However, we anticipate adding performance and functionality features to Theatre Manager in the next version that will rely on some new features in the Postgres 9.3 database engine. We also completed our PCI 2.0 DSS audit using Postgres 9.3.x, so when we receive our next PCI certification, they require using this latest software. |
The following changes have been made to Theatre Manager since version 9.24
Point releases are minor version fixes and small enhancements to any particular version.
We've finished off some more features that are no longer done by the classic listener. It now handles:
The following itemizes the changes made to web pages. In the 3rd Column are 3 flags:
Download the latest web page updates and compare the web pages to your existing pages. (If you have already implemented the 'tmCustom' folder, you can simply replace the pages below).
Files in main directory | ||
tmError.txt | Minor changes to the message text for messages 10014, 10024, 10032, 10034, 100162, and added 100186 to 10190. These messages relate to the new way of resetting passwords and for redemption of gift certificates and passes online. | R |
tmLogin.html | Made the login window a little clearer for customers. The functions are still the same. | O |
tmPasswordForgot.html | Revised text instructions to apply if using either classic or second generation listener. The second generation listener now uses a password reset approach rather than emailing the actual password. If you are using second generation listener, you may want to update this file as the wording changes are subtle, but clearer. | O |
TMtickets.html | Add optional column to show the ticket trove icon for the event in the event list. Make this change if you want to see the icons from inside theatre manager appear on the select your seats window. If you change this page, you muse also change rowTicketEvents.html. Note also, that the columns have been arranged a little to clarify meaning if you want to use the 'show event online' option even if the event is not yet onsale. The pagination options are now at the top and bottom of the list of events and now only appear if there sufficient events to warrant pagination. | O |
TMcart.html | Simplify show and hide of 'remove' button. Add internet pass redemption button to allow online gift certificates. | M |
TMcheckout.html | Add postdated payment options to the window that appear based on setup within Theatre Manager. Also changes for popup help. | M |
TMcheckoutConfirmation.html, TMcheckoutInvoiceEmail.html, TMCheckoutNoPayment.html, TMcheckoutProcessing.html |
Change so credit card area is not shown if cost of cart was free. Add post dated payment plan options. Add support for popup for help windows and fee descriptions. |
M |
TMcheckoutProcessing.html, TMfutureTickets.html, TMfutureTicketsPrint.html, TMpatronLimitedProfile.html, TMsubscriptionsRenew.html |
Add support for popup for help windows and fee descriptions. |
M |
TMhome.html | Revisions to 'back' button wording. Replace buttons at bottom with an include file for bottom nave buttons and add more options to the patron's online capabilities - such as reviewing future volunteer activities, available passes, and more. |
M |
TMlogin.html | Simplified the look of the login window and more the 'forgot my password' button to a more logical place. |
M |
TMpasswordChange.html, TMpasswordForgot.html, tmPasswordResetChange.html |
Changed to support a password reset style of email. Meaning, if a user forgot their password, this now allows them to use a time limited link embedded in their email to come directly to the web pages and change the password. Passwords are no longer mailed to the patron. |
M |
TMoldCartDetails.html, TMoldCartDetailsPrint.html |
Minor wording changes concerning total at the bottom of the cart contents |
O |
TMoldCartHeaders.html | add pleaseWaitMessageFunction include at top of page. |
O |
TMpass.html | Add show outstanding pass/gift certificate button for patron if online pass redemption is enabled. |
M |
TMpatronNew.html, TMpatronUpdate.html |
Minor cosmetic changes, no functional changes. |
O |
TMvolunteerActivity.html | Revisions to the list of upcomming actifities and search capabilities for volunteer activities. |
M |
TMpassAvailable.html, TMpassCheckBalance.html, TMpasswordForgotEmailReset.html |
NEW files for pass redemption and features in this version |
M |
Files in the TMtemplates directory | ||
tmNavButtons.html | Rename' 'What's New' to be the 'Home' button in recognition of the other patron related features available on this html page. Remove 'Mail Lists' to limit top navigation to the buying process and move it to the TMhome.html page | M |
rowPatronEmail.html | Remove buttons for changing password and replace with 'password reset' links. This is for the new password options in second generation listener. | M |
rowTicketPageList.html | Revised to make selection of page number at bottom of the event list look better and easier to click page area. | O |
rowFutureTicketPrintCourse.html, rowFutureTicketPrintFestival.html, rowFutureTicketPrintReserved.html |
Added option to remove the lower bar code when Theatre Manager is displaying QR bar codes on print at home tickets. That way only one bar code is printed for QR codes and two for 3 of 9 bar codes (one vertically and one horizontally). | O |
rowOldCartPrintCourse.html, rowOldCartPrintFestival.html, rowOldCartPrintReserve.html, rowOldCartPrintSub.html |
Remove internal comments regarding bar code images as they are no longer printable on this page. No functionality changes. | O |
rowTicketEvent.html | Add optional column to show the ticket trove icon for the event in the event list. Make this change if you want to see the icons from inside theatre manager appear on the list. If you also want to use the 'show events not yet on sale' feature, you will need to change this file. Abstracted the event description portion into a new file so it can be shared with eventNotOnSaleYet Abstracted out ticketEventAvailablility into separate file showing good/limited etc. so it can be more easily changed. |
O |
rowTicketEventNotOnSaleYet.html | If you want to use the 'show events not yet on sale' feature, you will need to add this file. It has columns matching rowTIcketEvent.html and TmTickets.html. If you use this feature, then you must make sure all 3 files agree regarding number of columns and column order. Even if you do not use this feature, you should add this file to tmTemplates. | O |
rowCartCoupon.html,
rowCartCourseNewGroup.html, rowCartDonation.html, rowCartFestival.html, rowCartFestivalNewGroup.html, rowCartMailFee.html, rowCartOrderCouponFee.html, rowCartOrder Fee.html, rowCartPass.html, rowCartReserve.html, rowCartReserveNewGroup.html, rowCartSub.html, rowCartSubNewGroup.html, rowCheckoutCoupon.html, rowCheckoutCourse.html, rowCheckoutDonation.html, rowCheckoutFestival.html, rowCheckoutMailFee.html, rowCheckoutOrderCouponFee.html, rowCheckoutOrderFee.html, rowCheckoutPass.html, rowCheckoutReserve.html, rowCheckoutSub.html, rowCheckoutSubNewGroup.html, rowFutureTicketHeader.html, rowOldCartCoupon.html, rowOldCartCourse.html, rowOldCartDonation.html, rowOldCartFestival.html, rowOldCartMailFee.html, rowOldCartOrderCouponFee.html, rowOldCartOrderFee.html, rowOldCartPass.html, rowOldCartPrintCoupon.html, rowOldCartPrintCourse.html, rowOldCartPrintDonation.html, rowOldCartPrintFestival.html, rowOldCartPrintOrderCouponFee.html, rowOldCartPrintOrderFee.html, rowOldCartPrintPass.html, rowOldCartPrintReserve.html, rowOldCartPrintSub.html, rowOldCartReserve.html, rowOldCartSub.html, rowPkgTicketFestival.html, rowSubBookedHeader.html, rowSubNewDetail.html, rowSubNewHeader.html, tmtermsandconditions.html |
Revise to popup into a separate window any fee, event, venue, policy and other descriptions. The popup window is re-used if it is open. The purpose of this subtle interface change is to help kee pthe patron focues on the sales process if they happen to click on something considered a help link. For some of them, add include files for online pass/Gift certificate redemption. Recommended that this change be made, especially if you want online pass redemption. |
M |
tmSocialMedia.html,
tmPoweredBy.html, cellCartPassMaxRedemptionExceeded.html, cellPassLookupDescription.html, cellPassLookupValue.html, rowCartPassRedemption.html, rowCheckoutPassRedemption.html, rowCheckoutPaymentPlan, rowOldCartPassRedemption.html, rowOldCartPrintPassRedemption.html, rowPassRemainingValues.html, rowTicketEventAvailability.html, rowTicketEventCallBoxOffice.html, rowTicketEventImage.html, rowTicketEventName.html, rowTicketEventNotOnSaleYet.html, rowTicketPageHeader.html, tmContactPopup.html, tmnavButtonsFooter.html, tmCheckoutPostDatedPayments.html tmCheckoutPostDatedPaymentRules.html |
NEW files to support pass redemption, post dated payments, event list icons, online pre-sales event display (but not sell), and other new online features | M |
Files in the tmFee directory | ||
tmBoxOfficePolicy.html, tmFeeDefault.html, tmMailFee.html, tmMailFeeDefault.html, tmOrderFee.html, tmOrderFeeDefault.html, tmPrivacyPolicy.html | Revise to use new .boxofficePopup style sheet. Also other changes so it can exist as a popup. Remove any navigation buttons in the popup windows. | M |
Files in the tmCampaign directory | ||
tmCampaignDefault.html | Revise to use new .boxofficePopup style sheet. Also other changes so it can exist as a popup. | M |
Files in the tmSubscription directory | ||
tmSubscriptionDefault.html | Revise to use new .boxofficePopup style sheet. Also other changes so it can exist as a popup. | M |
Files in the tmPass directory | ||
tmPassDefault.html | Revise to use new .boxofficePopup style sheet. Also other changes so it can exist as a popup. | M |
Files in the tmVenue directory | ||
tmVenueDefault.html | Revise to use new .boxofficePopup style sheet. Also other changes so it can exist as a popup. | M |
Files in the TMMaps directory | ||
tmTicketsSection_MapDefault.html | Add optional column to show the ticket trove icon for the event in the event list. Make this change if you want to see the icons from inside theatre manager appear on the select your seats window. | O |
tmTicketsSection_MapDefaultc.html | Same as above - for courses. | O |
tmTicketsSection_MapDefaultf.html | Same as above - for general admission events. | O |
Files in the tmEvent directory | ||
tmEventDefault.html | Modified the URL that will get the graphic image for the Event. It now comes directly from the second generation listener. This eliminates the need to FTP the pictures up to the apache site as the server reads them directly from the database and caches them. If you do not change the page, you will need to put images on the web site manually as the FTP process has been eliminated for simplicity of operation and to make a more live web site. Convert to user as popup style window |
M |
Files in the tmContent directory | ||
all files | revised links to use standard 'redirect links' as described in online document. For most venues, these files are never used. | O |
Files in the tmGifs directory | ||
stylePages.css | Added a .backgroundPopup stylesheet. It is similar to the existing .background except is missing the picture on the page header. This is to handle the new style popup assistance links. | M |
Please note: Apple no longer supports PowerPC Macs in Lion (OSX 10.7) (which are typically 8 years old or so). And, with each new release of their operating system, Apple is nudging developers in the direction that the minimum operating system be OSX 10.6.8 and we think that will soon be Lion.
While we still provide versions of Theatre Manager that run on PowerPC Macs, we anticipate Theatre Manager versions released by early 2014 may be the last that do support PowerPC Macs.
If any of these minimum requirements affect you, please let us know now by sending an email directly to the support team. In the past year we have not heard of any issues since providing this notice.
This means:
You can use Mojave, Catalina, Big Sur, Monterey, Ventura, or Sonoma. We recommend keeping workstations current to the latest version of MacOS is supported within each of these specific versions of macOS.
Apple's website contains instructions to help you update to various versions of macOS. Pick the version of MacOS that is best for your computer and/or other key applications. When selecting Mojave, Catalina, Big Sur, Monterey, or Ventura, please pay particular attention to the notes on machine compatibility. |
|
Arts Management support team does not assist with operating system updates. Please refer to your IT support people if you need technical assistance. |
Windows 10 Pro, Windows 11 Pro, 2016, 2019 or 2022 server with 64 bit OS. | |
Arts Management support team does not assist with Operating system updates. Please refer to your IT support people if you need technical assistance.
ZDNet has some instructions how to update Windows 7 to 10 for free (still) We have endeavoured to describe the pathway for free or inexpensive updates for your convenience. |
Ad of Nov 2022, Theatre Manager still runs on Windows 7 Pro 64 Bit.
Microsoft end of life for Windows 7 was January 14, 2020. We will do best efforts to support it but it is not guaranteed. |
For those who are not for profits, Techsoup has very inexpensive Windows 10 updates. Before buying, make sure that the product is windows 10 pro - licensing is not always clear on the Techsoup web site because Microsoft is not always clear.
For those who are a little more adventurous, Microsoft offered FREE Windows 10 updates (from Win 7 and Win 8.1) through to 2016. Apparently (with a little elbow grease) you can still get those updates for free and obtain valid licences.
ZDNET details how this can be done with success reported as of October 29, 2018. |
Microsoft has a support page on the steps to Change Windows 10 Home to Windows 10 Pro if you wish. After reading the instructions, it is apparently only getting a new product key.
Here are the links to obtain the latest Windows Standard Server from techsoup
Ancient/historical SVG maps created before 2019 may have visual anomalies. Recreating the map in Theatre Manager may resolve this. | |
If you see a visual anomoly in the theatre maps, please let us know and we can help show you how to rebuild them or you can follow the instructions provided. |
Adjusting the dimensions of the map's background display only works on 64 bit versions of Theatre Manager that have an SVG map already in place for pick-your-own seats. |
Step 1 |
When the maps are showing seats that are offset as per the image to the right, there are five general steps to take as per below. These steps should work if you already have enabled pick your own seats - which means you have previously created the SVG map for this venue.
If you see no picture, try step 2 & 3 once. if you still see no picture, then you'll need to drop in your SVG image as if you are making the map from scratch. Click the Graphic Map tab |
Step 2 |
There are three situations that occur:
|
Step 3 |
If there are no errors creating the background JPEG, a new image will appear behind the seats.
|
Step 4 |
Once seats and background are aligned, you need to rebuild the pick your own seat map.
|
Step 5 |
When you are completely satisfied with the look of the map on the Graphic Map tab and the SVG map for pick your own seats.
|
The key difference is that you only need the common SVG map to build for Mac, Windows and Pick your seats.
Optionally, you can still use:
|
As of Jun 14, 2019, there is one known outstanding issue with 64 bit TM - as below
All others are have been fixed - thank you for your assistance. |
Version 10 is the official release incorporating PCI PA/DSS 2.0 certification. Visa/Mastercard requires periodic certification of software that processes credit cards to ensure that the software observes their strict controls and recommendations.
Arts Management Systems has enthusiastically participated in the PCI process since 2000. The Visa/Mastercard audit process requires defining the technology requirements for the version and testing many combinations. For venues, this may mean some minor upgrades to Postgres or Apache. However, most venues will already meet the requirements, especially if already running 9.24 or 9.25 as we steadily implemented these technology advances during the past year. |
|
YOU MUST ALREADY BE AT VERSION 9.25 TO UPGRADE TO VERSION 10.
If your database is not at version 9.25, please use Theatre Manager version 9.25 to upgrade the database before installing version 10. | |
For version 10, the technology audited in the PCI certification process is:
Note: Windows 2003 was audited for use yet is no longer supported by Microsoft (unless you have an extended support agreement with Microsoft). |
Upgrading to version 10.00 requires, at a minimum:
There are no significant feature changes in this version compared to 9.25. It is simply a PCI Compliance release to ensure minimum technology versions.
You must be running version 9.25 before updating to 10.
Point releases are minor version fixes and small enhancements to any particular version.
According to pages 8 and 31 of the CRTC CIO discussion document, the default must be so that the user takes action to opt-in to get marketing email. The default for the USA is that you can assume the person opts in without action. Note that the legislation does not affect items sent by the web listener as a result of buying things or requesting passwords. There are also mitigating factors for not-for-profit organizations; so you may want to read the legislation. (10.00.05)
The goal of the second generation listener is to lessen the need for the classic listener and eventually retire it. This list shows a summary what has been added to the second generation listener as improvement that are compatible with this release of TM. Note also, that the second generation listener is auto deployed, so you will just have these changes, regardless of the version of Theatre Manager you are running.
Please read Canada's Anti-SPAM laws in Bill C-28 and get your own legal advice on this Act. The interpretations below are our understanding of the Act and are not to be construed as a legal opinion, nor should they be interpreted as providing any protection from the proposed remedies in the Act.
Business processes and web forms in Theatre Manager should be configured to favour explicit OPT-IN under bill C-28, to provide as much protection to a venue and its Board of Directors as possible. |
|
Consent falls under two basic categories that are described further below:
|
There is legislation pending in Canada (Jul 1, 2014), the key parts of which are addressed (specifically OPT-IN) in the release notes for version 10.00.05:
Note that the legislation does not affect items sent by the web listener as a result of buying tickets or requesting passwords. There are also mitigating factors for compliance for not-for-profit organizations; so you may want to read the legislation.
Theatre Manager complies with the legislation's requirement of EXPLICIT OPT-IN for all new patrons for marketing purposes.
The current process is:
Instead please:
The opt-in process using one checkbox is a bit of a 'one checkbox kills all emails' to patrons. A feature has existed for a long time in the web sales process to allow patrons to add (or remove) themselves from any mail lists that you have allowed them to manage online. In all cases, this is an explicit opt in (and out) and the date that the patron added themselves can be viewed on the mail list tab on the patron window.
The SecondGeneration listener is being enhanced to make the process more versatile for you (the venue).
The process of a patron adding or updating their personal information online will become:
These existing mail list features in TM to provide a flexible way for patrons to tailor how they wish to be reached. For example, you can have multiple email lists that effectively mean:
You can
There appears to be provisions in the act for implicit right to email people
Upgrading to version 10.01 requires, at a minimum:
Be absolutely sure to read your choices about CASL, the mail list double opt in feature and which replaces the do not email flag as part of the 'Things a venue may need to do'. Using double opt-in impacts your business practices as the do not email flag becomes extraneous. Criteria changes to use 'belongs to mail list' instead of 'do not email' in reports and building mail lists. |
The following changes have been made to Theatre Manager since version 10.00
Note: you can implement both single opt-in (click a checkbox and subscribe) or double opt-in (click checkbox, receive email, confirm and be added to mail list after the confirmation) on a mail list by mail list basis.
Point releases are minor version fixes and small enhancements to any particular version.
Examples:
Please download the latest web page updates and compare the web pages to your existing pages. (If you have already implemented the 'tmCustom' folder, you can simply replace the pages below). The Page changes below make print-at-home from the confirmation email and reprinting tickets from an old cart to be the same.
The following itemizes the changes made to web pages:
In the 3rd Column are 3 flags.
Files in the main WebPagesEN directory | ||
TMPatronNew.html | Add page redirection into the hidden param field. If nothing is specified for altbtn=xxx, then a new patron will take the patron to the mail list window to sign up for one or more mail lists - as suggested for opt-in for Canada's anti-spam legislation. To retain the web behaviour of previous versions of TM, change the parameter to be altbtn=btnHome per the example at the bottom of the web page.
added <!--#include virtual="TMtemplates/tmNotificationHeader.html" --> that provides for adding sign up email lists as a check box For example :
|
R |
TMPatronUpdate.html | Same as above.
Also hide the 'do not email' option (except for USA) due to explicit opt-in requirements of CASL and other countries. The wording for 'mail lists' has been changed to email notifications to encourage those affected by CASL laws to make some email notification settings. |
R |
TMPatronLimitedProfile.html | Replace so that it works with older versions of IE that have non-standard javascript implementations. Also, revise to easier implement CASL. | R |
TMmaillist.html | The layout of the mail list page has been altered slightly as more people should be going to it based on CASL (Canadian Anti-Spam Law). The wording of mail list has been changed to use verbiage like notifications and email to try to be clearer on the purpose of this window. Also added some styles to set the width of the right and left lists to be constant. | R |
TMpasswordLimitedProfileResetEmail.html | This is a new email that will be sent when a patron creates a limited profile account. The email contains the password reset link and is designed to encourage a patron to create a password and a full account later on. Also contains any double opt-in message if one is required for belonging to a notification list. | R |
TMpatronNewEmail.html |
|
R |
TMpatronUpdateEmail.html |
|
R |
TMpatronUpdateEmailBoxOfficeOptIn.html | This is a specific version of a double opt-in email created from a mail list build or if a staff member manually adds the patron to a double opt in mail list in any way. This generates one email for each person and mail list and sends it to the patron so that they can confirm their participation in the mail list. (10.01.03) | R |
TMmaillistVerifyOptIn.html | A web page to display to the patron that they have been opt-ed in to a double verify opt in mail list. They had to sign up on the patrin add or update page to receive this email. | R |
Files in the TMtemplates directory | ||
tmNotificationHeader.html | This file is used to define the mail lists that people can add themselves to online. Thy can be auto generated for mail lists available online using the F_HTML_NOTIFICATION_LIST parameter or you can build manual checkboxes for mail lists - refer to the documentation inside the file. | R |
rowNotificationCheckbox.html | Contains the code for a standard row that is repeated for each of the checkboxes in the F_HTML_NOTIFICATION_LIST list | R | rowFutureTicketPrintCourse.html | Show the ticket number and patron number with the bar code | O |
rowFutureTicketPrintFestival.html | same as above | O |
rowFutureTicketPrintReserved.html | same as above | O |
tmnavButtonsFooter.html; | change the wording of 'mail lists' to 'email notifications' for clarity on CASL | O |
tmLoginForm.html; | Revised so that it appears on top of partial patron account creation and options reduced to simplify the screen. Required to make limited profile patrons work with this version. | R |
tmLoginLimitedPatron.html; | Revised so that it appears at the bottom of partial patron account creation and options reduced to simplify the screen. Required to make limited profile patrons work with this version. | R |
Files in the tmScripts directory | ||
disclaimer.html | Added a reference to F_CURRENT_HTML_TEMPLATE within a comment in the include file. The can be used when 'displaying source' in a browser to tell which page is loaded. example: | O |
googleheader.html | Added a template script to show how including google analytics should be done to track all web pages by name inside TM. It makes use of a the new F_HTML_MAIN_TEMPLATE variables. This gives very good granularity for google analytics. | O |
Initial support for single opt-in came on April 5, 2014 - essentially a default was changed so that patrons needed to add themselves to the 'send me emails' button. Double opt-in features were added in mid June to version 10.01 in response to inquiries and deeper understanding of the law from seminars, etc. Opinions vary whether a venues needs single opt-in or double opt in. One things is certain, double opt-in where the patron confirms that they wish to receive emails is far stronger process and help ensure accuracy of emails.
Theatre Manager now has an even easier double opt-in process based on mail lists where emails are sent automatically to patrons and mail list status codes are change to confirm the double opt in status automatically - with limited work on the part of the venue.
The initial mail list can be build on those that want to receive emails -- and then turn that into an easy double opt-in. Emails sent before the deadline are not subject to CASL and there are special exceptions for not for profits.
This release mainly applies to Canadian venues. After changing TM to meet the CASL laws, we do think that our USA Customers can benefit from this process to improve the quality of their email addresses.
Updating from version 10 means downloading and updating TM to 10.01 and ensuring changes to 2 web pages are put in place in the webPagesEN folder: tmPatronUpdateEmail.html and tmMaillistVerifyOptin.html. (any other pages changes can be made later).
Jun 15, 2015 Important security update released |
Upgrading to version 10.02 requires, at a minimum:
The following changes have been made to Theatre Manager since version 10.01
NOTE: you may see a notification on starting TM after the update that some jobs are pending. It just means that the second generation listener hasn't done them yet. If the number does not go down, let us know.
Point releases are minor version fixes and small enhancements to any particular version.
The job queue process and auto updaters rely on the second generation server already running prior to installing this version. If you do not have the web sales component, you must still have the second gen server running (with one housekeeper and no listeners), ideally on your database server. |
|
If you are installing Theatre Manager on new workstation windows vista, 7, 8, 2008 server and above, make sure to read where the serial file is placed -- it has changed. Running the TMSetup.exe will make sure its in the right place when upgrading people. |
Added ability to specify certain events in the season package as being optional online. If prices are to be changed after removal of events, you will need a plug in. (10.02.18)
The only technical situation where a venue might not want auto updating is if they are using 2003 terminal server for Theatre Manager access somewhere on their network.
NOTE: Implementing this feature for 2008 terminal server means you will need to do a download and install of the FULL TM INSTALLER on the terminal server machine to set up the revised directory structure in program files properly -- a one time thing. (10.02.01)
Please download the latest web page updates and compare the web pages to your existing pages.
The following itemizes the changes made to web pages:
In the 3rd Column are 3 flags.
Files in the main WebPagesEN directory | ||
tmError.txt | Add error message 10198 indicating that a patrons account has locked out due to too many password attempts. There is a default for this error message, so you do not need to add it unless you wish to alter the text. |
O |
TMpatronLimitedProfile.html | Added some clarification and a little reorganization to the 3 options available to the patron. The functionality did not change, just visual layout was improved. | O |
Files in the main tmTemplates directory | ||
tmLoginLimitedPatron.html | Removed some instructions that were put into the TMPatronLimitedProfile.html web page | O |
rowCartSubCustomNewGroup.html | Used for subscriptions if optional events are enabled (V10.02.18) | M |
rowCartSubCustom.html | Used for subscriptions if optional events are enabled (V10.02.18) | M |
Jun 15, 2015 Important security update released |
The following changes have been made to Theatre Manager since version 10.02
However, two key tasks should be done during the upgrade process to add support for pick your seat, otherwise the feature will not be available. These, and the order in which they should occur, are:
Browsers and platforms that they have been tested on are:
Point releases are minor version fixes and small enhancements to any particular version.
The key new feature in this version is select your own seats.
Select your own seats allows patrons to click on specific seats on a map online after an initial set of best seats has been selected by Theatre Manager. The process is designed for speed and flexibility for varying degrees of sales volumes. When the sales volume exceeds hundreds of sales per minute, obtaining seats through a pick-first process would be extremely difficult (can't click fast enough). Refer to What the Patron Sees for more detail.
Enabling it can take as little as a few seconds if you have the original venue map file (.PPT format). The general steps are:
The feature allows a venue to decide which venues or performances can be used with the pick your own feature. Both pick your own and 'find best seats' are available to the patron online so that they can use either at any time.
Pick your own is designed for modern browsers: IE9 and up, Safari, Chrome, Opera, Firefox running on Windows, OSX, IOS and Android. The few remaining users of IE 8 and earlier represent less than 4% of the marketplace. They:
|
Upgrading to version 10.03 requires, at a minimum:
Please download the latest web page updates and compare the web pages to your existing pages.
The following itemizes the changes made to web pages:
In the 3rd Column are 3 flags.
In this release, every single web page has been changed - many are simply formatting changes to set the html tags to be lower case as per HTML5 requirements. If you have been using the tmCustom folder to track your custom changes, then you should simple replace all files and folders in the WebPagesEN folder (except tmCustom) and do a page comparison of WebPagesEN with your tmCustom folder for those that have changed.
The list below only highlights the minimum key pages that have changed and provide support for the pick your own seats. If you do not change them, web pages will probably work as they did, but:
There are no changes in tmGifs folder |
Files in the main WebPagesENdirectory | ||
tmError.txt | There are two new messages required for pick-your-seat. If you do not add the messages to this file, you will get the default provided by the second generation listener. | O |
Files in the main WebPagesEN/tmMaps directory | ||
tmTicketsSection_MapDefault.html | Visually, there is no change to this page, only a single parameter change under the hood.
The <img> tag that shows the map for the venue has some new parameters. A key one is the format=svg added to the end of the link. This will cause the map to be derived from the svg graphic you create as part of the conversion by the second gen listener. If you do not create an SVG graphic, the fallback is that the second gen listener will get the classic listener to draw the map the old way. (note: if the second gen listener does the map, the classic listener is one step closer to retirement). The recommendation is to create the svg map in the venue - which allows the second generation listener do maps from this point on. |
O |
tmTicketsPrice_MapDefault.html | This web page is the one that has all the code for pick-your seat. There is a small re-arrangement of the words to separate between the offered seats and the function of changing seats. It is best to compare this page if you have changed it, or get some help from the support team.
To make it easy to implement best seats, this page includes 3 other files in key spots, the purpose of which are also explained:
|
O |
tmPickYourSeatButtons.html | This page has instructions to the patron about the pick your own seats function. This one has minimal wording which we hope is clear. There is an alternate version called 'tmPickYourSeatButtonsWordy.html that has more words if that suits your patrons better. You can use or edit either one. | O |
tmPickYourSeatMapDisplay.html | This contains the actual map display, along with the buttons to scroll the map left, right, up and down. The movement buttons do not appear on an iPad and other mobile devices because the act of moving/swiping/pinching causes the map to grow and shrink. | O |
tmPickYourSeatScripts.html | This file contains some key linkages to make pick your own work - do not change this file. | O |
Jun 15, 2015 Important security update released |
The following changes have been made to Theatre Manager since version 10.03
Point releases are minor version fixes and small enhancements to any particular version.
There have been some changes to personnel window:
The upper tabs offer more information:
The bottom part of the window now has 4 tabs
This means, for personnel management, there are quite a number of fields available for tracking status and activities:
The record locking processes in ticket sales have been revised to remove database level contention for subscriptions and regular ticket sales. For many years, the manner in which TM updates summary statistics was to do it at the same time of the ticket sale. This could cause deadlock (two people trying to update the same record) under conditions of higher than normal single tickets sales or when two people tried to sell a subscription at exactly the same time. The updating of statistics has been delayed in a separate transaction by micro seconds - freeing the actual ticket sale to occur much quicker and with less database i/o. Anybody with onsales or using subscriptions are encouraged to upgrade.
Upgrading to version 10.04 requires, at a minimum:
Please download the latest web page updates and compare the web pages to your existing pages.
The following itemizes the changes made to web pages:
In the 3rd Column are 3 flags.
No web pages have been changed for version 10.04 - only changes to tmError.txt. If you are using 10.03 web pages, things will run without altering web pages at all. |
Files in the main WebPagesEN directory | ||
tmError.txt | There are some new messages that are used by the second gen listener for the checkout pages. If you do not add the messages to this file, you will get the default provided by the second generation listener. | O |
Jun 15, 2015 Important security update released |
The following changes have been made to Theatre Manager since version 10.04
Responsive pages enable your web site work on any device and at almost any resolution. Sample pages can be viewed at artsman test site or at a couple of venues Utah Shakespeare Festival or Theatre Orangeville. For those wishing to download and play with the responsive pages themselves, the notion is that there should be very few pages changed and probably only:
Point releases are minor version fixes and small enhancements to any particular version.
You may wish to download the latest web page updates and compare the web pages to your existing pages.
The following Web Page changes are available for Version 10.05.11 or later -- and are only if you want to allow customers to print tickets to PDF documents. If are using 10.03 or 10.04 web pages, this version will run without altering web pages at all (unless you want the feature). |
The following itemizes the changes made to web pages:
In the 3rd Column are 3 flags.
Files in the main WebPagesEN directory | ||
tmError.txt | Add error message 10269 indicating that the web server was unable to generate a PDF ticket. | O |
TMfutureTickets.html | Add a button to give the user the option of sending tickets to PDF instead of printing. It is beside the option to print the tickets as web pages to printer. | O |
TMfutureTicketsPDF.html | Page header for printing future tickets. It includes the base style sheet (removing all css) so that print at home tickets should print. Print at home tickets must be generally plain HTML based documents - complicated CSS affects the rendering for sending to PDF. | O |
TMcheckoutInvoiceEmail.html | Add download tickets to PDF -and- print tickets to the emailed confirmation page - to make it easier for patrons to get tickets again | O |
TMoldCartDetails.html | Add download tickets to PDF -and- print tickets when viewing an older cart - to make it easier for patrons to get tickets again for that cart. | O |
Files in the main tmTemplates directory | ||
tmCheckoutConfirmationDelivery.html | Add button to send completed cart to PDF | O |
rowFutureTicketPrintHeader.html | Add button to print events for current performance to PDF | O |
rowFutureTicketPDFCourse.html | Layout for a PDF ticket to a course - so it can be different from the print to html ticket | O |
rowFutureTicketPDFFestival.html | Layout for a PDF ticket to a general admission event - so it can be different from the print to html ticket | O |
rowFutureTicketPDFReserved.html | Layout for a PDF ticket to a reserved seating event - so it can be different from the print to html ticket | O |
rowFutureTicketPDFHeader.html | template to handle the tickets printed as PDF | O |
Files in the main tmGifs directory | ||
stylePDF.css | Style sheet used only for print to PDF ticket printing generally recommended to not change this | O |
Files in the main tmScripts directory | ||
PDFstyles.html | Include files for getting styles sheets (stylePDF.css) included in the print at home pages TMfutureTIcketsPDF.html.. This style sheet is only used when printing tickets to PDF and cannot contain complex styles, otherwise your print to PDF will not work. We suggest not changing this file - and using only the styles in it. | O |
The responsive web pages are available free to all venues. If you would like to try them out on our test web site, click this link for www2.artsman.com
A number of venues are already using them. If you would like assistance implementing them, please contact support@artsman.com. You need to be using Theatre Manager 10.05 or later and we can help you update if need be. These are now the preferred pages - but you can continue to use the old ones, if you want.
Jun 15, 2015 An update was released that all venues should installed immediately. Venues that auto-update already have the change in place. |
A way was found to show the name and address of a random patron who was not in your household via the account tab in web sales. No other data could ever be displayed (passwords and PCI information were never at risk). The worst possible outcome is that somebody, if they knew about the issue, could look up a name that they could find in the phonebook.
The issue was identified on Monday morning and a fix was auto-deployed by late afternoon the same day. Versions affected were TM 10.02, 10.03, 10.04, and 10.05 and a separate patch was issued for each version.
At this time there are no known compatibility issues. However, it you wish to install El Capitan at your venue, we advise doing it to only ONE machine to start with and use it for a few days to find out if you have compatibility problems with other applications used in conjunction with Theatre Manager. We cannot say for sure if all your other important applications work, so best approach is one machine at a time.
Please do not update the postgres, apache, or second generation listeners servers at this time. Those servers also work with El Capitan - but save those for a couple of weeks.
Watch our release notes and shortly. We have a sample site with responsive pages, with many thanks and contributions from some of our customers. They are being prepared for release to make it easy to update your pages if you want them -- or you can keep using your current pages if you prefer.
If you should have any questions or need assistance installing the latest version, please feel free to contact us -- happy to do it for you.
Version 10.06 is the first major release in over a year and a half. Upgrading Theatre Manager may simply require installing the latest version - or a bit more. Refer to the update options. Depending on your circumstances, you may need to do one or more of:
|
|
The conversion of timestamp data to be timezone aware could take a significant time and is dependent on the number of tickets and eblasts in the database. Most venues will update relatively quickly. Allow about an hour for the actual TM upgrade to run before web sales can come back online -- if you have a larger database. |
The following changes have been made to Theatre Manager since version 10.05
This includes:
A few TM venues use this tool, so we decided to integrate the process of accessing the wealth data. Using Donor Search requires the venue to have an account with Donor Search -- The Theatre Manager component is to enhance that capability. |
Point releases are minor version fixes and small enhancements to any particular version.
There are some key things to know about this version:
Refer to the full release notes and installation instructions for more information
Revert Theatre Manager back to version 10.06.106 due to an issue at some venues with timezone on web listeners. This was causing cookies to be rejected due to age
A use of this could be to sell a membership or pass that provides people advance access or discounts on tickets. If the mail list gets added to a patron, then there could be some coupon that is auto added to a patrons' cart based on a mail list.
Now fixed: an issue was introduced in version 10.06.90 on the patron window - if no tickets were selected, the 'tickets button would not work. (workaround was to use the orders tab).
Added a feature to show tickets held specifically for a patron in the patron's ticket list window. You will be able to see both tickets manually held for the patron and those automatically held for web sales.
Any tickets held for the patron appear with:
You can now select the manually held tickets and buy them - which opens up an order window with the specific events selected. You can also quickly release them.
Note: Tickets put on hold by web sales cannot be purchased from the ticket list, you must go through the cart window and take over the entire cart, if the cart is still active. If the cart is not active, you will need to wait till the tickets are released.
Simply seeing web held tickets in this window serves as a convenient reminder while talking to the patron that they are currently or were recently online.
Other features added:
Add restrictions about viewing .DS_Store files if the TM Server is on Mac. It involved a change to the nginx.conf file and is designed to help those sites pass PCI scans. The .DS_Store files are considered security risk on a web server. This does not affect those still using apache.
Introduced a significant meeting management enhancement to the TM Server for facility management. Now both outgoing meeting emails and incoming meeting responses are handled by the TM server. You no longer need to manually retrieve responses from patrons or staff by logging into TM. They will automatically update the meeting in the database in the background, 24 hours a day and let you know with notifications when you are in TM. Read here for setup of scheduling email/pop server.
In addition the ICS file was enhanced to be more compatible with recent standards, so it should work with more places. We have tested with iCal, Daylite, Google Calendar and iPhone/iPad.
Note: if emailing PDF tickets causes Theatre Manager to stop, please re-install Theatre Manager - it will fix it. |
<input class="form-control" id="C_BIRTHDAY" name="C_BIRTHDAY" placeholder="yyyy-mm-dd" type="date" value="
Also, if you meet a number of prerequisites, you may be able to take the fast track which only needs Theatre Manager installed on each workstation, resulting in a 10-20 minute update process.
If you meet all of the following pre-requisites, you can take the fast track/easy path on the right of the diagram.
In general, you should be able to install V10.06 on top of 10.05, 10.04 or 10.03 and it should work with your current web pages.
Always test a complete web sale and checkout after an update. |
The last major update was 18 months ago. There may be additional steps required if a simple update cannot be done. You many need to do one or more of the following:
Upgrading Postgres |
If you are using Postgres 9.3.8 or earlier, or 9.4.3 or earlier, then you must update the postgres database server. If you are at more recent versions (but not the latest) you can skip this step, or update if you wish. You will need to:
| ||
Upgrade Theatre Manager |
After the database sever is updated (if needed) follow the standard instructions to download and install Theatre Manager. Upgrading Theatre Manager automatically upgrades web services.
Optionally, you can install the following version 10.05 at any time on all workstations PRIOR to updating to version 10.06. They contain all the latest components that version 10.06 requires. If you do this, then Version 10.06 becomes a push out install for the machines where you physically ran the installers below. |
||
Upgrade Web Services |
Since the Theatre Manager server is paused, then automatically updates itself after updating Theatre Manager at a workstation, most upgrades can skip this step. However, there is one significant change for those venues running multiple outlets. If you have multiple outlets, you will need to:
|
||
Updating Web Pages |
Most venues have already updated to the responsive web pages. There are sufficient benefits in using the responsive pages such as:
Updating pages is a matter of:
|
Theatre Manager is fully 64 bit as of September 15, 2019.
The current version of TM runs on:
|
Theatre Manager will auto update most processes automatically via the TM Director. Example:
The above process are able to replace themselves very quickly with a newer version and keep on running, providing more or less an un-interrupted service to your patrons.
The postgres database server is the only component of Theatre Manager that does not auto-update - simply because the database server itself does not need to be updated as often, and if it is - it needs to be a planned outage.
Miscellaneous
Price = base price - discount + markup + fees + taxes
And for clarity, the price of the ticket has not changed, only that the reports now display a markup as a positive value in its own column, not as a negative discount in the original column.
Miscellaneous
Subscriptions
Miscellaneous
Miscellaneous
UTM Tags
UTM parameters (also called UTM codes or tags) are snippets of text you can add to the end of a URL. These snippets help you track where website traffic comes from. So if a user clicks on a URL from Facebook and lands on your landing page, you’ll be able to determine the source of the click, which in this case is Facebook. If most of the traffic came from Facebook, you’d know that you were doing something right with your Facebook strategy. These insights can be accessed in your Google Analytics account and can be searched within Theatre Manager.
Miscellaneous
Miscellaneous fixes
Report Search Criteria Changes
Facility Changes
Under the hood changes to enable new cosmetic options in Theatre Manager to allow various styled field types.
If somebody is unsubscribed, they can be resubscribed so you know how long they have been on the mail list. This also lets you find people who bought certain types of tickets or gave donations and said they didn't want to hear from you -- you might be able to touch based with them one more time to get them to change their mind.
The point if this feature is to 'retain' the knowledge that they were once on the list.
Also, remove most of the mail-chimp conditional html for the plain text version of the email to make it more readable on some older email clients.
For example, if somebody was to type card number into an order note for later use, it should not be there and instead, it should be set up as a post dated payment.
An adjustment to sending the Country Code in with authorizations where the merchant account is set up for AVS. This is in response to a changed behavior with Worldline's authorization API. If your merchant account was set to use AVS previously, you can now re-enable that feature in Theatre Manager's merchant account setup.
An adjustment to set each merchant account's credit card batch settlements into their own respective deposit. This affects those clients who have more than 1 merchant account accepting credit cards.
Theatre Manager will compress all data for sent letters/emails.
Theatre Manager will no longer indicate the database size comparison to the previous backup during the login process.
The credit card industry has alerted merchant providers and software providers that unscrupulous people are testing stolen credit cards using various online systems in an attempt to validate card data.
Add a feature to show a log containing a patron's forgotten password behaviour. This indicates when the patron might have asked for a password reset, created a patron record online, logged in, completed a shopping cart or received a confirmation email, as well as indicating if we know the patron read and emails, or made mistakes changing their password. This feature can be accessed from:
Documents and Reports have a couple of new features. They can be:
All attachments to tasks are marked permanent (This cannot be changed). Reports added to the report queue can be marked permanent as they are requested or after the report is run, which could be useful for those audit reports you wish to keep for year end.
This means that the document or queued report
reCAPTCHA uses an advanced risk analysis engine and adaptive challenges to keep malicious software from engaging in abusive activities on your website. Meanwhile, legitimate users will be able to login, make purchases, view pages, or create accounts and fake users will be blocked. Detail: https://developers.google.com/search/blog/2018/10/introducing-recaptcha-v3-new-way-to
It requires that you sign up for it and put your client and server key into company preferences. You can sign your domain up here: Google Admin Console
The purpose of the feature is prevent bad guys trying cards against your web site for low amounts to determine if the cart is valid or not.
have been ehanced with 6 more statistical columns containing
When this occurs, you willl need to ask the patron for their credit card and manually enter it into the recurring donation setup.
An example might be building list of donors having total donations > $xxxx in each of the past 5 years - the mail list needs 5 criteria groups to accomplish the task.
Numerous changes to enable access to donation receipts that where emailed by Theatre Manager automatically (as part of a confirmation) as a result of a donation on the web site.
This should help locate those ACTIVE coupons, pre-access codes, subscriptions, passes & gift certificates, etc that refer to the event in case you want to disable something. Only active items are shown since inactive do not affect any sales processes.
The shopping cart web page change means any venue that has over ridden the web pages in TMTemplates that start with rowcart... may need to merge in the current web page changes to add the remove button to that line item in the shopping cart. |
This slight change of process brings TM cart page more in line with other web shopping carts that allow removal of each item in the cart with a single click.
It will mean that if your venue sells combo subscriptions into one order, you may need to verify the subscriptions for your current season using the criteria to the right (once) if you use the above report.
This version contains a Beta online forms - with the ability to:
When the field is shown in the list, this may help highlight patrons with duplicate email addresses where the duplicated email address is one of the secondary emails (not the primary one).
We suggest bookmarking the status page in your browser
Some notes on this feature:
Note, for performances that are in the list:
Add Terms and Conditions and Covid 19 policy text boxes to Web Options - Carts and Checkout in company preferences window. This makes it easy to enable accepting covid 19 policies on checkout and track that people acknowledged them.
Note: you may need to verify your restricted donation campaigns to make sure they are ok. If one needs fixed, the rest will likely be ok.
These can be used to find any data connected to orders where the order might contain a donation campaign, specific event, pass/GC, payment method etc. While you could use it for any report containing orders, it might make sense for:
Merging two full profile patrons together will merge those flags as before.
Some enhancements in this and future updates depend on the latest walk-around version of TM being on your computer. You may receive:
|
|
There is a one-time conversion of report parameters that the first user that logs in will encounter. It may take a few minutes or so, depending on the number of criteria that have been saved. |
This version of Theatre Manager introduces tracking online unsubscribes to mail lists. Previously, if a person unsubscribed to a mail list online, they would be removed from the mail list. Now, their mail list record will be marked with a date that they unsubscribed. If they re-subscribe, that date will be cleared. There are a number of ramifications:
While picking people that belong to a mail list will never pick unsubscribed people, you may want to start building lists of people who explicitly indicate not to email them for some purposes. In such a case you might want to use criteria belongs to mail list - unsubscribed from IS NONE OF and the name(s) of the unsubscribed lists.
Note: there has been a significant change in donation receipt type options.
All tax receipt types that previously indicated a receipt was only needed 'when fully paid' have been converted to 'Annual Statement Style'. This clarifies receipt printing so that none get missed for recurring donations and post dated payments when those payments happen to cross the calendar year - in other words it ensures that everything paid during the calendar year gets receipted in the same calendar year. |
|
A default receipt option has been added to each campaign. This defaults to the default receipt option in company preferences (which has been removed, in favour of a unique option for each campaign).
A context menu allows you to set the default receipt option for a number of campaigns at one time on the campaign list. |
|
Tax receipt report is limited to 250 record for one receipt per payment and 500 records for annual tax receipts. This is a limit imposed to prevent receipt report running out of memory and to match the size of a ream of paper. |
If there are issues connecting and you get a TLS error, the steps to resolve are:
If you want to see the data again, click the search button for the window and the data will reappear.
This means that live events support:
At this time, there are no other known issues with Theatre Manager and Big Sur. As a pragmatic approach, we always suggest updating one machine to apple's latest operating system when you are ready and ensuring that all the programs you use (Theatre Manager, Excel, Word, HTML editors, etc) work before upgrading all your computers.
A number of changes have been made to add support for deferred revenues for projects. The significant changes are:
|
In addition, the default holds are often the default Return to Hold seats for each performance. If they are not normally sold, then we can leave them out of the social distance associated seats.
If you decide to use entry zones, you will need to update your ticket face to include the entry zone field under theatre/venue information somewhere on your ticket.
Note: There is one discrepancy when viewing background reports on MacOS - some fonts are not displayed properly, and as a result, print to PDF directly does not work.
The work around is to print the report and when asked about printer, save as PDF. |
Theatre Manager will download the update for the user automatically and all they need to do is click the Update TM button on a subsequent login.
During a full install you may need to:
|
For best results selling donations
|
Introduces a very small enhancement to linked refunds within a household. If the order (containing the original credit card payment):
The fix is to lengthen the number of days in the past to allow linked refunds in merchant setup.
For best results selling gift certificate and passes:
|
so that:
eg: When a patron uses a coupon code that causes a sales promotion to be changed (through a sales rule), implement an additional check to make sure the sales promotion cannot be over used on a per performance basis. Eg, if they venue allows 10% off coupon and the 10% off sales rule only allows a max of 15 tickets per performance, Theatre Manager will allow the entry of the coupon (since another mapping might be allowed) but not discount a ticket to the performance if there are no more permissible uses of that one promotion.
Most venues are using 64 bit and have been for a having converted sometime during transition period over the past year. Thank you to all who have done so. There are a few workstations till running 32 bit which will see a more insistent message that Sept 15, 2019 is the final date that 32 bit will be supported.
After Sept 15, 2019, if you are still using 32 bit theatre manager, it will still continue to work for the foreseeable future. Apple released Catalina (OSX 10.15) in Oct 2019 and no longer supports any 32 bit application (after a 15 year transition) We suggest updating to High Sierra or Mojave before the release date if you still need to run 32 bit.
What the Sept 15, 2019 release date signifies is that all new features will be placed into the 64 bit version of TM and they may note be able to be carried back to the 32 bit version due to technology limitations. We'll do our best to make sure that 32 bit still runs, but there will be no big fixes or guarantees.
The VIP list alert that pops up when opening a patron (if the patron is on a VIP mail list) has been modified slightly to respect the access groups set the mail list. In other words, if an employee is not allowed to see the mail list due to access restrictions, they will not get a alert when opening the patron that the patron is on that list they cannot see.
Added some standard glossary shortcuts that can be used in almost any field. These are in addition to personal ones in your own glossary of shortcuts. Shortcuts are very useful when you need to type the same type of phrase repeatedly in fields like patron notes or report cards and save time:
The fields include:
Attention all Authorize.net users
Authorize.net recently changed their policy on credit card refunds and will now only refund if:
|
NOTE: The performance improvement is currently OFF by default so that maps should behave as they did before. If you wish to try this feature:
The problem was insufficient width at the bottom to show all buttons and the search fields. The fix was to remove text from the buttons to give more space (use the tooltips if see what the buttons will do, or use the context menu as an alternative)
NOTE: printer preferences MOVED in this version into Setup->Hardware Preferences |
https://tickets.artsman.com/TheatreManager/1/online?bestavail=314&qty=0
If you prefer pick your seat functionality directly from the event list for all events, simply edit the link in rowTicketEventBuyButton.html
This avoids an issue where TM could have blacklisted shredded cards with the same first 4 and last 4 digits of a card number (since we don't know what the middle numbers are -- it is impossible to match with other patrons).
Merchant Profiles for patrons are managed by your service provider on your behalf and can be revoked should the patron's credit card get compromised, making them far safer since they are specific to your merchant account, your patron, and a specific credit card for them. They cannot be used by anybody other than you (so can't be stolen and be effective).
Note: Merchant profiles for Bambora require 64 bit theatre manager for implementation and is not possible until the 64 bit migration is complete. (approx may 2019) | |
Note: Some Service Providers may charge for using merchant profiles and it may be a feature you need to enable for your online portal - please be sure to contact them before attempting to use this feature. |
This should make it quick to align the seats and the background as you convert to 64 bit Theatre Manager. Once you've done the map on one computer, it is good for all machines.
If this describes your venue, set aside the last backup you have prior to August 8th, 8:00am eastern time (Monday morning. We will recover those past cards as time permits and wish us to do so.
Effectively, the main effect is that refunding to a credit card on file - will need you to ask the patron for the card to proceed. |
Currently there is only a Mac 64 bit version as well as the current 32 bit mac and windows versions. A windows 64 bit version is expected soon
If backup directory is configured in TM server, you can also:
Add security level access to:
Web Sales
Permission to manage an event online is occurs when three things are true:
The current version of Theatre Manager does not consider it mandatory. However, subsequent versions of Theatre Manager may rely on any new features.
This will require that you:
Note that the same update may be required on other workstations if the users receive the same message. They can use the same installer that you downloaded.
There are two ways to address this issue.
While the message says to try re-installing the program, the real issue is that some essential windows updates have not been installed.
We have encountered this on some Windows 8.1 installations that have never been updated. After running and installing all windows updates, TM was able to run.
You can revert back to 32 bit Theatre Manager by downloading it per these instructions if you have insufficient time to run windows updates. |
If you encounter this issue then you may need to cause existing TheatreManager preference directories under each user profile to be cleaned up before using Theatre Manager.
For venues using authorize.net, the issues authorizing cards was caused by authorize.net making production server changes and eliminating an important bit of deader information in the credit card authorization response send back to Theatre Manager. As noted in the developer comments for the day, they removed an important bit of information - the 'content-length' header which contains the size of the message being returned. This is a very important part of all https requests - and was restored towards the end of the day.
If you use authorize.net and Theatre Manager 10.05.xx, you may be running into issues authorizing and/or settling your credit card batches. Authorize.net indicated they would throw the switch to require TLS 1.2 sometime after they sent a warning letter to merchants in September 2015. In that letter, Authorize.net said they would follow the PCI council mandate for TLS 1.2 before June 2016.
Well, April 4th, 2016 is as good a day as any. We've had a few venues (using TM 10.05.xx) tell us that Authorize.net does not like the settlement message we've been sending for years while others (using 10.06.xx) are working fine. The conclusion is that authorize.net threw the switch to require TLS 1.2
What is TLS 1.2 anyway?
It is simply a more secure encryption mechanism compared to TLS 1.1 or earlier (which have been cryptographically compromised).
How to I solve the problem?
Theatre Manager has supported TLS 1.2 for months. If you are still using TM 10.05, you may need to download the installer (below) and put it on ALL workstations and ALL Theatre Manager Server machines (or you could update to TM 10.06). If you are using Theatre Manager 10.06, you are ok (it has been available since Oct 2016)
If you are using version 10.05.45 (and do not want to update to 10.06 yet), please re-install version 10.05.45 using the links below.
This currently only affects venues with Theatre Manager version 10.05 using authorize.net for merchant services. We suspect Orbital, Bambora, Moneris and Elavon will follow very soon because it is a forthcoming PCI requirement. | |
There is a potential catch 22 if you are on a Mac using OSX 10.08 and earlier. Safari on those versions of OSX do not support TLS1.2 to connect to our web site (we have to be PCI compliant too). Instead, use Chrome or Firefox if you need to. |
In Theatre Manager (version 10.07.10 and later), all venues using Orbital will automatically be converted to the new URL's per Chase Paymentech's note. They informed us that, as of end of May 2017, all merchants authorizing credit cards with Orbital must be using TLS 1.2 for security and the new URL's only accept this high level of encryption.
If you use Orbital and have any issues authorizing credit cards, let us know and/or try the following.
Until mid May, 2017, you can revert the URL's by going into your merchant account setup for orbital and changing:
OR address the issue permanently by:
|
NOTE: anybody using version 10.06.xx or earlier and Orbital for merchant services, will need to upgrade ASAP - otherwise Orbital's servers will stop accepting your payments. |
Since Authorize.net is NOT changing any of the authorization URL's (according to the tech note), this change does not affect any settings inside Theatre Manager in any way.
However you will need contact your IT staff to update your firewall to the new IP addresses specified in the tech note if your IT staff have programmed your firewalls to restrict outgoing access to Authorize.net's old IP addresses..
Most venues have not done this, but for the few that have, the key dates are:
|
In their own release own notes they indicate known problems that affect Exchange server (among other things) on all their operating systems and we have currently found that it also affects TM Server running on Win 7 and 2008R2 server operating systems as follows:
If web sales are not working, restart the machine. Web sales will run for about 12 hours before windows again starts to misbehave. Please turn off auto-updates.
We will happily reinstall the TM Server on a machine, if your prepare the machine as follows:
Arts Management investigated this vulnerability as soon as it was announced and there is nothing in our software solution that we supply to our venues that uses log4j.
For further reference, the NIST description of the log4j vulnerability
For those on AMS Cloud, our intrusion detection tools provide additional mitigation against this vulnerability as a precursor to all theatre manager server processes (which, as mentioned, don't use java and are not vulnerable). This provides multiple layers of protection to your data.
Self hosted venues should not be affected, especially if they have not installed any other server processes that run Java.
Apple is very strict that applications must be signed or they wont run. Quite inadvertently (and accidentally), our existing digital deployment certificate was revoked late in the evening of November 4th. Consequently:
If you run into the issue where Theatre Manager will not start and Apple says its not trustworthy, you will need to:
We apologize for any inconvenience this may have caused.
If you already have a relatively recent 64 bit operating system on your computer, you will likely have to do two things:
You may need to update your operating system.
Please be sure to read the latest release notes for any additional or late breaking information.
If you receive this message when running Theatre Manager, please
If you receive this message when running Theatre Manager, please
See the other power saving and setup procedures for OSX |
The current version of TM runs on:
|
Theatre Manager Version 11 is the official release incorporating PCI PA/DSS 3.21 certification. Visa/Mastercard requires periodic certification of software that processes credit cards to ensure that the software observes their strict controls and recommendations.
Arts Management Systems has enthusiastically participated in the PCI process since 2000. The Visa/Mastercard audit process requires defining the technical requirements for the version and testing many combinations. |
For Theatre Manager version 11, the technology audited in the PCI certification process is below. If earlier versions work, they are noted in parenthesis.
Postgres |
Postgres 11 or later.
Any version of PostgreSQL you are currently using will still work (Postgres 9.6 or later). |
Macintosh |
Workstation, TM Server or Database Server:
|
Windows |
Workstation, TM Server or Database Server:
|
Linux |
Database or TM Server:
|
Merchant Providers | Certified and tested against direct processors such as Paymentech Orbital, Worldline, Moneris, Elavon and Authorize.net |
You can review recent version 10 change history if you wish.