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
Removing certain seats from being available for events | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Removing certain seats from being available for events

Removing certain seats from being available for events

Posted: June 11, 2013 at 1:27 pm

Viewing 1 reply thread


Giles Tanja

June 11, 2013 at 1:27 pm

I am trying to remove certain seats from being available on an event by event basis. For example, all events will use the same seating chart, however the owners might reserve a row (or table) for themselves, so a transaction would not need to take place in order to reserve.

I know this is still in alpha, but this would help a ton. Also, there is the issue of certain events requiring the same seating chart, but costing different amounts. Just another issue I have run into.


Jonathan Wilson

  • Support Staff

    •

June 11, 2013 at 3:13 pm

Hi John,

At this time, you’ll need to copy the seating chart, then modify it to fit each individual event. There currently isn’t a way to say, “Use this chart, but only charge this price for these seats for this event.”
Viewing 1 reply thread

The support post ‘Removing certain seats from being available for 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.

The original Forum description...

Status: closed

Updated by Jonathan Wilson 11 years, 7 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server