Currently Rules' entity integration deals with all entity types, however we should deal with entity types that are configuration. We really don't want support automated site configuration ;)

Thus, let's remove exportable/configuration entity types from the entity_create(), entity_fetch() actions.
As this removes something that works now, we should do so before the stable release.

CommentFileSizeAuthor
#2 rules_config.patch918 bytesfago

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented
Component: Rules Core » Rules Engine

also see #1239062: determine entity types being configuration

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Fixed
StatusFileSize
new rules_config.patch918 bytes

ok, I've fixed it such that the configuration entity types are excluded from the list of entity types that can be selected when creating or fetching entities. Still they are accessible via the data selector, e.g. profile2:type and could be theoretically saved/deleted from there.

Well, there always ways to break things, so I think its fine that way. I've committed the attached patch.

Automatically closed -- issue fixed for 2 weeks with no activity.