Note: This blog post is from 2020. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.

Or you can change your CFML code to get around the problem, as I also discuss below.

[Update: As of Mar 2021, Adobe now offers implements this "hotfix" into CF2021 Update 1 (and above). You DO still need to add the JVM arg discussed, if you want to revert the behavior:

It's just that yo uno longer need to obtain and implement the specialhotfix jar file I'd announced with this post. Again the update does NOT change the DEFAULT behavior, which is why that JVM arg is still necessary. The rest of the information below applies.]

Read on for additional details.

[....Continue Reading....]

Note: This blog post is from 2020. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.

It turns out that with the release of CF2021, Adobe introduced a breaking change...if you use any of the CF tags or functions that use date formatting masks. The problem is that while a capital "D" value used in such mask used to simply mean the same as a lower-case "d" ("day of month"), the change in CF2021 is that "D" now means instead "day of YEAR"! That can be a devastating problem that might lurk for days or weeks, corrupting your data.

TLDR; You have two solutions:

• you can choose either find and change the affected code (not easy but using techniques shared below)
• or you can implement a new JVM arg that Adobe offers to revert this behavior back to how things worked before CF2021 (discussed below), which still applies in CF2023 and beyond

If you're affected, you must do one or the other of these things. For more, read on.

[....Continue Reading....]

Note: This blog post is from 2020. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.

The recent release of CF2021 is a great sign for the continued vitality of CF, but this looming deadline is a reminder that as the years roll on, we not only get new versions but we say good-bye to old ones.

Wondering what you can do? or when CF2018 or CF2021 support ends? And what's the difference between "core" and paid Adobe support plans? For more on these, as well as official Adobe documentation that discusses such things, read on.

[Update: CF2016 users got a "reprieve" of sorts, when Adobe released updates to CF2021 and 2018 in March 2021, and they also offered the final update to CF2016, update 17, especially because it address a security vulnerability. Sadly, some of the changes in the update--not related to the security fix--were "breaking" changes. For more on that update, see the Adobe blog post from March 2021.)

[....Continue Reading....]

Note: This blog post is from 2020. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.

As with each CF release, there are features great and small--ones that may "sell" it, and ones that may simply make your life easier.

This is a follow-up to my post from last month, Getting started with "Project Stratus" public beta, aka CF2021. In that I highlighted some key info one would need to get started USING the prerelease, which came out in August, but I only briefly mentioned then some of the key new features. (I also explained why I had referred even then to it being CF2021, given info I'd found in the prerelease.)

In this post, I want to highlight more clearly what those new features are, nearly 60 of them in several categories!--just with a brief mention of the feature and perhaps its sub-features--and most important with a pointer to where to find them discussed in far more detail.

[....Continue Reading....]

Note: This blog post is from 2020. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.

What matters most is that it's one of the boldest new versions of CF in quite some time. In this post, I want to share some tips about getting started with the beta, as I have seen many in the community left wondering about some things.

My focus here is not on "what's new" (I'll offer a brief list here, and more in a later post), but really just "how to get started", especially during the beta (or "prerelease") as some things are not as obvious as they perhaps should be. In fact, I make some pointed suggestions that I hope Adobe will consider, as well as share tips for you in the meantime.

In this post, I cover:

• How easily anyone can join the public beta (Don't miss all that's on the prerelease front page)
• Available documentation resources, don't miss them! (The 500-page (!) release notes, and separate system requirements and known issues docs)
• Getting help with the prerelease, don't go it alone! (Filing bug reports, feature requests for the prerelease; asking for help and learning in the available prerelease forums)
• The available installers and more
• A taste of what's new (more to come in a later post)
• About the use of the codename, Project Stratus

[....Continue Reading....]

Note: This blog post is from 2020. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.

[....Continue Reading....]

Note: This blog post is from 2016. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.

And you'll likely be in panic mode. Many find after applying a ColdFusion update that either CF won't start at all, or they can't access the ColdFusion Admin, or some part of CF or their app doesn't work. Or perhaps the problem may not become clear for hours or even days.

Typically the issue is that there was an error during the update process which CF attempts, and that might be rather easily confirmed and resolved. In this post, I share several tips and observations related to all this, based on my years of providing remote CF troubleshooting support.

[....Continue Reading....]