This post is to announce the release of ColdFusion 11 Update 11 and ColdFusion 10 Update 22.
Update 11 and Update 22 fix approximately 164 and 45 bugs respectively. For the list of bugs fixed in these updates, refer the following documents:
Bugs fixed with Update 11
Bugs fixed with Update 22
Follow the steps below to apply the updates:
- Navigate to ColdFusion Administrator -> Server Updates -> Updates.
- Switch to the "Settings" tab.
- Ensure that the update site URL is set to the right value by clicking on the "Restore Default URL" button.
- Click on "Submit changes" to save your changes.
- Switch to "Available Updates" tab. Click on "Check for Updates".
- "ColdFusion 11 Update 11" or "ColdFusion 10 Update 22" should be listed under the "Available updates" tab.
- Click on the "Download and Install" button to install the update.
Refer the following technotes for instructions and other details related to the updates:
ColdFusion 11 Update 11 technote
ColdFusoin 10 Update 22 technote
To apply these updates manually, download the required update by clicking on one of the applicable links below:
ColdFusion 11 Update 11 jar
ColdFusoin 10 Update 22 jar
To run the downloaded jar, execute the following command:
java -jar <jar-file-dir>/hotfix_0xx.jar
You should use the JRE used by ColdFusion for running the update jar (for standalone CF, it should be <cf_root>/jre/bin)
For further details on the manual application of the updater follow this help article.
The build number after applying this update should be:
11,0,11,301867 for ColdFusion 11;
10,0,22,301868 for ColdFusion 10.
We would like to inform you that we have moved to a new bug tracking and reporting application called “Tracker". This was necessary as internally at Adobe, we have now transitioned to JIRA for issue/bug tracking for all the products. While functionally Tracker is similar to the BugBase application, there are still few inherent differences, that we thought, we should highlight. The same have been listed below:
1. While logging a bug, you will see a field, Component, which is equivalent to Product Area in BugBase. Any Component in Tracker is a combination of Product Area: SubArea, for example, Administrator: Admin API, Administrator: Code Analyser.
2. You will also see fields "Status, Resolution & Reason Code", which is equivalent to BugBase’s "Status, State & Reason".
3. 'Duplicate ID' for any old bugs would be seen as a part of 'Bug Description'.
4. Voting comments for old bugs would not be seen. However, count of votes is visible for all the old bugs.
There are some issues with Tracker that we are currently working on . While using Tracker, you may face:
- Issues in receiving mail notifications for any change in a bug.
- Some discrepancies in the number of bugs, that you had logged or voted for.
- Some discrepancies in the number of comments in the bug(s).
- The field “Reported By” for all bugs is missing.
As always, we request you to test drive our new bug tracking system and send your valuable feedback, so that, we can enhance the overall user experience. We will keep you posted once we fix the issues listed above.
An important security fix for ColdFusion Builder 3 is now available for download. For more information on the vulnerability refer APSB16-44.
You can download the patch from here (md5 checksum : b67914e27ca4fb8e0fc5ecd354e9a330). Apply this patch to secure your ColdFusion Server and Builder installation. Follow the installation instructions detailed at this technote.
The server and express installers for Adobe ColdFusion (release 2016) have been refreshed. The installers are available for download at the ColdFusion product page at www.adobe.com. The new installer includes the following changes:
- The API Manager installer is decoupled from the ColdFusion Server installer.
- The new API Manager installer incorporates certain new features such as multi-tenancy, enhanced security, configurable policies, a dedicated update mechanism and support for Redis cluster and request/response compression. For a detailed description of these new features follow the links embedded in this technote. The API Manager installer would be made available very soon. We will update this post to share the location where the installer would be hosted.
- The ColdFusion installer incorporates ColdFusion 2016 Update 3 and updates JDK to version 1.8.0_112. For details on the changes that went out with Update 3 refer the Update 3 Release Notes document. The build number for this installation should be 2016,00,03,301771.
- The features listed below have been retired from the product and no longer ship with ColdFusion. For a detailed overview of the affected areas, refer the "Portlets" and "YUI and Spry" sections of the coldfusion-deprecated-features technote. In case you need to use any of these libraries you can download them from locations mentioned below.
- Portlets. download (md5 checksum : 93273a7b4ab8c650e5fa9cece518e099);
- YUI. download (md5 checksum : 827e0f8395d176ac28f46ed5e78004fd);
- Spry. download (md5 checksum : 750c275c20b291f00c1ba92c855a09d7).
To integrate the downloaded library, follow the instructions below:
- Stop ColdFusion sever.
- Download the libraries from the links mentioned above.
- Extract the downloaded files to the following locations:
- Extract portlets.zip file to <cf_root>/cfusion directory. Update the web.xml file at <CF_HOME>/cfusion/wwwroot/WEB-INF to re-introduce the mappings mentioned in the "Portlets" section of this technote.
- Extract yui.zip and spry.zip to ColdFusion's webroot at <cf_root>/cfusion. If your scripts directory is mapped to a non-default location (setting at CF admin > Settings > Default ScriptSrc Directory), unpack the zipped package manually and place it in the custom location following the structure in the package.
- Restart ColdFusion server.
If you are restoring just the YUI or Spry libraries, restarting the ColdFusion server is not required.
20 Dec, 2016 - added the web.xml mappings step in restoring portlets instruction. added reference to coldfusion-deprecated-features article.