displaying top 100 results
Tracker Comment Comment on Regression: request event handlers fired twice when servicing a REST request by Vamseekrishna N.
3415293 CF-4199508 Vamseekrishna N. Issue is specific to v10 and v10 is EOL
Tracker Comment Comment on CFSCRIPT QoQ issue (when querying object created via 'queryNew') by Vamseekrishna N.
2825017 CF-4198309 Vamseekrishna N. This will not be fixed for CF 10 as it is EOL
2613171 CF-3341767 Vamseekrishna N. Changing the version info to 10.0 for as 8.0 and 9.0 are EOL
ColdFusion now supports Java 12, which is already EOL. Should you use it? Java 13? 11?
Portal Comment Comment on ColdFusion (2018 release) Update 4, ColdFusion (2016 release) Update 11, and ColdFusion 11 Update 19 released by SauravGhosh
SauravGhosh Charlie,
Update 19 is the final update of CF 11. CF 11 is now out of core support. Check the EOL matrix, eol-matrix.html#CD" rel="nofollow">https://helpx.adobe.com/support/programs/eol-matrix.html#CD
We'd put this as a note
Portal Comment Comment on ColdFusion now supports Java 12, which is already EOL. Should you use it? Java 13? 11? by Delxino
Comment on ColdFusion now supports Java 12, which is already EOL. Should you use it? Java 13? 11? by Delxino
Portal Comment Comment on ColdFusion now supports Java 12, which is already EOL. Should you use it? Java 13? 11? by Paolo Olocco
Comment on ColdFusion now supports Java 12, which is already EOL. Should you use it? Java 13? 11? by Paolo Olocco
Portal Comment Comment on ColdFusion now supports Java 12, which is already EOL. Should you use it? Java 13? 11? by Paolo Olocco
Comment on ColdFusion now supports Java 12, which is already EOL. Should you use it? Java 13? 11? by Paolo Olocco
Portal Comment Comment on ColdFusion now supports Java 12, which is already EOL. Should you use it? Java 13? 11? by Charlie Arehart
Comment on ColdFusion now supports Java 12, which is already EOL. Should you use it? Java 13? 11? by Charlie Arehart
2609748 CF-3785874 External U. Push a fix for this off 3 versions? That is asinine. This is not 'minor' by any stretch of the imagination. By pushing it off to 13, you will effectively NOT fix it for 10 as 10 will likely be EOL'd by then.
Tracker Comment Comment on cfimage writetobrowser throwing error on CF10 Mac OS X Mavericks Java 1.7 by External U.
2609838 CF-3759721 External U. Personally I don't see requiring an EOL'd JDK as an acceptable workaround. I hope that a more forward-thinking resolution will be found.
2609521 CF-3837347 External U. In case Adobe has forgotten ColdFusion 10 is supported until 5/16/2017 (https://www.adobe.com/support/products/enterprise/eol/eol_matrix.html#63). This means that Adobe is supposed to be fixing bugs in ColdFusion 10 until 5/16/2017. The last time I checked we
Portal Comment Comment on Oracle’s Java policy change by Peter Freitag
Peter Freitag FYI Oracle has released Java Security patches... So Java 10 is now EOL and presumably vulnerable to security issues. This is really the worst for CF2018 customers because it ships with Java 10 and there is no security update for Java 10.
We have heard that there is a CF update
Portal Comment Comment on ColdFusion now supports Java 12, which is already EOL. Should you use it? Java 13? 11? by Charlie Arehart
Comment on ColdFusion now supports Java 12, which is already EOL. Should you use it? Java 13? 11? by Charlie Arehart
Portal Comment Comment on ColdFusion now supports Java 12, which is already EOL. Should you use it? Java 13? 11? by Peter Tilbrook
Comment on ColdFusion now supports Java 12, which is already EOL. Should you use it? Java 13? 11? by Peter Tilbrook
Portal Comment Comment on ColdFusion now supports Java 12, which is already EOL. Should you use it? Java 13? 11? by Anonymous
Comment on ColdFusion now supports Java 12, which is already EOL. Should you use it? Java 13? 11? by Anonymous
2611731 CF-3598342 External U. With limited IP space, some web services/APIs are now switching to certificates that use SNI. As a result, ColdFusion 8, 9 & 10 can't perform HTTP requests using CFHTTP. CF 8 & 9 are EOL, but 10 should seriously be updated... especially since this bug is already ~2
6259329 CF-4205250 Vincent K. According to Adobe's website, CF 2016 is under core support until 2/17/2021 so I sure hope this patch is available for CF2016. https://helpx.adobe.com/support/programs/eol-matrix.html#CD
Tracker Comment Comment on SideBySide Error for TypeViewer.dll - Visual C++ 2008 Redistributable Package EOL by Piyush K.
Comment on SideBySide Error for TypeViewer.dll - Visual C++ 2008 Redistributable Package EOL by Piyush K.
Portal Comment Comment on Public beta for Adobe ColdFusion (2018 release) and Adobe ColdFusion Builder (2018 release) by Benjamin Reid
Benjamin Reid With regard to Java versions:
I see the ColdFusion 2018 Public Beta is currently shipping with Java 9.0.4. Given that Java 9 has already reached Public EOL in March 2018, and Java 10 is GA but due for Public EOL in September 2018 (due to both Java 9 & 10 not being classified as Long
2611035 CF-3648781 Rupesh K. Knowing Adam, I can't expect anything better from him. But I expected better from you Sean as I have respect for you. The bug was marked for 'ToFix' on Aug 4, 2014 and the audit trail shows that. https://picasaweb.google.com/lh/photo/iEol1JIDV-x1IJj2Vl2-d27qq
Tracker Comment Comment on CFPARAM by External U.
2613457 CF-3312096 External U. This bug was reported for ColdFusion 10 only 3 months after it was official released (5/15/2012) and almost 5 years before EOL (5/16/2017). Will it be fixed in CF10?
Was this one of the announced bugfixes for CF11? I don't see this bug mentioned on this official
2601257 CF-3038157 External U. I realize that with CF9 about to go EOL for support, it seems prudent to try to close out as many issues as possible. But closing a bunch of actual bugs (not ERs) with "NotWorthEffort" when users took the time to report and vote on them is rather rude. Have you
Tracker Comment Comment on Mod_jk.so not valid in MacOS 10.14 Mojave by e c.
4900753 CF-4203359 e c. Jose,
we're in the same boat too. We're thinking once we run out of mileage with CF11 (EOL or security flaw), we will probably move off of CF. Adobe had plenty of time to test CF out with Mojave before it was released. To me that indicates, Adobe treats CF
Portal Topic ColdFusion 11 “Core Support” ends on April 2019
Anit Kumar Panda ColdFusion 11 “Core Support” ends on April 2019 The “Core Support” for ColdFusion 11 ends on April 30, 2019. That means, no more Security patches/updates by Adobe for this version of ColdFusion after end of April 2019. The detailed timelines are mentioned here in the EOL Matrix
Tracker Issue ArrayFilter only works when used in CFScript.
as EOL there.)
It works with ColdFusion 2018 (and all versions of Railo & Lucee), but not CF2016.
Actual Result:
invalid CFMLConstruct error
Expected Result:
The filtered array (without any error).
Any Workarounds:
Modify your CFML and use cfscript tags when using the function.
4230220 CF-4202069 Nimit S. As per support matrix we do support RHEL 7.0 with 64Bit
Support matrix: [https://wwwimages2.adobe.com/content/dam/acom/en/products/coldfusion/pdfs/cf11/coldfusion11-support-matrix.pdf]
ColdFusion 11 is EOL. Hence, I am withdrawing this bug. If you are still facing
SideBySide Error for TypeViewer.dll - Visual C++ 2008 Redistributable Package EOL
for a given CF or CF Builder version ends/ended? appeared first on ColdFusion. Blog,Extended Support,Support,ColdFusion,Core Support,eol,support,updates
_Kurma_Kurma_Kurma" but instead you get "?rtibat _urma _urma _urma"
From the stack trace, ReplaceNoCase seems to send a map to Replace which is then tries to replace a sub string. The double byte char in the string is giving the wrong position to replace on.
While this exists in CF11 and CF10, and I know CF9 is EOL, you can
Tracker Comment Comment on The cfinclude attribute runonce not working inside components by James M.
. It has a "normal" priority with a "to fix" status. CF11 is EOL in 5 days (April 30, 2019). Are there any plans to fix this in CF2016, CF2018 or an unannounced, yet-to-be-released version?
Tracker Issue Re-querying a cached query doesn't return the initial cached query after result variable is modified
post-query, they become a permanent part of the initial cached query. NOTE: This has worked consistently in ColdFusion 4-11 (and Railo/Lucee) until ColdFusion 2016 (which we're required to upgrade to due to CF10 EOL.)
Steps to Reproduce:
1) Perform a cached query.
2) Modify one of the column values
to CF9's EOL. It's possible that it was a ColdFusion9 bug that was upgraded to 10 and ignored in 9. I don't understand why it wasn't additionally tested w/CF9. I'm posting it here so that other CF9 users are aware of the issue.
https://bugbase.adobe.com/index.cfm?event=bug&id=3123950
Steps to Reproduce
Tracker Comment Comment on SideBySide Error for TypeViewer.dll - Visual C++ 2008 Redistributable Package EOL by Robert E.
Comment on SideBySide Error for TypeViewer.dll - Visual C++ 2008 Redistributable Package EOL by Robert E.
2018, eol-matrix.html#CD" rel="nofollow">whose core support ends in 2023.
Note that since CF2018's release, there has been a discounted price for those on CF2016 to upgrade it. (Those on 11 or earlier must buy a full license.) I do realize
.
Any Workarounds:
Downgrading to the EOL Java 1.6 (u43, specifically) has eliminated the problem.
Alternatively, restart the server every time it happens and wait.
I was able to mitigate this partially by using try/catch when an entity was not found in the XML file and then on-the-fly reload