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:
|