davemaxg → created an issue.
davemaxg → created an issue.
davemaxg → created an issue.
I can confirm that using the View result counter - Global field from views also causes this error. I am using 8.x-1.15.
The patch does not apply to this version either. I will look into a new patch if I have some time.
#17 worked for me. Thank you!
davemaxg → created an issue.
The point with the older user account that I meant to mention was that the account existed before eca was installed.
davemaxg → created an issue.
davemaxg → created an issue.
Upon further investigation, I see that this is an issue with entity_clone. Please close this ticket.
Thanks @ jurgenhaas, bpmn_io is working for me. I started with classic as it seemed an easier way to get started with ECA, but I can see how bpmn is much richer.
davemaxg → created an issue.
This is happening for me too. The value is there when I export config, but not when I view the action.
Upon more investigation, I see that easy email only provides the action and eca takes care of the rest. Didn't realize it worked that way. This issue is already open.
https://www.drupal.org/project/eca_cm/issues/3419019
🐛
When viewing or editing a model containing an Easy Email action, the previously entered data for the object field for that action is not displayed
Active
That's not the issue that I'm bringing up. The issue I was trying to outline is that when I try to save the Send Easy Mail action, the Entity token name that I specify doesn't get saved. I sent the yml file so you can easily replicate the issue.
davemaxg → created an issue.
That worked. Thank you!
This module is awesome.
davemaxg → created an issue.
Patch attached. This may need a little cleanup but it works for me.
davemaxg → created an issue.
I believe this also happens when a field is added to an entity after entities already exist. In this case, these fields wouldn't exist in the database and would be nulls and would trigger the same error. This is happening to me on 10.2.2
davemaxg → created an issue.
davemaxg → created an issue.
The patch at #8 does not work on Drupal 10.1 which has a newer version of symfony. On Symfony 4.3+ the dispatch method has been changed
from
public function dispatch($eventName, Event $event = null);
to
public function dispatch(object $event, ?string $eventName = null): object;
This new patch addresses that issue. It's a one line change.
davemaxg → created an issue.
davemaxg → created an issue.