Revision History

[BUGFIX] The last 4 digits of the card number and the card's type weren't being recorded properly in the Zen Cart order's info.

[UPDATED] The card's type is now displayed using its name, rather than the Sage Pay code for the card's type.

[UPDATED] The module will no longer return to the payment page with an error if the IFrame wrapper page is refreshed by the customer. This seemed to happen often when the customer was using a mobile phone to view the site. Refreshing the page will now result in the Sage Pay card details page being displayed again. If a refresh takes place just as the IFrame is being broken out off, to complete a payment, this could cause a customer to be charged by Sage Pay but no Zen Cart order to be created. This situation is very unlikely though whereas the refreshing of the IFrame wrapper page when the card details page was to be displayed was occurring a lot more than anticipated and causing lots of timeouts to occur.

[UPDATED] A more informative error message is displayed to the customer when too many attempts have been made to enter correct card details.

[BUGFIX] Major bug, introduced in 1.2.0, fixed. Notification handler was still using old Vendor Name configuration information!

[BUGFIX] When upgrading the database from 1.0.0 to 1.2.x the auto-upgrade code was not storing the vendor name alongside the transactions, meaning that transactions could not be performed successfully against any transaction performed using version 1.0.0. Software will now restore the vendor name - and therefore the transaction action functionality - for previous transactions by assigning the default vendor name account to them (which is the most likely to be have been used given the small time frame between versions in which this problem could have occurred).

[UPDATED] Documentation updated further with additional information for new version of My Sage Pay. Information for old version of My Sage Pay removed as the old version has been discontinued.

[ADDED] Support for multiple Sage Pay Go accounts added. Any number of Sage Pay Go accounts can be used with the module by configuring which currencies use which account (by specifying the currency/currencies and the Vendor Name for each account). This replaces the “Default Merchant Account Currency” and “Accepted Merchant Account Currencies” functionality used previously, which could only handle one vendor name being used for all currencies. The default currency is now simply the first currency defined in the list of “Merchant Account Accepted Currencies and Associated Vendor Names”.

[ADDED] Summary panel added to Transaction Admin. When an order is first displayed, a space-saving summary of the transaction information is shown, rather than the full admin panel, so the admin user can still see the order information on one page without having to scroll un-necessarily. This summary panel is now displayed by default but there is a new option to always display the full panel if desired.

[ADDED] Module now checks if any of the database table name files are missing and if the notification handler file or the IFrame breakout file is missing. This should help prevent problems when the person installing the software forgets to upload some files, or when they upload files to the wrong place.

[UPDATED] The transaction admin panel is no longer included when the order page is printed, making printouts of the order page neater and clearer.

[UPDATED] If module has found out that the transaction has been modified in My SagePay, its status is set as such. No actions can be performed against it using the Transaction Admin.

[UPDATED] Transaction Admin updated with better compatibility with different character sets.

[UPDATED] The last 4 digits of the card number and the card's type are now recorded in the Zen Cart order's info as well as in Ceon Sage Pay Server's “Initial Transaction Info”, so this information is always displayed on the order page and in printouts of the order page.

[UPDATED] Notification handler no longer fails when Zen Cart is in maintenance mode. The notification handler now prevents Zen Cart from setting a 503 HTTP status header so that Sage Pay doesn't reject its output.

[UPDATED] The configuration check observer will now only run if the module is enabled. It will now also output individual warnings, a warning if the module is in debug mode and/or a warning if the module is using a test server.

[UPDATED] Text of 3D-Secure options updated.

[BUGFIX] URI for simulator server was wrong.

[BUGFIX] When attempting to (partially or fully) release a transaction which has already been released through My Sage Pay, the database call to record the transaction as already having been released was missing the value for the primary key's field and therefore failing to complete.

[BUGFIX] When attempting to (partially or fully) authorise a transaction which has already been authorised through My Sage Pay, the database call to record the transaction as already having been authorised was missing the value for the primary key's field and therefore failing to complete.

[BUGFIX] Security check on IFrame wrapper page was using a function not supported by Zen Cart 1.2.x. Compatibility code for Zen Cart 1.2.x added.

[ADDED] Default style added for 3D-Secure images on IFrame wrapper page, to better use the space by aligning the images to the right of the text.

[ADDED] New “Transaction Admin User Guide” added to the documentation, including informative slideshows with screenshots and informational text.

[UPDATED] Installation instructions and FAQs updated with information about configuring/fixing SEO software to work with the module.

[UPDATED] Installation instructions and FAQs updated with information about the “Back” button bug on the Zen Cart admin order page and information on how to apply the bug fix supplied in the sample modified core file.

[UPDATED] Installation documentation updated to stress the separation of the files for the admin from the files for the main store. Most Zen Cart stores have renamed their admin folder but some people were forgetting to check what the name the store's admin folder has before copying the files across. This should further reduce the number of people making that mistake.

[UPDATED] Documentation updated to add information for new version of My Sage Pay.

[UPDATED] Initial release.

[UPDATED] Initial release to betatesters.