Resolved
Reported for: Toolset Forms 2.3.2
If a form is configured to send email notifications when a custom field value changes, these notifications are sent every time the post or the user is updated on the backend. This happens if the field value meets the form notification condition.
Any updates on this? I’m noticing that when I move posts to the trash on the WordPress backend it triggers email notifications. I asked about a similar issue in an earlier thread here: https://toolset.com/forums/topic/cred-notification-from-form-a-sent-when-form-b-is-submitted/
It would be ideal if the notifications only triggered when that particular form was being filled out. I can’t think of very many use cases where this wouldn’t be the desired behavior, which makes me think this has to be a bug.
If notifications didn’t apply to individual forms it would make more sense to remove notifications from the form editor completely, and make a separate page to edit and view all form notifications (kind of like a the Views or Layouts editors).
If this is the desired behavior, I would like to request a future update includes ways to limit what events notifications trigger from.
Thanks
Hi Doug,
The issue is already in our development team queue.they will work on as soon as possible.
I’ve added a note mentioning your complaint so that they look into the issue sooner.
We already did a test round for the forms notifications including the notifications that trigger when trashing the posts. This should be fixed as well.
We are happy to see your comments and tickets which help in improving our products. Please keep watching this errata and we will notify you once we fix this issue.
Hi there, any updates on this issue? Currently have an email notification set to send only when a particular field is changed by the user (have also checked the ‘Only if field value has changed’ option in the form notification settings) but it is triggering again when the admin user goes into the backend and publishes the post (even though the field is not changed). Any workaround would be appreciated as the website is for an events festival which is open for registrations very soon. Cheers, Julia
Hi Julia, I am sorry to say that this issue is still not fixed, the truth is that we were busy with finishing the Toolset Blocks development which was needed and thus prioritized. The good news is that now with the Toolset Blocks development out of the door we can come back to this (and a few other pending issues).
I will raise that issue to our lead developer in 20 minutes and I’ll make sure it’ll be attended, a fix won’t be offered overnight, of course, so please follow here or on our announcement posts for newly released versions.
I understand this is not the reply you were hoping for, but I wanted to be straight forward and I hope you will have the patience to wait for the fix.