- πΊπΈUnited States DamienMcKenna NH, USA
There are also core bugs related to block visibility rules.
Previously I had block visibility settings on a block using the Core block visibility configuration options (to limit by node type, vocab, URL, etc.).
I noticed that the block I was trying to control was not displaying at all on the types of pages I was configuring it to show up on.
I decided to install this module. I created a block visibility group with these settings:
`Allow other Conditions on blocks` - unchecked
`All conditions must pass` - unchecked
`Only one condition must pass` checked
IMO, these All/Only options are where this module shines more than what Core blocks functionality offers. Basically allowing you to say "AND" or "OR" in the deciding logic.
I started out simple with a single condition of node type = Page.
But, there was a problem. When I visited a Page node, the block was not showing.
The problem is the `Allow other Conditions on blocks` option seems to only hide the Core visibility options from the block configuration page, but it seems the logic doesn't account for that setting. I had to go back to the block configuration page and remove any of the old settings that were set in the core block visibility options. Once i did that, lo and behold, the block was showing only on Page nodes.
Closed: duplicate
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
There are also core bugs related to block visibility rules.