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 Pre-purchase Questions | Event Espresso - Staging Server
Can you please advise if it is possible to set up multiple payment options (not gateways) on one event. For example, my client wants to offer the ability for people to register for a workshop and pay a) in full, b) a 50% deposit and send an invoice for the balance by email. We also want to include an automatic member discount when the member is logged in. I have read through documentation but it is not clear to me whether this can be done on the same product/workshop.
We do not have a standard deposit feature, it’s either pay all or nothing. We plan to eventually add that into Event Espresso 4, but if you want to have that option in Event Espresso 3 then you might contact one of the Event Espresso Pros: http://staging.eventespresso.com/developers/event-espresso-pros/
So with the multiple prices/tickets your attendees will have the option to make their own choice… there isn’t a way to configure this with two ticket options? One ticketing being full price and one being a deposit option?
Sure, you can set up two different types of tickets per event. It will flag the registration as paid and complete so you’d have to manage the deposit payments manually. After someone registers with a deposit ticket, you can manually edit their payment so they have a remainder balance then send them an invoice that they can use to finish their payment.
Good thinking, didn’t expect you to want to go that direction.
Viewing 3 reply threads
The support post ‘Pre-purchase Questions’ 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.