#Updating drupal core update#
#Updating drupal core manual#

Read the manual on the Terminus commands and plugins used below. If you’re patching core, use your preferred process to handle that, not the outline below.

#Updating drupal core update#

This depends on which files the update touches, and what you’ve patched. The processes below may blow away applied patches or other changes to core. Sites using composer workflow are not handled with the instructions below. Use your normal multidev workflow, and make sure that they are locked until you can apply updates. Or, the security patch could be applied to the multidev branch locally and pushed up to Pantheon. Usually a merge or rebase from the master branch will be required. Multidevs should not be ignored, but are not handled with the bulk commands below. Once the new upstream is available, sites can be updated manually through the Pantheon dashboard, individually using Terminus, or in bulk using Terminus and a couple of helpful Terminus plugins. The forked version is called the “upstream”. When Core is updated, Pantheon must merge those changes into its forked version before making it available to sites. Pantheon uses a forked version of Drupal. This post assume you’ll fit that in where you need to. Sometimes you may not have time to use your normal QA process if it’s not built into whatever your using for integration and deployment. While the benefits might be obvious - you need to update all of your sites fast and with confidence, there is one potential risk. The examples below show some of our favorites and how they might be used. Many tools and Terminus plugins are available. Taking care of multidevs or sites using composer-based workflows is not covered. This post covers basic Drupal sites on Pantheon. Attackers were exploiting Drupal sites within hours of the most recent update.įortunately, Pantheon and other hosting platforms provide tools to make the update work easier.

For agencies or busy freelancers, when an urgent security update is announced, and it applies to all your clients, you need to be prepared to take care of it fast. Hackers are smart and want to park on your lawn, or steal your bike. Drupalgeddon? Again? Yup, it happens, with Drupal or any software exposed to the internet.