|
JacquesMivi
|
January 18, 2017 at 2:44 am
Hi,
After the inscriptions emails are not automatically sending to the participant and the admin of the events. Its random, I think one on twenty doen’t work.
My EE4 message option is “send email on the same request”. When I activate “On separate request”, it is not send at all. You can see it on the following image (the page admin of EE messagee). On the blue box : emails generated are not corrects.
Also on the same image, you can see on the red box that a message have been send or the inscription of mcyferman at 20h17.
But when I check with the user, it does not have received the email. So I have installed the plugin wp-mail-log, and on this following printscreen, you can see that the only email sended to the participant is the confirmation at 21h17. It does not have receive the inscription of 20h17
I really need to fix this issue. because I can lost some participants if i d’ont check every day.
My Configurations
EE4 4.9.24p.
Wordpress 4.7
OVH
Thanks a lot
|
|
JacquesMivi
|
January 18, 2017 at 2:52 am
After verifications, it is the same mail between wp-mail log and EE4 message admin page.
The registration email (Inscription non approuvée) was not generated at all by EE4. It is not on the tab “Failed sending.
|
|
JacquesMivi
|
January 18, 2017 at 3:29 am
Update – I have received the messages with the option “On seperate request” 40 minutes later.
I can try to use this option, to improve the reliability of the system, but 40 minutes is too long. Can i make it shorter ?
|
|
Josh
|
January 18, 2017 at 2:15 pm
The “on a separate request” setting uses wp_cron. So it’s actually not set by time, it actually relies on someone clicking on a page of your website to trigger the messages. So it’s less than 40 minutes on a site with more traffic, and more than 40 minutes on a site with less traffic.
One thing that you can do that may help is you change the From and To fields in the message templates to include only the email address instead of Name + Email address. Your mail server may be having difficulty with the Name + part.
So in your message templates, in the To: and From: fields, you can use a short code like [CO_EMAIL] instead of [CO_FORMATTED_EMAIL] and so on.
|
|
JacquesMivi
|
January 19, 2017 at 2:49 am
With “Separate request” If I switch mozilla to chrome, then public navigation to private naviguation, clear the cache, naviguate between the back and the front… nothing improve the time limit to trigger the message.
So I d’ont understand, how works this trigger.
I Have switch [CO_FORMATTED_EMAIL] to [CO_EMAIL] I will check the improvments.
|
|
Tony
|
January 19, 2017 at 5:04 am
There is a time delate between each of the steps for the message to send, but its around 3 mins. The delay in receiving the email may well be caused by the mail-server you are using rather than EE/WP Cron etc.
To test when EE is sending the email open up the message activity page.
Now in another tab register onto an event and leave the thank you page open in that tab.
Switch back to the message activity page and you’ll view messages queued for generating, wait around 3-5 mins and refresh the thank you page.
Again view the message actitivty page, the message should be ‘queued for sending’.
Another 3-5 mins and refresh the thank you page again, the messages should switch to sent (green status bar)
From that point EE has triggered the email and sent it off to your mailserver, it does not have any further control over the email its all down to the mailserver.
How long after the message switch to green does it take for them to arrive?
|
|
JacquesMivi
|
January 19, 2017 at 10:27 am
I have try this process and it does’t work at all. Message is locked in “queued for generating” no matter what I try (New inscription, change user, change browser, clear cache, refresh “thank you” page etc.). I have to wait around 40 minutes to see the message to change. Then I immediately receive the message.
If I switch back to “on the same request” option. When I reserve an event I immediatly receive the inscriptions by email.
|
|
Josh
|
January 20, 2017 at 7:00 am
You could try installing the wp-crontrol plugin to look into why there’s a 40 minute delay, or you can use the Send on the same request option.
|
