Copy link to clipboard
Copied
Sent 1:37 PM
It's not just cf11 but also cf2018, 2016 and 10. Adobe is aware of the problem (I found it a couple of days ago and reported it), and they are working on it. It was not intentional, but also not something the cf team directly controls.
Since the gears grind slowly there sometimes, I will point out that I have yesterday put the most recent updates for all 4 versions on the http://www.cfmlrepo.com site, where a few trusted community members post also past cf (and lucee and railo and cfbuilder) ins
...Copy link to clipboard
Copied
It's not just cf11 but also cf2018, 2016 and 10. Adobe is aware of the problem (I found it a couple of days ago and reported it), and they are working on it. It was not intentional, but also not something the cf team directly controls.
Since the gears grind slowly there sometimes, I will point out that I have yesterday put the most recent updates for all 4 versions on the http://www.cfmlrepo.com site, where a few trusted community members post also past cf (and lucee and railo and cfbuilder) installers.
I have also put there as many other update jar files for the 4 cf versions as I have. I'll add more as I can. Just go to the folder for each version, and see the "fixes" folder. (That name goes back to before cf10 started calling them updates, as you'll see we had a fixes folder for cf9, for instance, with hot fixes, security fixes, etc).
I understand some people will only want to get update files and installers directly from Adobe, but until their problem is resolved I hope this will help others.
Copy link to clipboard
Copied
Thank you – We have downloaded it and verified the digital signature.
$ md5sum.exe ~/profile/Downloads/hotfix_018.jar
8270f3d08054e87fb24d4dad7c0cacda */home/jpyeron/profile/Downloads/hotfix_018.jar