Hi there! We are experiencing this issue as well.
We were able to get `drush` working again (and get the site working as well) using Pantheon's SFTP dev mode, and editing `settings.pantheon.php`. There, we are temporarily commenting out the following:
if (isset($_ENV['PANTHEON_ENVIRONMENT'])) {
$GLOBALS['conf']['container_service_providers']['PantheonServiceProvider'] = '\Pantheon\Internal\PantheonServiceProvider';
}
Which suggests that pantheon service provider is the one messing things up. We have an open case with Pantheon's support, and they are looking into it. I'll report back as soon as they fix the issue.
Cheers!
The patch in #6 works for me. Thanks!
D11 Rector fixes for the current 5.1.x version.
Hi there! #14 works for me. We're on version `^2.0`.
Thanks for the patch!
Re-rolling patch to work with version that includes information added by Drupal.org.
Hello there.
This might be related:
https://www.drupal.org/project/drupal/issues/3442910
🐛
Error "Non-reusable blocks must set an access dependency for access control." with layout builder and media library
Active
I hope it helps.
Hello there. I just added a patch to issue 3442910 that might help with this.
https://www.drupal.org/project/drupal/issues/3442910#comment-15887170 🐛 Error "Non-reusable blocks must set an access dependency for access control." with layout builder and media library Active
I hope it helps.
I believe the issue is that Content Blocks can have revisions turned off on a per bundle (type) basis. When this is the case, the access dependency fails to work properly in `getInlineBlockDependency` , since it tries to work on the latest revision only.
This patch might be helpful. I hope it helps.
Re-rolling patch to make it compatible with Drupal 10.3
The patch mentioned in #17 breaks the Remove button of image fields using the Entity Browser + Image Browser, on a content type.
Patch #6 fixes the original issue for me; without affecting regular image fields.
The issue is still present on the latest version (`8.x-1.16`). Re-rolling patch.
Re-rolling patch for version `2.3.0`
Hi @lemming thanks for the explanation and reviewing the patch. Here's the change you requested.
Patch didn't pass automated tests. Fixing.
esolano → created an issue. See original summary → .