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
Limiting number of tickets for sale to number of bookings as opposed to payment | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Limiting number of tickets for sale to number of bookings as opposed to payment

Limiting number of tickets for sale to number of bookings as opposed to payment

Posted: January 8, 2014 at 1:19 pm

Viewing 3 reply threads


Nick Putman

January 8, 2014 at 1:19 pm

Hi,

It looks EE is using the number of completed bookings to judge how many tickets are left – is there are a way of using the number of bookings (whatever their status) instead?

Thanks,

Nick


Jonathan Wilson

  • Support Staff

    •

January 8, 2014 at 2:41 pm

Hi Nick,

Registrations with status of Pending or Complete will reserve a space. You can set the default payment status to Pending in the General Settings.


Nick Putman

January 8, 2014 at 2:47 pm

Perfect. Thanks Jonathan.

Best Wishes,

Nick


Jonathan Wilson

  • Support Staff

    •

January 8, 2014 at 2:52 pm

You’re quite welcome, Nick.

Let us know if we can help with anything else.
Viewing 3 reply threads

The support post ‘Limiting number of tickets for sale to number of bookings as opposed to payment’ 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.

The original Forum description...

Status: closed

Updated by Jonathan Wilson 11 years, 1 month ago ago

Topic Tags

Tagged: ,

Notifications

This topic is: resolved
Event Espresso - Staging Server