Updating modules in Drupal 8 is similar to updating modules in Drupal 7 - the drush pm-update (drush up) command still works, but there's a new "gotcha" that you need to look out for when updating modules that work with entities.
Sometimes, after updating modules that interact with entities, you'll see a "Entity/field definitions: Mismatched entity and/or field definitions" error on your site's status report (admin/reports/status).
Calling this book a "second edition" is more than a little bit curious, since there is no Drush for Developers (First Edition). I can only assume that the publisher considers Juampy's excellent Drush User's Guide (reviewed here) as the "first edition" of Drush for Developers (Second Edition), but that really minimzes ths book, as it is so much more than an updated version of Drush User's Guide. It would be like saying The Godfather, Part 2 is an updated version of The Godfather - which is just crazy talk. Drush Developer's Guide is more of a sequel - and (like The Godfather, Part 2) a darn good one at that.
I recently made the switch from another (several) code editors to PhpStorm based on the recommendations of several members of the Drupal community - not to mention all the postive things I've heard about it on IRC and various other places.
My main motivation for making the switch was the ability to have a integrated debugger - both when running Drupal in a web browser and via Drush. While there are plenty of resources online demonstrating how to set up the debugger, I found that I needed to do a combination of things to make it happen
I recently discovered the solution to a long-standing drush issue I have been experiencing on Mac OS X. The symptoms of the problem included several mysterious fatal errors that would crop up from time-to-time as well as the fact that I've had to use the --uri=mysite.dev parameter for every local site on my computer.
Doug Hercules ( dhercjr on drupal.org ) is a graduate of the 2012 class of the DrupalEasy Career Starter Program ( http://drupaleasy.com/dcsp ) and currently working as an intern with DrupalEasy. This week I had the opportunity to clone a website from a git repository using Quickstart . Quickstart is a really quick, pre-made PHP Drupal development environment in a VirtualBox , which allows you to install a virtual machine to run Linux on your Windows PC. I've only gone through the process of cloning a site into Quickstart once before, and this time I thought I’d document it in my blog for myself and anyone else who might want to do this in the future. The general idea is this - there’s a site that I need to work on that is stored in a remote git repository. I want to get a copy of the site up-and-running inside Quickstart. To get started, I downloaded Quickstart, installed VirtualBox, then imported the Quickstart file into it.
3.. 2.. 1.. and lift-off of a new career!!! Here I go off to explore a new world that just 6 months ago I’d never even heard of! The strange blue teardrop world of Drupal! For the past 20 years, I have been blessed to work my dream job as an engineer in the Space Shuttle Program, what a ride! The retirement of the shuttles meant a new direction in my life, and since there’s not a huge demand for rocket scientists these days, it meant seeking some new doors to open up and see what’s out there. I happened upon a chance to enroll in a 10-week web development course called DrupalEasy Career Starter Program , so I dove right in not having any computer background, but realizing the web is the future! I successfully completed the class and am now starting an internship and an introduction into the community of Drupal. With all the helpful support in Drupal, it’s not a program you learn - it’s a universe of mutual relationships you join... so here’s my first step towards growing in the community.
Every so often I will find myself needing to update lots of Drupal modules but not one in particular. Perhaps I have patched the module, or perhaps there is a new version of the theme that I know will break my site layout.
Drush can save you from this dilemma, as of version 4.x - yes, it's true!
It never fails - regardless of the skill level of the Drupal workshop that I'm teaching on any given day, the topic of Drush always sneaks its way into the conversation. Normally, it's because I have to quickly download a module to demonstrate something that has come up in class. Rather than navigating to the module's project page, I just quickly jump to the command line and do a "drush dl whatever" and hope that no one notices the witchcraft I just invoked - this inevitably results in the nerdiest student in the class perking up and wanting to know what the magic is that they just saw...
One of the primary ways of keeping a Drupal site of any size running securely and at peak performance is to ensure that all of its modules stay updated. With thousands of modules in the Drupal eco-system, updates are released literally every day. Luckily, Drupal core's Update Status module helps site administrators keep notified of modules in need of updating. In this article, you'll learn how to use the power of Drush and Apache Subversion (aka "svn"), a revision control tool, to update your site's module quickly and safely. You'll be presented with two methods for solving the problem. The second method is much faster, but comes with a caveat. Read on.
We love Drush, Drupal's all-purpose command-line tool, for people who can't stand checkboxes. It's fast, efficient, plays nicely with Version Control Systems like CVS, SVN and Git, and even cleans the kitchen sink. However, after moving our DrupalEasy.com site to a new server we encountered a minor snag. When trying to run even the simplest of Drush commands, we were faced with the following error:
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 311296 bytes)