Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When I enable "Overwrite internal link target access check" so I can disable menus, I receive a WSOD for anonymous users.
The error logged is
Drupal\Component\Plugin\Exception\PluginNotFoundException: The "views_view" entity type does not exist. in Drupal\Core\Entity\EntityTypeManager->getDefinition() (line 133 of /var/www/html/web/core/lib/Drupal/Core/Entity/EntityTypeManager.php).
This may be being caused by a menu item being created by views.
Comment | File | Size | Author |
---|---|---|---|
#15 | 3005803-15.patch | 795 bytes | LiamPower |
|
Comments
Comment #2
Spanxya CreditAttribution: Spanxya commentedComment #3
LiamPower CreditAttribution: LiamPower commentedCan you try clearing your caches with drush?
Is there anything else you had recently done, added or removed any modules?
Comment #4
Spanxya CreditAttribution: Spanxya commentedFair call. I gave it a go, but the behaviour was the same.
Nothing comes to mind. I can cause this by simply toggling "Overwrite internal link target access check"
Comment #5
LiamPower CreditAttribution: LiamPower commentedI'll give the scenario a run when I get a chance if you get a chance to before I do. Could you let me know if updating your links to or to google or something makes a difference?
Comment #6
Spanxya CreditAttribution: Spanxya commentedSorry it took a while to get back to you. Looks like I missed the notification.
I've just swapped out all of the
route:<nolink>
s withhttps://google.com
and I am seeing the same result. Clearly that's not the issue. Sorry about the misdirection.Comment #7
Spanxya CreditAttribution: Spanxya commentedComment #8
Spanxya CreditAttribution: Spanxya commentedOn further research, I have found that one menu item was a view. When this menu item is enabled I get an error, with it disabled the module performs as expected.
The view has permission restrictions: permission: view published content.
Actually, I've changed it to permissions: none, and back again and this error seems to have gone away.
Now I'm wondering if it was to do with having this view on a menu before
menu_item_role_access
was installed.Anyway, for me, for now, I have no problems. Thanks for taking the time to respond LiamPower
Comment #9
LiamPower CreditAttribution: LiamPower commentedHi @Spanxya
Thanks for investigating further and letting me know where the issue is. I think I'm going to take a look and see if there is something I can do to stop the WSOD if a view menu item has been added to the menu as I don't think this module should be causing an issue with that, it should just pass over that menu item and pass off the permission checking to the view.
Thanks,
Liam
Comment #10
LiamPower CreditAttribution: LiamPower commentedComment #11
LiamPower CreditAttribution: LiamPower commentedI'm unable to replicate this error.
Comment #12
drupgirl CreditAttribution: drupgirl commentedI just replicated the anon WSOD. Spanxya, thank you so much for making this post because disabling this module brought the site back. I would have been stymied for much longer trying to sort this message out and relating it back to this module...
Drupal\Component\Plugin\Exception\PluginNotFoundException: The "views_view" entity type does not exist. in Drupal\Core\Entity\EntityTypeManager->getDefinition() (line 133 of .../code/core/lib/Drupal/Core/Entity/EntityTypeManager.php).
I'm going to reopen this, because it is a thing, and it would be good for others to know that when the get this message, disabling the mod brings the site back. I only noticed after logging out as as admin. drush uli got me back in, where I could then access the error log.
I do concur that the issue is probably related to views adding menu links to the menu when this mod is installed.
Comment #13
LiamPower CreditAttribution: LiamPower commented@drupgirl are you able to provide any more information about this:
It would be great if you could help me to replicate this as I'm still unable to replicate it.
Comment #14
smmoraco CreditAttribution: smmoraco as a volunteer commentedI found that i was able to cause and then clear up the cause for this error simply by toggling module settings:
When i first found the problem i had both checked.
I found the problem occurred in two places on my site: (1) showing the calendar view, and (2) editing an existing basic page.
My workaround for now was to turn off both of these options.
Here are the stack traces from both:
### Error accessing calendar page
Comment #15
LiamPower CreditAttribution: LiamPower commentedThanks for the stack trace @smmoraco
Can you give the attached patch a try and let me know how you get on with it?
Comment #16
LiamPower CreditAttribution: LiamPower commentedComment #17
jaesperanza CreditAttribution: jaesperanza commentedHaven't tried the patch yet. Just reporting same issue is still happening for:
Drupal version : 9.5.7
PHP Version 8.1.17
Module version: 8.x-2.19
Allow parents to override children is usable intermittently, I think as long as you run drush cache:rebuild
Enabling both options crashes the website with the same error