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
Booking Conflict Resolution | Event Espresso - Staging Server

Support

Home › Forums › Pre-Sales › Booking Conflict Resolution

Booking Conflict Resolution

Posted: December 2, 2013 at 1:46 pm

Viewing 1 reply thread


Brandon Harvey

December 2, 2013 at 1:46 pm

How does the system handle conflict resolution?

Ex.

I have 4 events with likely the same starting times.

I want to attend all of them (physically this is impossible)

However I don’t pay attention.

Will the system be able to detect that i’ve already booked an event at that time and give me an alert and or prevent me from doing this without some sort of admin approval?

If this exists, can I still have booking confirmation on the admin side? And if so will it still work properly?

Thank You


Dean

  • Support Staff

    •

December 3, 2013 at 1:04 am

Hi Brandon,

There is no system in place for managing booking time conflicts at this moment, it would be up to the registrant to make sure they are not booking conflicting times.
Viewing 1 reply thread

The support post ‘Booking Conflict Resolution’ 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.

Status: closed

Updated by Dean 11 years, 1 month ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server