displaying top 100 results
Tracker Issue TimeFormat backward compatibility bug
TimeFormat backward compatibility bug
Tracker Issue replaceList backwards compatibility problems
replaceList backwards compatibility problems
Tracker Issue Backward compatibility issue with CF11
Backward compatibility issue with CF11
Portal Topic Axis-2 and Axis-1 compatibility issues in ColdFusion
Axis-2 and Axis-1 compatibility issues in ColdFusion
Comment on replaceList backwards compatibility problems by External U.
Comment on replaceList backwards compatibility problems by External U.
Comment on replaceList backwards compatibility problems by External U.
Tracker Comment Comment on Backward compatibility issue with CF11 by External U.
Comment on Backward compatibility issue with CF11 by External U.
Tracker Comment Comment on Backward compatibility issue with CF11 by Rupesh K.
Comment on Backward compatibility issue with CF11 by Rupesh K.
Tracker Comment Comment on TimeFormat backward compatibility bug by Dattanand M.
Comment on TimeFormat backward compatibility bug by Dattanand M.
Comment on replaceList backwards compatibility problems by External U.
Tracker Comment Comment on Backward compatibility issue with CF11 by External U.
Comment on Backward compatibility issue with CF11 by External U.
Tracker Comment Comment on Backward compatibility issue with CF11 by External U.
Comment on Backward compatibility issue with CF11 by External U.
Tracker Comment Comment on Backward compatibility issue with CF11 by External U.
Comment on Backward compatibility issue with CF11 by External U.
Tracker Comment Comment on TimeFormat backward compatibility bug by Dattanand M.
Comment on TimeFormat backward compatibility bug by Dattanand M.
Comment on Backward compatibility issue with CF11 by Himavanth R.
Comment on Backward compatibility issue with CF11 by Himavanth R.
Comment on replaceList backwards compatibility problems by CFwatson U.
Tracker Comment Comment on Backward compatibility issue with CF11 by External U.
Comment on Backward compatibility issue with CF11 by External U.
Tracker Comment Comment on Backward compatibility issue with CF11 by External U.
Comment on Backward compatibility issue with CF11 by External U.
Tracker Comment Comment on Backward compatibility issue with CF11 by External U.
Comment on Backward compatibility issue with CF11 by External U.
Comment on replaceList backwards compatibility problems by CFwatson U.
Tracker Issue Revert Jetty libraries to version 7 on Solaris 11 due to compatibility issues with Jetty 9.
Revert Jetty libraries to version 7 on Solaris 11 due to compatibility issues with Jetty 9.
Tracker Issue Dramatic change to CF9's implementation of CFQuery causes major backwards compatibility issues
Dramatic change to CF9's implementation of CFQuery causes major backwards compatibility issues
Tracker Comment Comment on Dramatic change to CF9's implementation of CFQuery causes major backwards compatibility issues by Sanjeev K.
Comment on Dramatic change to CF9's implementation of CFQuery causes major backwards compatibility issues by Sanjeev K.
Tracker Comment Comment on Dramatic change to CF9's implementation of CFQuery causes major backwards compatibility issues by External U.
Comment on Dramatic change to CF9's implementation of CFQuery causes major backwards compatibility issues by External U.
Tracker Comment Comment on Dramatic change to CF9's implementation of CFQuery causes major backwards compatibility issues by Aaron N.
Comment on Dramatic change to CF9's implementation of CFQuery causes major backwards compatibility issues by Aaron N.
Comment on Bug 79313:Backwards compatibility is broken through the new implicit getter/setters from the use of when onMissingMethod() is used to provide similar functionality by External U.
Comment on Bug 79313:Backwards compatibility is broken through the new implicit getter/setters from the use of when onMissingMethod() is used to provide similar functionality by External U.
Bug 78715:The new, implicit "local" scope within a breaks backwards compatibility with previous versions of CF when creating a var'd variable called "local"
Comment on Bug 79313:Backwards compatibility is broken through the new implicit getter/setters from the use of when onMissingMethod() is used to provide similar functionality by External U.
Bug 79313:Backwards compatibility is broken through the new implicit getter/setters from the use of when onMissingMethod() is used to provide similar functionality
Bug 81714:(Watson Migration Closure)Please make backwards compatibility setting for JSON serialization numeric fix available as a setting in the administrator instead of requiring modification of the JVM config file
Comment on Bug 78715:The new, implicit "local" scope within a breaks backwards compatibility with previous versions of CF when creating a var'd variable called "local" by External U.
Comment on Bug 78715:The new, implicit "local" scope within a breaks backwards compatibility with previous versions of CF when creating a var'd variable called "local" by External U.
Comment on Bug 78715:The new, implicit "local" scope within a breaks backwards compatibility with previous versions of CF when creating a var'd variable called "local" by External U.
Tracker Comment Comment on GetPageContext().getRequest().getParameter('param_name') is undefined by External U.
2613565 CF-3222889 External U. Please treat this as a bug.
1) this maintains backward compatibility with existing applications.
2) it will maintain CFML / JSP compatibility
5120520 CF-4203580 Aaron N. +1 - CF2018's behavior, when null support disabled, should match CF2016's. The entire reason for maintaining backward-compat was, well, to maintain backward-compat ;)
Cold Fusion 2016 Compatibility with Windows Server 2016
Comment on Cold Fusion 2016 Compatibility with Windows Server 2016 by Michael Thomas
Tracker Comment Comment on [ANeff] Bug for: queryNew() not respecting column type by Vamseekrishna N.
2608346 CF-4117243 Vamseekrishna N. This will have backward-compat issues
2613912 CF-3148706 Rupesh K. The decision is not to break any backward compatibility for CF12.
Security Analyzer Does not warn about CFMX_COMPAT algorithms
Tracker Comment Comment on Can no longer include non CFML files by External U.
2610332 CF-3710270 External U. Considering how important "backward compatibility" is when denying so many enhancement requests, to break backward compatibility like this in a way that can only be overridden by manually modifying server-wide configuration files and restarting the service is insane
Portal Comment Comment on Is Adobe ColdFusion (2018 release) backward-compatible with previously released versions of ColdFusion? by erodrig911
Comment on Is Adobe ColdFusion (2018 release) backward-compatible with previously released versions of ColdFusion? by erodrig911
Portal Comment Comment on Is Adobe ColdFusion (2018 release) backward-compatible with previously released versions of ColdFusion? by dorothyp22194219
Comment on Is Adobe ColdFusion (2018 release) backward-compatible with previously released versions of ColdFusion? by dorothyp22194219
Tracker Comment Comment on UNIX and Windows CFINCLUDE inconsitancy by Poonam J.
4084966 CF-4201529 Poonam J. As mentioned below, this is as Designed. Fixing this will break backward compatibility. Closing this track.
Tracker Comment Comment on queryExecute doesn't like single-quotes in sql-style comments by Scott B.
3375340 CF-4199452 Scott B. It's not a huge deal, but it affects backward compatibility for no beneficial reason
2608346 CF-4117243 Nimit S. Aaron,
It will have backward compatibility issues. We recommend not to fix this issue.
-Nimit
Tracker Comment Comment on CFID & CFTOKEN include "hash" prefix this is not compatible with previous versions by External U.
Comment on CFID & CFTOKEN include "hash" prefix this is not compatible with previous versions by External U.
Tracker Comment Comment on Deprecate `int` in favour of `floor` by Nikhil S.
2608625 CF-4044533 Nikhil S. Added the Floor() function which acts the same as Int() function. Int() is not removed for backward compatibility.
Tracker Comment Comment on Null by External U.
2608750 CF-4010516 External U. I agree but i think a switch to enable/disable the functionality would be great as there will be a lot of backward compat issues.
Tracker Comment Comment on Null by External U.
2608750 CF-4010516 External U. backwards compat be damned. If you want to compete against the big boys it's time to get this sorted out.
Tracker Comment Comment on Null by External U.
2608750 CF-4010516 External U. +1 as this is way overdue. If backwards compatibility is an issue, maybe include a way to toggle the behaviour - but make this per application not per CF server!
Tracker Comment Comment on Null by External U.
2608750 CF-4010516 External U. ColdFusion needs NULL support, to hell with backwards compatibility. Please implement real NULL support!
Tracker Comment Comment on cfstoredproc problem in cf11 update 3 by External U.
2608777 CF-4001377 External U. dbVarName can be rather important and backwards compatability should be maintained.
Tracker Comment Comment on CFScript 2.0 by External U.
2609610 CF-3822362 External U. This would be a nice way to fix cfscript without having to worry about backward compatibility.
Tracker Comment Comment on Updating structkey presevation doesn't work unless you edit the CFM by Nimit S.
2609626 CF-3818776 Nimit S. This fix has been reverted because of a backward compatibility issue.
Tracker Comment Comment on writeLog(), throw(), writeDump() not implemented as fucntions correctly by External U.
2609737 CF-3788414 External U. I'd be curious to see what real backward compatibility issues are at play here.
Comment on CFTEXTAREA richtext="true' and IE 10+ - NOT COMPATIBLE by External U.
Tracker Comment Comment on InputBaseN returns incorrect result by S P.
2610306 CF-3712098 S P. Although this bug is fixed, there seems to be a backward-compatibility issue. As a result, this fix will be part of next release.
Tracker Comment Comment on Fix the isValid('integer') function or Provide a Version that actually does work by External U.
2610311 CF-3712010 External U. There is no question this should be fixed. (Backwards compatibility is not an acceptable reason to defer this bug.)
Tracker Comment Comment on casting to DATE do not do what they imply they do: it simply returns a full date+time. by Himavanth R.
2610651 CF-3688938 Himavanth R. Too risky.
Will have backward compatibility issues.
Tracker Comment Comment on deserializeJson does not properly handle high-ascii characters by External U.
2612661 CF-3476661 External U. Compatibility issues continue to plague the JSON functions and should be addressed as a priority.
Tracker Comment Comment on json serialization by Rupesh K.
2596935 CF-3342785 Rupesh K. This is a fundamental behavior of CFML where yes/no is automatically converted to boolean and changing this will cause backward compatibility issues. Deferring this.
Tracker Comment Comment on GetPageContext().getRequest().getParameter('param_name') is undefined by External U.
2613565 CF-3222889 External U. This should be fixed to ensure backwards compatibility. If it worked it 9, it should in 10.
2613619 CF-3199281 External U. Really needs to be fixed to maintain backwards compatibility.
Tracker Comment Comment on IsValid("integer") does not exclude some none-numeric characters by Rupesh K.
2597048 CF-3169196 Rupesh K. This has always been the behavior and changing this would result in backward compatibility issue. It will not be fixed.
2613912 CF-3148706 External U. Okay, you can break backward-compat now in CF12 and fix properly.
Thanks!,
-Aaron
Tracker Comment Comment on Bug 78588:When using Mach-II 1 by External U.
2600303 CF-3039173 External U. Important for Mach-II compat; please consider fixing.
Tracker Comment Comment on Calling GetHttpRequestData() in application.cfm breaks REST services by Aaron N.
2611853 CF-3581691 Aaron N. Backward-compat (JRun behavior) should've been maintained.
Tracker Comment Comment on writeLog(), throw(), writeDump() not implemented as fucntions correctly by External U.
2609737 CF-3788414 External U. Go on then... do tell... what is an example of a potential backwards compat issue you perceive here. An actual *real world* example.
You can't just say "backwards compat" and then not demonstrate how this is the case.
2609741 CF-3787631 External U. I've verified this is fixed in CF11 Update 3. The default value of reuseInstance is false, which maintains backward-compatibility. Good, b/c opting into performance improvement here is probably preferred over opting into backward-compat.
Thanks!,
-Aaron
2613912 CF-3148706 External U. Hi Immanuel,
Regarding: "Changing the attribute name would result in backward compatibility issues."
Yes, b/c Adobe's replies came nearly 2 years after I filed this ER. I filed this during CF10 Public Beta. At that time, backward compatibility wasn't an issue
Tracker Issue [ANeff] Doc Bug for: lack of String member functions on NULL creates backward-compat issue
[ANeff] Doc Bug for: lack of String member functions on NULL creates backward-compat issue
specify a specific compatibility mode.If we have a 10 page source PDF, and the thumbnail call works on the source PDF...Then if we open that PDF in Acrobat X Pro and extract page 1, and save that single page as a new PDF, the new PDF will cause the ACTION="THUMBNAILS" call to fail.We have been able
Portal Topic Is Adobe ColdFusion (2018 release) backward-compatible with previously released versions of ColdFusion?
Is Adobe ColdFusion (2018 release) backward-compatible with previously released versions of ColdFusion?
We are planning to upgrade RHEL 7.3 Linux server and wanted to know is this compatible with Coldfusion 11. And if no, then suggest us what would be the best option to do from our end. Could you please confirm the same.
their code slightly. It's also a very SIMPLE refactor. I know that backwards-compat has some sort of grail-like status with the CF team - and this is usually good - but, face it, there are always backwards compat issues with each CF release anyhow, and this particular backwards compat issue would be one
Portal Topic ColdFusion 2016 Support for SQL 2019?
christopheru99796564 ColdFusion 2016 Support for SQL 2019? ColdFusion 2016 Support for SQL 2019?
The post ColdFusion 2016 Support for SQL 2019? appeared first on ColdFusion. Discussion,Updates,2016,compatibility,discussion,updates
Portal Comment Comment on Cold Fusion 2016 Compatibility with Windows Server 2016 by Charlie Arehart
Comment on Cold Fusion 2016 Compatibility with Windows Server 2016 by Charlie Arehart
Tracker Issue Bug 82576:cfexchange tags are not compatible with Exchange Server 2010, presumably because Exchange 2010 no longer uses WEBDAV
Bug 82576:cfexchange tags are not compatible with Exchange Server 2010, presumably because Exchange 2010 no longer uses WEBDAV
Tracker Issue [ANeff] Bug for: lack of String member functions on NULL creates backward-compat issue
[ANeff] Bug for: lack of String member functions on NULL creates backward-compat issue
Tracker Comment Comment on When enablecfoutputonly is on, output cascades into included templates. by Nimit S.
2608159 CF-4177084 Nimit S. Thanks Stephen for pointing this out.
This is a very old behavior. I am able to repro the same issue on CF8 as well.
Fixing this issue may break backward compatibility.
Tracker Comment Comment on Security Analyzer Does not warn about CFMX_COMPAT algorithms by CFwatson U.
Comment on Security Analyzer Does not warn about CFMX_COMPAT algorithms by CFwatson U.
Tracker Comment Comment on [ANeff] Bug for: Code Analyzer doesn't warn when assigning local to non-struct by Nikhil S.
2608401 CF-4101908 Nikhil S. Code Analyzer only checks the conflicts/compatibility issues of Functions and Tags. This type of errors are handled during runtime.
Tracker Comment Comment on [ANeff] Bug for: Code Analyzer doesn't notify about cflocation's addtoken default value change by Nikhil S.
2608402 CF-4101905 Nikhil S. added the file compatibility.xml to the build.xml. Now it should be included in the HF build.
Tracker Comment Comment on CFID & CFTOKEN include "hash" prefix this is not compatible with previous versions by External U.
Comment on CFID & CFTOKEN include "hash" prefix this is not compatible with previous versions by External U.
Tracker Comment Comment on CFID & CFTOKEN include "hash" prefix this is not compatible with previous versions by Aaron N.
Comment on CFID & CFTOKEN include "hash" prefix this is not compatible with previous versions by Aaron N.
Tracker Comment Comment on cfquery query of queries count(*) returns nothing when there are 0 rows by Rupesh K.
2608593 CF-4054576 Rupesh K. We had fixed this in some earlier release but the fix was reverted because of the backward compatibility issues.
Tracker Comment Comment on cfquery query of queries count(*) returns nothing when there are 0 rows by External U.
2608593 CF-4054576 External U. I'm keen to know what real-world backwards compatibility issues you encountered, Rupesh.
Tracker Comment Comment on Member functions for encoding by External U.
2608653 CF-4033628 External U. Hi Pavan,
Thank you very much for considering.
Hi Adam,
I'm looking forward to Aether fixing stuff by busting backward-compat like none other :)
Thanks!,
-Aaron
2608707 CF-4019629 Vamseekrishna N. This has backward-compatibility implications. We'd made this change but saw several applications break because of the change, and had to eventually roll-back the fix.
2608707 CF-4019629 External U. Hi all,
"The decision is not to break any backward compatibility for CF12."
Please see Adobe's comment on CF-3148706.
Thanks!,
-Aaron
Tracker Comment Comment on In CF11 (not 9) , structKeyExists() returns false when cfdump shows true. Which is it? by External U.
2608793 CF-3993581 External U. Voting primarily because this appears to be a regression in behavior. That said, also voting to fix null and break backwards compat.
Tracker Comment Comment on Daily task w/o startDate gives a bad error by Uday O.
2609116 CF-3928030 Uday O. @Suchika Handled point 1. Rest 2 can cause backward compatibility issues, so avoiding them
2609166 CF-3916950 External U. +1. Can't see any backwards compat issues with this? Just need to check if the usage already has the prefix for the given DB platform, and if not: append it.
Tracker Comment Comment on isDate('16.51p') eq true by External U.
2609313 CF-3859758 External U. +1 to fixing this in ColdFusion 12, backward-compatibility be darned. Rip the band-aid off now and get it over with.
Tracker Comment Comment on Calling Randomize() with the SHA1PRNG does not create "repeatable number patterns". by External U.
2609722 CF-3792283 External U. In CF10, the IBMSecureRandom algorithm also has the same issue. Only the CFMX_COMPAT algorithm gives "repeatable number patterns".
2609729 CF-3791392 Rupesh K. The earlier addition of uppercased extention for .cfm and .cfc was done to keep the backward compatibility. For REST, there is no such issue. This would not be done.