That may sound like a boring or simplistic topic to some. "Doesn't everyone already know how to install CF?" Trust me, they do not. :-) I help people do it every week, whether CF2021 or earlier versions. There are various tips I can and will share, and of course some about CF2021 in particular. But much will benefit you even if still using an older CF version.
For more on the talk, including a description (and my bio) see the meetup event page, which offers details like the URL for attending, the date and time (Thursday at 12p Eastern), and more.
I have just realized that I've been derelict in announcing here on my blog when I'm giving such talks. I did 3 meetup sessions last year, as well as a couple of AMA ("ask me anything") sessions with Dan Wilson, who has been helping me in running the group the past year, with my sincere thanks! :-)
How and why your sites may break, and what to do, after applying March 2020 update to CF2018 or 2016
To be clear, I do not mean with this warning to suggest that you should NOT apply the update! It implements an important security fix.
Instead, it's that after applying it, your CF web sites served via IIS or Apache WILL likely break initially, until you take one at least and perhaps two extra steps. The good news is that these steps are both easy and documented by Adobe in the update technotes, but they do require that someone do them, if needed. Let me explain.
[Update: I did an abbreviated version of this post on the Adobe CF portal: Three reasons your sites may break, and how to fix them, after applying March 2020 update to CF2018 or 2016. Note I also titled it differently. Just trying many ways to get people's attention. That post may interest some, either to read first (but my TLDR below also tries to abbreviate things also), or especially if you may prefer to give others a link to a post on this matter that is not as "dense" as this one. :-) I do point to this post from there, of course, for the many additional details that some may appreciate.]
Sadly, because many people don't bother to read the CF update technotes (linked to below), and they just apply the CF updates, they are not noticing this issue until they or their users start screaming because their sites are down. There's also a fair bit of "screaming" in the CF community, and folks responding may not know the info that I (or Adobe) have shared, to get things "working again", so I hope this helps bring some calm, and most important the clear solution/s needed.
For some, that's all they need to know. For most, they will probably want to read on.
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.Here's some news that Adobe may not herald, but many users certainly would want to know and celebrate: as of today, when you download ColdFusion 2016 (whether the trial edition, developer edition, or on buying Standard or Enterprise, or the Express edition introduced in CF11), you are no longer forced to go through the Akamai Download Manager! :-)
For many, that's all they need to know. For others, there are some more points worth discussing. Read on, if that may interest you.
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.Someone presented a problem on a discussion list where they found that upon installing CF, they got to the "migration wizard" screen, and though it offered the option to "continue" if it hung up, it did not continue for him.
In this post, I'll share how to get past that prompt, if this happens to you. (And despite that image on the right showing ColdFusion 11, this could conceivably happen in CF10, CF9, and so on, and this same solution applies to all.)
For the anxious folks who want to "skip the waffle" and context/setup, the solution is at the very bottom. :-)