Support

Home Forums Event Espresso Premium event registration email not sending

event registration email not sending

Posted: May 27, 2020 at 3:33 am


KerrieBowles

May 27, 2020 at 3:33 am

Can you please tell me why I’m not receiving the event Registration Approved email.
It worked for the test which Lorenzo did on 16th May, then worked for the first event registration I received and has not worked for two registrations since then.
I’ve taken screen shots but can’t include them here. The people who have registered are receiving the Payment Received email but nothing else. The only way I can get them to people is to use the send immediately function. The emails are Queued for Generating. In the Message Activity there is no recipient for To or From. I have searched the forums – is this the answer?
December 1, 2017 at 3:04 am

Hi there,
EE uses WP Cron to send the emails work through the email queue and it sounds like it has been disabled on your server.
Go to Event Espresso -> Messages -> Settings
You’ll see the option ‘Generate and send all messages:’
Set that to ‘On same request’ and restest a registration, do you receive it without forcing the email through the queue then?

Thank you.


Tony

  • Support Staff

May 27, 2020 at 6:38 am

Hi Kerrie,

I have searched the forums – is this the answer?

It may be the answer but it depends.

EE uses WP Cron to send emails and if yours are sitting at ‘Queued for Generating’ then there is either an issue with WP Cron or it has been disabled on your server.

Switching the above setting tells EE to stop using WP Cron and just send the emails immediately. If you do that on your site and add a test registration to an event (create a test event with a free ticket to test), does it send immediately?

If it does, then there is an issue with WP Cron and really that should be investigated further as other areas of your site us WP Cron. Your host may have disable it and set up a ‘real’ cron on the server, or disabled it completely. If thats the case I recommend requesting the enabled it or setup a real cron to takes its place.

Who hosts your site?


KerrieBowles

May 28, 2020 at 7:01 pm

Hi Tony, I did as you suggested above and yes that worked – I received the registration notification immediately.Our site is hosted by Zuver which is based in Australia. Looks like I need to contact them? or just leave it at this setting?
Many thanks, Kerrie


Tony

  • Support Staff

May 29, 2020 at 5:08 am

Leave it as is for now so your emails work.

To troubleshoot, go to Dashboard -> Tools -> Site Health

Leave that page open for a little so it can run tests in the background (usually takes up to a minute).

In another tab, go to Plugins -> Add new and add WP Crontrol, install and activate it.

It’s this one: https://wordpress.org/plugins/wp-crontrol/

Then go to Dashboard -> Tools -> Cron events.

At the top of the page does it have a notice about WP_CRON at all?


KerrieBowles

June 1, 2020 at 10:51 pm

Hi Tony, I completed your above suggestions. The site health check came out as Good with 4 recommended improvements – removing inactive plugins, removing inactive themes, one or more recommended modules missing ( to do with PHP), and the site doesn’t use https. This is the PHP message “PHP modules perform most of the tasks on the server that make your site run. Any changes to these must be made by your server administrator.
The WordPress Hosting Team maintains a list of those modules, both recommended and required, in the team handbook (opens in a new tab).
Warning The optional module, imagick, is not installed, or has been disabled.”

The only thing I can see after installing and activating WP Crontrol and going to Cron Events is this message which wasn’t at the top of the page -“The scheduled cron events have changed since you first opened this page. Reload the page to see the up to date list.” Reloaded the page, message wasn’t there, then came back after a short time.


Tony

  • Support Staff

June 3, 2020 at 3:52 am

“The scheduled cron events have changed since you first opened this page. Reload the page to see the up to date list.” Reloaded the page, message wasn’t there, then came back after a short time.

That’s fine, it likely means you have a corn running on a short interval that is updating.

So it does sound like WP Cron is active on your site then.

So to troubleshoot this further you’ll need to switch back to using ‘On separate request’ in the Message settings.

