This file contains instructions for updating your FGP-based Drupal site.
FGP 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 FGP cannot safely modify it without potentially changing your site's behavior or, in a worst-case scenario, causing data loss.
As it evolves, FGP's default configuration may change. In certain limited cases, FGP will attempt to safely update configuration that it depends on (which will usually be locked anyway to prevent you from modifying it). Otherwise, FGP 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 FGP using our Composer-based project template, all you need to do is:
cd /path/to/YOUR_PROJECT
composer update
- Run
drush updatedb
or visitupdate.php
to perform db updates. - Perform any necessary manual updates (see below).
Do not use drush pm-update
or drush up
to update FGP!
FGP 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 FGP safely:
- Download the latest version of FGP from https://github.com/drupalwxt/fgp and extract it.
- Replace your
profiles/fgp
directory with the one included in the fresh copy of FGP. - Replace your
core
directory with the one included in the fresh copy FGP. - Visit
update.php
or rundrush updatedb
to 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 FGP. These changes are never made automatically by FGP because they have the potential to change the way your site works.