Problem/Motivation
This is a regression caused by #2208429: Extension System, Part III: ExtensionList, ModuleExtensionList and ProfileExtensionList.
system_get_info() used to return the module name passed in even when it was handed something invalid. ModuleHandler::getName() used to call it, when it was changed to call ExtensionList::getName() directly, that behaviour wasn't preserved.
The issue is that the module list always includes the profile (for example on an 8.5 site I have locally, 'standard' is in core.extension.yml as a module). However the newly added extension list only has the profile as a profile.
I found #2939904: Fix system_get_info() for non-installed modules. ModuleHandler::getName() used to call system_get_info(), but now it calls ExtensionList() directly, so it needs to catch the exception too.
Proposed resolution
If an invalid module name is passed, catch the exception and return the raw module name passed in.
The root cause here is that profiles are sometimes treated as modules and sometimes not, #3023133: [PP-1] Extension System, Part V: Decouple profiles from modules is one issue trying to deal with that, but this is critical bug and clear regression.
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
Original report
I recently upgraded from Drupal 8.5.6 to 8.6.1 and everything appeared to go well. But I noticed today that when attempting to edit a view or review the user list on the site, I received this message:
Drupal\Core\Extension\Exception\UnknownExtensionException: The module minimal does not exist. in Drupal\Core\Extension\ExtensionList->get() (line 257 of /core/lib/Drupal/Core/Extension/ExtensionList.php).
I happened to be on the Status page for the install and noted the installation profile looked liked this:

