Adobe Coldfusion Builder extension for Visual Studio Code question. Is this still valid: https://marketplace.visualstudio.com/items?itemName=com-adobe-coldfusion.adobe-cfml-lsp? I ask because if you click Download Extension and try to install, you'll receive a fatal error indicating that the signature has expired:

2/22/2023 12:39:22 PM - Initializing Install...

2/22/2023 123922 PM - Extension Details... 2/22/2023 123922 PM - Identifier : adobe-cfml-lsp 2/22/2023 123922 PM - Name : Adobe ColdFusion Builder 2/22/2023 123922 PM - Author : com-adobe-coldfusion 2/22/2023 123922 PM - Version : 1.0.443 2/22/2023 123922 PM - Description : Extension to help ColdFusion developers to manage projects, debug code, scan files for vulnerabilities and much more. 2/22/2023 123922 PM - Locale : en-US 2/22/2023 123922 PM - MoreInfoURL : 2/22/2023 123922 PM - InstalledByMSI : False 2/22/2023 123922 PM - SupportedFrameworkVersionRange : [0.0,2147483647.2147483647] 2/22/2023 123922 PM - SignatureState : InvalidSignature 2/22/2023 123922 PM - SignedBy : Adobe Inc. 2/22/2023 123922 PM - Certificate Info : 2/22/2023 123922 PM - ------------------------------------------------------- 2/22/2023 123922 PM - [Subject] : CN=Adobe Inc., OU=Cold Fusion, O=Adobe Inc., L=San Jose, S=ca, C=US, SERIALNUMBER=2748129, OID.2.5.4.15=Private Organization, OID.1.3.6.1.4.1.311.60.2.1.2=Delaware, OID.1.3.6.1.4.1.311.60.2.1.3=US 2/22/2023 123922 PM - [Issuer] : CN=DigiCert EV Code Signing CA (SHA2), OU=www.digicert.com, O=DigiCert Inc, C=US 2/22/2023 123922 PM - [Serial Number] : 0F25C5A91B63906481873E67DEF97109 2/22/2023 123922 PM - [Not Before] : 12/18/2020 40000 PM 2/22/2023 123922 PM - [Not After] : 12/21/2022 35959 PM 2/22/2023 123922 PM - [Thumbprint] : EFDEC600A43E9D55625E7AD6D2ED2F0CFC5C8D6F 2/22/2023 123922 PM - Supported Products : 2/22/2023 123922 PM - Microsoft.VisualStudio.Code 2/22/2023 123922 PM - Version : 2/22/2023 123922 PM - ProductArchitecture : x86 2/22/2023 123922 PM - References : 2/22/2023 123922 PM - Signature Details... 2/22/2023 123922 PM - Extension is signed with an invalid signature. 2/22/2023 123922 PM - Searching for applicable products... 2/22/2023 123922 PM - Found installed product - Visual Studio Professional 2022 2/22/2023 123922 PM - Found installed product - ssms 2/22/2023 123922 PM - Found installed product - Global Location 2/22/2023 123922 PM - VSIXInstaller.NoApplicableSKUsException: One or more extensions are for Visual Studio Code. Try installing them in Visual Studio Code. at VSIXInstaller.ExtensionService.GetInstallableDataImpl(IInstallableExtension extension, String extensionPackParentName, Boolean isRepairSupported, IStateData stateData, IEnumerable`1& skuData) at VSIXInstaller.ExtensionService.GetInstallableData(String vsixPath, String extensionPackParentName, Boolean isRepairSupported, IStateData stateData, IEnumerable`1& skuData) at VSIXInstaller.ExtensionPackService.IsExtensionPack(IStateData stateData, Boolean isRepairSupported) at VSIXInstaller.ExtensionPackService.ExpandExtensionPackToInstall(IStateData stateData, Boolean isRepairSupported) at VSIXInstaller.App.Initialize(Boolean isRepairSupported) at VSIXInstaller.App.Initialize() at System.Threading.Tasks.Task`1.InnerInvoke() at System.Threading.Tasks.Task.Execute()

I saw someone mention that ACF2023 was in Alpha 2. Can anyone from Adobe speak here about the status of this issue, what the state of "cfscript 2.0" is, and whether it's going to be part of 2023? https://tracker.adobe.com/#/view/CF-4210829 @priyank_adobe @Mark Takata (Adobe)

we're in process of 2018 -> 2021 and I'm wondering if this is a feature or a bug: 2018

a = {}
a.b.c = 1
writedump(serializeJSON(a)) // {"B":{"C":1}}

2021

a = {}
a.b.c = 1
writedump(serializeJSON(a)) // {"b":{"C":1}}

in our JS that consumes JSON responses, we've relied on all keys being upper-cased. For some reason, even though CF identifiers are case-insensitive and, in the past if you wanted case sensitive keys in structs you had to do something like

a["b"]

, the implicitly created

b

struct is now being created w/ a case-sensitive key instead. 🤷

so before we can roll 2021 to production, we have to comb our code base and try to identify all places where we might be implicitly creating structs like this and update our JS to use the casing that it will be receiving.

if it's a bug, I can log it as a ticket (though if it's fixed, we'll have to go back and swap out our casing in JS to use upper-case)

personally I'd love to have CF say "b is undefined on a" when you try to do

a.b.c = 1

rather than being magically helpful 🙂 but I know that's been a feature of the language for lo these many times

question: getting an odd error we've narrowed down to a <cfreport> tag. Some of our devs can run the code, no prob. For others of us, it throws an error with a message of type

com.lowagie.text.ExceptionConverter

and a message of

The document is not open.

Anyone seen anything like that before?

@Prashant S has left the channel

ANNOUNCEMENT The currently active Alpha programs will be ending this week in order to usher in the upcoming public beta program. Any users who are interested in testing will be able to go and download beta servers for all platforms in all installation types. We will also be releasing detailed documentation for all new capabilities. Our forums will have dedicated channels for all new features, and engineers will be assigned to check each channel daily to respond to issues, bugs, etc. The link for the beta program will be available here (and basically everywhere, I might even write it on the bus stop by your house). Unfortunately, I am unable to simply lift & shift all alpha users to the new site. Thought I could. I was wrong. My bad. Come to CFSummit & I'll buy you a beer or something at the party 🙂

I am currently working with scheduled task event handlers and I was wondering if there was any documentation in regards to the

fireInstanceID

returned in the handler functions ( I could not find any ). At the moment I am using

bigint

to store it as

int

was too small, but I wanted to confirm this was safe to continue to use as I am using the event handler to keep a log of task execution, completions and errors if any.

(i was wrong, the time was "not quite yet")

The time is here, the time is now! CANCEL ALL YOUR WEEKEND PLANS! 😄 We are pleased to announce the opening of the CF Fortuna Open #Beta, now available on the Adobe Prerelease site! Features available in this release include: * GraphQL Client (native GQL support for consuming GraphQL endpoints) * Google Cloud Platform (FireStore) * Google Cloud Platform (GCPStorage) * Google Cloud Platform (PubSub) * Central Configuration Service * HTML to PDF engine upgrade * PMT Integrations for GCP (Firestore, Pub/Sub, Storage monitoring) * JSON Web Tokens * SSO CF Administrator (LDAP/SAML support) If you are interested in taking part, please sign up for free here to download installers & documentation for Windows, Linux and Mac platforms (as well as Docker!) https://www.adobeprerelease.com/beta/48C2D737-9CB4-445E-E39C-90CB6381919A Docker files available from Docker Hub and AWS ECR. DockerHub image: adobecoldfusion/fortuna:latest AWS ECR: public.ecr.aws/adobe/fortuna:latest FOR BUGS & ISSUES, PLEASE USE THE OFFICIAL PRERELEASE FORUMS (Engineers & support staff are assigned to watch the forums, which are now separated into all of the new features, including documentation for that feature.)

I just ran the CF2021 installer again on my LINUX system to change the user. Websockets did not kick back on so I uninstalled the package and attempted to reinstall. Now I am getting an encryption error: “An error has occurred while installing the package websocket. Exception : An error occurred while trying to encrypt or decrypt your input string: Given final block not properly padded. Such issues can arise if a bad key is used during decryption.” Anyone?

It looks like cffiddle.org is down

{
  "status": 500,
  "error": "None",
  "message": "I/O error on POST request for \"<http://cf2021.cffiddle.org:8500/cffiddle/c85fa036-5a93-423a-b748-4f0852e91d64/b0faac60-e774-4e5c-aff0-ce794e966d29/tmp_9c697291-50c9-4fad-b3ff-8dc1e0db29b8.cfm?__fiddlecall=true&__sandbox=c85fa036-5a93-423a-b748-4f0852e91d64&__appid=b0faac60-e774-4e5c-aff0-ce794e966d29>\": Connect to <http://cf2021.cffiddle.org:8500|cf2021.cffiddle.org:8500> [<http://cf2021.cffiddle.org/10.0.0.4|cf2021.cffiddle.org/10.0.0.4>] failed: Connection refused (Connection refused); nested exception is org.apache.http.conn.HttpHostConnectException: Connect to <http://cf2021.cffiddle.org:8500|cf2021.cffiddle.org:8500> [<http://cf2021.cffiddle.org/10.0.0.4|cf2021.cffiddle.org/10.0.0.4>] failed: Connection refused (Connection refused)",
  "timeStamp": 1678715421916,
  "path": null
}

ANNOUNCEMENT: CF2021 & CF2018 Security Updates https://community.adobe.com/t5/coldfusion-discussions/released-coldfusion-2021-and-2018-march-2023-security-updates/td-p/13649873

Did we ever get a better way to create Java objects than

createObject()

? I think Lucee has a more integrated syntax but I can't remember whether the tickets requesting better syntax in ACF ever happened?

@carehart can you ping this channel when you post the update to your comment on the adobe post RE the latest exploit?

Also in the latest bulletin it says you’ve added jvm flags wrt to the exploit but not a) whether we should use them or just apply the update and b) what the correct setting is.

In this release, we’ve addressed some security vulnerabilities and added the following jvm flags to that effect.

-Dcoldfusion.cfclient.enable=true/false

-Dcoldfusion.cfclient.allowNonCfc=true/false

so cool that you added them but are they required for mitigation and if so is it true or false they should be set to?

(@saghosh)

Also the UK version of the update page doesn’t have update 16 listed

@salted The other EN pages are getting localized as I write. Usually takes 24-48 hrs. Meanwhile, you can refer the EN page for a while.

Can you pls send me the url @salted I'll get it checked?

I’m giving @carehart a quick shout-out for his most recent blog post about the most recent ColdFusion updates and the additional information about what that update addresses and steps needing to be taken. Thank you, Charlie. https://www.carehart.org/blog/2023/3/17/coldfusion_march_2023_emergency_update

Has anyone else had trouble with the GUI updater (in CFIDE) failing to apply updates?

The Manual Install instructions are atrociously bad. All I had to do was to download the hotfix jar and run it as root. I don’t know what all of that other stuff about unzipping and “the repository” and editing XML files was about.

Adobe's response to this latest patch seems a bit 'muted'. It reads very much like every other recent CF update. Yet reading Charlie's post (thanks Charlie!!) it seems like a very serious situation.

Cockroaches and CF11 will be all thats left of humanity one day. Thanks for keeping it alive @carehart!