Problem/Motivation

Installing the Acquia DAM module on Drupal Core 9.5.x throws following error:

In Route.php line 523:                                                                                       
  Routing requirement for "_acquia_dam_site_authenticated_access_check" must be a string.  

This is caused because of the change introduced in #3446787: If site is not authenticated, hide metadata form and user auth page.

Steps to reproduce

composer create-project drupal/recommended-project:9.5.11 9.5.11 && cd 9.5.11
composer config minimum-stability dev
composer require drupal/acquia_dam:1.1.x-dev drush/drush
./vendor/bin/drush site:install minimal --yes && ./vendor/bin/drush en acquia_dam --yes

Proposed resolution

The value for _acquia_dam_site_authenticated_access_check must be string here, but boolean value TRUE given. This is causing it to fail. But strangely, this is not failing on Drupal Core 10.x and above.

Issue fork acquia_dam-3457556

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:

Comments

vishalkhode created an issue. See original summary.

vishalkhode’s picture

Title: Installating Acquia DAM on Drupal Core 9.5.x throws error » Installing Acquia DAM on Drupal Core 9.5.x throws error.

vishalkhode’s picture

Status: Active » Needs review
chandu7929’s picture

Status: Needs review » Reviewed & tested by the community

Looks good to me.

baluertl’s picture

I was needed to use this patch for some other reason (1.0.x-dev on 9.5.11 core), confirming RTBC +1.

baluertl’s picture

Title: Installing Acquia DAM on Drupal Core 9.5.x throws error. » Installing Acquia DAM on Drupal Core 9.5.x throws error
baluertl’s picture

Setting the MR's target branch to the default 1.0.x as Jakob suggested.

baluertl’s picture

Version: 1.1.x-dev » 1.0.x-dev

Balu Ertl credited japerry.

baluertl’s picture

Status: Reviewed & tested by the community » Fixed

Suggested change was committed into the default branch 1.0.x in commit 1eb3f167.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.