Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Email Attendees option failing, but other emails work | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Email Attendees option failing, but other emails work

Email Attendees option failing, but other emails work

Posted: September 9, 2013 at 10:17 am

Viewing 5 reply threads


Ross Willits

September 9, 2013 at 10:17 am

I am trying to send an update email to all attendees of a particular upcoming event. I use the Easy WP SMTP plug in to send messages using our gmail account, and this works just fine for all transaction emails, but I have received a “configuration error” when trying to send this particular message.

The message will be sent to 91 addresses, which doesn’t seem like too many to me, but could that be the issue? And if so, how can I automate sending a message in smaller blocks, without sending to each individual?

Thank you,
Ross


Ross Willits

September 9, 2013 at 10:26 am

UPDATE:
Here is the error I receive:

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator to inform of the time the error occurred and of anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

I also turned on SMTP logging, but it’s not getting to the point of opening an SMTP session before it fails.

We have WP 3.6, and EE and all its plug ins are up to date.


Josh

September 9, 2013 at 12:35 pm

Hi there,

The first thing I would advise trying is increasing the memory allocated to PHP. Event Espresso’s email features do not have a way to automate sending the messages in smaller blocks, but I’ve tested the same feature out on over 200 emails and it worked.

One thing that may help is to avoid using custom email tags where possible to reduce querying the db for each email that goes out. For example, if your email includes the answers to each attendee’s registration this will increase the number of queries it runs when it sends out the emails.


Ross Willits

September 9, 2013 at 12:39 pm

Thanks for the response.

I have since discovered that despite the error, the mail was sent–4 times. Ugh.

I’ll have to just ignore the error in the future, I guess.

As for the db queries, the only info that I included was first name and number of tickets, but that still hits the db twice per message. Is that too much?

Thank you,
R


Sidney Harrell

  • Support Staff

    •

September 9, 2013 at 2:52 pm

I took a look at the email code and it will do 3 db queries per message but it does it whether you use any shortcodes or not.


Ross Willits

September 9, 2013 at 2:56 pm

OK Thank you.
I’ll just be very careful with this function in the future.
Viewing 5 reply threads

The support post ‘Email Attendees option failing, but other emails work’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

The original Forum description...

Status: closed

Updated by Ross Willits 11 years, 4 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: resolved
Event Espresso - Staging Server