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 Layout of seating chart | Event Espresso - Staging Server
We at ORSO (www.orso.org) are very interested in buying EventEsspresso for our WP-Environment. But before that we need to clarify how flexible the seating charts are. I understand that there is a database we have to provide (like csv or excel data) but I don’t find any information about special layouts like side-balconys, curved rows, things like that.. can I find some examples of seating charts used in EE somewhere? Thanks a lot! Wolfie
The seating chart has a level feature that allow for layouts that have different sections (like a balcony section) and has a placeholder feature that lets you add structured gaps to the seat chart to help approximate an actual layout. The seats are laid out in a grid, so no current support for curved rows. Here’s a link to a PDF copy of the documentation so you can review how a chart can be built.
I couldn’t find a good example of a site where the seat chart is in actual use, however we have a live demo that you can test to see how the tickets gets selected by the ticket purchaser right here:
The support post ‘Layout of seating chart’ 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.