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 EE Email Transactions Overloading Server | Event Espresso - Staging Server
I’m using the latest versions of EE and EE-Email-Transactions (hooked up to Mandrill), and am encountering a major problem. We have a couple thousand attendees that we’re trying to email at once, and the process takes so long that eventually we end up with a HTTP 504 error.
I can’t be sure that all the emails have sent, but my guess is that they haven’t.
Is there a way to alter the sending process so that the emails are lumped into a queue or something…and then slowly released to Mandrill for sending?
There isn’t currently a feature that splits up the all attendee email into batches.
One thing that may help is reduce the number of shortcodes within the email template in order to speed up the request. For example: if the email has the [start_date] shortcode you can swap it out with the actual start date. You’ll likely use the custom email feature within the event’s editor to make this happen.
Viewing 3 reply threads
The support post ‘EE Email Transactions Overloading Server’ 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.