Hello,
Any news about that?
Maybe the cleanest (and complex way) would be to look for an existing node type parameter.
This in order to avoid to add an extra dropdown list.- 🇩🇪Germany Anybody Porta Westfalica
I can confirm this issue, which makes "Layout builder" variant practically useless / unusable when overriding entity paths like:
/taxonomy/term/%term
For that reason, I'm setting priority to major and hope it's OK.So could someone turn this patch into a MR to further work on this?
Currently the following contexts are available when overriding an entity route:
@user.current_user_context:current_user Aktueller Benutzer entity:user current_user Aktueller Benutzer entity:user language_interface Anzeigesprache der Website language
And like this, the entity (here %term) should be generally available, similar like how it worked in Drupal 7 page_maanger.