This update responds to a small number of specialty requests or problems reported recently.

• Allow the sell window buttons to be visible without having access to the patron window as well
• Added a new security case for the order window. This will allow restriction of employee permissions so that they can sell items in an order, but not edit or view patrons.
• Adding a New subscription via the Order Window or Client Window fixed
  • When clicking "New" via the Patron or Order window's subscription tab, you will be prompted with the 'Which package' messages, but following those messages the new package will be opened, where-as in the past it was just added to the list
  • Fixed an issue where the book button was not enabled after adding seats to a new package from the package detail window.
  • The Book button is now enabled on the package detail window when creating a new subscription from the Order window, when pressed it will call the booking routine from the order window and close the package detail window.
  • Prevent an infinite loop when booking subscriptions that resulted in a message, "Too many methods or attributes stacked"
• Receivables As Of Specific Date Report Could Create Incorrect Donation Balances. Fixed issue where the Receivables As Of Specific Date Report could create incorrect donation balances in specific cases of split payments.
• Fixed issue where the Transaction History - By Sales Promotion Group (Totals Only) report would not print.
• Fixed issue where the hold count could not be set from the performance detail window for a course performance.
• Fixed Volunteer Hours By Performance Type report to display precision in 2 decimal places instead of 1.
• Fixed issue when printing the Course Attendance Sheet report to a PDF with the narrow columns option; the text would appear incorrectly and have extra characters.

Other items requiring an install

The following fixes are currently optional and can only be fixed by a full install of Theatre Manager on any affected workstation.

• Fix an issue that might cause intermittent or random crash when saving an empty text string to the database during the edit of a record.
• Opening a calendar may cause a random crash after running Theatre Manager for a while
• Printing a PDF from a report with rotated vertical text on it will now function properly without overlaying the text.

This update responds to a small number of specialty requests or problems reported recently.

• The web listener now requires that the apache module be either version 1.2.9 or 1.4.4 before it will start. (Versions 1.4.2 or 1.4.3 of the apache module may cause the actual apache server to restart under load).
• The web listener now filters out a 00x characters on the web if the patron entered specific hexadecimal characters in character input fields. Specifically, a user needed to enter '0%a' in a text field. If they did this, it may cause an infinite loop on the specific web listener that handled the request.
• The code for checking for all double clicks on any list in any window has been changed to avoid using timers. Under certain circumstances, it might be possible for TM to crash if there was a lot of activity on the network.
• There are some updates to the word processor module to address various small issues. Examples are colours on grids, copy/paste of grid objects, the mouse wheel did not always work on all windows, searching text in an entire document and the current selection is inside a text box, prevention of the tab key from deleting an image in a cell when tabbing from cell to cell.
• Printing reports to a PDF would over-write text if the text on the report was vertical. This addresses that issue on one report
• Merging of donation campaigns now works correctly and no longer gives an SQL error at the end of the merge process.
• Update lock process for selling tickets by holding on to locks for a slightly longer time
• Add a small feature to the subscription detail window to allow performance to be changed as many times as desired between saves if there are no favourite seats.
• Fix an issue of batch printing passes and gift certificates.

Note: this update must be installed on each computer. You will also need to update the apache module if it is version 1.4.2 or 1.4.3 in order to start the listener after the upgrade.

This is release is recommended for all venues to install as it addresses somewhat rare conditions in a number of areas: Specific fixes are:

• Fix two issues that were causing EOD imbalance. First was that fees could be added to an order where the GL# was still zero. This could happen if the venur was using a database built from the empty database. Solution: don't show fees on the window if there is no G/L code
• Second issue is that if those fees got in a transaction, they would leave the EOD out of balance. The posting routines were changed to allow a zero GL account and create the description. This operates more like verison 6 and causes documentation of the error. It could catch other possible similar EOD issues from tickets, etc.
• Split the fee postings in to fee sales and fee refunds so it is easier to balance to transactions.
• Optimize the G/L transaction debug rpeort to only look at valid transactions. It now counts POT,POF,PTT,PTF in the transaction counts so that we can match to the GL journal entry... which now counts all tranasctions attached to it. Doing an order transfer meant that the POT would get the same deposit number as the original payment... and thats ok.. it just needed to be counted in the report.
• Allow duplicating of events and at the same time, create price codes, promotion settings and other parameters that are the same as the original event.
• When building a performance, and add some special error checking to prevent some not-so-right situations when duplicating courses
• Fixed an important issue where reserving a ticket was placing a lock on a ticket. If the user continued and added the ticket to the order, then all was ok. However, if the user released all tickets in a current cart, it could leave some advisory locks in place on the ticket - that would only be released when the employee quit TM. Some venues were getting messages that tickets could not be booked when the tickets were available
• The check ticket-transaction report performance has been vastly improved
• The 'current' column in the 30/60/90 dat A/R report now calculates correctly. Previously, anything in the current column was being placed in the 90+ column incorrectly.
• Added a number of checks on parameters for the web sales module to further limit possibility of cross-site script injection.
• Fix error where patrons to whom you own money now show up in blue on any list. Previously, they also showed up in red
• Fix a small issue in the event window so that it shows up the cash flow and transaction totals properly in the G/L tab when only comps have been sold to an event.
• Enhance the security setting for the sell process so that there are separate settings for patron information and order information. Previously, TM assumed you needed to be able to edit patrons in order to sell. This is no longer the case

This version of Theatre Manager addresses a possible memory issue.

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.