Several weeks ago, I did an entry, CF911: Why/when you MUST update the web server connector for #ColdFusion 10, and may have missed it.
In this entry, I want to throw in another reason why it’s important to make sure you properly update (reconfigure/rebuild/upgrade) your web server connector after applying certain CF10 updates, or if applying only the latest update for the first time to a newly installed CF10 instance.
It could help fix CFML that seems “broken”
There are some fixes addressed in various updates with respect to how your CFML may work, which are affected by the connector updates. The problem is that while the “fix” may be reported as being implemented by a given CF10 “update”, if you do that “update” but then do NOT also reconfigure/rebuild/update the web server connector as may have been required by that CF10 “update”, then you will not get some of the benefits of that “update”.
I discuss in the last entry how this is a problem especially if you are skipping updates (or applying the latest one for the first time on a new CF10 install). You will be getting all the previous updates, and one (or more) of them may have required that you reconfigure/rebuild/upgrade the web server connector. The CF10 “update” lets you know that in the update page shown on the “server updates” page of the CF admin, but many people miss that and never bother with the web server connector reconfigure/rebuild/upgrade. See the previous entry for more on that tale of woe.
(And I explain in the other entry why I refer to the process as a need to “reconfigure/rebuild/upgrade” the web server connector, as well as how to do it, of course.)
The point here is to stress yet another reason (a few, in fact) that you want to reconfigure/rebuild/upgrade your web server connector, if the current or previous CF10 “updates” had said you should.
The official app for the Adobe ColdFusion Summit happening in Las Vegas between 24th and 25th of October.
The app can be used to view the entire schedule of the two day conference, create a schedule, submit session survey, watch the conference twitter feed and receive notifications about the conference.
Apple has determined that certain 64GB and 128GB flash storage drives used in the previous generation of MacBook Air systems may fail. These systems were sold between June 2012 through June 2013.
Apple or an Apple Authorized Service Provider (AASP) will replace affected flash storage drives, free of charge.
If you ran a firmware update and were directed to this web page, skip to Replacement Process section for next steps.
To see if your drive may be affected, go to the Mac App Store, click on Updates and choose the MacBook Air Flash Storage Firmware Update 1.1. The firmware update will test your drive to see if it is affected. You will be directed back to this page for next steps if needed.
IMPORTANT: If your drive is affected, we strongly recommend that you do not install any operating system updates or new applications. We also recommend backing up your data on a regular basis until you receive a replacement drive.
Cyber attacks are one of the unfortunate realities of doing business today. Given the profile and widespread use of many of our products, Adobe has attracted increasing attention from cyber attackers. Very recently, Adobe’s security team discovered sophisticated attacks on our network, involving the illegal access of customer information as well as source code for numerous Adobe products. We believe these attacks may be related.
Our investigation currently indicates that the attackers accessed Adobe customer IDs and encrypted passwords on our systems. We also believe the attackers removed from our systems certain information relating to 2.9 million Adobe customers, including customer names, encrypted credit or debit card numbers, expiration dates, and other information relating to customer orders. At this time, we do not believe the attackers removed decrypted credit or debit card numbers from our systems. We deeply regret that this incident occurred. We’re working diligently internally, as well as with external partners and law enforcement, to address the incident.
Over the last few weeks there have been quite a few passionate discussions happening on ColdFusion, including the blog post from Cutter recently.
I thank the ColdFusion community for all the feedback and I want to assure you that Adobe is very much a part of the story on the revival of ColdFusion. There is no denying that the road ahead is challenging, but all of us here at Adobe strongly believe that there is enough potential in ColdFusion and want to see the platform as successful as ever. Rather than viewing Adobe and community as two separate entities, we are keen to work with the community with a common goal of reviving ColdFusion. And in that context the feedback that we have been receiving is extremely valuable.
While not every single feedback can be acted upon, I want to make the point that ‘WE HEAR YOU’ and we are taking actions and will continue to take them for the better of ColdFusion. I want to use this opportunity to discuss with you the initiatives, updates about the product and its ecosystem as well as product news from Adobe.
Just over a year ago, the Open CFML Foundation was launched with a focus on the fact that Open Source CFML is a vital part of the CFML ecosystem and as such, it deserves an advocate beyond the developers and organizations that rely on CFML and the solutions built on it. We wanted to share with the greater web community a side of CFML most aren’t familiar with, and trumpet all the benefits open source CFML has to offer.
We got off to what we felt was a great start — we created a small board (to make decision-making as easy as possible), we enlisted projects we felt help told the OS CFML story well, we engaged Joel Kinney of Fort Point Legal (jQuery Foundation) to help with the legal formation of the foundation, we incorporated and set up bank accounts, we created a website and newsletter, we made our first foray outside of the CFML community (CMS Expo), and we sponsored and hosted our first events (Open Gov Day in Washington D.C., MuraCon).
Unfortunately, shortly after launch, all but a few of the original participants left to pursue other interests. And as result, the remaining members were forced, in many ways, to start over. So we did just that.
At Open Gov Day and MuraCon 2012, we met with people who didn’t just love OS CFML, we met with people who have a vested interest in the success and longevity of OS CFML. We shared with them our passion and determination to see it thrive, and convinced them to be a part of a reformed Open CFML Foundation. Fortunately, they all accepted : ).
So, it is with great pleasure that we’d like to announce the new Open CFML Foundation board and our plans for the next year.