This is what appears in the error log:
Uncaught PHP Exception Drupal\Core\Extension\Exception\UnknownExtensionException: "The module minimal does not exist." at /core/lib/Drupal/Core/Extension/ExtensionList.php line 257
So it looks like the install profile was removed when the upgrade was conducted.
| Comment | File | Size | Author |
|---|---|---|---|
| #112 | DrupalCoreExtensionList.patch | 979 bytes | meendru |
| #80 | drupal3000677.diff | 843 bytes | prlw1 |
| #79 | 3000677-79.patch | 2.01 KB | catch |
| #79 | interdiff-3000677-68-79.txt | 1.6 KB | catch |
| #68 | 3000677-68.patch | 1.45 KB | catch |
Comments
Comment #2
cilefen commentedComment #3
shane birley commentedAn update for this issue. I was digging around in the repository and I noticed that the file is still present in Drupal 8.5.x (at least in my files) and when I did the upgrade to 8.6.x the file was still there and it was used.
I have a suspicion the Acquia Dev Desktop software flubbed the install or the upgrade somewhere. A quick fix to this particular issue is to generate the file and place it back into that directory.
But moving forward, I should be removing the file in a future upgrade but where can I adjust the settings to make sure the upgrade uses the appropriate setup?
Comment #4
cilefen commented@Shane Birley To which file are you referring?
Comment #5
shane birley commentedAck. The problem has returned.
The file in question is: minimal.install in /core/profiles/minimal
Comment #6
shane birley commentedI placed the file into the directory and the problem appeared to be rectified. But after a cron run, the issue has returned.
There must be a process where I can reset the install profile correctly and remove the file that appears to have started the problem.
Update
At the moment, it appears to only be affecting the /admin/people page. Still digging.
Update II
Noted this on the status page. Hadn't seen it before.
Comment #7
ravi.sidd commentedHi
I am getting the following error when try to upgrade from 8.5.6 to 8.6.1
In ExtensionList.php line 257:
[Drupal\Core\Extension\Exception\UnknownExtensionException]
The profile Array does not exist.
Can someone suggest anything around this?
Comment #8
cilefen commentedThat could be the problem. This change record may be involved: https://www.drupal.org/node/2538996
Comment #9
shane birley commentedUsing the information from issue 2538996, I have:
The noted change on the status page is the installation profile has changed from "(-)" to "minimal-". It should be displaying "minimal-8.6.1".
Comment #10
shane birley commentedAfter making these changes, the site appears to restore functionality (no more white screens of death on certain pages). But two errors are now being generated in watchdog.
Error 1:
Error 2:
I haven't followed these down the rabbit hole yet.
Comment #11
cilefen commentedIndeed, minimal.install should not be there. #2914379: Remove minimal_install(), ship with default configuration instead
Comment #12
shane birley commentedFor my records here, after a couple of days, this error resurfaces when accessing /admin/people:
Clearing the cache fixes it. Then reappears a day or two later.
Comment #13
myriam_b commentedDo you find a solution ? Same problem with standard profile.
Comment #14
catchBumping to critical. Marking #3005074: The module standard does not exist as duplicate.
Comment #15
googletorp commentedIt would be helpful to know how your core.extensions.yml configuration looks like. I have a hunch this might be related to some of the changes done in 8.3.x. I remember having similar issues back then, but not quite the same.
Comment #16
myriam_b commentedI looked at my core.extensions.yml and found this line: "profile: standard", is it required ?
Comment #17
googletorp commentedRe #16
Do you mind sharing it. Also very important that what you get is your active configuration in case you use yml files to sync configs from dev to production in which case your files might not reflect the state of your site 100%.
Comment #18
asghar commentedHi All,
I upgraded the 8.5.6 to 8.6.1 with lando(docker) development environment and could not produce the error. I used the fresh version of 8.5.6 and upgraded to 8.6.1. Everything working fine. Thanks
Comment #19
badzilla commentedI got the same symptoms as https://www.drupal.org/project/drupal/issues/3005074 with the message 'The module standard does not exist'. I commented out the profile reference in settings.php with
#$settings['install_profile'] = 'standard';then
drush crand that solved the problem for me.
Comment #20
ConradFlashback commentedSame error, I have not updated the core but only migrated the site to another database with a simple settings.php change.
Drupal\Core\Extension\Exception\UnknownExtensionException: The module standard does not exist. in Drupal\Core\Extension\ExtensionList->get() (line 257 of /home/core/lib/Drupal/Core/Extension/ExtensionList.php).In the status panel I have this:
INSTALLATION PROFILE (-)I've commented this as suggested by #19
$settings['install_profile'] = 'standard';but nothing.
[EDIT]
I've run update.php and it works.
Comment #21
asghar commentedHi @ConradFlashback,
Are you facing issue on Acquia Dev Desktop(https://dev.acquia.com/downloads)?. I tried on Lando but could not produce the error. Thanks
Comment #22
asghar commentedAs mentioned in the settings.php
I think we can fix this by commeting *$settings['install_profile'] = '';* line.
Comment #23
ConradFlashback commentedHi asghar
No I'm not in Acquia.
Comment #24
shane birley commentedI have already removed my settings.php entry but the problem persists. Just want to point out that the removal of the entry in settings.php is not the only solve.
Comment #25
catchIt would help to get a backtrace from when this error occurs. If you don't know how to get one, this is a quick way - in ExtensionList.php, or apply the attached files using patch p1 < backtrace.txt
public function get($extension_name) {
$extensions = $this->getList();
if (isset($extensions[$extension_name])) {
return $extensions[$extension_name];
}
$e = new \Exception();
print_r($e->getTraceAsString());exit;
throw new UnknownExtensionException("The {$this->type} $extension_name does not exist.");
}
Obviously remove this change after you've got the backtrace.
Comment #26
joachim commentedHere is my backtrace of the crash on admin/modules
This is on a plain Drupal core site that I use for working on core patches. It was installed with the 'standard' distribution and I recently updated it to 8.7.x from (IIRC) 8.5.x.
Comment #27
catchOK this is a regression caused by #2208429: Extension System, Part III: ExtensionList, ModuleExtensionList and ProfileExtensionList.
The issue is that the module list always includes the profile (for example on an 8.5 site I have locally, 'standard' is in core.extension.yml as a module). However the newly added extension list only has the profile as a profile.
I found #2939904: Fix system_get_info() for non-installed modules. ModuleHandler::getName() used to call system_get_info(), but now it calls ExtensionList() directly, so it needs to catch the exception too.
Here's a patch, but we need test coverage for it.
Yet another reason install profiles shouldn't double up as modules.
Comment #28
catchNeeds to return a string, not an array.
Comment #29
catchThat's not right either. This is the code that was replaced:
Not worth an interdiff.
Comment #30
catchComment #33
tritof commentedHi, not sure to give any new info, but I have the same pb without using any profile (
$settings['install_profile'] = 'standard';is my settings but I suppose it is just the installation profile type), and I'm still on 8.6.0 version of Drupal.Drupal\Core\Extension\Exception\UnknownExtensionException : The module standard does not exist. dans Drupal\Core\Extension\ExtensionList->get() (ligne 257 de [...]/core/lib/Drupal/Core/Extension/ExtensionList.php).Also it came up without any update or anything. Yesterday working just fine on some views, today crashing. The ony action I did was sending a simplenews test. (Like 15 times.)
And I have an active duplicate version of the site just in case, hidden but on the same server, and it still works.
EDIT : 5 minutes later, I cleared the cache, and now it works, not right away clearing the cache though...
Comment #34
eppik commentedFollowing this thread. I run a Thunder profile on a build and a have a similar error now that we're up to 8.6.1.
Drupal\Core\Extension\Exception\UnknownExtensionException: The module thunder does not exist. in Drupal\Core\Extension\ExtensionList->get() (line *** of /var/www/***/core/lib/Drupal/Core/Extension/ExtensionList.php).
Comment #35
shelaneRight after updating from Drupal 8.5.6 to 8.6.2 and running drush cache:rebuild, I got this error:
I am using a custom profile that is a sub-profile of lightning. Both exist and my settings.php file has:
$settings['install_profile'] = 'thunder';
If I try to run drush updatedb, I get this error:
Comment #36
catchThe test needs fixing, but if you're getting this issue and confident trying a patch, please test the patch in #30.
Comment #37
shane birley commented@catch,
Will try the patch today and see if it helps to resolve the issue. I will run it against 8.6.2.
Comment #38
cesarg commentedI had this same issue and was resolved by simply doing a cache rebuild using Drush.
Comment #39
shane birley commented@cesarg,
Make sure to track how long this holds. I have a couple of sites with similar issues and one of them requires a cache clear every week to prevent this problem. Let us know if the problem returns in the future.
Comment #40
juagarc4 commented@shelane (#35),
I think your problem is more related to this issue: https://www.drupal.org/project/drupal/issues/3009548
Comment #41
shane birley commentedI am running with Drupal 8.6.2 now and so far the issue might be fixed. I will monitor over the next week or two to confirm. And to clarify, the status page now as the proper profile displayed (minimal-8.6.2).
Comment #42
yazzbe commentedHad this issue too.
After updating to 8.6.2 + run update +run cron the problem was gone.
Comment #43
jweirather commentedI just did a clean install (8.6.2) for the first time today and experienced this issue when visiting "Extend". Simply running update.php resolved the issue for me.
Comment #44
jonathanshaw#30 works for me reliably
Comment #45
featherbellyRemoving/commenting the
install_profilefromsettings.phpseems to do the job.$settings['install_profile'] = 'PROFILE';Use
drush crordrupal cr(Drupal Console) to clear the cache from the command line.Comment #46
shelane@juagarc4 Turns out my issue is related to this https://www.drupal.org/project/lightning_core/issues/2997990
Comment #47
cesarg commented@shane-birley (#39) I encountered the issue once more today. Once again, a cache rebuild did the trick.
Comment #48
brightboldConfirming that removing the install profile line from settings.php and clearing the cache has fixed the problem, for now at least. Mine was occurring on the admin/modules page (maybe elsewhere but that's the one I noticed before fixing it.)
Comment #49
dave kopecekI've had #30 in place for about a week and the error hasn't happened again.
Comment #50
scrumorg commentedWe have encountered this about once a week since our upgrade to 8.6.2, today being the most recent. Every time, a cache refresh fixes the issue.
We don't have an install profile in our settings.php file.
Comment #51
biigniick commentedI've encountered this error today on the views page clicking on the 'edit' button. Thanks for the info, and clearing the cache fixed it for me.
Drupal 8.6.0
PHP 5.6.37
Thanks
Comment #52
jonathanshawAnyone got an idea why the test in #30 is failing? It looks like the exception is not being caught, but I don't see why.
Comment #53
scrumorg commentedIs it possible the failed tests are identifying the problem that the patch is compensating for? The exception thrown is not the exception caught (or expected)...
Comment #54
jonathanshawI figured out what it was: it's simply a unit test so no container is available, but the method being called in the ModuleHandler needs a container. It should be a simple fix to the test.
Comment #55
vrwired commentedupdating database worked for me to resolve.
drush updatedb required for system module
Force cache clear to ensure aggregated JavaScript files are regenerated. @see
https://:www.drupal.org/project/drupal/issues/2995570
Comment #56
bitcookie commentedI experienced this bug on a fresh install of 8.6.3.
I don't have any install_profile declared in settings.php
Patch #30 seems to have helped. I applied it without clearing the cache and the error resolved.
Comment #57
ikaros123 commentedI also had the same issue after moving my site to a new database.
Running update.php solved the problem.
Comment #58
joelpittet@catch, how does the 'standard' profile get in the module list to begin with?
EDIT: I did #45 to resolve the problem. Remove
$settings['install_profile'] = 'standard';from my settings.phpComment #59
Prabhu.shan commentedEven we face the same issue after we upgraded to 8.6.2 Core. Any idea why it happens only in prod environment but not in lower environments.
Does load on the prod site is creating this issue?
Comment #60
BalrajB commentedHad a similar issue, but clearing cache fixed it for me.
Comment #61
brightboldOn Nov. 2 I said:
But as @Shane Birley reported, that only solved it temporarily. Today I was locked out of admin/people, admin/modules, and at least one other key admin page. Fixed with another cache clear. I'm moving the site to a new host later this week so I'll try the patch then.
Comment #62
shane birley commented@BrightBold,
I upgraded the site to the latest Drupal 8.6.x and applied the patch. I haven't seen the issue since. I am still watching, however.
Comment #63
scrumorg commentedWe have not seen this issue since applying patch #30 2 weeks ago. Looks like it probably takes care of it.
Comment #64
tjtj commentedI got:
when I display the people page.
Comment #65
oujasper commentedWe just upgraded from 8.5.6 to 8.6.4 and we are getting this when you click "Extend", but when you click "Install New Module" you get a Drupal "Access Denied" and when you click "Uninstall module" you get in. Makes no sense. Once in "Uninstall module" if you click the "List" tab, you get the "The module standard does not exist" error again. We have similar issues other areas of the admin as well.
Comment #66
catchSame patch with a test that should pass/fail properly.
Comment #68
catchTidied up the test a bit.
Comment #70
nchase commentedDrupal\Core\Extension\Exception\UnknownExtensionException: The module standard does not exist. in Drupal\Core\Extension\ExtensionList->get() (line 257 of /core/lib/Drupal/Core/Extension/ExtensionList.php). in a Drupal 8.6.4.
The problem leads to the entire site crashing and only showing "The website encountered an unexpected error. Please try again later.". The above error message is the only error message in the log.
Comment #71
antojoseThe patch in #68 worked fine for me. Thank You!
Comment #72
catchUpdated the issue summary.
Comment #73
alexpottCan we deprecate this path? I feel like thew module handler shouldn't be dealing with modules that are not installed.
The situation where we have a profile configured but not in the module list should never happen. As a follow-up I think we should consider always adding the profile to module list once Drupal installation is finished.
Comment #74
catchI think these are pretty standard Drupal installations that are hitting this though, although given it's a bug then getting the deprecation is probably OK.
That's the opposite direction to #3023133: [PP-1] Extension System, Part V: Decouple profiles from modules.
Comment #75
tjtj commentedI am getting
I tried the patch 3000677-68, and it totally broke my site. I get errors accessing the People pages.
Comment #76
begun commentedI am periodically experiencing the same issue on a site. Would be happy to test any fixes, but not sure how to reliably reproduce the issue. Seems to be intermittent.
Comment #77
mlzrOk, I had found te error found in the logfile "The module standard does not exist." and the path /admin/modules was given a blank page.
I read this page and places $settings['install_profile'] = 'standard'; in settings.php as mentioned in #19 and did a /update.php as I don't have command-line acces for this website as mentioned in #20.
Now I can acces /admin/modules again. So far so good :-)
Thanks,
MarchelloDePello
Comment #78
larowlanNeeds work for the deprecation in #73
Comment #79
catchAdding the deprecation.
Comment #80
prlw1 commented3000677-79.patch works for me on php 7.2, drupal 8.6.4.
Before patching, trying to enter maintenance mode:
Drupal\Core\Extension\Exception\UnknownExtensionException: The module standard does not exist. in Drupal\Core\Extension\ExtensionList->get() (line 257 of /usr/pkg/share/drupal/core/lib/Drupal/Core/Extension/ExtensionList.php).After applying the first part of that patch (attached), I can successfully enter maintenance mode. [Obviously you want the whole of the above - I'm just being clear about what I tested.]
Comment #82
catchPatch in #79 is the one to review still.
Comment #83
catchComment #84
alexpottSo I think we should target 8.6.x with this. Apart from changing this I think we're rtbc - for the mitigation. But I feel we need a following to deal with sites where the install profile goes missing because I think this might break more than just this in the long run.
Comment #85
catchI think we should introduce the deprecation in 8.7.x, and commit #68 to 8.6.x without it. https://www.drupal.org/project/drupal/issues/3000677#comment-12897126
Comment #86
alexpottThat's a good plan.
Comment #87
catchFor the follow-up, this issue is old, but probably the closest #1170362: Install profile is disabled for lots of different reasons and core doesn't allow for that?
Comment #88
larowlanreview credits
Comment #90
larowlanCommitted as6cbe4ea and pushed to 8.7.x. Thanks!
Didn't commit to 8.6 because release window
Comment #92
larowlanSeems I was wrong about commit freeze
Committed #68as 12dbf59 and pushed to 8.6.x. Thanks!
Comment #93
tjtj commentedThis is still not fixed in the latest Drupal 8.6.6. And no patch here for 8.6.x
Comment #94
catchThat's because Drupal 8.6.6 is a security release, not a bugfix release, it will go out with the latest bugfix release. The patch in #79 applies to 8.6 too.
Comment #95
tjtj commentedComment #96
tjtj commentedSeems to me that a critical bug that stops sites from working needs to be put in any new release. It is very time-consuming to update the core and remembering how to get around this bug, and repatching it is a real issue. I spent a morning doing the updates
Comment #97
cilefen commented@tjtj You will have to make a case that security releases are also bugfix releases (or with criticals) in another issue. We are not going to change the policy in this issue.
Comment #98
razunter commentedThis is not fixed, no stable release with this fix yet.
Comment #99
cilefen commentedHi @Razunter: Issues are marked fixed here when they are committed, not upon release. Many OSS projects work the same way.
Comment #101
ejah commentedI encounter the same message with different origin after upgrade to 8.6.8 from 8.6.7:
"Uncaught PHP Exception Drupal\\Core\\Extension\\Exception\\UnknownExtensionException: "The module standard does not exist." ....core/lib/Drupal/Core/Extension/ModuleHandler.php line 176"
Commenting out install_profile and flushing caches did not fix it.
Comment #102
calbasiThis fix has been added at 8.6.8 release
Comment #103
alexmoreno commentedI can confirm after upgrading to 8.6.9 the issue is not present anymore
Comment #104
shakeeltariq commentedExperienced this issue on 8.6.3 (with pending updates etc.) after clearing cache, there was no $settings['install_profile'] = 'standard'; line in settings.php, had to add this line to resolve the issue.
Comment #105
Abhinaw commentedfollow these steps for unexpected shutdown
9. execute
rebuild.phpeg.(www.abc.com/rebuild.php)10.execute
update.phpeg.(www.abc.com/update.php)11.clear the cache
if some modules is making problem or not uninstalling remove modules to use step 1
Comment #106
niky_chavan commented$settings['install_profile'] = 'standard'; adding this has solved the issue for me.
Comment #107
jlbrewster47 commentedI started with 8.7.6, and was getting this error. Upgraded to 8.7.7, as well as trying patch #79 above, and still same.
I also tried adding the "profile" :standard line to settings.php and running update.php. Still get the error. I think I tried everything. most don't apply because my version is the latest..Shouldn't this be fixed for me?
I'm out of things to try..
Comment #108
junaidpvWe are getting same error after updating from 8.7.9 to 8.8.1.
Comment #109
nulf commentedGetting the same as @junaidpv, did an upgrade from 8.7.5 to 8.8.1.
Edit: I have only seen it on "Status report" so far. Clearing caches didn't help. I get a "The website encountered an unexpected error. Please try again later.".
Edit2: And in "Recent log messages" I get the same error as @junaidpv
Comment #110
cola commentedsame issue here with 8.8.1
we installed the drupal with existing configs. the profile (on core.extension.yml) is set to "profile: minimal". This is needed because Drupal only allow install with existing configs if the profile is minimal.
solution: We found our issue. If you install drupal over configs, take care, that you als enable the module "minimal: 1000" (section module) in core.extension.yml
Comment #111
nulf commented@cola's solution seems to sort out the error for me.
Comment #112
meendru commentedI have an installation that is set to
$settings['install_profile'] = NULL;(no installation profile)
This simple patch is working for me. I checked it for side-effects but can't find some until now.
Please note: In my case, the Drupal 8.8.2 project is running in Docker Containers. It is powered by
composer, but because of restrictions in our setup, I was not able to apply it as acomposerpatch. Instead, I usegit applyComment #113
pasan.gamage commentedI'm having the same issue after updating from 8.7.9 to 8.8.3.
And my install profile is null as well, but I cannot change it like @cola said because Drupal doesn't allow it to be changed to something else after installation.
I tried what @meendru did and seems to be working. But I'm not sure if it will cause different issues down the line.
But thanks for coming up with it.
Thanks
Comment #114
aw-developer commentedI have the same issue after updating 8.7.8 to 8.8.3. Our install profile is minimal.
Drupal\Core\Extension\Exception\UnknownExtensionException: The module minimal does not exist or is not installed. in Drupal\Core\Extension\ExtensionList->getExtensionInfo() (line 346 of core/lib/Drupal/Core/Extension/ExtensionList.php).Clearing the cache doesn't help and I don't see a clear resolution in this thread.
Does anyone have any suggestions?
Comment #115
vrwired commentedAs noted in #104, adding $settings['install_profile'] = 'standard'; to settings.php resolved issue on my end.
Comment #116
swentel commentedI've ran into this one myself, adding or removing $settings['install_profile'] line in settings.php didn't fix it at all, clearing caches neither.
The problem in the end was that 'standard' still was in system.schema at schema version 8000, but nothing in core.extension.
To get around the problem, I just did an unset of the standard module and finally upgrades could run.
Comment #117
tneo commented@swentel #116
Which file did you edit for that change?
I've tried all options in the thread and none of them worked for me.
Comment #118
tneo commentedI was able to sort out my issue. By removing the entry from the key_value table as I found in this forum topic.
Comment #119
inders commentedToday got same issue & was able to fix it by using #116
File:- core/includes/update.inc
After running update.php i reverted to previous code without any issues. "I am not using standard profile"
Comment #120
meendru commentedI dag a bit deeper into the context of my issue and want to annotate my patch in #112.
Please keep in mind: I'm coming from the error
when I try to open, for instance,
/admin/module.ExtensionList->getExtensionInfo()is called bycore/modules/system/system.installon line 58 (Drupal 8.9). Line 57 insystem.installis introducing a hardcoded if statement relying tostandardprofile:As far as I know, Drupal uses installation profiles only during the first run. Once installed, they won't be needed substantially again. So, as far as I can currently suggest, you should first try to set
$settings['install_profile']tostandard(#115) for existing installations before you consider my patch in #112.Comment #121
bob.hinrichs commentedThis issue is still not fixed. Steps to reproduce:
1) a config install Drupal, that has minimal profile specified in core.extension config.
2) updated Drupal core code (via composer update). to 8.9.10
3) Visit the admin/config page.
Fatal Error: Drupal\Core\Extension\Exception\UnknownExtensionException: The module minimal does not exist or is not installed. in Drupal\Core\Extension\ExtensionList->getExtensionInfo() (line 346 of core/lib/Drupal/Core/Extension/ExtensionList.php).
Tried everything here. Nothing works.
Why does system.install hard-code 'standard'? If I add into system_requirements() in system.install if ($profile != 'standard' && $profile != 'minimal') { then it works.
Update: in Drupal 8.9, the $settings variable does not work as per the fix above (anymore); but if you put install_profile: standard into your services.yml file, it works. This points to another very confusing issue with Drupal currently, which is where you should put parameters (settings.php or services.yml parameters), and changes are in the works according to Drupal 9 issues.
However: this is still a hack, around the fact that 'standard' is hard-coded into the system_requirements. Because this "fix" involves putting a lie into the configuration and tricking Drupal to think it is using standard profile, when it is anything but. That is the real issue here, I think.
Comment #122
gpsloco commentedI have this problem, too. Can you please clarify, where I would find the system.install? statement or file? I cannot open admin/people and admin/modules as well as I can't edit any views.
Comment #123
avpaderno@bob.hinrichs If you can reproduce the issue for Drupal 8.9.x, you should open a new issue, and provide a link to this issue too.
Comment #124
ikit-claw commentedI can confirm I have just found this issue on 8.9.13
Comment #125
danielmmda commentedUsing #121 worked for me.
Comment #126
edmund.dunn commented#121 worked for me. I found this issue in 9.1.10. Created new issue at https://www.drupal.org/project/drupal/issues/3219126
Comment #127
ajay gadhavana commented#110 @cola's solution working fine for me
Comment #128
j.b commentedI've just upgraded from 8.9.18 to 9.2.5 and i am having this problem.
running drush updatedb :
The module standard does not exist.Comment #129
loopy1492 commentedThis worked for me:
https://www.drupal.org/project/drupal/issues/3219126#comment-14261556
Comment #130
quietone commentedpublish the change record