You have no choice about the necessity to integrate your observations, your experiences, your knowledge into abstract ideas, i.e., into principles. Your only choice is whether these principles are true or false.
Migrate is horribly broken! Migrate works awesome! Both are true. (Yes!) So Keith Dechant reported migrating a live Drupal 7 site to Drupal 8. Melissa Anderson is migrating a Drupal 6 site and gets mostly bugs. How is this possible? Well, Keith was coding his way around bugs, not just using what core provided (this should be obvious since we do not yet provide Drupal 7 sources in core) and Melissa had a site builder approach to it. Both of them are poised to contribute: Keith will share his code for Drupal 7 in the sandbox and Melissa files great bug reports and writes documentation with tips of how to use xdebug to find out what's broken with a migration. At this juncture if you are not prepared for either you will have a bad time with using migrate. Otherwise, see, it works!
Weather.com is the highest trafficked Drupal site in existence, with over 1 billion unique visitors per month. The Weather Channel teamed up with Mediacurrent to migrate from their previous content management system to Drupal. Not only were we able to help The Weather Chanel adopt an open-source solution, but the new website has drastically improved page load times and reduced infrastructure requirements.Key modules/theme/distribution used: PanelsServicesWysiwygOrganizations involved: MediacurrentAcquiaTeam members: jeffdiecksSilicon.ValetKendall TottenkbasarabjamesrutherfordAndrew M Rileypaulmckibbenderek.derapsmrjmdmarkie
There are many paid and free Drupal training sites on the internet. To the best of my knowledge, none of them is open source. And I'm quite certain none of them is "ridiculously open."
In the first post of this series on Drush Make we looked at building a custom Drupal install profile on Acquia Cloud using Drush make. In this installment, we look at managing and updating the code in your install profile and deploying it onto Acquia Cloud. Keeping up with new releases is one of the most important aspects of maintaining any site and leveraging Drush make can dramatically reduce the effort involved with that process.
As things stand today, Drupal.org's mirror network is an essential part of the Drupal.org infrastructure. The ftp.drupal.org infrastructure hosts millions of files, serving everything from Drupal Core to contributed modules and themes, but it's beginning to show its age.
Our current FTP mirrors (co-located, in Oregon, Illinois, and New York) have been behaving erratically: projects have been failing to sync to the mirrors, being deleted before update, and sometimes disappearing from the mirrors for hours or days at a time. Even when working properly, the replication from the primary to additional mirrors can take as much as 45 minutes.
Compounding these issues is the fact that we do not have robust control or access to the existing architecture when problems arise.
So we've taken a step back to ask:
How can we deliver these files in a more reliable way?
On the modern web, the key elements of file delivery are:
- High availability
- Peering capacity designed for global delivery
- Fast replication
- HTTPS/TLS support
A Content Delivery Network is the answer to these problems, which is why we're evaluating MaxCDN to replace the ftp.drupal.org infrastructure.
But wait - does this mean the ftp:// protocol will no longer work?
Yes. The FTP protocol is aging as well...
- In the month of October 2014, ftp:// had 96 unique visitors. Of those 96 unique visitors, only 33 of them made over 10 requests.
- The ftp pathing differs from http, making the experience of using ftp:// confusing and inconsistent.
- Replacing the ftp:// protocol with http will enable us to secure Drupal.org with HTTPS across all domains.
How you can help
We need users to help us test MaxCDN as an alternative for file delivery. You can track the issue here, and help us by testing the MaxCDN based downloads. Please report back your findings (good or bad) and let us know if there are any showstoppers.
To test, add this line to your /etc/hosts file:
~$ sudo vim /etc/hosts
And continue using ftp.drupal.org as you normally would through Drupal.org project pages, drush dl, etc.
When my business partner, Paul Chason, and I joined forces over seven years ago we had a rather simple vision for Mediacurrent. We were convinced that open-source software offered a superior value proposition over proprietary, licensed based solutions. We had an ambitious goal of starting a digital agency that was going to revolutionize how companies thought about the way they managed their web properties. As Simon Sinek so eloquently describes, this was our "why" and purpose.
As AppNeta’s developer evangelist, I work with customers in five different programming languages to monitor application performance. Drupal is just one part of one language, but I’ll always have a soft spot for it because it’s where I learned to program. When I get a chance, I like to keep my skills sharp by contributing to the community-maintained TraceView integration module. Last spring, I decided to port it and learn Drupal 8 the hard way.
Like most Drupal developers, I’d never tried writing Symfony code or using Composer to manage packages. Before attempting it, I decided to research both Symfony in its own right and how it is being leveraged to rewrite Drupal. Thankfully, there were many rich tutorials on “the basics” even then, and, after a relatively painless porting process, I had the module running with a skeletal Symfony bundle inside it.
Initially, I relied on the same strategy as the Drupal 7 version of the TraceView module, which monitors hook execution time by installing two additional modules: an “early” module with a very low weight and a “late” module with a very high weight. As each hook was removed from core, I moved its implementations from the modules into the bundle and tagged that event with listeners at maximum and minimum priority.
One of the world's most trafficked websites, with more than 100 million unique visitors every month and more than 20 million different pages of content, is now using Drupal. Weather.com is a top 20 U.S. site according to comScore. As far as I know, this is currently the biggest Drupal site in the world.
Weather.com has been an active Drupal user for the past 18 months; it started with a content creation workflow on Drupal to help its editorial team publish content to its existing website faster. With Drupal, Weather.com was able to dramatically reduce the number of steps that was required to publish content from 14 to just a few. Speed is essential in reporting the weather, and Drupal's content workflow provided much-needed velocity. The success of that initial project is what led to this week's migration of Weather.com from Percussion to Drupal.
The company has moved the entire website to Acquia Cloud, giving the site a resilient platform that can withstand sudden onslaughts of demand as unpredictable as the weather itself. As we learned from our work with New York City's MTA during Superstorm Sandy in 2012, “weather-proofing” the delivery of critical information to insure the public stays informed during catastrophic events is really important and can help save lives.