This file contains instructions for updating your Skeleton-based Drupal site.
Skeleton has a two-pronged update process. Out of the box, it provides a great deal of default configuration for your site, but once it's installed, all that configuration is "owned" by your site and Skeleton cannot safely modify it without potentially changing your site's behavior or, in a worst-case scenario, causing data loss.
As it evolves, Skeleton's default configuration may change. In certain limited cases, Skeleton will attempt to safely update configuration that it depends on (which will usually be locked anyway to prevent you from modifying it). Otherwise, Skeleton will leave your configuration alone, respecting the fact that your site owns it. So, to bring your site fully up-to-date with the latest default configuration, you must follow the appropriate set(s) of instructions in the "Manual update steps" section of this file.
If you've installed Skeleton using our Composer-based project template, all you need to do is:
cd /path/to/YOUR_PROJECTcomposer update- Run
drush updatedbor visitupdate.phpto perform db updates. - Perform any necessary manual updates (see below).
Do not use drush pm-update or drush up to update Skeleton!
Skeleton includes specific, vetted, pre-tested versions of modules, and
occasionally patches for those modules (and Drupal core). Drush's updater
totally disregards all of that and may therefore break your site.
To update Skeleton safely:
- Download the latest version of Skeleton from https://github.com/drupalwxt/skel and extract it.
- Replace your
profiles/skeldirectory with the one included in the fresh copy of Skeleton. - Replace your
coredirectory with the one included in the fresh copy Skeleton. - Visit
update.phpor rundrush updatedbto perform any necessary database updates. - Perform any necessary manual updates (see below).
These instructions describe how to update your site's configuration to bring it in line with a newer version of Skeleton. These changes are never made automatically by Skeleton because they have the potential to change the way your site works.