Webtix 5 changelog

(Last Updated On: March 15, 2021)

December 8, 2006 (Friday)
Attached is the latest centerstage ticketing software in ZIP format. This version fixes a bug just found regarding surcharge calculations while in shopping cart mode.
It currently runs on PHP 5.1.0 or higher with working PDF and barcode on both Windows and Linux. Some of the changes are:
* security fixes
* first-run installer for creating config.php
* NO SSL authorize.net and merchantplus credit card modules

March 18, 2007 (Sunday)
It contains fixes to the reports.php and includes the new Error Report.
Features and changes include:
* Promotional-codes
* Updated installer to handle PC Charge credit-card processor.
* Custom email receipts for promoters.
* Updated card response field saving for better compatibility with Wintix credit card details page.
* Customer record not found message displays on getname.php.
* Secure URL redirects were made compatible with PHP5.2.2.
* Updated admin/testinstallation.php with more test data.
* Added the fields xdim,ydim,plan_name to the DBF export of DailySalesReport.
*
May 12, 2007 (Saturday)
There were two minor display errors corrected.

May 29, 2007 (Tuesday)
The feature for automated exports of dbf to wintix is enabled in webtix.
File Location: admin/service_dbf_export.php

POST Parameters (case-sensitive)
clerk        = MD5(clerk)
password    = SHA(CONCAT(clerk,password))
Type        = “DailySales”
StartDate    = “some start date”
EndDate        = “some end date”

If something fails, the first item returned will be “0;error message”.

If everthing goes ok, the return value will be “1;md5 hash;file name;url to download file”.

June 15, 2007 (Friday)
Attached is fixed code for saving the credit card to the audit table. The only file that needs updating is:
_includes/lib.php

July 24, 2007 (Tuesday)
* Changed code how email receipts are sent for compatibility with the latest PHP and Windows servers.
* The table structure is checked so that important tables are validated to exist and that all tables are InnoDB for security purposes.
* There is now a promoter & admin notification when seats remaining is less than a config setting.
* The clerk code is now configurable in config.php.

Since transactions is an important part of Webtix/Wintix, it is *Very Important* that the tables be InnoDB.  If you are worried about performance speed, you would see much more benefit by adding individual key/indexes to fields searched.  The speed difference between no-index tables vs indexed tables is much, much greater than InnoDB vs MyISAM.

(MyISAM vs. InnoDB)  MyISAM performs fast with LOTS of indexes and DB-replication.  NOTE: Currently in your system, there are few or no indexes on tables, which greatly slows performance.  Per my experience, MyISAM with few-indexes is actually slightly slower than InnoDB with few-indexes.

However, I feel that transaction security is more important than speed.
That is why I coded the InnoDB format.

August 6, 2008 (Wednesday)
It enables diagonal and vertical charts to work correctly with orphan seat detection and best-available seat selection.  The “order1″ field on a plan needs to be defined to a unique sequential number for intended adjacent seats.

August 7, 2008 (Thursday)
I was able to recreate the problem with Suhosin and auto-moving-seats. Some of the code had to be massaged into Suhosin’s tolerance. Auto-moving-seats to prevent orphan seats is now working for horizontal, vertical, diagonal, and circular seating charts.

August 14, 2008 (Thursday)
Code changes force browsers to recognize CSS and Javascript correctly.

August 14, 2008 (Thursday)
It includes the new promoter/showinfo/perfinfo1 features that you requested on August 8.

August 17, 2008 (Sunday)

Thank you for informing of not being able to customize _media/maincss.php in the _custom directory.  That problem is now corrected.

RE: reports interface
In testing, some of the reports used a session field that conflicted with the public interface causing the domain to be lost.  Certain reports would display empty stating nothing found for domain ”.  That problem is now corrected.

September 23, 2008 (Tuesday)
2008.09.23_base.  Features added are domain-offset of off-sale time (Saint Norbert College) and pc-charge time-out-auto-acceptance becoming a config option rather than previous forced behavior (Keswick Theatre).

September 26, 2008 (Friday)
It includes the USAePay payment module that you requested.  It seems to communicate with USAePay servers.  I was not able to fully test the module because of lacking a USAePay test account.  (Their example code and Webtix tests returns “invalid source key” responses.)

September 8, 2008 (Monday)
This version fixes two bugs involving reported season ticket email receipts (reported by Click4Tix.com) and restricting ticket quantities by ‘tixpersale’ setting for a show (reported by St. Norbert College).  I have already emailed updated copies of Webtix.

December 10, 2008 (Wednesday)
It contains the feature you requested for Auto-selecting the only available option on Best-Available charts.

December 10, 2008 (Wednesday)
It makes the Webtix patron email address domain validation feature an optional configuration setting for those that want it or disabled for those that cannot use it.

December 12, 2008 (Friday)
This fixes an email receipt error. Enhancements include your requested features:
1) seat-categories displaying on email receipts
2) separation of sale processing and email receipt processing in final sale

January 17, 2009 (Saturday)
This includes the new iCalendar module for importing shows/performances into MS Outlook, Mozilla Sunbird, and other calendar software.  Various code changes and fixes per your request are included also.  I upgraded “centerstage.com/ticketing” to the latest Webtix code.

January 28, 2009 (Wednesday)
It contains code modifications for handing a wider range of best-available plan data.  The (non-rtt) seating chart was unified and made more customizable for customer needs.  It is now possible to have a single file customized (“_includes/libf_renderSeatingChart.php”).  All open seats can be made to appear as sold if customized correctly.

February 25, 2009 (Wednesday)
This includes the experimental code for Webtix permissions system.  The login for “sysadm” will always have access to all parts of Webtix.  All other logins will need to be modified in Webtix to re-enable access.
*** The default state of a login is to have NO-ACCESS to Webtix admin.
*** Features are domain specific.  Only “sysadm” can edit users belonging to all domains.

February 28, 2009 (Saturday)
This version of Webtix includes advanced search, search by calendar, performance summary report, domain and WhatShows reports including “oldsales” records, and an email report bugfix to re-enable background images.

March 4, 2009 (Wednesday)
I looked into the problem with the “Down for Maintenance” page on “demo/authorize.net”.  The problem was caused by the old template database connection code looking for a deprecated table.  Following are changes made to Webtix:
1) I enhanced the “Down for Maintenance” page so that it has a more customer-friendly message and auto-refreshes the browser every 10-seconds until the site is back up.  This enables users to pick up where they left off in a purchase if the down period is short.  This page was also enhanced to work better with old custom-config files and force use of the updated default config file.
2) The template configuration file was altered relocating all database connection code to the file “_includes/lib_connectDatabase.php”.  This enables the database connection code to be update-able.
3) I enhanced the default configuration file enabling administrators to use the traditional test url “?page=testRequirements” in addition to “?displayTestRequirements=yes” and “?displayPhpInfo=yes” while Webtix is displaying the “Down for Maintenance” page.

March 5, 2009 (Thursday)
1) A code work-around to bypass a PHP-MySQLI-core bug which adversely affected admin logins in Webtix.
2) A code enhancement to grant “SYSADM” the same Webtix admin access as “sysadm”.
3) A code enhancement to have a customer’s new password entry masked and then verified for typo’s with a repeat password masked entry field.

This entry was posted in Updates and tagged . Bookmark the permalink.