Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
This needs a check to ensure the entity can be added through the UI. Entities like contact form messages and payments shouldn't just be added anywhere. IIRC Rules for Drupal 7 uses a simple boolean flag in the entity type definition. Maybe we can do the same here?
I was unable to complete this because of issues with the test framework, as discussed with fago.
We also decided to skip the check in #1, if an entity type is able to be constructed using entity_create(), then the same reasons apply to this action. Modules with corner cases can alter the definition and unset the derivative for the entity type they want to hide.
Comments
Comment #1
xanoThis needs a check to ensure the entity can be added through the UI. Entities like contact form messages and payments shouldn't just be added anywhere. IIRC Rules for Drupal 7 uses a simple boolean flag in the entity type definition. Maybe we can do the same here?
Comment #2
bojanz commentedComment #3
bojanz commentedMy current progress is up at https://github.com/fago/rules/pull/146
I was unable to complete this because of issues with the test framework, as discussed with fago.
We also decided to skip the check in #1, if an entity type is able to be constructed using entity_create(), then the same reasons apply to this action. Modules with corner cases can alter the definition and unset the derivative for the entity type they want to hide.
Comment #4
fagoThanks, I commented the PR - functionality basically looks great. So it's "just" missing tests then.
Comment #5
mariancalinro commentedI am writing the tests for this @drupaldevdays Montpellier.
Comment #6
dasjoComment #7
mariancalinro commentedThe pull request is at https://github.com/fago/rules/pull/158
Comment #8
mariancalinro commentedComment #9
mariancalinro commentedComment #10
klausiMerged, thanks!