MissingValueContextException: Required contexts without a value: node

Adding a related issue, but not sure if that is the real underlaying problem.

Thank you for providing that, I ran into it on a site that was using 2.0.x but when it went away when I upgraded to 2.1.x I thought I had just borked up a patch locally.

We'll get this out in a new release so the 2.0.x branch can be stable again.

Hi, I'm moving this to needs work, after applying the diff with a patch (attached here), the blocks with multiple conditions did show were they should.

I attached the image of my block_visibility_group configuration.

the blocks with multiple conditions did show were they should.

What's the issue then? :-)

Sorry, I mistyped! They did not show as they should.
When should match the Request Path, is always false and not showing on the page.
Seems that is not properly handling the context for the Request Path condition

By testing here, seems that the early is causing the issue, it's not allowing to go to the second condition to allow match the RequestPath conditon

if ($context->getContextData()->getValue() === NULL) {
  return FALSE;
}

I changed here for testing:

         if (empty($contexts)) {
            continue;
          }

          $isEmptyContextData = TRUE;
          foreach ($contexts as $context) {
            if ($context->getContextData()->getValue() !== NULL) {
              $isEmptyContextData = FALSE;
            }
          }
          if ($isEmptyContextData) {
            continue;
          }

I will prepare the interdiff and a new patch in a few minutes to send here.

Here the interdiff patch and a fullpatch for the current 2.0 version.

The patch in #11 looks good. We are using it on our project.

I am using this on multiple sites, seems to do the trick. Thanks

I have also tested the patch from #11 🐛 MissingValueContextException: Required contexts without a value: node Active and it is working for us. Any idea when this might get added to a release. I have hundreds of sites using this module and would prefer to not patch if possible.

Thank you all for working through this bug and building a fix.

Committed.

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