v2.2.5 Available in Members Area

[Varun Shoor]

v2.2.5 is now available in Members Area. This is primarily a bug fix release and resolves certain long pending issues with eSupport. This version had been delayed a bit as we are working on v3 release side by side and PHP5 compatibility was a tricky task as the problem was with certain free libraries used with the product. We are trying to avoid adding any complex features to the v2.2 branch due to the overly unorganized nature of current source code (Which was basically an extension of our original v1.x release). Any suggestions you provide us are being duly noted and will be in v3 release.

All in all this will make your current version a lot more stable and snappier. As much as we would like to add new feature to the current product in the end it will not be worth it as we will have to port the code to v3 again.



UPGRADING INSTRUCTIONS

Upgrading from v2.2 to v2.2.5 Stable

• IMPORTANT! Backup BOTH your Database (mysqldump) and your Files before proceeding.
• Replace all your existing files with the new ones in upload_zend/upload_ioncube directory
• REMOVE admin/setup.php
• Make sure BOTH your config.php AND key.php are in admin/ directory after you have replaced the files
• Upload the file "upgrade_v2.2_to_v2.2.5.php" from your upgrade/ directory over to admin/ directory and run it from your web browser
• Follow the steps, it should finish without any issues.
• Delete "upgrade_v2.2_to_v2.2.5.php" from your admin/ directory

Upgrading from v2.1.x to v2.2.5 Stable

• IMPORTANT! Backup BOTH your Database (mysqldump) and your Files before proceeding.
• Replace all your existing files with the new ones in upload_zend/upload_ioncube directory
• REMOVE admin/setup.php
• Make sure BOTH your config.php AND key.php are in admin/ directory after you have replaced the files
• Upload the file "upgrade_v2.1.x_to_v2.2.5.php" from your upgrade/ directory over to admin/ directory and run it from your web browser
• Follow the steps, it should finish without any issues.
• Delete "upgrade_v2.1.x_to_v2.2.5.php" from your admin/ directory

CHANGELOG FOR THIS RELEASE:

[*] The Ticket Attachment clearing functionality under Settings > Database will now delete attachments for only CLOSED tickets

[*] Added <{$level}> Variable to All Email Templates, This Variable can be used to denote the Priority of the ticket.

[*] eSupport will now goto last page of tickets when it is replied to, it will goto first page if Reverse Order is enabled - We somehow missed this feature in original v2.2 release but have since added it into v2.2.5

[*] Added index for ticketidchar field in asTicketsData. This was causing certain areas like deletion of tickets to slow down, deletion, closing etc should be snappy now.

[*] Added a Quote Image along with replies in the Ticket Listing. Clicking the Image fills up the Post Reply page with the Reply contents automatically.

[*] Fixed "HELO" Issue with SMTP, This was causing SMTP to fail on certain Windows machines

[*] Changed the way of loading of SMTP class, This too was the cause of SMTP to fail on Windows servers.

[*] Added "Empty Parser Log" functionality under Settings > Database. Deleting entries from Parser Log will result in the Email Body data being deleted from the database as the Email Body is now stored in asParserLog rather than asTicketsData table.

[*] Changed the valuem field in asFieldData to MEDIUMTEXT

[*] Removed the a_fields text field from asTickets, Should speed things up considerably.

[*] Added Client Full Name column in Ticket Listing. You can enable this by clicking on the Options button.

[*] Fixed a bug where the Troubleshooter Entries in client area were not sorted according to the sort order specified during creation

[*] Fixed a bug where the Attachment Paper Clip would show up even when the Attachments were cleared from database.

[*] eSupport will now remove an Email Handler assigned to a department if you delete that department from the admin area. This should prevent the "ghost tickets" issue from happening where tickets would be received by eSupport but would not appear in any department

[*] Fixed a bug where the Knowledgebase InstaSearch suggestions were displayed from all Template Groups

[*] Added PHP5 Compatibility, required editing of the free libraries used by eSupport.

[*] Fixed Compatibility issues with the new ModernBill 4.2. On certain systems the integration would result in a "Blank Page" being displayed

[*] Fixed a bug where the Links to tickets in Email Alerts sent from eSupport would not contain a ticket id

[*] Fixed the bug where Blank Replies would be dispatched from the system when you forwarded a ticket with HTML Emails enabled

[*] Added Updated Spanish Language Pack, Fixes certain errors in earlier translation

[*] Added French Language Pack

[*] Fixed HTML Issues for Predefined Replies which would result in stray Javascript code being displayed on the Ticket Viewing page

[*] Fixed a bug where it would display HTML Special characters for subjects in ticket listing if an email was received in a UNICODE language

[*] Fixed a bug where deleting a ticket would not result in deletion of asTicketsData entry. This would result in gradual increase of the database.

[*] Fixed a bug where Reply-To had a different email for outgoing emails

[*] Fixed a bug where "@" was displayed for Emails that had special characters like (, ), {, }, [ or ]

[*] Fixed a bug where it would display an error relating to genUniqueTicketId function in ticketcore.php

[*] Fixed a bug where Parser would fail if the incoming email had multiple "To:"'s

[*] Fixed the bug where Rating of tickets would result in "Invalid Email or Ticket Key" error

[*] Fixed the "Invalid Email or Ticket Key" errors that would happen on certain systems

[*] Fixed Ticket Search Errors when using a Custom Query

[*] Added Index on parentid field of asAttachments table, This was another reason for slow deletion of tickets

[Varun Shoor]

There was a minor glitch in the upgrade scripts that happened on certain installations that upgraded v2.2 from v2.1.1 (From what it seems, I have not been able to confirm the cause though), It has now been fixed and new updated builds are being uploaded. In case you ran the previous upgrade script and now get an error during upgrading, Just run the following SQL queries and run the Upgrade script again.

ALTER TABLE asTicketsData ADD emailbody MEDIUMTEXT;
ALTER TABLE asTicketReply ADD emailbody MEDIUMTEXT;

These queries need to be ran only if the upgrade failed for you. If you have any questions then please open a support ticket by mailing support AT kayako.com

Regards,

Varun Shoor