![]() ![]() Read the full change record for more technical details: The sync directory is defined in $settings and not $config_directories. Now in Drupal 8.8.x, this setting should be updated to look like this: $config_directories = dirname(DRUPAL_ROOT). Here is what a custom config sync directory might have looked like in Drupal 8.7.x or lower. If you do customize this location, note that Drupal no longer uses the $config_directories variable. It makes config files easier to understand and manage. It is very common practice to customize this location. The default location for Drupal’s config sync is sites/default/files/config_. The configuration management system introduced a new sync directory syntax for 8.8.0. It also describes how to walk it back to a working state if you encounter this problem. This Drupal core bug report provides more detail. What if I neglect to update Pathauto? How can I identify the symptoms of this problem? After running drush updb, I would expect to see this SQL error: SQLSTATE: Integrity constraint violation: 1062 Duplicate entry '7142' for key 'PRIMARY': INSERT INTO ![]() Visit the full change record for more details: Drupal 8.8.0 requires pathauto version 8.x-1.6 or higher if installed. While the release notes say it is safe to update “before or at the same time” as core, it is good to have some extra precaution around the sequence of events. The order of operations is important here, because updating Pathauto after core will result in data loss. I strongly suggest updating Pathauto as a first step, and deploying all the way to production. If you have Pathauto installed on your site, you must first update to Pathauto 8.5-1.6 or later. However, this module conflicts with the Pathauto contrib module at version 8.x-1.5 or below. With over 7 million downloads and 675K reported sites using Pathauto, chances are high that this section applies to you.ĭrupal core 8.8.0 introduced the path_alias module into core. The Pathauto module has been around for a long time. Comfortable using the command line tool Drush.Maintaining a Drupal 8 site on version 8.7.x.This post will cover four common pitfalls of upgrading to the 8.8.x branch: Drupal 8.7.11 also has fixes for those SAs, but developers might consider this a golden opportunity to take care of both updates at once. On the heels of this release, we also saw a security release for Drupal 8.8.1, which covers four distinct security advisories (SAs). Welcome! If you need to update your Drupal 8 site to the latest feature branch, this post is for you.ĭrupal 8.8.0 introduced many exciting changes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |