ColdFusion MX 6.1 Resolved Issues
Updated August 12, 2003
This document lists significant issues that were fixed in ColdFusion MX 6.1.
ColdFusion MX 6.1 also fixes many additional problems that are less significant
or affect a small subset of users; these issues are omitted for clarity.
For Release Notes and a list of known issues,
see the following web pages:
Contents
Administrator
32028 |
The behavior of the Administrator debugging settings and what the settings
allow programmatically were not consistent with ColdFusion 5. |
38219 |
The HTTP_USER_AGENT for scheduled tasks was set as "Java1.3.0" instead
of "CFSCHEDULE" as in previous versions. |
38572 |
Spaces in Microsoft Access data source names caused a generic "SQLException
occurred in JDBCPool while attempting to connect" error. |
39482 |
ColdFusion MX Administrator used the REReplace function
instead of the Replace function.
|
44664 |
Migration errors were logged when migrating scheduled tasks that contain
dates with invalid formats. |
44935 |
When migrating scheduled tasks from earlier versions of ColdFusion,
the proxy port was migrated even if the proxy server was undefined, causing
the scheduled
task
to fail. |
45187 |
Code Analyzer would not run if session variables were not enabled. |
45481 |
The Migration Wizard was unable to run if browser pop-windows were blocked. |
| 45746 |
When clicking the Driver column within Data Sources in
the ColdFusion MX Administrator, an error stated "Sorting by driver type
does not work in MX admin."
See TechNote
18282 for additional details. |
45947 |
The DataSourceFetchTimeStampAsString attribute was not exposed as a
data source option in the ColdFusion MX Administrator. |
46450 |
A leading space in the data source name caused the data source to verify
in the ColdFusion MX Administrator, but throw an error when connecting
in
an application. |
46910 |
If a site-wide or missing template handler in the root of
the wwwroot was specified and a leading slash was not used, a warning was thrown
that the
files don't exist. The files did exist, and the exception subsystem used
them despite the warning. |
47211 |
An "Element SQLEXECUTIVE is undefined in REQUEST" error could occur
after clicking on the Data Sources link or editing data sources in the
ColdFusion
MX Administrator,
and when running a query on a ColdFusion page.
See TechNote
18299 for additional details. |
47673 |
If the "One-Time" frequency was selected and an invalid time was specified
for a scheduled task, a CFLocaleTimeFormatException
would be
thrown. |
48538 |
Attempting to verify a bad data source within the Administrator would
cause the Administrator to hang. |
48930 |
Scheduled tasks ran with a -1 hour time shift after the
October daylight savings time change. |
49158 |
In the Japanese version, the Code Analyzer results pop-up
information contained a nonlocalized string. |
49551 |
Changing the ColdFusion MX Administrator password in "Security/CFAdmin
Password" to an extremely large password caused the user to be logged
out (expected) to try the new password, but then did not accept the
new password
because it was too long. |
49662 |
A scheduled task entered with a date in the past would
be performed. |
49867 |
Added a
Cache web server paths option to the ColdFusion MX Administrator. |
50033 |
The ColdFusion MX Administrator appended
the user's locale
to the end of each Macromedia.com GO URL in the Administrator, which resulted
in
errors
if the user's locale had a language that didn't
have GO URLs. |
50180 |
The two data source XML configuration files
could become out of sync if you specified an invalid data source name
and click Cancel
before creating the data source. |
50417 |
The Keep Library Loaded check box on the Add/Edit C++ CFX
Tag page in the Administrator did not keep the DLL for a C++ CFX in memory. |
50605 |
When configuring data sources of type 'Other' within Macromedia
ColdFusion MX, if a trailing space was added to the Driver Class field
information,
the data source would fail to verify.
See TechNote
18612 for additional details. |
| 52522 |
HomeSite+ was missing from the list of products in the "Use
an RDS password for Dreamweaver MX or ColdFusion Studio" section of the
ColdFusion MX Administrator RDS Password page. |
| 52497 |
You could not click the "Use J2EE session variables" text
option in the Memory Variables section of the Administrator to
select
the corresponding check box. |
Back to Contents
CFML functions
Note: Other sections of this document also list problems
that affected specific functions.
31866 |
The RepeatString function cropped the string
after 65535 characters. |
47496 |
You could not use the Duplicate function to duplicate
the Arguments scope |
| 47803 |
In some cases, the NumberFormat function worked differently
with negative numbers in ColdFusion MX than it did in ColdFusion 5. |
48035 |
The QuerySetCell function truncated long strings to ~39798
characters. |
48592 |
<cfoutput>#ListLast(",,", ",")#</cfoutput> returned
invalid output. |
48694 |
The Fix function didn't return the proper value. |
49281 |
The DateAdd function did not properly add weekdays. |
49415 |
The XMLFormat function did not handle high ASCII characters. |
49960 |
The LSCurrencyFormat function could not take
a NULL numeric value from a database. |
| 49972 |
When a DateFormat or LSDateFormat function
used a Japanese date format mask in a ColdFusion MX installation with
a 1.4 level JVM, the function
threw a CFML template error. |
49977 |
A query of queries using the Avg function returned the
same data as the Sum function. |
50121 |
The GetTickCount function returned a negative
number. Previous versions of ColdFusion returned a positive number. |
| 50309 |
The DateDiff function output an incorrect difference for
some date combinations when using years as the unit of comparison. |
50451 |
Using a UDF as the value of a ColdFusion tag attribute resulted in a
Method Not Found error. |
50950 |
Errors regarding path information for Crystal Reports 8.5 were not
generated properly. |
51587 |
The LSTimeFormat function did not handle string
datetimes using yyyy-mm-dd format for the date even though the IsDate function
identified the string as a valid
date. |
| 52685 |
The DateDiff function was off by an hour when
one of the times was in daylight savings time and the other was not. |
Back to Contents
CFML tags
Note: Other sections of this document also list problems
that affected specific tags.
23288 |
Credit card validation using the cfinput tag didn't accept
numbers between 13 and 16 digits. |
28947 |
The cfhttp tag did not support a HEAD
operation. |
30424 |
Running the cfexecute tag with an output file
defined put the file in \winnt\system32 on Windows systems. |
34052 |
You could not upload multiple files with the cffile tag. |
34125 |
The cfhttp tag allowed invalid
query column names. |
34166 |
Added name and password attributes
to the cfmail tag. |
37498 |
Using a 'from' address containing spaces in a cfmail tag
caused the tag to fail. |
37683 |
When using the IBM JRE, the cfhttp tag did not properly
connect to HTTPS URLs. |
37684 |
When using the Sun JRE, the cfhttp tag might
not always properly return a 404 status code from HTTP requests to URLs that
contained
nonexistent pages. |
37685 |
In the cfhttp tag, if you specified firstrowasheaders="no" and
did not specify a columns attribute, the tag did not generate
column headers like column1, column2, and so on. |
38383 |
Added the ability to perform raw HTTP posts using the cfhttp tag. |
38567 |
Added the ability to return cfexecute tag results
in a variable. |
39216 |
Using the cfinvoke tag to call
a nonexistent CFC didn't result in a clear message. |
39490 |
The cfexecute tag timeout attribute
was not working properly. |
39496 |
The cffile tag rename action required
the full path for the destination
attribute. Previous versions of ColdFusion required the filename only.
|
39564 |
Added username and password attributes
to the cfmail tag
for those mail servers that need to verify a user before sending an e-mail
message.
|
44733 |
An "illegal target of jump or branch" error
often occurred when a large CFML file had a switch statement spanning the
entire file. |
44931 |
When the OS Locale was set to English (Australian), the cfdirectory tag
returned the date object in a format not accepted by the DateFormat function. |
45093 |
When <cfset var...> was
not at the top of the cffunction block, an "UnmatchedEndTagException" was
thrown. |
45471 |
The cfhttp tag did
not allow custom headers. |
45813 |
The cffile tag threw a nondescriptive exception
message, "The
cause of this exception was: sun.io.MalformedInputException," when using the
wrong value for the charset
attribute when action="read". |
46480 |
ColdFusion MX threw an error if you specified
a cookie name that is not a valid ColdFusion variable name. |
46536 |
Using the cfftp tag with the getfile action
and not specifying a full path to the file placed the file in a nonobvious
directory. |
46687 |
If you specified a structure for argumentcollection and
you also specified any argument as an attribute of the cfinvoke tag,
ColdFusion threw an error saying that the value specified in argumentcollection didn't
exist.
|
47014 |
The cffile tag with makeunique set
to True reached a hard limit of 237 files uploaded when looping
238 or more times. |
47108 |
The cfchart tag failed with more than 16 series.
See TechNote
18673 for additional details. |
47279 |
A connection failure occurred when attempting to use the cfhttp tag
to access an internet site from behind a firewall. |
47322 |
An extra closing cfif tag correctly threw a 'context validation' error
but ColdFusion did not report the line number of the bad tag. |
47433 |
When the number of columns returned from a cfhttp tag did
not match the number of columns specified, cfhttp threw
an error instead of ignoring the missing columns. |
47541 |
If you called a template that used the cflocation tag
from a browser with cookies turned off, ColdFusion would generate a URL with
an improper query string for Jsession
(script_name;JSESSION=...) . |
47677 |
Using the cffile tag to write a number to a file threw
an error. |
47686 |
If mail was in the spool with HTML format and ColdFusion was restarted,
the spooled mail would be sent as plain text. |
47731 |
ColdFusion MX returned Replication IDs (GUIDs) as
a byte array, whereas ColdFusion 5 returned them as strings. |
47831 |
Using cffile action="upload/copy" without specifying a
full pathname caused errors. With action="upload", the cffile tag
threw an Invalid Destination exception. With action="copy",
the cffile tag copied
the file to the temp directory instead of the source directory. |
48012 |
The cfhttp tag failed to time out. A timeout
error was returned only after the called URL timed out. No timeout was returned
if the called URL
did
not
complete. |
48190 |
The cfhttp tag did not communicate over SSL to proxy
servers, even when HTTPS was specified in the URL. |
48216 |
ColdFusion MX sent a Cache-control: no-cache header. |
48231 |
If you had a call to a custom tag that took content inside
a cfoutput tag that
used the
group attribute, and the code inside the custom tag did the inner cfoutput,
only one row was printed in the inner loop. |
48392 |
Using the cfpop tag to access the contents of
a mailbox stripped out most of the line breaks from the headers. |
48566 |
When the cfftp tag encountered an invalid date, it generated
an IllegalArgumentException error. |
48616 |
When using the cfchart tag, unexpected sorting
behavior occurred when charting multiple series. |
48800 |
Using the cfgrid tag and the ODBC Socket/MS Access
driver to update a memo field with double-byte data in an Access database caused
a ColdFusion
MX SequeLink
JDBC internal error. |
49007 |
Submitting a selected row in the cfgrid tag that
contained NULL values from a database query produced the error "The submitted
cfgrid form field is corrupt." |
49116 |
If you used a cfhttp tag with POST data inside
of a loop, the first call executed correctly, but all subsequent calls would
not
have the form data. |
49182 |
Japanese version: A query of queries failed when you used
certain double-byte characters, including a Unicode-encoded single quotation
mark
('), in the WHERE clause. |
49189 |
The cfimport tag did not use cfmappings to look up
folders. |
49196 |
When using the cfmailparam tag to attach files with Japanese
characters as the filename, the attached filename would be corrupted. |
49240 |
A Null value was not being set with WDDX. |
49269 |
Single-quotation marks were not always escaped by the cfquery tag. |
49468 |
If you specified proxy settings in a cfhttp tag,
the settings were ignored. See TechNote
18602 for additional details. |
49488 |
Mail spooler logic was incorrect, and only sent half of the spooled
messages in each iteration. If new mail was being added frequently, some
email messages
might not be sent. |
49504 |
The cfquery group function didn't
work if a cfsavecontent tag
contained a child cfoutput tag. |
49513 |
A self-closing cfdefaultcase tag caused an error. |
49595 |
The cfhttp tag hard coded the "Content-Type: application/pdf" header
to MIME parts of files attached with cfhttpparam type="file". |
49704 |
If you attempted to use the cfldap tag to delete a
single value from a multivalue attribute, ColdFusion threw an exception. |
49707 |
When using the cfcontent tag to download a file, if you
specified a filename with double-byte Japanese characters, the filename
would get
corrupted. |
49769 |
When using the cfpop tag, if the parent message was multipart/*
(report, alternative, and so on ) and contained an embedded message
that was also multipart/*, ColdFusion threw
an exception. |
49779 |
Using dates to set the expiration
in a cfcookie tag did not work correctly. |
49787 |
When you used the cffile action="upload" tag,
the fileWasOverwritten value
always was "Yes" if you specified the conflict="overwrite"
attribute. |
49851 |
When looping over a cfhttp get, only the first file was
retrieved successfully.
|
49895 |
The cfgridupdate tag would return a "cfgridupdate
could not find the row to update or delete" error even
though the record was updated. |
49947 |
When a cffile tag delete action followed an upload with
the cfftp tag,
the file would be locked and it would throw an error "Attribute validation
error for tag CFFILE." |
49950 |
ColdFusion MX processed currency entries in a different form than
ColdFusion 5. |
49959 |
Running a large number of cfmail tags with a
short mail interval set caused ColdFusion to send duplicate mail messages. |
50015 |
ColdFusion did not close named cfftp connections properly. |
50091 |
The cfdirectory tag's list action always set
a blank mode value. |
50148 |
The cfselect tag's required attribute did not
work. |
50272 |
ColdFusion MX produced an error when an invalid attribute
was used in a cfinput tag.
ColdFusion 5 did not produce an error for the same code. |
50310 |
The value of the cffile.serverFileName variable was not
correct. |
50433 |
When using the cfftp tag to retrieve directory information
from a Microsoft FTP server, the directory list returned nothing if there
was
only one file in
the target folder. |
51100 |
A query of queries DISTINCT on BIT column caused a Java casting error. |
51391 |
Putting an invalid character, such as a comma, in a cookie name in the cfcookie
tag caused ColdFusion to generate an empty page. |
52374 |
Text was truncated in a cfcontent tag used inside
of custom tags when the execution mode was End. |
52661 |
When using the cfcontent tag to set the page encoding type,
the remainder of the page did not appear and ColdFusion truncated
characters from the end of the HTML output. |
52737 |
The cfdirectory tag was not thread-safe. |
52039 |
The cfldap tag did not handle rebind correctly. |
52467 |
Using both the cfsilent tag and the cfexit tag
in a custom tag could cause errors. |
Back to Contents
Code Analyzer
39428 |
Some of the regular expressions in ColdFusion Administrator
code didn't meet the new standards. |
44684 |
The Code Analyzer did not recognize that Scope names are reserved words
in ColdFusion MX where they were not in ColdFusion 5. (It still cannot
identify
issues with dynamically named variables.) |
47517 |
If a session timed out while running the Code Analyzer and
you clicked one of the icons, the feature, or the document link, the
Administrator login screen appeared. If you entered the Administrator password,
the Code Analyzer screen appeared with the Code Analyzer Return to Feature,
Print Report, and Close Window links in a frame at the top, the Administrator
menu to the left in a frame, and a blank blue frame in the main body of
the screen. |
49229 |
The behavior of the cfprocparam tag maxlength attribute was changed for
ColdFusion MX, but the Code Analyzer failed to issue warnings about the
change. |
Back to Contents
ColdFusion components
34762 |
A cfinclude tag used in a cffunction tag did
not inherit access to the Arguments,
local variables, and This scopes. |
38118 |
Variables set in the Variables scope in components were not available
in the unprefixed scope. |
44580 |
When a component method was invoked dynamically, the arguments
had to be passed individually, not as part of the ArgumentCollection. |
45138 |
There was an overlap between the Variables scope of the calling page
and that of the CFC. |
45387 |
Variables declared without a prefix weren't accessible with the Variables
prefix within a CFC function. |
45655 |
When creating a ColdFusion component for Flash Remoting, adding a roles attribute
in the cffunction tag caused Flash to not recognize the function. |
46981 |
Added the Super keyword, which lets you call
overridden methods. |
48093 48234 |
CFC lookups on UNIX did not default to the lowercase filename. |
49602 |
Invalid characters in a cffunction tag name attribute
weren't
caught by the ColdFusion MX compiler. |
49705 |
cfquery tags used in CFCs did not participate
in cftransaction operations
of the code that called them. |
50100 |
ColdFusion MX did not search for both the given (case-correct)
name and the all-lower-case name for custom tags and components on UNIX. |
51062 |
A Variables scope variable on included pages couldn't be
found. |
Back to Contents
COM
|
Enhancement |
COM support has been upgraded to use J-Integra Release 1.5.5. |
Enhancement |
A new ReleaseCOMObject function releases COM object resources
immediately. Previously, the resources were not released until the Java
garbage collector
cleared them. For more information, see the
CFML
Reference. |
Enhancement |
ColdFusion can now handle COM objects that do not have a classID or progID. |
44527 |
The cfdump tag can now dump COM objects, and displays the
methods and Get and Put property TypeInfo of the object. |
46305 |
ColdFusion MX did not manage COM object reference counts properly. If
you instantiated one COM object explicitly using a cfobject tag,
called a method of that COM object to instantiate a second COM object,
then explicitly
destroyed both objects, ColdFusion MX did not destroy the second object. |
47371 |
In some cases, using stubs generated by com2java would generate
exceptions. |
48092 |
If you used the cfobject tag to call a Crystal
Reports DLL, the DLL would not be released from memory. |
48530 |
ColdFusion could not handle user-defined types. ColdFusion
now tries to cast the type to a simple type or an object. |
48564 |
ColdFusion could not assign values to properties of the RightFax
COM object coversheetnotes. |
48896 |
A COM object method that returned a COM object caused a "method
selection" error. |
48916 |
ColdFusion threw a code error when building an argument
list for the style sheet and code while attempting XSL processing with the
msxsml2 parser. |
48925 |
You could not use a cfloop tag to loop over a collection
of collections. This could cause an issue for most COM objects that are
written
in Visual
Basic. |
48964 |
When two empty string variables were passed by reference to two different
COM objects, their values got mixed up in memory. |
49692 |
When a method argument was
described in the TypeInfo as VT_USERDEFINED, ColdFusion passed it
as VT_DISPATCH. |
49836 |
When calling a COM object method with an int as an input
argument, ColdFusion MX threw a "java.lang.RuntimeException: Can not handle
VT 22" error. |
49840 |
If you created an Excel object and called the Excel quit
method, the Excel process did not exit. Running
a page
multiple
times
could result in multiple Excel processes. |
50026 |
When TypeInfo for a method specified VT_VARIANT, and ColdFusion
MX passed a COM object as an input parameter, the passed COM object was
prematurely released. |
50354 |
Using the Outlook COM object caused an index of out bounds
error. |
50427 |
Excel COM object methods that return IDispatch produced
objects with methods that could not be called. |
50747 |
Memory was not released correctly. |
Back to Contents
Database
| 45816 |
The cfquery tag occasionally threw the exception "[Macromedia][SQLServer
JDBC Driver]No ResultSet set was produced." |
47822 |
The SQLServer data type REAL with NOT NULL could not be retrieved
by the JDBC driver.
|
48745 |
ColdFusion MX terminated varchar strings returned by an Oracle stored
procedure at 4001 characters. |
48773 |
When using the Oracle OCI8 Type 2 driver or Oracle JDBC Thin Type 4 driver
to insert blob data, the error "Error casting an object of type [B to
an incompatible type" was generated. |
49715 |
A data type such as Oracle number(22) lost precision to 12
digits when referred to as a variable and used in a second cfquery tag.
Sybase was also affected. |
49733 |
Using the ColdFusion driver to select a CLOB field from
a DB2 database threw a "String index out of Range" exception. |
49753 |
The cfstoredprocparam tag failed to insert NULLs into CF_SQL_NUMERIC
and CF_SQL_INTEGER, but not CF_SQL_VARCHAR. |
49775 |
Client variable storage to an Oracle database using the ColdFusion
JDBC driver threw exceptions under load when large amounts of text data
were stored.
|
| 50588 |
When using the char data type in an Informix 9.21 database
accessed using the ColdFusion Informix driver, if the field type was 4093
( my_field
char( 4093 )) or higher, any SELECT statements
failed with a "Column size too large" error. |
51595 |
Doing a number of insert queries within a cftransaction block
with a string that contained a single-quotation mark caused ColdFusion
MX to throw an error. |
| 52014 |
DB2 users had to put all SQL statements in a query
on a single line when using the ColdFusion MX DB2 driver. The ColdFusion
MX 6.1 driver now automatically strips newlines from the SQL. |
52378 |
A query of a query of queries that was generated with the maxrows attribute
did not produce the expected results. |
52419 |
Some ODBC data sources could not be verified after upgrading from
ColdFusion 5 due to errors in port number migration. |
52485 |
A database query that ran longer than the data source timeout
could hold up all attempts to get a connection until it completed if the data
source was pooled. For more information on this problem, see
ColdFusion Technote 18772 |
52567 |
If the database timeout was set to less than the data source
timeout, a deadlock could occur in any Oracle driver, causing ColdFusion to
hang.
For
more information on this problem, see
ColdFusion
Technote 18772 |
| 52639 |
JNDI data sources configured using a J2EE server appeared
in the ColdFusion MX Administrator Data Sources page, but not in the drop-down
list of data
sources on the Client Variables page. |
Back to Contents
Debugging
45798 |
Once any user received debugging output, the IsDebugMode function
always returned Yes, even if the current browser's IP Address
was not in the "debugging
IP addresses" list. |
47173 |
The Error message for a syntactically invalid SQL statement did not
include the statement. |
48477 |
The cftrace timestamp value did not change after the
first trace point. |
48690 |
There was an error in the information output of the ColdFusion MX classic.cfm
debugging template. |
Documentation
The ColdFusion Documentation group has made over one hundred fixes to
the documentation set. In particular, the CFML Reference has undergone extensive
improvement,
including application of many LiveDocs comments.
Back to Contents
Exception handling
39265 |
The cflocation tag did not work correctly inside
an error handler. |
44651 |
When using the cfinvoke tag to call a template
that did not exist, the error was reported to be in the wrong line number. |
45604 |
A grouped cfoutput tag with an invalid group column
threw an ArrayIndexOutOfBoundsException error instead of returning an informative
error message. |
48089 |
A server-side ActionScript context could throw nontranslated
errors when required parameters were not passed to the special versions of
the cfhttp and cfquery tags
in server-side ActionScript. |
48921 |
The site-wide error handler displayed incorrect output behavior. See
TechNote
18681 for additional details. |
Flash integration
| 45655 |
Setting roles="" in a CFC function
caused the Flash Authoring service browser to fail browsing anything within
the component.
|
Back to Contents
General server
45017 |
The HTTP_USER_AGENT value for the cfhttp tag was set as "Java1.3.0" instead of "ColdFusion" as in previous versions. |
45253 |
URLs of the style downloader.cfm/filename.txt did not work with the
IIS connector. |
46095 48216 |
Under certain circumstances, ColdFusion would include
the following HTTP headers in a response: Expires: Thu, 01 Dec 1994
16:00:00 GMT
Cache-Control: no-cache="set-cookie,set-cookie2"
As a result, refreshing or backing up to a page that was the result of a
POST request would produce a "Warning: Page has Expired" message.
Refreshing or backing up to a page that was the result of a GET request
would cause the GET request to be re-sent to the server; if this page contained
a form tag, the form fields wouldn't have the values
that the user previously entered. |
47271 |
The scheduler would only run approximately 16 tasks scheduled
at the same time. |
47462 |
When using the SunOne iPlanet Server 6.0 as the web server, ColdFusion
did not make several CGI variables available in the CGI scope. |
48778 |
When an XML document object text node was written with CDATA,
the CDATA tag was incorrectly escaped. |
48876 |
When a template was restored to the server, ColdFusion MX continued to
run the previous version and not the backup version that was restored.
This was because the modified date was older than the cached version. |
48912 |
The Developer Edition did not reset the allowed IP address following
a restart of the ColdFusion service. |
48961 |
There was an issue when storing Client scope data with a pound sign as
the last or only character when the Client data store was a database.
|
49236 |
The jikes.exe compiler could bring the server's CPU usage to 100% and
never let go. |
49935 |
The way ColdFusion MX worked with structures as pointers
differed from ColdFusion 5. |
49973 |
Writing to a ColdFusion MX session using the put method
on the casted Map object would throw an UnsupportOperationException error
with named applications. |
52714 |
Submitting a form with a large number of fields could intermittently
result in an HTTP status of '500 Resetting to invalid mark'. |
52816 |
When doing an exclusive lock with scope="session",
ColdFusion MX locked all Session scopes and not just the Session scope
of the request. |
Back to Contents
Internationalization
49234 |
Use UTF-8 as the default character set encoding (defined in the cf_root/lib/neo-runtime.xml file). |
49904 |
ColdFusion MX and ColdFusion MX J2EE could not correctly handle
non-ASCII characters in Client variables in the registry. |
50415 |
In Asian Locales, the LSEuroCurrencyFormat function
did not generate output with a Euro symbol or EUR text prefix; it used the
locale's
currency symbol and text instead. |
Back to Contents
Installation and configuration
35173 |
The installer installed the Win32 and UNIX CFX header
files on all operating systems. |
37230 |
On UNIX and Linux, custom tag paths were migrated correctly
but threw an error. |
37749 |
The Migration Wizard is no longer a pop-up. |
38034 |
Errors could occur when the wizard was migrating Client variables. |
38993 |
The Migration Wizard did not migrate SQLOLEDB data sources. |
44787 |
The Migration Wizard failed if expected ColdFusion 5 registry
keys were missing, particularly when installing ColdFusion 5 and then ColdFusion
MX (standalone).
|
44816 |
During the installation, passwords for the Administrator and RDS
weren't
hidden. |
44829 |
An error occurred during data source migration on UNIX and
Linux platforms when the ODBC data sources existed in the ColdFusion 5 cfregistry
but
not in the ColdFusion 5 odbc.ini
file. |
44972 |
The ColdFusion MX Application Server service did not start automatically
following a Windows startup or reboot. |
45217 |
The Migration Wizard did not copy
all user data from ColdFusion to ColdFusion MX. |
45324 |
ColdFusion 4.5.0 to ColdFusion MX migration reported "Element
LANGUAGE is undefined in ITEM. ()" when migrating Verity collections. |
45414 |
Windows 98 ColdFusion 5 to ColdFusion MX migration failed
to copy client variable data from the ColdFusion 5 registry branch to
the ColdFusion MX registry. |
46161 |
Migration of Verity collections was not done after full installation
of ColdFusion MX and Verity Language locales if any collections were created
with a non-English language. |
47414 |
Installation of ColdFusion MX on a Japanese operating system
(choosing to migrate from ColdFusion 5J, not co-exist) removed the registry
keys
created
by
other Macromedia
products. |
49000 |
When the Installation Wizard probed for RDS, an error was thrown to
stdout on JRun.
|
49427 |
The jvm.config classpath setting in ColdFusion MX had an additional
path.
|
49783 |
Updaters did not install fully because the ColdFusion MX service did
not properly stop jrun.exe. |
50225 |
The Installer did not back up the Updater 2 version of wsconfig.jar or
the /wsconfig directories.
|
51890 |
ColdFusion and associated links were not put in the Macromedia
folder in the Start Menu, but in an independent Macromedia ColdFusion
MX folder. |
Back to Contents
Other
47287 |
(Performance) The ColdFusion MX cftree tag took
significantly longer to process than it did in ColdFusion 5. |
45767 |
(Remote access from client) There was an extra space in
the URL of the Administrator page when selecting to administer a
server
via RDS. |
Security
| 46806 |
A security hole existed in RDS.
|
47786 |
The Cflogin scope was independent of the Session scope. It
can now be tied to the Session scope. |
48559 |
There was a security issue with the cflogin tag. |
49304 |
The Cflogin scope was not populated properly when using IIS
5.1. |
Back to Contents
Verity
49010 |
Verity failed to index PDF files created with Acrobat Distiller
4.05. |
49728 |
Searching K2 collections on ColdFusion MX was slower than with
ColdFusion 5. |
51176 |
Using the cfif tag inside a cfquery tag caused
Verity to not index the title of the document. The same documents indexed
on ColdFusion
5 had their titles indexed. |
52540 |
The stopK2server script did not work on HPUX 11. |
Back to Contents
WDDX
45438 |
The cfwddx tag created a bad
packet when serializing a structure with a key that contained a single-quotation
mark such as foo["l'name"]="baker". |
46614 |
A WDDX null string did not
deserialize.
|
47716 |
Large WDDX packets (around 10 MB) could be read from a
file in ColdFusion 5, but failed in ColdFusion MX. |
49240 |
A null value could not be set using the cfwddx tag. |
Web services
44912 |
Dashes in the filename caused an error in WSDL
generation, although the component worked.
|
44924 |
CFCs didn't work as web services when nonalphanumeric characters
were used in CFC names, method names, or argument names. |
45709 |
If any directory within the path of a CFC used only numeric digits in
its name, Axis would generate an error when the WSDL for that CFC was
browsed.
|
45949 |
Web services could not be consumed from behind a proxy server. |
Back to Contents
More information about this release
©2003 Macromedia, Inc. All rights reserved.
|
