Problem/Motivation

Once the drupal_cms_seo_basic recipe is applied, reapplying it or applying any recipe that depends on it fails with an error:

The configuration 'pathauto.pattern.menu_path' exists already and does not match the recipe's configuration

This is because the pathauto.pattern.menu_path config lacks a starting slash in its path pattern, which Drupal detects and adds when importing the config.

Steps to reproduce

  1. Install any site template.
  2. From the command line, run drush recipe /var/www/html/recipes/drupal_cms_seo_basic

Proposed resolution

Add a starting slash to the path pattern in the pathauto.pattern.menu_path config.

User interface changes

None.

Configuration changes

The pathauto.pattern.menu_path config will match the config that Drupal saves on import.

Issue fork drupal_cms-3589783

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

darren oh created an issue. See original summary.

darren oh’s picture

darren oh
Primary language English
Location Lakeland, Florida
commented
Issue summary: View changes
darren oh’s picture

darren oh
Primary language English
Location Lakeland, Florida
commented
Issue summary: View changes

darren oh opened merge request !879

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
commented

Sounds like a reasonable fix to me.

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
commented
Status: Active » Fixed

Thanks, Darren! This bug fix is a no-brainer for sure.

I confirmed that this would make the menu_path pattern match other Pathauto patterns we ship in our recipes. Merged into 2.x and cherry-picked to 2.1.x.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.