Hi Patrick, I am back.
1. If you would log into the live site and test these emails: [...] You will see that all of those emails create the Filtered Email posts currectly, but fail to send the notification to that email as CRED is configured to do.
==> I did indeed log in, send the emails, and confirmed they are not working.
You can see and read this statement in my first reply to you, here:
https://toolset.com/forums/topic/new-post-notification-emails-are-not-functioning/page/2/#post-1249815
2. It seems that the CRED notifications do send correctly from the live site unless there has been a Filtered Email post in the past
==> Notifications are not related to the post fields or posts saved or trashed, they are sent when you submit that form.
Hence there is another code in place that makes it stopping to send the emails in case some kind of entry exists already.
Having posts in the database will never stop a notification to be sent when the form is submitted since Toolset Forms simply does not provide methods to limit submits and also notifies you each time the form is submitted. If that stops once certain entries exist then it's due to additional code or plugins and not Forms native behaviour.
That'd explain why locally it works - probably some of the required steps are not happening locally. Remains to figure out which those are to solve the issue.
3. I have searched the WordPress database and have found that for every email that fails, there are posts and post meta that are labelled CRED auto-generated post
This is not possible. Toolset Forms does not store emails sent in the database.
It stores emails that you save to be sent - the blueprint so to say - but not the mail you have sent.
It also creates no posts for failed emails. It might be there is either code or plugin interrupting post creation - then you see autodrafts.
4. I modified the validation function in the child theme functions.php to verify that form.
So there is custom code validating this form.
This confirms it:
Then, I switched to the 2019 theme and deleted all of the Filtered Email posts I had just created with the form. I then repeated the process and all of the filtered email posts were created and all of the notifications WERE SUCCESSFULLY SENT!
5. It's most likely not Avada but that code.
I've checked the code and in fact, you use "already created posts with such email" to interrupt the script:
==> //check if email is already in the database
if (count($posts) > 0){
//set error message for my_field
$errors['wpcf-domain-limited-email']='This E-mail is already registered. Please use the link you received via email to manage your nominations.';
}
I am quite sure, as soon that code is removed from the Avada theme (and any related, or similar, applying to the same form) the issue will be solved
Adding custom code to Theme Twenty Seventeen Functions.php is not an issue, this work - however, with Custom Code we can help only limitedly.
The first I saw is that you return array($fields,$errors); twice.
That would be incorrect, according to the API DOC we should return it at the end:
https://toolset.com/documentation/programmer-reference/cred-api/
Can you confirm:
- using a Fresh copy of the Avada Theme solves the issue
- using a copy of the Avada theme without the above code solves the issue
If so, we have a point to start where you can then re-introduce the code you removed piece by piece to know where it fails.
Related to custom fields, I see you check upon those to verify the existence of emails, those are always attached to the post and get deleted when you delete the post.
Not when you trash the post, but only when you delete it.
Then, the meta is removed and has no more occurrence in the database unless otherwise added by code previously.
