Pre-Beta 6 Released to Donators

31 January 2010

The latest version of Fusion Ticket, beta 6, was emailed to the Donators today.

If you are a Donator and did not receive your copy please contact us on the forum or at the IRC channel.

The Fusion Ticket Team

 Some of the highlights of this release are:

• A new email engine that is more stable than the current one. Also it gives extra information about the results of sending emails. The good news is that without any changes the old templates still work
• All tables now use the InnoDB MySQL engine, so we can use transactions, and the possibility to setup FOREIGN KEYS to avoid deleting a record that links to another record.
• We have rewritten most of classes which are used to communicate between the database and other parts of fusion ticket.
• We have added logging programs to help you see what is going on within your system, like an email-log, an order-log, and some debugging trace log's that can help us find many of the problems.
• In the past we found that some servers changed the file names to lower case when those files where copied to the server. We have changed all file names to lowercase.
• Consolidated admin, pos, and control images to the root image directory.
• Can no longer add Discounts, Categories, or Zones after an event is published for the first time.
• Changed navigation links to buttons for ease of use.
• Category size for numbered seats is now computed by the program which eliminates cat errors when publishing.
• Program no longer allows duplicate template names.
• Fixed captcha error in registration.
• Discounts in main events are automatically transferred to sub events.
• In previous versions whenever an order was reused (= now reissued), or changed from reservation to ordered, there was a new order created, this is now changed.
An order will keep its Order Id for the life of the order.
• New Utilities tab which includes: Orphans, Garbage, Email Log, and DB Backup.
• New tabs in Order Overview: Tickets, User, Status log, Notes
• Added a “custom” folder for Pos templates.
This folder, like the one in the web shop, can be used to make changes to the default templates. This will make it easier to update your site to a new version.
• System managers can now be activated or deactivated. This avoids deleting a manager you may use in the future. It also sets up the possibility of grouping managers in future versions.