As far as I know all actions that are available in core are also available as actions in ECA.
So maybe an action plugin that presents actions like "Assign access policy POLICE_NAME" could also be used as an ECA-Action and also as an action for node bulk editing of selected nodes in a view, isn't it?
Hi partdigital, thanks for the reply.
My bottleneck is that for my use case, I need to assign multiple access policies to some nodes, but I want this to happen dynamically by setting field values or generally when creating nodes, without the user being able to influence it.
An ECA module integration would be ideal for this, so that there is an ECA action that allows multiple access policies to be added to a node in an ECA model by entering the machine name, separated by commas.
Would such an integration perhaps be of general interest?
Thanks, especially for the idea to deprioritize the nodes and make a bulk edit.
Improved description to make it clearer
The feature in core (since 10.1) that the privileges of user 1 may be turned off argues against using "switch to user 1." However, since this ECA option is already available in the settings and as a single action, there would be nothing wrong with offering it as a per-model option, unless there are more robust options (as outlined above), right?
Any new insights on this issue? I've been using the "Execute models with user" setting by default, and a per-model setting would be very helpful.
It works. Used "Compare two scalar values" as condition to compare [current-page:url:path] with my path as fixed string.
Thank you.
Thanks. I cannot see how I can check for the current path. I don't find the condition for it.
Am I wrong, or isn't the module obsolete for Drupal 11 anyway because the functionality is in the core?
marco.b → created an issue.
patch #24 worked great thank you!
@ albertho425
> I tried gutenberg 3.0.6 and the issue persists.
Did the issue even persist after installing drupal/gin_gutenberg? It worked for me.
IMHO the use of a a simple contrib module seems to be better that patching, isn't it?
I overlooked that this is about version 4.0.x-dev.
drupal/gin_gutenberg solves the problem with gutenberg 3.0.6. Has anyone tested here?
theme_switcher to use Claro Theme at affected node forms can be used as a workaround.
Thx for the quick response.
I made a mistake and if the 2 files are und libraries/chosen it works.
Thx for feedback.
Tested upload of eca.eca_.process_kko3nmq.yml.tar.gz via /admin/config/development/configuration
Error message
The intended configuration cannot be imported because it comes from a different installation than this one. Only cloned instances of the same website can be synchronized.
I see I have to generate the file through config export and not through the ECA model export function. I will test again and report.
> You should only import the eca.eca.*.yml file
I tried that before.
Upload 'eca.eca.process_kko3nmq.yml.tar.gz' contains only 'eca.eca.process_kko3nmq.yml'
--> brings error message: Uploaded archive is not consistent.
Upload 'eca.eca.process_kko3nmq.yml' directly
--> brings error message: Unsupported file extension.
OK thx. Attached is the merged model.
My test failed with error 'Uploaded archive is not consistent.' at /admin/config/workflow/eca/import
> You have to being them together so that after merging there is still just 1 list for each.
Ok, but when I have 2 separate events with relating conditions and actions, how can this work?
For example I want to merge 2 models to one model - all regarding article nodes
Model 1:
E: insert article
C: field_tags value is empty
A: display msg
Model 2:
E: edit article
C: field_image value is empty
A: display another msg
If I would merge this to one list all events would trigger all actions at all conditions, isn't it? Or have I misunderstood something?
Thanks for the news.
Did I understand correctly:
As a test, I can try copying the contents of 1 eca.eca.*.yml file and adding it to another one to test whether it can be opened with the bpmn_io modeller in ECA?
thx megachriz - your proposal for the field descriptions in #6 makes it clear to me.
typos
It has turned out that the requirements in the related web project have changed and this calculation has now become obsolete. Nevertheless, I would like to see this problem solved out of interest in further training and also for the community.
In principle, the modelling approach would be as follows:
Add 3 years to the field_startdate and compare with current_date. If the result date is smaller (older) than the current_date, repeat this operation until the result date is in the future.
The eca_tamper plugin must be used to convert between Unix timestamps and formatted dates.
Unfortunately, I don't have the time this week to build the ECA-Moidel. The maintainers may therefore feel free to close this issue.
Thank you. I imagine the requested new tamper plugin could help here. I will try out.
There is a correspondingly open issue for 3.x-dev (needs work):
https://www.drupal.org/project/simplenews/issues/2556441
✨
Sending an item to multiple newsletters
Needs work
SocialNicheGuru commented 4 days ago:
> the patch no longer applies to simplenews 4.x
> Just wanted to mention that #31 doesn't work with Drupal Symfony Mailer 1.4.1 but it does with 1.3.2.
I'm still using the patch from #11 and it still works with Drupal Symfony Mailer 1.4.1. Are there any disadvantages against the newer patch #31 ?
Do you have a suggestion how this can be formulated on the project side?
Would it be helpful to insert the following after the first paragraph?
"This module allows for the add and edit form displays to be configured differently. There is no configuration fot form display paths provided."
patch #2 works for me.
Patch #2 works for me, thanks!
@kopeboy
Thank you for your valuable addition.
Big sorry, I misconfigured the translations and caused this error by writing into the help fields.
All works well.
patch in #4 works great for me. Thanks.
Patch in #11 works for me. A new ECA Action to send html mail is available and works.