I did a test, and the submission seems unsaved when the SMTP is not working. It is important to save the submissions if SMTP is not working.
This should not be a suggestion This is a bug in the work. Big one.
revised it to a bug
Hi @vincentczb,
I donât think this is a bug, as mentioned here:
"The form actions run when the form is submitted. You may set one or multiple actions for your form. They will run in sequence according to the order defined, except for the âRedirectâ action, which will run after all other actions. "
So if the âsave submissionâ action is added before the âemailâ action then the form should be submitted even if the email fails to send.
But if you did the above and the form entries are still not being saved, then that would indeed be a bug.
It is fixed. But tbh, it is not good for users to define the order of actions. I donât think people will pay attention to it. When I used a form plugin before, I did not face this issue even if SMTP not working
I think it might be best if we can make it more explicit in the builder itself, but I think it can be useful to have some control over execution. For many use cases you might want to only proceed with an action only if the previous succeeds (e.g. only save if the email actually went through).
As a new user, this isnât very clear.
I enabled form submission saving in the general options and expected to see my test email saved, but it wasnât. I have to manually turn it on in each form.
Googling that, I found this thread which suggests changing the order of the actions, but there doesnât appear to be any way to reorder them other than by deleting them and adding them again.
So if you want to add a new action at a specific point, the only way is to delete everything after the position you want the new action in and then re-add everything back.
As email is added by default ( I think save submission should be when enabled globally), to get the submission saved in the event of an email error, you first need to delete the default email action.