Allow other conditions on blocks option not working completely

Created on 2 March 2018, almost 7 years ago
Updated 27 February 2023, almost 2 years ago

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.

πŸ› Bug report
Status

Closed: duplicate

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States joshua.boltz

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024