tracker issue : CFB-4198446

select a category, or use search below
(searches all categories and all time range)

Installer points to a failing page:

| View in Tracker

Status/Resolution/Reason: Open//

Reporter/Name(from Bugbase): Charlie A. / ()

Created: 03/12/2019

Components: Installer

Versions: 2018

Failure Type: Incorrectly functioning

Found In Build/Fixed In Build: current cfb 2018 installer as of 3/12/19 /

Priority/Frequency: Normal / Most users will encounter

Locale/System: / Windows 10 64 bit

Vote Count: 1

There is a page pointed to by the CFB installer which offers a failing URL: The URL is also not offered as a hyperlink, which would be very helpful (as we cannot highlight and copy the text within that page).

When we install CFB2018 (even downloaded today, 3/12/2019), the installer includes among its few screens one called, "install type", and it talks about how Builder will revert to the Express edition, if a license key is not offered.

This is basically a repeat of the same problem reported in CFB 2016 as ticket CFB-3772315, reported by Ray V. He saw the same problem in the CFB2016 installer: the URL ( failed, and was also then not offered as a link. 

I have not checked to see if that was ever fixed in CFB 2016's installer. But I can report that sadly the CFB3 url there does "work", in that it redirects to But that page makes no mention of the Express edition.

I have tried to find a good page that you could have that CF2018 express edition help link to redirect to, but I find none. (I had also looked when I did a blog post on the Express edition on the CF Portal: If there is a good URL for that that should redirect to, please share that here even if it may take a long time to get that installer corrected.



I ran into this as well, please fix the link. Charlie, for what it's worth, this page in the CFB documentation is the one place where I could find details of the Express edition: However, even the list of limitations for the Express edition is confusing and incorrect. For example, it lists "Code insight" as a missing feature, however this exact phrase does not appear anywhere else in the entirety of the CFB documentation as far as I can tell. (There is plenty of explanation on Code Assist, but it's unclear if this is the same thing as Code insight).
Comment by Legorol S.
31041 | July 17, 2019 04:47:08 PM GMT
Yep, Legorol. I suspect the list on that doc page is one that's been brought forward from older releases, so may mention things perhaps no longer in CFB (like this "code insight" reference) or things added recently (and not supported by Express) like the security code analyzer. As for what told me that (that the Sec Analyzer is not supported in Express), it's among a few shown in the popup when launching CFB when in this Express mode (where the trial has expired). As for "code assist", I will clarify for readers that it's not that Express doesn't support it. Instead, it's specifically "Code assist for extensions" (so for extensions, only) which Express does not support. This is indicated on that page Legorol mention and on that popup I checked. Just clarifying so that users don't misread your comment as saying that Express does not support "code assist" at all. :-) All that said, I'd hope that Adobe would respond about the original issue raised here.
Comment by Charlie A.
31042 | July 17, 2019 05:46:29 PM GMT
Actually, Code Assist encompasses a range of helpful things, including showing lists of available tags, functions, components, component methods, application variables etc. I rather suspect that some of these carry on working in Express (e.g. lists of tags/functions), but many won't (e.g. introspection of component methods and Application variables to provide assistance). The reality is most likely that *some* of Code Assist still functions, but the more advanced part doesn't.
Comment by Legorol S.
31043 | July 17, 2019 05:52:29 PM GMT
Yep. It would indeed be nice if they would be more specific. I will say that I just tried and the CFC Explorer does indeed work, as does the list of CFCs popup in tags like cfobject and cfinvoke (or their function/script equivalents)--at least as long as you have a) a file opened that's in a CF project, and with that project connected to a server, and that server configured for RDS, etc. But we are getting far afield of the purpose of this bug report. You may want to create a blog post or question on the CF portal (, to open up a broader discussion (and with more people) about the pros and cons of the Express edition. :-)
Comment by Charlie A.
31045 | July 17, 2019 06:37:44 PM GMT