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 Require Payment Before Adding Attendee | Event Espresso - Staging Server
This is my first time using Event Espresso and it is a great plugin. I have one small question though – which involves a process that seems backwards to me.
When you sign up for an event, you submit your information and then are registered in the database. You are then taken to a second area to complete payment. My problem is that I am having tons of people that register for the event and never pay. I am not sure if they don’t understand or they don’t see that they still have yet to pay.
I want a way to not add the attendee to the event until their payment is completed. It is not because I only have a limited number of seats or anything, but because I want to send out reminder emails to people who haven’t paid yet. But for most of these people, they actually have paid, just on a second registration record. Sending out the email may get them to pay a second time be mistake.
I thought I read in the forums that there was a way to do this. If I am correct, could you please provide a link?
The system is built to add the attendee to the database fairly early on to enable clients to be able to contact non payers etc so there is no way that I know of to stop this short of editing large chunks of the code.
However, if the non payee is being set (correctly) as incomplete, it will not affect the total spaces for the event.
I cannot find any forum posts regarding something like this, and as mentioned it would require some heavy customisation I believe to get it to work as you would be changing one of the core elements of the registration process.
Viewing 1 reply thread
The support post ‘Require Payment Before Adding Attendee’ 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.