User/Content fields not available in Layout Builder variant.

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.

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.

After removing a few of the other critical patches i need on PM, i was able to apply the one above. I do see the new setting to pick bundle, but it doesnt add that bundle's fields to available blocks.

I agree with Anybody, this is a pretty major issue for PM.

As a possible work-around for people hitting this issue; you can great a simple view (block) to simply list your field (with content id from url contextual filter) and then place that views block.