Issues Solved by Using Kayako 4.98.9

Overview

Kayako Classic version 4.98.9 is the latest and most stable build and will remain like that indefinitely now that the product has reached its End of Engineering cycle.

We urge all our customers who encounter any technical issues to upgrade or downgrade to this version. Our support team won't be troubleshooting issues in any other versions than that.

Information

Below will provide a list of the most common issues that are resolved after installing Kayako Classic 4.98.9.

Note: This is not an exhaustive list and some issues that are not mentioned here can also be fixed after switching to this version. Please note that the latest version 4.99.x that was introduces to support PHP 8 is less stable and not recommended for use.

Also, you can review older Kayako Classic Release notes.

List of issues that are resolved by installing version 4.98.9:

• After filtering the results using the magnifying glass, the "Click to Reset" button is unresponsive, the window refreshes and nothing happens
• XSS injections vulnerability
• PHP crashes when testing 4.99 version
• 4.99.x installer package missing subfolders under __swift folder
• Error displayed for reports that actually contain valid data:
  "This report didn't produce any results, so there is nothing to display"
  
• If you create a ticket via API it has in DB emailqueueid set to 0
• email ticket content is not processed correctly leaving only the banner
• Mails with Emojis are not fetched by the Email-Parser
• Users receive all of their responses to tickets via Email
• The system does not see the requester of the ticket (staff) as a user (customer)
• Apostrophe is not displayed when sending emails from Kayako
• Problem with encoding/decoding on edit reply
• Square brackets prevents the email address from being parsed
• Emails with emojis are not being processed
• PHP error - undefined offset
• The system does not see the requester of the ticket (staff) as a user (customer)
• POP3 queues are throwing Malformed header detected
• From Email not parsed correctly
• Tickets switch to open after staff replies without changing status
• OAuth Consent Flow Broken when Do not allow user consent is enabled in Azure
• Duplicate tickets being generated for the same email
• Tickets created via API uses for Reply-To disabled queues
• Mail parser truncates the beginning of the email, if later in the email is a opening html tag
• Undefined offset: 0 (./__apps/reports/library/Report/class.SWIFT_ReportBase.php:159)
• Apostrophe character is encoded when outgoing from our Kayako
• Issue with Chinese Characters
• Audit Log language inconsistencies
• Private replies are not updating the Staff Updated timestamp
• Audit Log language inconsistencies
• Emails fail to be parsed with The input is not a valid email address. Use the basic format local-part@hostname
• Why some emails with the To field being empty are fetched while others are not?
• Emails with subject [EXTERNAL]: cannot be parsed into tickets.
• Some emails with the To field being empty are fetched while others are not
• Reply Due and Resolution Due dates are calculated incorrectly after changing SLA plans