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 Multiple Confirmation Emails sent | Event Espresso - Staging Server
We have set up Event Espresso and we got everything working and ready for launch.
There is only one problem. We get multiple confirmation emails from WordPress.
We have disabled all other plug-ins except the Event Espresso.
we have looked into this thread http://staging.eventespresso.com/topic/multiple-confirmation-emails/ adn our forcing HTTPS on return URL option is unchecked.
We also have tried using WP MAIL-SMTP. It is not our server or the email server because it works fine with the test email and we have tested it with our sites we run using the same email adress.
ps. we also got 9 welcome emails from you guys when we signed up and purchased EE a couple of days ago. Not sure if these events are connected but i thought it might be worth mentioning it.
it would be useful for our client if the cart page could be password protected though. they host exclusive and secret parties. They would quite like the feature. Any way we can do that?
In short, no. The page itself needs to be available for the plugin to work, password protecting it will just break the plugin in a variety of ways.
Another option would be to put the events behind a membership wall. Helps keep them “secret” and means the plugin will function correctly.
Viewing 6 reply threads
The support post ‘Multiple Confirmation Emails sent’ 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.