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 Non-prepay events | Event Espresso - Staging Server
All of the events I’m adding to my website have a price, but I am not using EventEspresso to collect payments ahead of time – people pay at the event. The default seems to be that EE assumes payment will be handled on the site. Is there a way to adjust this so that customers don’t get messages that ask them to pay? Registration confirmation is automatic as soon as they sign up.
Two ways come to mind;
1) set the price to zero and don’t show price just put it in the description.
2) use a promo code “Pay at Event” with the code being 100% off.
The down side is that you will not record the $ for the event.
There are two payment options that you could set up: Check/Money order and/or Invoice. Either of these should work in this scenario. Simply add the instructions to pay at the event to either of these in the payment settings.
When someone clicks through to either download the invoice, or finalizes their registration for the Check/Money order option, their registration status will be set as pending and it will count toward the max limit of registrations. Alternatively, you can set the default registration status to pending, and clicking through to finalize the registration will not be necessary to reserve a spot. This can be set for all events on the Event Espresso>General settings, or per event in the event editor.
Viewing 2 reply threads
The support post ‘Non-prepay events’ 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.