It works with the https://ecaguide.org/plugins/core/actions/action_send_email_action/ action, but not with the https://ecaguide.org/plugins/eca/tamper/actions/eca_tamper_math/ action.
I tried every possible variation of the Math action, luckily I remembered to try it with another action, and it turned out that it only doesn't work with the Math action. Math doesn't get the value of the loaded entity, even though I provide the same as for example the Display message or the Mail action.
Screenshots attached.
I browsed the https://ecaguide.org/ page a lot, but I didn't always find a detailed description that would have helped, but it's probably enough for a more experienced Drupal developer. What is required in the configuration form is not always clear. Obviously, you have to get used to it after the Rules module, where the module already provided the values to be set in a drop-down list, but in ECA you have to enter them manually and the form of entering tokens and more, it's a bit confusing.
I'll go through the section about Tokens in the description again.
Thank you!
Solved.
So, if it is "Event: Cron", "Action: Entity Load", then "Entity: set field value", then when setting "Action: Entity Load", the following fields cannot be left blank, but the field token must be entered in both: "Name of token" and in the "Entity" field.
But I gave Admin 1 permissions at the beginning of the process.
In the original post, I included the model and the SVG image of the model, so you can see that I did it this way and gave permission.
https://ecaguide.org/plugins/eca/user/actions/eca_switch_account/
tetatu → created an issue.
I'll try it when it's included in the version after 8.x-1.8, I can update it with Composer, I don't know how to do this Git thing.
I installed a fresh Drupal 10 and there is no problem, hiding the fields work.
tetatu → created an issue.
only the Save & Edit button text can be specified there
Drupal 10.4.5.
It is also illogical that on the "Content type" settings page, if "Preview before submitting" is set to "Required", once we have clicked the Preview button and returned to the editing interface, the Save button is already available on the editing page. After all, the essence of the "Required" setting is that the user checks the node on the Preview page after every change. The logical operation is: in the case of the "Required" setting, the Save button should never appear on the editing page, but only on the "Preview" page.
tetatu → created an issue.
tetatu → created an issue.
tetatu → created an issue.
I'm new, I thought comments were disabled for closed questions.
Let's put this bug report aside then, as soon as I get a chance I'll install a fresh Drupal and if there's still an error then it will bring me closer to solving it.
I'm sorry that the Condition Field module is not replaced by ECA, because what I was able to do with ECA so far worked beautifully, quickly and without errors, but the Conditional Field module was not flawless even in D7, and it was always an alpha version, it often works incorrectly and many options are no longer in it, and apparently its developers don't care much about it. And the feature that allows you to enter a given value into another field depending on the value of a field doesn't work. It's there, but it doesn't work. I tried to do this with ECA, with the Form submodule.
Obviously, doing this with ECA would be more resource-intensive, so I understand, but it would have been nice to replace as many modules as possible with ECA.
I tried it in Firefox and Chrome, it didn't work.
I just checked the Drupal error log, there is no entry.
I checked the Browser error messages, there is 1 entry:
Uncaught TypeError: rowHandlers[data.rowHandler] is not a constructor
I've taken note. I'm at a loss as to how to prove it.
But I specified Drupal 10.4, that's where the problem occurs. I haven't tried Drupal 11, as I don't use that.
I have Drupal version 10.4.4 and it doesn't work. No matter how much I drag the given field into the given area on the edit form, after saving everything is as it was. Although this would be necessary, I don't understand why Layout Builder doesn't do this, and I was also told that LB won't implement it.
I looked through the list to see which component this could be, this is the core state, so the separate Field Layout module is not enabled, so this is the default state after installation.
I attached the screenshot earlier in case it helps.
tetatu → created an issue.
I recently changed from Drupal 7 to Drupal 10. I've been waiting to do it because many important modules weren't available on D10. I'm just getting to know 10. Is it worth changing to Drupal 11 now, or will there be module issues again and it's completely different compared to D10?
I haven't reported anything since then because although there have been results, new things have also arisen and I don't want to bring up so many problems, so for a while now I won't be submitting any questions, requests, or bug reports and burdening the developers with them.
tetatu → created an issue.
Is there a way to have ECA warn you when importing that some elements (views, fields, etc.) will be overwritten?
I didn't want to take up your time, but I've been trying every option for days to solve this. In the case of Load Entity, as I wrote, I specified the ID and only got the ID back, although I obviously don't want the ID of a given entity, but rather its name, e.g. the field value, or the name of the Taxonomy.
Returning to the original topic: I would modify the previous ones so that if I put the entire view query as a token in the Display Message, it always appears, but if I include only one of the elements queried, e.g. the queried field, it no longer appears.
I'll keep trying and if I come up with something, I'll let you know.
Until then, if you think about it, suspend this topic.
I saw in one of your tutorial videos that you did it this way, where you queried multiple nodes of a content type and hid the nodes based on a certain condition. That worked for me too. But here you don't need a custom event, because I only want to insert the field value of a queried node of another content type into the field of a given node. If I do it immediately after the view query, there is no result. That's why I did it after the Trigger, and it did work, but as I wrote, it only worked when displaying the message, not when entering the field.
I also tried Entity Load, but there only the ID was included in the token, so there was nothing I could do with it.
I also looked at the Get solution, and that didn't lead to any results either.
To be honest, I don't know when to use a View query, when to use an Entity Load or a Get solution, and which one is better in terms of resource requirements.
I can export the model, but it also has a View, a content type, a field, and if you import it, it will overwrite the settings of that view, etc. I did this before, I imported a previously exported ECA model and unfortunately Drupal did not indicate that all fields and views used by that ECA model would be overwritten, so I lost a lot of previous settings.
The key question is this:
I don't understand why, after the query was successful and the content of the given field was displayed, later, in the same model, when I want to insert the value into a field with a different content type, it is not available.
tetatu → created an issue.
So sorry for pointing this out, take it as irrelevant, this problem is not that important. If I knew it only affected me, I wouldn't have sent it.
I use that version of Firefox because I haven't switched to Windwos 10 or 11, I plan to switch to Linux, but I just haven't gotten there yet.
Okay, it's understandable if this bug affects only a few people and requires more research. I'll move on to another topic. I don't like Chrome.
Regarding the Firefox version, I've attached a screenshot showing that version 115.21 is 2025
This Firefox version is March 2025, so it's up to date.
I tried the Drupal base themes in addition and as I mentioned there was no problem. And out of dozens of ECA models, it only happened with one, which is a pretty complex model anyway. I cloned it, hoping that it would resave and the error would go away, but it didn't.
This is the first time it's happened, and it's not even a working model yet, it's just a draft, a drawing in which I outlined the later steps.
I haven't heard of the Gin theme, I just checked it out, it's an admin theme. I need one that I can customize with CSS like Zen used to be, but unfortunately it doesn't have a D10 version.
tetatu → created an issue.
This is unnecessary extra work for you developers. The 2.0.14 runs on the same ^10.3 || ^11 system as the latest one, so anyone who used that could upgrade to the latest one.
I'm using ECA version 2.1.5, will this fix be included in the next update? I see there's also a version 2.0.14, what's the purpose of that?
https://www.drupal.org/project/tamper/issues/3509682 🐛 Array to string Active
I uninstalled ECA and all its dependencies, because Composer wouldn't let me uninstall the new version of Tamper. Then I managed to uninstall it. Then I reinstalled ECA, then the previous version of Tamper, but even though I specify the exact previous version
composer require 'drupal/tamper:^1.0@alpha'
Composer installs the latest one, so I can't 100% verify that this module is causing the problem.
This error has been present since the Tamper module update.
https://www.drupal.org/project/tamper/releases/8.x-1.0-beta1 →
So we avoid using Gateway and only use "Chain action for AND condition" for And Condition conditions.
It is reassuring that every ECA update will be done in a way that will not break previous Models, so you don't have to check every function of every Model again and again after every ECA update to see if something has broken.
Thank you for the attentive development!
tetatu → created an issue.
tetatu → created an issue.
Maybe it's just me that's bothered.
I'll write to a BPMN.IO developers, maybe.
Thank you for the info!
tetatu → created an issue.
Yes, and Thank you!
I recently replaced the BPMN.iO 2.0.6 version with Composer for the 2.1.x-dev version and the SVG button is now working.
What I don't understand is that I exported and then imported the BPMN.iO 2.0.6 state with the
Configuration management module, and after replacing it with the 2.1.x-dev version, Configuration management did not detect any changes and the version of the modules does not appear for BPMN.iO, like for the other modules.
UI. Beginners but enthusiastic Drupal users who are also beginners in programming can help with the development of ECA? I don't understand why Rules still has 100+ thousand users, when the version for Drupal 10 is very incomplete compared to the Drupal 7 version. ECA varies around 6-8 thousand, although in theory (looking at the video demonstrations and descriptions, it already knows everything that the old Rules knew...).
Sorry, I didn't know it wasn't an ECA topic.
Thanks for reporting it to the bpmn_io UI module developers!
tetatu → created an issue.