Are there any known issues supporting CF2016 on Windows Server 2022? It is a temporary situation while we migrate off of CF2016, but I'm noticing some odd issues like POI class loading failures and new Query() bugs.

Hey Alpha testers, need a bit of feedback. I would like to have a meeting next week, open to all Alpha testers. It will be myself and a few engineering/support folks on Adobe site, and as many alpha folks as can make it. we will go over some of the new features and try to answer questions live. Since it will be myself and the engineers, the time would have to either be in the 7am-9am PST slot or like 7pm-10pm PST slot. Which of these is better for folks?

Hi @Daniel Mejia

#advent-of-code join there. Share invites to leaderboards. Share your code repos. Get stuck on a puzzle - Ask questions there.

I am having an issue with ColdFusion 2021 Update 4 server licensing. It appears it is not contacting Adobe and reverts to developer mode after 15 days. If I reboot or restart the server it is back to Enterprise. Is there any diagnostic or logs I can look at to diagnose the issue? On the Licensing and Activation --> Usage page: "no entries to display" Also on the Settings --> notification page, I tried to enable Notify every 3 days and entered my email, but after submit it removes all of the settings.

We applied ColdFusion 2018 update 15 on our dev boxes shortly after it was released and on our acceptance server on 03-Nov without any issues. When I went to apply the same update to our production server this evening, the update installer prompts for the CF install location as expected, I choose it, and it shows a dialog reading “You cannot install this hotfix for ColdFusion .. The hotfix applies only to ColdFusion 2018.” I am quite certain this is really a CF 2018 installation as I’ve installed all of the previous updates without issue. In the CF Admin’s “Settings Summary”, it shows the version as “2018,0,14,330003”. Anyone have any ideas on why the update applied without issues on our other servers but not now? It is the same hotfix JAR file we used to apply the update early in November.

@Mark Takata (Adobe) I can’t seem to create a new bug report at

<http://tracker.adobe.com|tracker.adobe.com>

and upload a spreadsheet with the found issues. How should I submit this. There is another one coming for 2021 for similar vuln scan issues.

NM. It went through when I used an

xls

file instead of

xlsx

@Mark Takata (Adobe) @Vikram Kumar It appears to submit and gives me an issue number, but the report does not appear publicly. Is this on purpose?: https://tracker.adobe.com/#/view/CF-4216105 ( the 2021 report )

This message was deleted.

How does one go about getting the default 8500 directory listing to be sorted ALPHABETICALLY? I never really took notice before, but I have a todo list which requires a lot of navigating here…

is there a JVM arg (or some other setting/toggle) to force semicolon statement terminators in 2018+?

i can't seem to find anything other than announcements around them now being "optional" in some contexts

Who is responsible for tickets i.e. moving them on or commenting on them? Just so I know who to aim any conversation at

@pegarm The Webinar for today says it’s at 3 PM EST. However, I’ve been getting reminders to be there at 12PM. So…there’s a group of us in there waiting. Not sure what the scoop is.

Email heading out to Alpha folks with an event next week. If you're not in the Alpha yet and want to be, please join.

I've seen examples of cffile supporting s3 file paths but the Adobe doc history formatting seems totally borked? What version of CF was this introduced? @Mark Takata (Adobe) https://helpx.adobe.com/coldfusion/cfml-reference/coldfusion-tags/tags-f/cffile.html

Is the next version of ColdFusion called

ColdFusion Forta

? 🙂

ben-tuna?

I guess Charlie Tuna is already taken

I'm running into an issue with adding a data source to a fresh install CF2021 (with update 5). When trying to save a new DSN pointing to a MSSQL database, I get an error stating the sqlserver package is not installed. I have ensured the sqlserver package is installed via the package manager UI in the CF Admin, and also tried uninstalling/reinstalling from the UI and CFPM CLI. The error persists. Any suggestions?

Members of the Alpha, you should have received an email from me about a special event happening Tuesday morning. If you ARE in the alpha, and did NOT receive an email from me today, please DM me.

Reminder: tomorrow morning, 7am pst, alpha event. Dm with questions.

What’s Adobe’s take on precompiled binary compatibility for Patch versions? ie. CF 2018u15 and CF 2021u5, XMLSearch compiled on earlier versions of CF are incompatible with these two updates, we get coldfusion.runtime.CFPage.XmlSearch(Lcoldfusion/xml/XmlNodeList;Ljava/lang/String;)Ljava/lang/Object;

Thank you to all the folks from our Alpha test who came to the demo. It was great (outside of a few Mark-related stupidity issues early on, which I take full responsibility for and will sack myself later regarding). A recording of the event will be posted on the alpha site later today, once I edit in full-volume k-pop to cover up all my mess ups. 🙂

A quick heads-up for folks, I will be on the road tomorrow afternoon/evening and then Friday morning to attend the Adobe 40th Anniversary celebration in San Francisco. If you have support issues or questions, please email cfsup@adobe.com or tag Sandip or Vikram here. If you have issues with the documentation, please connect with Saurav. I'll be back online in the early afternoon on Friday. I am also around in the morning (PST) tomorrow.

Is there a way to force UDF argument names to preserve the case-sensitivity of how the UDF arguments are written in the code? When I dump the arguments of a UDF within the UDF, all of the arguments are upper-cased. I have come into a situation where the case-sensitivity of the argument names must be kept as they are written in the method because the API that I call that uses these argument names and the argument values are passed along to the API. The API will not operate correctly if the argument names are upper-cased or any other case variation. IE)

function A(aRguMent1="test"){ ... }

The argument name must be kept as "aRguMent1" and not "ARGUMENT1" or any other case variation. If not, then I will have to come up with an uncountable amount of arguments as a list to search for the proper casing to match and pass along the correct cased argument name to the API. This would be extremely unfortunate given that this API has an incredible amount of API functions with multiple arguments in every function.

This message was deleted.

I'm also noticing that in

replaceNoCase

function, it does not keep the expected case of the search string after replacement. The issue is that I want to replace 'app' with 'aPp'. Instead, it replaces 'app' with 'APP'. Here is an example: https://cffiddle.org/app/file?filepath=7a89e97a-846e-4c37-b96c-2ae8aaf9dbab/97001d3[…]266-9190-00db99167135/3989fe4a-fe71-43c0-a59d-4303754b8f59.cfm Is there a way to manipulate strings with the exact casing in any way?