I didn't complain that they didn't answer there, but that they deleted the questions. Before you speak, you should understand what I'm writing.
And as for free time: I also help others in my free time, so don't be disrespectful!
Have fun with the ECA user base, which is still only 7 thousand, compared to 140 thousand for Rules.
I wanted to discuss the aforementioned questions with the aim of helping in development, but this is no longer relevant. If you keep this attitude, ECA will sink, but that's not my problem!
Dear jurgenhaas, I wrote down dozens of ECA questions and problems, and I submitted them to Drupal Answers a few weeks ago, but they rejected the questions, they're pretty grumpy there). Where can I send them? And one request: it would be nice if the tutorial videos were uploaded to YouTube! Because there's a translation option there, but there's none at https://tube.tchncs.de/w/5cs5Du3579Nwau1m9Rv92G, and not all Drupal users speak English...
I can only repeat that ECA Export gives me a .gz file, not a tar.gz. But for me it doesn't matter, it works, that's the point. By the way, I'm using the latest version of Drupal 10 and from ECA as well.
In the case of "Tamper: Get string length", a given field is specified between [ ] brackets and it works properly.
You claim that in the example model you sent, if you specify the given field without [ ], then your system correctly recognizes the "empty" and "not empty" states?
By exporting in the ECA module.
As for the token: I tried without brackets, but it didn't work either.
By the way, it's confusing that even within a given rule, sometimes it's mandatory to put the token in parentheses, and sometimes it's the opposite.
An example model is attached.
Anyway, it can be solved with the "Tamper: Get string length" condition, but everything in the Drupal system should still work.
Nem segített, sőt, le se tudott futni a javasolt Drush parancs:
drush config:delete workflow.state.dummy_action_creation
A teljes Drupal újratelepítés nem opció, ilyen javaslatot nem is kéne adni.
Azzal sikerült megoldani, hogy az összes ECA modult kikapcsoltam a Drupal-ban, töröltem a Drupal cache-t, lefuttattam a cron-t, majd ismét bekapcsoltam az ECA modulokat. Ezután sikerültek az elmentett ECA model importálások.
Rendben, telepíteni fogom és megnézem, hogy működik-e.
Hol jelentsem a hibákat?
Kedves Ilma! Inkább megvárom a végleges verziót, nem szeretek toldozgatni, foltozgatni. :-)
A Maillog modul fejlesztője vagy?
Coaston, Could you elaborate on the solution?
I tried the "Trigger a custom event" and the "Trigger a custom event (entity-aware)" Action, I entered the specific Model ID, but it doesn't work.
When is this error expected to be fixed?
Is it already fixed in the August .dev version?
Notice: iconv_mime_decode(): Detected an illegal character in input string
atomi → changed the visibility of the branch 3482301-registration-form-permission to active.
In the Drupal 10 version, it doesn't save the value written in the admin field, I had to try for a long time, then I tried it with a normal user's field and it was already saved there. Isn't that the case with you? So it's not the Views, but the field that's the problem for root admin.
So if we create a new field in the profile then we have this error. I tried this with ECA first, and it took me a long time before I thought to see if it was even possible to write directly into the field. There are gross errors in version 10 compared to version 7. This is not the only error.
atomi → changed the visibility of the branch 3482301-registration-form-permission to hidden.
Years ago, I was a prepress operator. There, only the printing press could spoil what I did. Ever since I've been in the online world, creating websites, I've often thought of giving up on this whole thing, because it depends on so many things whether something is good or not, and what's good also breaks down because one of the components (hosting provider, php, mysql, server component changes, but even the ISP) can mess something up. This is so fucking shit. And then I didn't even talk about modules and browsers.
The Drupal 7.98 update fixed the problem, no need for the Imunify360 exception setting
The hosting provider said there were no changes to their system.
The interesting coincidence is that before that there was an error phenomenon that I had never experienced before: the size of the database suddenly became 8 GB, cPanel showed this, but phpMyAdmin showed the normal size of 40 Mb. Because of this, the storage space was also marked as full, but the registration, content uploading and backup from Drupal still worked. The service provider said that they don't know the reason, because they can't look that deep into MySQL and cPanel either. They said it was caused by stuck data. What is stuck data? And 8 GB???
It really works, but we should know what caused this error and what we changed with this setting, whether it will cause problems later.
Addendum: when the mail is processed by the SMTP Authentication Support module, the mail is entered into the Mail Logger module, but before it is sent, which is incorrect, because it should only be entered when it has actually been sent.
Workaround:
Another feature of Rules, which also includes offset, counts well. This is interesting, because I think the module takes this action from the same place, but according to them, it doesn't?
So this solves the problem, avoiding the date offset error:
Action: Calculate a value
I do not understand. I'm not at home on this forum.
Why was my post copied and rewritten as version 7.x-2.x-dev? That the fix is in the dev version and should I test it?
I'm shocked that this bug has been in the Rules module since 2012!
Date offset is incorrect 🐛 Date offset is incorrect Closed: duplicate
I undertake the testing.
I can't fix the module because I can't program in PHP and I don't know how to create a Drupal module, yet.
I don't understand that it didn't bother others, since there can be many cases when it is important.
For example, if I want to hide a content 30 days after a given date, then it doesn't matter how many +/- days have passed due to the error, if that content is related to a subscription.