Problem/Motivation

Suddenly an error appears when calling up the menu administration

Steps to reproduce

call the menu Admin link

/admin/structure/menu/

Drupal\Core\Entity\EntityMalformedException: The "menu" entity cannot have a URI as it does not have an ID in Drupal\Core\Entity\EntityBase->toUrl() (Zeile 192 in /home/linux/www/html/project/web/core/lib/Drupal/Core/Entity/EntityBase.php).

But if, for example, I call up the main menu directly, there is no error

/admin/structure/menu/manage/main

Comments

hermanP created an issue. See original summary.

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented
Status: Active » Postponed (maintainer needs more info)

Does this happen on a clean install?

hermanP’s picture

hermanP commented

It is not a fresh installation.
but also no custom theme or modules installed.
the problem exists with drupal 8.8.3.

hermanP’s picture

hermanP commented

okay.. fixed..

for some reason there was entry "system.menu.devel" stored in the table "config".
this entry had no further equivalent in the menu_tree. therefore the menu development could not be built correctly.
I cannot answer why the entry "system.menu.devel" was saved in the config.
alleged sloppiness on my part ..

hermanP’s picture

hermanP commented
Status: Postponed (maintainer needs more info) » Fixed
larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented
Category: Bug report » Support request
Issue tags: +Bug Smash Initiative

Glad to hear

Status: Fixed » Closed (fixed)

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

designcrs’s picture

designcrs commented

No idea how I could find out something like that, but deleting the row containing "system.menu.devel" also fixed the issue for me! Thank you very much!

mdranove’s picture

mdranove commented

I also ran into this problem. #4 fixed for me.

This was a really nasty surprise for me. I had no issues locally and when I deployed to my dev site the entire site went down until I uninstalled admin toolbar. The only guess I could have on root cause was various config changes that had been done on dev which put it out of sync with local dev. In theory ofc this shouldn't really matter. Just thought I'd mention it because this was a really nasty exception.