Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException: The service "pathauto.alias_storage_helper" has a dependency on a non-existent service "path_alias.repository". in Symfony\Component\DependencyInjection\Compiler\CheckExceptionOnInv [#3100173]

I updated Core to 8.8 after running drush updb I'm getting the following error:

Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException: The service "pathauto.alias_storage_helper" has a dependency on a non-existent service "path_alias.repository". in Symfony\Component\DependencyInjection\Compiler\CheckExceptionOnInvalidReferenceBehaviorPass->processValue() (line 31 of /Users/ahmadk/Sites/auto_d88/vendor/symfony/dependency-injection/Compiler/CheckExceptionOnInvalidReferenceBehaviorPass.php).

I restored the site before updating core, uninstalled path_auto module, then did the update of core, everything works perfectly. When enabling path_auto module on updated site I'm getting the same error message.

Please note the original site before the update was at version 8.7.7 and path_auto module was at version 8.x-1.4

Comments

Comment #1

11 December 2019 at 03:03

WebKings.ca created an issue. See original summary.

Comment #2

cilefen CreditAttribution: cilefen commented 11 December 2019 at 14:03

Did you consider updating pathauto?

Comment #3

cilefen CreditAttribution: cilefen commented 11 December 2019 at 14:05

In the issue you related, comment #12 points out that the 8.8.0 release notes specify that you must upgrade pathauto.

Comment #4

WebKings.ca

He/Him

London (Canada)

CreditAttribution: WebKings.ca commented 11 December 2019 at 22:18

Status:

Active

» Fixed

I have tried the Update again using a different procedure and this time it worked!.

To help others facing this issue, below is the full procedure that worked to update my existing site with the drupal-composer/drupal-project composer template to the Drupal Core 8.8 version with the new drupal/recommended-project composer template.

1) Updated Core, pathauto and other Contrib modules in the existing site's composer.json file using instructions from the following blog:

https://www.previousnext.com.au/blog/updating-drupal-880-beta-composer

2) Update your composer.json file to the new composer.json Drupal recommended template (Add your modules from the require and require-dev sections to the new template)

3) Remove vendor and composer.lock:
rm -rf vendor
rm composer.lock

4) Change permissions of /web/sites/default folder:
chmod -R 755 ./web/sites/default

5) Run composer install:
composer install

6) Update Database:
drush updb

7) Clear Cache
drush cr

Test site's status report page.. Should indicate latest core version and everything should be running...

Comment #5

xurizaemon

he/him

Ōtepoti, Aotearoa 🏝

CreditAttribution: xurizaemon at Catalyst IT commented 12 December 2019 at 22:15

I ran into this too, having run up a project with drupal-composer/drupal-project rather than the new drupal/recommended-project.

Fix was to regenerate the project as Webkings.ca says above. I just created a new project based on the documented method and copied the essentials over into my existing project.

Before that, Drupal had no path_alias module available and would not move past version 8.8.0-alpha1 (clue). Afterwards, proper 8.8.0 and all good. Don't forget to `drush updb` :)

Thanks!