lohanuts.blogg.se - Drupal 8 upgrade core shell script

#Drupal 8 upgrade core shell script install#
#Drupal 8 upgrade core shell script code#

htaccess, which are required for Drupal to run but don't live within the core/ directory. The scaffolding manages core files like index.php and.

On Pantheon hosting, the host-specific temp directory is set in their drops-8 distribution.ĭrupal 8.8 introduced scaffolding in core and separated dev dependencies into a separate package.On Acquia hosting, the temp directory path can be found in the environment variable $_ENV, as shown in the snippets above.Replace this (using your environment-specific path) with: $settings = $_ENV More information local development.Ĭheck your settings.php files for the temp directory configuration: $config = $_ENV The temp directory is usually specific to your host or the environment where your Drupal site is running, so you may need to set this differently for production vs.

The sync directory is defined in $settings and not $config_directories.Replace this (using your original path) with: $settings = './config/sites/default' More information

Before Drupal 8.8, you could configure multiple directories for exporting config now there's only one, and the variable name has changed.Ĭheck settings.php files for the $config_directories variable: $config_directories = The config sync directory is where Drupal stores your exported configuration YAML files. : Coder is a library to review Drupal code.įirst, find your settings.php file this will be within your Drupal site at sites/default/settings.php, or may be an include file named like sites/default/settings.*.php. (develop) $ composer show drupal/coderĭescrip.

You'll see the package information with the version - in this case, 8.2.10:.

Drupal 8.8 requires a minimum of version 8.3.2.

#Drupal 8 upgrade core shell script code#

If you're using Coder to do automated code review against the Drupal coding standards, you may need to update.

#Drupal 8 upgrade core shell script install#

Additionally, the Drupal 8.8 release introduces an incompatibility between core Content Moderation module and the contrib Workspace module.Īs of December 2019, there is no ready-made upgrade path from the contrib module to the core module the recommendation is to uninstall the contrib module - which will delete all workspace content that is not yet live - and then install core's module ( documentation).Ĭheck this bug report on the contrib Workspace moduleįor now, if you're using the contrib Workspace module and the core Content Moderation module, you will not be able to update to Drupal 8.8 Workspace isn't common on our sites, so running into an issue with it usually means doing some research. The contrib Workspace module has been moved into core, and renamed "Workspaces" installing both modules on the same site creates code-level conflicts.

While your site is still running Drupal 8.7, update Pathauto to the latest release (8.x-1.6):.

If you don't update Pathauto while you're still on Drupal core 8.7, you could lose your path alias data! We use the Pathauto module on all of the sites we build, and Pathauto needs some handholding in this update process.

Update composer.json: Manually update your composer.json.

Update settings.php: Change the temp and config sync directory variables settings.php.

Contrib module conflicts: If your site is using the contrib modules Pathauto, Workspace, or Coder, update those first.

We also want to give a shout-out to the folks at PreviousNext for their post on what they learned when updating to the 8.8 beta release. The update to 8.8 is more involved than previous Drupal 8 point releases because 8.8 renames some configuration variables and changes the core drupal packages and dependency structure in composer.json, which means that updates need to be made to both settings.php and composer.json.Īt Palantir, our team maintains many Drupal 8 sites in both active development and support, and we've documented some important tips that are important to keep in mind when updating your site to 8.8. Drupal 8.8 contains both the deprecated APIs and the new APIs that will become standard in Drupal 9, so once your site is on 8.8, you can begin to review your contrib modules and update your custom code to move from deprecated APIs to the state of the art. No new features will be added in the 9.0 release, which means that 8.8 has feature parity to streamline the upgrade path between 8.x and 9.x. If you're currently running a Drupal 8 site and are interested in upgrading to Drupal 9 when it is released in the summer of 2020, the first step is to update to the recently-released Drupal 8.8.