Slide and code from my session at ColdFusion Summit on language additions to ColdFusion 2018

October 9, 2018
Staff 98 posts
Followers: 6 people
4

Slide and code from my session at ColdFusion Summit on language additions to ColdFusion 2018

Staff 98 posts
Followers: 6 people
October 9, 2018

First of all, thank you for attending my session – Developer’s Las Vegas: Geek out with the smart language additions in ColdFusion 2018. As promised, here is my slide deck and the entire code samples.

I had a great time presenting this really powerful set of language improvements to CF 2018. I loved the interaction and the questions that you had as an audience. The code samples actually point to a shared fiddle application of mine. Once you login to CFFiddle and refresh the link, you will see CFSummit2018 show up as a shared application in your list of applications in CFFiddle. Play around with it and have fun! Except for the code samples where I have with database interaction, everything else should run on fiddle. The code under comingup folder too will not run because it is yet to be introduced into the language. Since all the code examples I have are from CF 2018, make sure to run the examples making selecting ColdFusion 2018 as a server. You can also download the entire code samples by hitting the download button. CFFiddle is awesome!

Hope you use CFFiddle as your medium of choice for sharing code samples. So much easier! Have a question to ask on the community portal? Don’t post a code snippet, just provide a link to your CFFiddle application.

Comments (4)
2018-10-18 08:28:52
2018-10-18 08:28:52

 Hi Rakshith and Suresh,

Currently, CFFiddle’s “ColdFusion Version” lists:
– Adobe ColdFusion 2016, Update 6
– Adobe ColdFusion 2018

Suggestion:

– Adobe ColdFusion 2016, Update 6
– Adobe ColdFusion 2016, Update 7
– Adobe ColdFusion 2018
– Adobe ColdFusion 2018, Update 1

Issues:
1) “Adobe ColdFusion 2016, Update 6” auto-switches to “Adobe ColdFusion 2018” when clicking “Run” button. The “Adobe ColdFusion 2016, Update 6” option doesn’t work.
2) “Adobe ColdFusion 2018” should be “Adobe ColdFusion 2018, Update 1” (Update level should be clear)
3) Users should be able to check CF behavior across update levels, not just version levels. Use-case: CFFiddle links in Tracker tickets, b/c bugs/ERs are often specific to a version+update combination.

Thanks!,
-Aaron

Like
(1)
>
Aaron Neff
's comment
2018-10-18 08:50:16
2018-10-18 08:50:16
>
Aaron Neff
's comment

Forgot to say, thank you very much for the presentation and code samples – and, yes, CFFiddle rocks! I was just giving suggestions 🙂

Like
2018-10-12 05:25:53
2018-10-12 05:25:53

Thanks charlie for reporting this . We shall look into this at the earliest

Like
2018-10-10 13:39:17
2018-10-10 13:39:17

Thanks for this, Rakshith. But there is a problem logging in (as discussed here), at least using the option to login via facebook, and it seems it could be easily solved with a change in the URL used in cffiddle.org to login via FB.

First, I’m curious if anyone else can confirm experiencing the problem. When I click the offered button to login via facebook, I get this in the pop that appears:

Facebook has detected CFFiddle isn’t using a secure connection to transfer information.

Facebook will limit what CFFiddle can ask you to share when it’s using an insecure connection. This might cause CFFiddle to not work properly.

Warning

You are a developer, administrator, or tester for CFFiddle. To remove this warning, enable HTTPS for your website.

Continue Logging In / Don’t Continue

It appears that the problem is that the link for the “login” button that is offered is using http rather than https. We don’t see it by mousing over the button, nor in the source for the page, but instead we see it in the URL of the popup, which shows the URL that was used to call FB which then launched that popup. See the reference to http://cffiddle.org/login/facebook, below:

https://www.facebook.com/dialog/oauth?client_id=131979487506336&redirect_uri=http://cffiddle.org/login/facebook&response_type=code&state=tA98jM

We could wonder how no one at Adobe would have seen this yet, but perhaps folks testing things who are NOT seeing such an error had already told their browser to ignore such errors. They should try this in a new browser, which they’ve not used to login to cffiddle via FB. That’s how I experienced this, on a computer where I’d not visited it before.

Finally, FWIW, the button to login via google doesn’t show the same problem, but given how many people use FB, and how many may try to login based on this blog post, it seems important to get this resolved ASAP. Hope that’s helpful.

Like
Add your comment