Sometimes I get too nostalgic over computers or software that I once used in my daily life. I remember my first computer (the Commodore Vic-20), I remember my first programming language (BASIC), and I remember my first spam filtering software for user generated content (Akismet). But nine years ago, a new spam filtering service originally intended for Drupal called Mollom emerged and I quickly forgot about the other spam blocking software.
Your hosting account was found to be causing an overload of MySQL resources. What can you do? Upgrade your Drupal 8 website to Drupal 8.4 or higher.
One of my goals in rebranding my website from CMS Report to socPub was to write diverse articles beyond the topic of content management systems. Yet, here we go again with another CMS related article. The Drupal open source project recently made available Drupal 8.4 and for me this version has been a long time coming as it addresses some long standing frustrations I've had with Drupal 8 from the perspective of a site administrator. While Drupal 8.4 adds some nice new features, I'm just as excited about the bug fixes and performance improvements delivered in this new version of Drupal.
Last week, I received an email inviting me to take a sneak peak at a press release that became public today. In the email, I was asked if I would be interested in hearing "news from new open source startup, DRUD Tech, founded by a couple of long-time Drupal contributors". According to the email, the company has been in "stealth mode" quietly working on their new product which is ready for launch this week. Given that I'm a long time fan of the Drupal content management system of course I said yes.
As was mentioned earlier this week, today is the day Drupal 8 becomes official and is released for public consumption. The last time CMS Report was given the opportunity to talk about a major Drupal release was in January 2011 with the release of Drupal 7. If you thought the three year waiting period from Drupal 6 to Drupal 7 was long, waiting nearly half a decade for Drupal 8 certainly feels like a lifetime in the world of content management. During this cycle of development, Drupal's own open source community has evolved and its developers have introduced hundreds of changes into the Drupal content management platform.
I admit it. When looking at the calendar my eyes have been focused on November 19, 2015. This is the date that Drupal 8, under development since 2011, is expected to be released. But for Drupal 6 users, the beginning of Drupal 8 also marks the beginning of the end for Drupal 6 support. Announced on Drupal.org, Michael Hess writes that Drupal 6 will reach end-of-life on February 24 2016.
As announced in the Drupal 6 extended support policy, 3 months after Drupal 8 comes out, Drupal 6 will be end-of-life (EOL).
On February 24th 2016, Drupal 6 will reach end of life and no longer be supported.
What this means for you:
On March 24, 2015, the Drupal community lost Aaron Winborn who was diagnosed with ALS a few years ago. In honor of Aaron, the Drupal Association and Angie Bryon recently announced the Aaron Winborn Award. The announcement reads as is:
When I talk about Drupal, information technology and the weather all in the same breath, I get a little excited. I can't help myself. I'm biased toward Drupal as it is one of my favorite content management systems. I'm also a former meteorologist working in information technology for a very large organization that is heavily involved with the weather. Needless to say, a year or two ago when I heard that The Weather Channel started using Drupal to meet the needs of it's customers and meteorologists, it caught my attention. I think the use of Drupal is a win-win for everyone around and given my background, I wish my own employer had adopted a similar solution. I think organizations miss out on a lot when they don't utilize open source or even proprietary systems in favor of an in-house CMS.
For the first time in 15 years, my family doesn't have a website to call their own. In January 2000, I registered the domain Bryansplace.com. This was the first website I ever built outside of work and it became a sandbox for me to express my interests as well as a way to seek personal growth. From handwritten HTML pages into Frontpage to a number of CMSs, the software and content at Bryansplace evolved as my life evolved.
Over the years, I've made it an unwritten policy not to sensationalize bug fixes and security vulnerabilities in content management systems. While there may be great interest in such stories, I believe such stories have a tendency to cause more harm than good. When sensationalized, such articles tend to cause customers to address security concerns with emotion instead of logic which is never a good thing. So, when the security vulnerability known as "Drupageddon" broke and Drupal developer Bevan Rudge posted "Your Drupal website has a backdoor", I knew this story was going to eventually reach mainstream media. In the meantime, I've been struggling on how best to write this article and what story need to be told.
Well, this certainly wasn't on my radar. Gábor Hojtsy, Drupal 6 lead maintainer, announced that starting March 1, 2014 support for PHP 4 in Drupal 6 will end. I wasn't surprise to hear about Drupal developers dropping support for PHP 4. Instead, I was in shock to hear that Drupal didn't drop support for this ancient version of PHP sooner.
To put this announcement in perspective, the PHP project developers said their goodbyes to PHP 4 back in 2008 and I personally said my "see ya later" back in 2007. Needless to say, I don't think anyone with merit can complain Drupal is dropping PHP 4 support. In Gábor Hojtsy's words:
Drupal 6.0 was released almost 6 years ago in February 2008. The Drupal community is committed to release Drupal 6 bugfixes until Drupal 8.0 is released and with recent changes provide security fixes much longer.
The hosting and development landscape was very different in 2008 though. PHP has gone a long way since we released Drupal 6. While Drupal 6 is still supported on PHP 4.x, the PHP developer community itself end-of-lifed PHP 4 just half a year after Drupal 6.0 came out. According to public statistics and data available to us about Drupal 6 sites, we estimate that there is a very small number of Drupal sites which may still run on PHP 4. We also don't believe it is in our best interest to support Drupal 6 on a possibly insecure but definitely unsupported base system, so we discussed and decided to drop support for PHP 4 on March 1st 2014.
Typically, Drupal has dropped support for an older versions of Drupal when a new version of Drupal is released. The expectation was Drupal 6 support would be dropped when Drupal 8 becomes an official release. I suspect the delay in dropping Drupal 6 support is postponed partially due to a change in Drupal 8's new site migration approach. There is a new workflow for site migration that has the potential for site owners to migrate their content not only from Drupal 7 to Drupal 8 but also allow Drupal 6 sites to migrate directly into Drupal 8. Until the new migration approach is proven, it is in everyone's interest to continue support for secure Drupal 6 sites. For the "secure" mandate to be supportable no website should be running on PHP 4.