Revision History
| Date | Version | Release Information |
|---|---|---|
| 25th March 2009 | 2.4.0 |
[ADDED] Option to disable Blowfish encryption added.
[ADDED] Information about switching off Blowfish encryption or storage of details in session added to admin and ConfigCheck class. [ADDED] ID attributes added to all form gadgets to allow for custom styling of the payment form. [ADDED] Module now automatically checks include paths against any open_basedir restrictions and displays the information necessary to fix a misconfigured server's access to its PEAR installation/Crypt_Blowfish files. [BUGFIX] Visa Debit, Visa Electron and Maestro cards which weren't enrolled in a 3D-Secure scheme were returning the wrong ECI code. [BUGFIX] Solo cards can no longer be checked for 3D-Secure as they don't support it. [BUGFIX] Method of encoding/decoding error messages for passing back in the query string updated to not rely on urlencode function to prevent the use of illegal characters as it didn't work as expected. [UPDATED] FAQs completely rewritten to make them a lot more informative, usable and easier to comprehend. Lots more information about configuring servers for access to PEAR/Crypt_Blowfish added. [UPDATED] Minor documentation updates - table of contents added to configuration and placement of top anchor adjusted. |
| 24th September 2008 | 2.2.2 | [BUGFIX] Two of the defines being used in the module were incorrectly named. |
| 21st August 2008 | 2.2.1 | [BUGFIX] An incorrect expiry date for the card was being shown on the confirmation page. The transaction was unaffected, only this display was wrong. |
| 18th August 2008 | 2.2.0 | [ADDED] Option to enable/disable storage of entered card details added. If details aren't being stored, encryption is not necessary.
[ADDED] Module now checks for ability of PHP installation to access PEAR library on the server, as well as its ability to access PEAR:Crypt_Blowfish. [ADDED] Module now warns the user on the catalog side if the card details are being stored in the session but encryption can't be used. [UPDATED] Code added to account for Zen Cart bug in zen_href_link() which wrongly appends the session ID to a static URL with an ampersand (&) instead of a question mark when there are no parameters for the URL. [BUGFIX] Security problem fixed. A malicious customer was able to modify their cart's contents after having reached the 3D-Secure screen without the amount being billed being adjusted! Now any hack attempts are detected and the customer is returned to the first checkout page if they have attempted to “hack” the 3D-Secure checkout in this way. [BUGFIX] Debug output now always outputs information about the open_basedir setting for the server. Previously this information was (wrongly) only displayed if safe mode was enabled. |
| 1st July 2008 | 2.0.0 |
[ADDED] Full support for 3D-Secure (“Verified by Visa”/“MasterCard SecureCode”) added, using Realex's RealMPI service. Includes full automatic IFrame generation and handling: customer stays within main layout of store and is given full instructions/information on what is happening, why it is happening and what they can/should do next. All browser technologies (IFrame support/Javascript support) are accounted for, with automatic fallback to simpler output if a particular technology is not supported/active.
[ADDED] Surcharge/Discount support added. [ADDED] “Cards Accepted” sidebox added to allow dynamic display of accepted card types even before the checkout stage. [ADDED] Ability to set custom formats for the month and year select gadgets added. [ADDED] Module now automatically disables itself if a configuration problem is identified. [ADDED] Version information section added to Admin to aid identification of the currently installed version of the module. Also allows online version checking through use of “Check for updates” link. [UPDATED] Error handling improved by including checks for specific error codes in returned status detail. [UPDATED] Module now allows usage of normal HTML tags for error messages due to new support of error message encoding. [UPDATED] A warning is now displayed when Debug Mode is being used. [UPDATED] Length of Encryption Keyphrase restricted to 56 characters. |
| 12th June 2006 | 1.0 | Initial Release to private clients. |
