portal entry

Thanks for this, Rakshith. But there is a problem logging in (as discussed here), at least using the option to login via facebook, and <strong>it seems it could be easily solved</strong> 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: <blockquote>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</blockquote> 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 <a href="http://cffiddle.org/login/facebook," rel="nofollow">http://cffiddle.org/login/facebook,</a> below: <a href="https://www.facebook.com/dialog/oauth?client_id=131979487506336&redirect_uri=http://cffiddle.org/login/facebook&response_type=code&state=tA98jM" rel="nofollow">https://www.facebook.com/dialog/oauth?client_id=131979487506336&redirect_uri=http://cffiddle.org/login/facebook&response_type=code&state=tA98jM</a> 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.

Comment by Charlie Arehart

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

Comment by Suresh Jayaraman

 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

Comment by Aaron Neff

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

Comment by Aaron Neff

Hi Charlie, Thank you for reporting this issue. We have fixed this issue now. Can you please try and confirm? -Nimit Sharma

Comment by nimsharm

Yep, thanks Nimit. :-)

Comment by Charlie Arehart