Latest version of Backdrop CMS; Basis sub-theme; Harris layout, with both sidebars enabled. Some of my custom blocks are not displaying in either sidebar. Seems to be an erratic issue, affecting some but not other blocks, arising when visibility condition, set for url path, has two or more "node/[number]" items. (Ie, show this block on this one page and this one other page.)
In the layout configuration page, the blocks are listing, and clicking on the link for visibility displays the correct conditions.
Experimenting -- think I found out what the problem is -- in the non-working blocks, I had originally added the second condition by (with the existing block in the given region) selecting "configure", and then in visibility conditions, using "add condition". Which seemed to be the logical, user-interface, way to do things.
Doing things this way creates two separate condition statements:
Current path is "node/103"
Current path is "node/91"
But the condition logic turns out to be more subtle than that. To correctly add a second url path, one must use the "configure" item that shows in the first-made visibility condition itself, to add the second node path.
Which then gives this form of condition statement:
Current path is one of "node/103 , node/91"
and the block displays on the two pages as intended.
Comments
Correct, if you add multiple condition statements they are treated as AND so it would appear to the system as:
node/103ANDnode/91which will never happen.Glad you found the way to do it. It does say add "Enter one path per line." but perhaps the help text needs to be clearer.
Thanks. I think, for me, the user-interface issue is that one uses (can only use) the "big" configure to add a first condition. And that made me think that I should use that same method to add the second condition of the same kind, with the programming being smart enough to insert the second condition underneath the first, per the instruction. Rather than needing to use the "small" configure if one has an already-existing condition.
Fwiw, my use case was that I was placing blocks to match an existing Drupal site, and had to go page by page (node by node) to find which blocks went where. Rather than knowing ahead of time all of the affected nodes that I needed to list.