Then open up the corn events page again and search for ‘AHEE__EE_Messages_Scheduler’ do you see 3 jobs listed there then?

If yes, test another registration and see if the email arrvies.

Note that WP Cron relies on ‘hits’ on your site, so trigger a message and look in the message queue to see if the message shows as ‘no recipient’ (expected at that point), wait for more than 5 mins and refresh the page, does it change?

It should have a blue ‘status bar’ (the coloured bar to the left) and have be ‘waiting for sending’ or possible switch to green and already sent.


KerrieBowles

June 27, 2020 at 8:08 pm

Hi Tony, firstly apologies for taking so long to get back to you on this – there’s been a lot happening here and I haven’t had time to go through your response.
I’ve done as suggested above – the‘AHEE__EE_Messages_Scheduler’ I see looks like this ‘AHEE__EE_Messages_Scheduler_cleanup’ – under actions it’s EE_Messages_Scheduler::cleanup() Not sure if that’s what I’m supposed to be seeing?? I haven’t done a test rego as I don’t think that’s what you mean?

On another question – is it possible to hide the amount of tickets left to sell for an event from the public in the registration page? so when you click on show details under Access it is showing how many tickets are remaining.
Many thanks, Kerrie


Tony

  • Support Staff

June 28, 2020 at 12:12 pm

the‘AHEE__EE_Messages_Scheduler’ I see looks like this ‘AHEE__EE_Messages_Scheduler_cleanup’ – under actions it’s EE_Messages_Scheduler::cleanup()

Sounds like you only have 1 of the 3 corn jobs set.

De-activate the Event Espresso 4 plugin, then re-activate. That will force EE to recheck various options, including the corn jobs it needs.

Side note, de-activating EE will also de-activate some of its add-ons, once you’ve re-activated EE you will then also need to re-activate the add-ons.

On another question – is it possible to hide the amount of tickets left to sell for an event from the public in the registration page? so when you click on show details under Access it is showing how many tickets are remaining.

Currently, you can either remove the ticket details section completely or just hide those ticket values with some CSS if that will work for you?

If you let me know which option you prefer I’ll add more details.


KerrieBowles

June 29, 2020 at 5:12 am

Thanks Tony. I’d like to remove the ticket section completely.

Re deactivating and reactivating EE – that makes me very nervous that I’ll lose all the data I’ve got in each event – 23 in total!! Is there any problem with just leaving the setting at “on same request”? It’s working fine with that.


Tony

  • Support Staff

June 29, 2020 at 5:33 am

Thanks Tony. I’d like to remove the ticket section completely.

Then go to Event Espresso -> Events -> Templates

In there you’ll find a ‘Ticket Selector Template Settings’

Set ‘Show Ticket Details’ to No and save.

That will remove those details.

Re deactivating and reactivating EE – that makes me very nervous that I’ll lose all the data I’ve got in each event – 23 in total!!

All of the Event data, (Events themselves, registrations, venues, everything you create/set) is stored within the database itself, you won’t lose any data by de-activating the plugin but I understand if you prefer not to.

Is there any problem with just leaving the setting at “on same request”?

No problems as such, there are 2 things that come to mind.

It means that when emails are triggered the user’s request will take a little longer to load the page but it’s not usually significant. So for example when the user registers and pays, it will take a little longer for the thank you page to load as it has to wait for the email to send first.

The other is your can’t just the Automated Upcoming Events Notifications add-on as it relies on WP_Cron to function, if you’re not using that add-on anyway thats no issue.

It’s working fine with that.

If the above is working for you there’s nothing wrong with leaving it like that.


KerrieBowles

June 29, 2020 at 7:18 pm

Thanks so much Tony. I think I’ll leave the messaging as it is for now. Maybe I’ll look at it again later when I have a little more time.
I’ve changed the ticket selector and it’s worked fine too. Many thanks for all your help with my questions. Even when I was feeling very challenged by this your clear instructions really helped step me through everything I needed to do.
Take care. Kerrie


