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 MER sending multiple emails when more than 1 price point selected | Event Espresso - Staging Server
I am currently using MER version 1.4 with 3.1.21p.
I have multiple price points (children and adults and toddlers). Registration goes fine, but one email is sent to the registrant at each price point. I know that this is being dealt with in 3.2, but is there any way to only send one email in 3.1 as getting 3 is confusing for the customer and they do not know if they have been charged twice or not, a situation which I would love to avoid.
That’s not something that can be changed in 3.1. That said, there was some work done in a recent version where the emails sent to the admin are truncated and the payment emails are sent only to the primary attendee. It’s better that what was before, so you might want to check out version 3.1.24.
I tried 3.1.24 subsequently and got the same result 3 separate emails sent to the primary attendee! Any idea on availability of 3.2? Is it a month 2 months 3 months?
That’s the registration confirmation email, correct? I don’t know how you have the emails set up, but if you set them to go out after payment is made, you can make it clear in the content of the email that they have paid.
I do not have a date for 3.2. We have a planned alpha preview release that is contingent on getting the invoice payment option finished, but this will not be recommended to use in a live environment.
Viewing 3 reply threads
The support post ‘MER sending multiple emails when more than 1 price point selected’ 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.