MissingValueContextException: Required contexts without a value: node

I'm getting the same error

Here is how to reproduce this error:

1. Create a Visibility Group with at least two condition one Request Path and another one with Content type
2. Apply this group to a block
3. Go to any pages that's not a node page or page listed in request path condition

You will have this error, it seems that the node (maybe any other entity type) it's required in the context, it seems that module evaluate the condition even if the context don't have value.

this line of code who throw the exception
$this->contextHandler->applyContextMapping($condition, $contexts);

because the $contexts will have ["@node.node_route_context:node" => "contextValue":protected]=> NULL ]

Here is a patch needs reviews, the idea is to filter out the contexts without value before passing them to applyContextMapping.

I am seeing a similar issue but it's not quite the same:

Drupal\Component\Plugin\Exception\ContextException: Assigned contexts were not satisfied: node in /app/web/core/lib/Drupal/Core/Plugin/Context/ContextHandler.php:145

the error log is quite long. Hoped this patch might solve my issue but i am still seeing the same error in the logs

Ah i don't have this error,
I guess it's better to create a new issue and make it a follow up to this one, and describe what Block Visibility Groups you have.

We were encountering this error on Views-created search pages (like one at /path) with Block Visibility Groups with two "request path "conditions (Return true on the following pages: /path* and Do not return true on the following pages: /path/*)

The patch in #4 does make the errors go away, and I still see the things governed by the correct Block Visibility Group on the Views page at /path and /path?query=etc but not on a node at /path/test - just as I expect.

Thanks!

patch #4 worked for us too. Want to turn to an MR.

Committed. Thank you!

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

Sadly this is filling up our logs too, and the patch on #4 applies cleanly to 2.0.3 but not 2.0.4. It was committed on the 2.1.x branch, I presume that the 2.1.x branch has diverged quite a bit from the 2.0.x branch, meaning this needs a reroll until 2.1.x is stable.

Ah. I just found that the fix for the same issue on the 2.0.x branch was done in a separate issue and there was no mention of that from this issue... So I'm linking these now. 😅

🐛 MissingValueContextException: Required contexts without a value: node Active