We will cover "Getting off the Island" and learning from other projects and technologies, the state-of-play in the Drupal 8 release cycle, the integration and use of the Symfony framework components, new development techniques, and more.
Mike Ryan (mikeryan), author, maintainer of the Migrate module, and Acquia’s unofficial “migration guy” joins Ted Bowman and Mike Anello on the one-hundred-and-twelveth episode of the DrupalEasy Podcast. The Migrate module is covered from all angles, including the Drupal-to-Drupal Data Migration module, the future of the migrate module, and contributed module support. Recent departures from the list of Drupal 8 maintainers leads to an interesting discussion about the possible effects of the major Drupal 8 code changes on the rate of Drupal 7-to-Drupal 8 module upgrades. Finally, we wraps things up with some picks of the week and Mike Ryan’s answers to our five questions.
If you work on large Drupal sites, you probably run into the problem of the enormous "files" directory. Keeping your development server (or personal computer) in sync with production is a big pain, but without those uploads and file attachments it's easy to miss important design problems with site content.
There are lots of slow, complicated ways to solve the problem. Drush commands, shell scripts and even (please say no!) FTP can be used to download all of a site's image assets and file uploads to your local development machine. I want to save that precious disk space, though!
There are many times when a custom module provides functionality that requires a tweaked or radically altered template file, either for a node, a field, a view, or something else.
While it's often a better idea to use a preprocess or alter function to accomplish what you're doing, there are many times where you need to change the markup/structure of the HTML, and modifying a template directly is the only way to do it. In these cases, if you're writing a generic custom module that needs to be shared among different sites with different themes, you can't just throw the modified template into each theme, because you'd have to make sure each of the sites' themes has the same file, and updating it would be a tough proposition.
I like to keep module-based functionality inside modules themselves, so I put all templates that do specific things relating to that module into a 'templates' subdirectory.
Shield is a cool module that lets you set up HTTP authentication for your Drupal site if you are running it on an Apache server.