Error 10.4.45 after running update.php

#0 /data/sites/web/site/www/vendor/twig/twig/src/Extension/CoreExtension.php(1882): Drupal\Core\Url->getRouteName() #1 /data/sites/web/site/www/sites/default/files/php/twig/67db52c7d2605_menu--navbar.html.twig_J2ZTzU3g6DgaO5hL6vS7JIOrM/E-xszOHwhE1YTsf1XE5tWNTA3TSJQg8-NUQ5yQ5pY2I.php(129): Twig\Extension\CoreExtension::getAttribute(Object(Drupal\Core\Template\TwigEnvironment), Object(Twig\Source), Object(Drupal\Core\Url), '...', Array, '...', false, false, true, 58) #2 /data/sites/web/site/www/vendor/twig/twig/src/Extension/CoreExtension.php(2079): __TwigTemplate_b7d7de5d26554f8456ba75f53bc9a62a->{closure}() #3 /data/sites/web/site/www/sites/default/files/php/twig/67db52c7d2605_menu--navbar.html.twig_J2ZTzU3g6DgaO5hL6vS7JIOrM/E-xszOHwhE1YTsf1XE5tWNTA3TSJQg8-NUQ5yQ5pY2I.php(70): Twig\Extension\CoreExtension::captureOutput(Object(Generator)) #4 /data/sites/web/site/www/sites/default/files/php/twig/67db52c7d2605_menu--navbar.html.twig_J2ZTzU3g6DgaO5hL6vS7JIOrM/E-xszOHwhE1YTsf1XE5tWNTA3TSJQg8-NUQ5yQ5pY2I.php(49): __TwigTemplate_b7d7de5d26554f8456ba75f53bc9a62a->macro_menu_links(Array, Object(Drupal\Core\Template\Attribute), 0)

Comments & Activities

Issue created by @yazzbe
Comment 18 days ago →
🇧🇪Belgium yazzbe
Comment 18 days ago →
🇧🇪Belgium yazzbe
Found the cause of the error in my menu--navbar.html.twig file.
This code was causing an issue after running update.php

{% if item.url.routeName == "<front>" %}

Removed it from my custom theme to get the site working again.
Don't know if this it related to the latest drupal 10.4.45 update.
Comment 18 days ago →
🇧🇪Belgium yazzbe
Bumping this to major since it is a breaking change (WSOD).

I think it should be still possible to use item.url.routeName == "" in a twig menu template, without breaking the site after running update.php
Comment 17 days ago →
🇬🇧United Kingdom catch
Which version of core did you update from?

Also there's no 10.4.45 do you mean 10.4.5?
Comment 17 days ago →
🇬🇷Greece vensires
The my menu--navbar.html.twig file phrase in #3 confused me; I'm changing this to a support request.
Feel free to revert my change in case I was mistaken.
Comment 17 days ago →
🇧🇪Belgium yazzbe
Ok fine.

The update was from D10.4.3 to 10.4.5

I’ll try to work around and not use item.url.routeName == "<front>" anymore in Twig templates.

This is possibly breaking after the security fix and sanitization of link attributes in the latest security release.
Comment 17 days ago →
🇧🇪Belgium yazzbe
Comment 17 days ago →
🇬🇧United Kingdom catch
This is the error in the issue summary:

UnexpectedValueException: base:regions has no corresponding route. in Drupal\Core\Url->getRouteName() (line 567 of /data/sites/web/site/www/core/lib/Drupal/Core/Url.php).
Have you checked your code base for base:regions? I very much doubt this is actually about the <front> route because there'd be a lot more bug reports.
Comment 4 days ago →
🇧🇪Belgium yazzbe
I was eventually able to update the site.

When creating a menu link, I usually type the relative path directly into the link field — but that field is actually an autosuggest field.

When using the autosuggest (instead of entering the path manually), the custom menu Twig template no longer throws an error.

So, it’s probably better not to enter the menu path manually, but to let Drupal set the lmenu ink by selecting a value from the autosuggest.
Comment 4 days ago →
🇧🇪Belgium yazzbe