Spin-off from https://www.drupal.org/node/2269561#comment-10859464:

Sime wrote there:

I'm noticing that in d8 all the rules conditions appear to be broken in the block configuration - was this due to a change in core since they were done? or was the block configuration integration a pending task?

The block condition UI is rather limited, but yeah I also noted that the Rules condition do not make it very nice.

So we need to make sure the default UI is at least not broken. If it's not looking nice, that the UI's fault (it should be able to deal with modules using the API to add conditions, that's what the API is there for.

Moreover, we could build upon #2659016: Embeddability of condition and action forms basics to provide a small Rules Block UI module that hooks into the process to allow the use of Rules conditions for core blocks.

Comments

fago created an issue. See original summary.

sime’s picture

sime
any/any
Location Melbourne
commented

I'm sure the Rules developers are all over this, but here's a condition plugin that integrates with Drupal core block visibility, for reference.
https://github.com/simesy/uuid_condition

ckaotik’s picture

ckaotik
Primary language German
Location Berlin
commented
Related issues: +#2789051: Add schemas for Rules condition plugins

Core has since fixed unrelated Condition plugins showing up in #2811519: Blocks do not appear after being placed with the Rules module enabled (or other missing schemata for Condition plugins). It also fixed core blocks gaining a dependency on Rules even though no condition was used.

What's left is to provide a working config schema so other modules that wish to use Condition plugins (e.g. menu_position) do not suffer the same problems. This has already been started in #2789051-4: Add schemas for Rules condition plugins.