Problem/Motivation

Enabling migrate_drupal_ui via command lines breaks drupal.

Steps to reproduce

  1. ./vendor/drush/drush/drush en --yes migrate_drupal_ui
  2. Load a random page e.g. /admin/appearance
  3. [php:notice] Uncaught PHP Exception BadMethodCallException: "The "\\Drupal\\migrate_drupal_ui\\MigrateAccessCheck::checkAccess" method is not callable as a _custom_access callback in route "/upgrade"" at web\\core\\lib\\Drupal\\Core\\Access\\CustomAccessCheck.php line 78, referer: admin/appearance

Workaround:

  1. ./vendor/drush/drush/drush pm:uninstall migrate_drupal_ui
  2. Enable migrate_drupal_ui via modules page.

Proposed resolution

Remaining tasks

User interface changes

None

Introduced terminology

API changes

None

Data model changes

None

Release notes snippet

Comments

marc.bau created an issue. See original summary.

marc.bau’s picture

marc.bau
Primary language German
Location Germany
commented
Issue summary: View changes
aaron.ferris’s picture

aaron.ferris commented

Interesting, I don't seem to be able to recreate this based off the steps provided.

/admin/appearance loads as I would expect.

Drupal 10.4 as per the issue version?

quietone’s picture

quietone commented
Status: Active » Postponed (maintainer needs more info)

Same here. I can not reproduce with the given steps.

marc.bau’s picture

marc.bau
Primary language German
Location Germany
commented

Sorry, Drupal 10.3.2

marc.bau’s picture

marc.bau
Primary language German
Location Germany
commented
Version: 10.4.x-dev » 10.3.x-dev
quietone’s picture

quietone commented
Category: Bug report » Support request

Are you using a drush version compatible with Drupal 10.3?

marc.bau’s picture

marc.bau
Primary language German
Location Germany
commented

Drush Commandline Tool 13.0.1.0 got automatically installed... something wrong with it?

yuvania’s picture

yuvania
she/her
Primary language Spanish
commented

You could perhaps try using an older version of Drush, such as 12.x, which is known to be stable with Drupal 10.3, to see if that resolves the issue

marc.bau’s picture

marc.bau
Primary language German
Location Germany
commented

Today I have seen that enabling "navigation" module is also causing this issue.

I tend to say it may have something to do with modules that output a custom message after installation. This happens with migrate_ui and navigation. Both show a special info message with links after they have been enabled. Just a guess.

@yuvania: Thanks for this hint. Based on https://www.drush.org/13.x/install/ - drush 13 is compatiple with Drupal 10.2+. I can try v12, but I just followed the documentation and it should be fully supported with D10.3.

tolstoydotcom’s picture

tolstoydotcom
Location L.A.
commented

I tested this with D10.3.5 and Drush 13.2. I was able to visit content and admin pages after enabling that module with Drush. I didn't see any issues.

If you start a new site with 10.3.5, does this still happen? Maybe it's just a problem with the site you tested with.

quietone’s picture

quietone commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

So far, this has not been reproducible and tests exist for installing and using both modules. Therefor closing.

If you are experiencing this problem on a supported version of Drupal reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue starting from "Install Drupal core".

And a reminder that the Drupal Core issue queue is not the ideal place for support requests. There are several support options listed on our Support page. This is 'Get Support' at the top of Drupal.org. There is also information about Drupal Slack , at 'Get Support -> Drupal Slack' also at the top of Drupal.org. You may get better replies in one of those places.