3.70 Release Candidate 1 available now

[Jamie Edwards]

We're pleased to announce that 3.70 Release Candidate 1 is now available for download from the Members' Area (https://members.kayako.net). The correct file to download is the one marked '3.70.00 UNSTABLE', which can be found under the Builds tab.

Please report any problems you experience with this build in this forum (create a new thread to report a new issue): Alpha, Beta and Release Candidate Feedback - Kayako - Community Forums

Please remember, before upgrading to Release Candidate builds, take full database and file backups.


Upgrade incentive offer

In return for your time trying out the preview release, we are offering a free month of support and upgrades or a free InstaAlert Pro license to the first 20 self-hosted customers to update to 3.70 RC1. This offer is only available to customers whose support subscription is currently active. After updating, please e-mail jamie.edwards[at]kayako.com with a link to your support desk. Once verified, we will add your additional month of support and upgrades.

* This offer is now closed *



What is a 'Release Candidate'?

Release candidates builds are made available to customers before we ship a new release as stable. We publish the build early so that customers who like to test and tinker can do so.

All release candidate builds have undergone at least two stages of testing and peer code review. We'd say that a release candidate more reliable than a beta release, but not quite fully stable. For this reason, we recommend most customers do not update their live support desks to a release candidate build.



3.70 Release Candidate 1

Features, notes and highlights:

• Resolves 52 issues, fixes 45 bugs.
• Resolves 12 security issues.
• Enhanced cross-site request forgery protection.
• Enhanced cookie security.
• Resolves minor Google Chrome comparability issues.

Improvements:

• [SWIFTTHREE-136] - Rebuild cache automatically after updating template
• [SWIFTTHREE-169] - Impex comment cleanup

New features:

• [SWIFTTHREE-170] - Cookie hashing

Bug fixes:

• [SWIFTTHREE-20] - Typo in Admin CP language pack (Ignore E-mail Message)
• [SWIFTTHREE-23] - Can't set ticket to "-Unassigned-" after ticket has been assigned.
• [SWIFTTHREE-25] - Regression of swappable iconv/mbstring option in functions_mime.php
• [SWIFTTHREE-30] - Database password in config.php mustn't be in double quotes due to variable parsing
• [SWIFTTHREE-38] - Ticket Sorting on the Client End is not properly working when sorted by 'Status'
• [SWIFTTHREE-39] - Advanced Search not working in Staff CP: Teamwork > Manage Contacts >> detailed list tab option >> advanced search tab
• [SWIFTTHREE-40] - Captcha rejecting the input in Google Chrome while registering
• [SWIFTTHREE-45] - Queue Overrides (Optional)does not work for the non registered mail.
• [SWIFTTHREE-50] - Cannot change password in the Support Centrer >> Client Area, "Invalid Session ID detected" Error is returned.
• [SWIFTTHREE-51] - Parser rules using "Match All" broken
• [SWIFTTHREE-54] - Due time set to default SLA time when setting status and due time from 'Reply' tab
• [SWIFTTHREE-61] - Problem with Look-up Users & Contacts with cyrillic
• [SWIFTTHREE-63] - Negative value of 'offset' GET variable throws SQL error in news>>view action
• [SWIFTTHREE-69] - Requesting a chat with a visitor twice results in SQL error (Duplicate entry for key..)
• [SWIFTTHREE-82] - Staff CP Permission blocking Staff User(s) to delete File(s) not working.
• [SWIFTTHREE-84] - When updating Attachment Types, Cache not being rebuilt, resulting in changes being made to the original table and not in cache.
• [SWIFTTHREE-85] - Custom Field Code being added to the Template are not displaying these Custom Fields at the Staff CP.
• [SWIFTTHREE-90] - Parser can fail to search for ticket id in email body if it finds the ticket mask but not ticket id.
• [SWIFTTHREE-92] - Securtiy fix
• [SWIFTTHREE-94] - Securtiy fix
• [SWIFTTHREE-124] - Creation of Ticket View with " (Quotes) results in all mouse-over menus such as view, search, create new ticket, etc. not to pop up
• [SWIFTTHREE-125] - Incorrect cron run time
• [SWIFTTHREE-127] - In 'functions_ticketmain.php', the following code snippet is buggy
• [SWIFTTHREE-153] - Cross-site request forgery protection
• [SWIFTTHREE-161] - Security fix
• [SWIFTTHREE-162] - Security fix
• [SWIFTTHREE-163] - Security fix
• [SWIFTTHREE-166] - Replace use of split() with explode()
• [SWIFTTHREE-171] - Add upgrade step for cookie hash code added in SWIFTTHREE-170
• [SWIFTTHREE-172] - Remove unnecessary comparison
• [SWIFTTHREE-174] - 'buildHash' and 'buildHashBlock' functions being defined twice resulting in breaking Setup/Upgrade/Impex
• [SWIFTTHREE-179] - Variable cleanup in functions_parserrules.php
• [SWIFTTHREE-180] - variables that are no longer used now, should be removed from the code in file functions_parserrules.php
• [SWIFTTHREE-181] - Unnecessary Overhead to clear Core Caches while modifying existing template(s)
• [SWIFTTHREE-182] - Rebuild cache automatically after restoring template
• [SWIFTTHREE-183] - Security fix
• [SWIFTTHREE-186] - Security fix
• [SWIFTTHREE-190] - Security fix
• [SWIFTTHREE-191] - Security fix
• [SWIFTTHREE-192] - Security fix
• [SWIFTTHREE-196] - No need to sanitize dictionary phrase in client_news.php
• [SWIFTTHREE-197] - No need to escape the entire block of IRS data
• [SWIFTTHREE-198] - Wrong variable sanitized in client_knowledgebase.php
• [SWIFTTHREE-199] - Double HTML sanitization in ?_m=downloads&_a=viewdownload
• [SWIFTTHREE-205] - Double-quotation problem in sanitization in functions_knowledgebase.php
• [SWIFTTHREE-206] - addslahes() needed for "Add to fav" functionality in client_knowledgebase.php
• [SWIFTTHREE-207] - HTML entities being shown in category listing when adding a troubleshooter step
• [SWIFTTHREE-215] - Seed buildHash() internals with mt_srand()
• [SWIFTTHREE-218] - Security fix

Project summary: SWIFT V3 - Kayako JIRA



Template change log between 3.50.04 and 3.70.00

If you are upgrading to 3.70 from a version earlier than 3.50.04, this change log does not cover all of the required template changes, and you are suggested to revert all templates that are marked as such.

• changepassword
  • Changed:

    •  <tr>
              <td width="30%" align="left" valign="top" class="row2"><span class="<{if $posterror == true && $oldpassword == ""}>redtext<{else}>smalltext<{/if}>"><{$language[oldpassword]}></span></td>
              <td width="70%"><input name="oldpassword" type="password" size="25" class="swifttext" value="<{$oldpassword}>"></td>
            </tr>
            <tr>
              <td width="30%" align="left" valign="top" class="row2"><span class="<{if $posterror == true && $newpassword == ""}>redtext<{else}>smalltext<{/if}>"><{$language[newpassword]}></span></td>
              <td width="70%"><input name="newpassword" type="password" size="25" class="swifttext" value="<{$newpassword}>"></td>
            </tr>
            <tr>
              <td width="30%" align="left" valign="top" class="row2"><span class="<{if $posterror == true && $newpasswordc == ""}>redtext<{else}>smalltext<{/if}>"><{$language[newpasswordc]}></span></td>
              <td width="70%"><input name="newpasswordc" type="password" size="25" class="swifttext" value="<{$newpasswordc}>"></td>
            </tr> 

  • To:

    •  <tr>
              <td width="30%" align="left" valign="top" class="row2"><span class="<{if $posterror == true && $oldpassword == ""}>redtext<{else}>smalltext<{/if}>"><{$language[oldpassword]}></span></td>
              <td width="70%"><input name="oldpassword" type="password" size="25" class="swifttext" value=""></td>
            </tr>
            <tr>
              <td width="30%" align="left" valign="top" class="row2"><span class="<{if $posterror == true && $newpassword == ""}>redtext<{else}>smalltext<{/if}>"><{$language[newpassword]}></span></td>
              <td width="70%"><input name="newpassword" type="password" size="25" class="swifttext" value=""></td>
            </tr>
            <tr>
              <td width="30%" align="left" valign="top" class="row2"><span class="<{if $posterror == true && $newpasswordc == ""}>redtext<{else}>smalltext<{/if}>"><{$language[newpasswordc]}></span></td>
              <td width="70%"><input name="newpasswordc" type="password" size="25" class="swifttext" value=""></td>
            </tr> 

[Jamie Edwards]

To make tracking feedback easier, please keep threads on topic and about one particular issue.

If you cannot find an existing thread for the issue you wish to report, please create a new one. Do not report it in an unrelated, existing thread.

[Jamie Edwards]

Thanks to everyone who has participated in the release candidate programme so far.

We've extended the offer to the first 40 early adopters.

[Jamie Edwards]

Thanks to everyone who participated in the early upgrade scheme.