Is it necessary to make it configurable? Emails will only fire if they are assigned to specific workflows. If you don't want Publish >> Publish to send an email, then don't assign one to it. Unless I'm missing something, it seems like this would be an okay feature to add to the module without also needing to add options/settings to the config.
Is it necessary to make it configurable? Emails will only fire if they are assigned to specific workflows. If you don't want Publish >> Publish to send an email, then don't assign one to it. Unless I'm missing something, it seems like this would be an okay feature to add to the module without also needing to add options/settings to the config.
- 🇩🇪Germany anruether Bonn
@hannakras I agree with you and also keep my transitions tidy in the sense that I do not allow multiple "From" states in the same transition. In that case you are right.
But it is possible to configure multiple from states in one transition so that your assumption is not always right.
- First commit to issue fork.
- Merge request !19Remove $original_state !== $new_state check for content moderation. → (Open) created by Noemi
- 🇺🇸United States goose2000
Hi, wondering about this in my project. If I understand correctly, if a transition stays the same, and the entity exists (edit form, not create form) - no email is sent.
Example: content type "Job Reference" has reference email field, when the reference is created (submitted to submitted transition) email template is fired of to the reference person to complete the form.
However, job applicant realizes email address was bad, and needs to correct that, hits the edit tabs and fixes the email address. Clicks Save, (submitted to submitted transition still) and this time, no email is sent to the corrected email address.
Well, this is my experience. I get how this would not work for other use cases, would be nice to have a global configuration :
Send email template(s) to same state transitions (submitted to submitted) Y/N ?