Tony

  • Support Staff

June 30, 2020 at 8:47 am

You’re most welcome, Kerrie.

If you run into any issues just let us know, we are here to help 🙂

You must be logged in to reply to this support post. Sign In or Register for an Account

Support forum for Event Espresso 3 and Event Espresso 4.
Documentation for EE3 and EE4
Documentation for Event Espresso 3 Documentation for Event Espresso 4

Status: publish

Updated by  Tony 3 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Do NOT follow this link or you will be banned from the site!
[gravityform id=80 title=false description=false ajax=false]
<div class='gf_browser_unknown gform_wrapper' id='gform_wrapper_80' ><form method='post' enctype='multipart/form-data' id='gform_80' action='/topic/event-registration-email-not-sending/'> <div class='gform_body'><ul id='gform_fields_80' class='gform_fields top_label form_sublabel_below description_below'><li id='field_80_1' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_80_1' >First name<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_text'><input name='input_1' id='input_80_1' type='text' value='' class='medium' aria-required="true" aria-invalid="false" /></div></li><li id='field_80_2' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_80_2' >Email address<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_email'> <input name='input_2' id='input_80_2' type='email' value='' class='medium' aria-required="true" aria-invalid="false" /> </div></li><li id='field_80_3' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' >GDPR Agreement<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_checkbox'><ul class='gfield_checkbox' id='input_80_3'><li class='gchoice_80_3_1'> <input name='input_3.1' type='checkbox' value='I consent to have this website store my submitted information so they can respond to my inquiry.' id='choice_80_3_1' /> <label for='choice_80_3_1' id='label_80_3_1'>I consent to have this website store my submitted information so they can respond to my inquiry.</label> </li></ul></div></li><li id='field_80_4' class='gfield gform_validation_container field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_80_4' >Name</label><div class='ginput_container'><input name='input_4' id='input_80_4' type='text' value='' autocomplete='off'/></div><div class='gfield_description' id='gfield_description_80_4'>This field is for validation purposes and should be left unchanged.</div></li> </ul></div> <div class='gform_footer top_label'> <input type='submit' id='gform_submit_button_80' class='gform_button button' value='Download Now' onclick='if(window["gf_submitting_80"]){return false;} if( !jQuery("#gform_80")[0].checkValidity || jQuery("#gform_80")[0].checkValidity()){window["gf_submitting_80"]=true;} ' onkeypress='if( event.keyCode == 13 ){ if(window["gf_submitting_80"]){return false;} if( !jQuery("#gform_80")[0].checkValidity || jQuery("#gform_80")[0].checkValidity()){window["gf_submitting_80"]=true;} jQuery("#gform_80").trigger("submit",[true]); }' /> <input type='hidden' class='gform_hidden' name='is_submit_80' value='1' /> <input type='hidden' class='gform_hidden' name='gform_submit' value='80' /> <input type='hidden' class='gform_hidden' name='gform_unique_id' value='' /> <input type='hidden' class='gform_hidden' name='state_80' value='WyJbXSIsIjBiNjdjZjkyMDUzOWUxOWY5Y2NiZjIwMzM4YjA1Mjk4Il0=' /> <input type='hidden' class='gform_hidden' name='gform_target_page_number_80' id='gform_target_page_number_80' value='0' /> <input type='hidden' class='gform_hidden' name='gform_source_page_number_80' id='gform_source_page_number_80' value='1' /> <input type='hidden' name='gform_field_values' value='' /> </div> </form> </div><script type='text/javascript'> jQuery(document).bind('gform_post_render', function(event, formId, currentPage){if(formId == 80) {} } );jQuery(document).bind('gform_post_conditional_logic', function(event, formId, fields, isInit){} );</script><script type='text/javascript'> jQuery(document).ready(function(){jQuery(document).trigger('gform_post_render', [80, 1]) } ); </script>
[i]
[i]