I often find myself in need of actions and rules that will work on several bundle types on the same time.

Example: Only today, I needed a rule that will delete all nodes from a group, independent on the node type (bundle).

Having to define parallel rules and actions for exactly the same purpose is very inefficient.

Comments

Deno created an issue. See original summary.

yseki’s picture

yseki commented
Assigned: Unassigned » yseki

Hi @Deno,

It makes sense, and I do believe it could make life easier for many people.
I may be wrong, but as I remember how it's implemented, it's not a big deal.

We need to change the bundle selection to accept multiple values and the tests to check the selected values instead of only one.

There is one catch:
- Only the fields that are common to all bundles will gonna be available for selection on the action/condition.

If anyone has already created the patch, please, upload it here.

Thanks,

Yuri

Deno’s picture

Deno commented

This makes sense to me. Field that aren't available in all bundles should not be available for choosing.

However, there is one thing... Imagine that I want to go through all nodes and set a value of "field_set_by_human" variable to false (0, I suppose) if such a field is defined in a bundle.

I know, stupid example but there are places where this would be very useful. Above all, I don't need to change the rule when new bundle is added or when another bundle gets this field.

So I don't mind choosing the variable from a single bundle as it is now, but I would like to have a second option "applicable to" that can take several values or "any". I am very fond of "any"

djdevin’s picture

djdevin
he/him
Primary language English
Location Philadelphia
commented

Looking forward to this. Something that is not possible right now is reacting on a Webform submission for example. If we wanted an action that fires on any webform submission we would have to create an action for every bundle of webform (which could be 100s+).