#REVERT DRUPAL CORE UPDATE MINOR HOW TO#
#REVERT DRUPAL CORE UPDATE MINOR INSTALL#

#REVERT DRUPAL CORE UPDATE MINOR INSTALL#

# and a link to composer.phar in the install directoryĮcho ' MAJOR: The new MAJOR version to install - e.g., 8.6'Įcho ' MINOR: The new MINOR version to install - e.g., 14 (for 8.6. # This script uses drush to initiate database updates Assumes there is a drush link to vendor/drush/drush/drush # A script to upgrade a Drupal installation to the next minor version Once you have confidence in the script, you can remove the diagnostics and pauses.

Save the script in your main Drupal directory. I have used this script to successfully update major (5.5 -> 5.6) updates, and minor updates (5.6.14 -> 5.6.15).

#REVERT DRUPAL CORE UPDATE MINOR HOW TO#

The information in exceptions may provide important cues to users as to how to address the problem. For example, a potentially common source is missing config entity dependencies. Adopting semantic versioning simplifies this. Problem/Motivation Configuration revert and import operations may throw exceptions for various reasons. The projects info.yml file resolved the ambiguity. In earlier versions, for example, a contributed module of version 1.0.0 might refer to 8.x-1.0 or 7.x-1.0 depending on the Drupal core version. When you are confident of the script, comment them out. Starting with this version, Drupal adopts semantic versioning.

I inserted pause statements in the script to enable you to make sure things are working correctly as the script is executed.

I assume that there are links to composer.phar and vendor/drush/drush/drush in the installation directory (where vendor and this shell script are located).

Although my script makes a backup of your files and database, I suggest you make your own until you have confidence in the script.

There are no guarantees of correctness or application to your site.

It occurred to me that I essentially do the same things to each site each time I update them, so why not create a shell script? So I did, and I offer it to others with the following provisos: And this is if there are no bugs in the provided update, and all goes smoothly. The Features module will notice any changes made to a component of any features and signal this with an Overridden state on the Features administration page. As a result, there have been a half-dozen Core updates in the past month, and it wastes 2–3 hours of my time whenever I must update my 6 sites. Asz a result, whenever any of the included projects have an architecture change, or security issue, the Drupal Core must be updated, and there is not an automatic way of doing this. Drupal 8 has integrated other projects and modules into the Drupal Core.

Revert drupal core update minor