Bugs fixed in ColdFusion (2018 release) Update 2

Known issues in this release

Fonts

Issue #1

If there is an error, as shown below, with fonts in cfdocument , you must install the respective fonts in your system before executing the tag.

coldfusion.document.spi.DocumentExportException: java.lang.ClassCastException: class sun.font.CompositeFont cannot be cast to class sun.font.PhysicalFont (sun.font.CompositeFont and sun.font.PhysicalFont are in module java.desktop of loader 'bootstrap')

The issue occurs because the Lucida Font has been removed from Oracle JDK.

Oracle JDK no longer ships any fonts and relies entirely on fonts installed on the Operating System.

Fonts in the Bigelow & Holmes Lucida family (Lucida Sans, Lucida Bright, and Lucida Typewriter) are also no longer available to applications from the JDK.

If applications rely on fonts that are included in the JDK, they may need to be updated.

For more information, see release notes from Oracle.

Issue #2

For a few archiving cases, there could be archiving failures related to fonts/annotations.

Archiving

Issue #1

If you are unable to archive a .cfr using standard 1b, add the flag  -DARCHIVE_ENCODING=MacRoman in jvm.config.

Issue #2

CAR creation/deployment does not work as expected.

Mobile support

Issue #1

Ajax calls for Cordova apps do not work if the request being made is not through https. Also, self-signed certificates won’t work. It has to be a domain associated with a CA-assigned certificate.

Issue #2

If you have a build server different from your target server, you cannot use any new feature of mobile.

Workaround: 

1. Navigate to your build server.
2. Copy the file data.ser from [CF Home]\cfusion\lib\mobile\data.ser.
3. Navigate to your target server.
4. Paste this data.ser file to folder [CF Home]\cfuson\lib\mobile.

Issue #3

cfclient throws Error 400 bad request for cfftp.

Issue #4

Scope variables, such as, cfdocument.currentPageNumber do not work as expected in the cfdocumentitem tag.

cfpdf

In cfpdf , sign or unsign actions may not work as expected in Solaris 11.3.

Workaround:

1. Navigate to [CF Home]/[CF Instance]/wwwroot/WEB-INF/lib.
2. Take a backup of the file jcmFIPS.jar 
3. Delete the jar.
4. Restart ColdFusion.

Connector

Web pages do not render as expected when document root of Apache contains localized characters.

Workaround

Create a document root with only English characters.

Scheduler

Issue #1

When you create a task ColdFusion Administrator, it displays the scheduled time in 1899 format.

Issue #2

A daily/monthly task when modified to set a crontime , does not set as expected.

Language

Issue #1

The ListDeleteAt function removes the last symbol instead of the entire delimiter.

Issue #2

cfsearch fails when DisMax query parser is used.

AJAX

When using the grid component, you must click a check-box twice to select. This occurs intermittently due to an upgrade to the ExtJS library.

Install

The update installer searches for the  cfscripts folder if the folder is moved to a different location.

Server Auto-Lockdown

After uninstalling Server Auto-Lockdown, a few folders (such as,   jre , uninstall, or logs) are left behind. Delete the folders manually.

Caching

If you specify a datasource on a persistent CFC with secondary caching enabled, the application will not start as it attempts to create a new cache with the same name as the cache specified in the caching configuration.

Document management

The " backgroundcolor " attribute for cfpresentation tag does not work as expected.

queryExecute

If you assign the result of a QueryExecute directly to a bracket style variable reference, an exception occurs.

Revision history

2/15/2019: Added a known issue for queryExecute function.