Hello!
We are going to be adjusting one of our spaces to include a lot of table seating next season and I am concerned about making this clear on the seatmap for SYOS. Could anyone point to a good example of someone currently doing this on TNEW?
Thank you,
We currently have some events that are partially reserved seating at tables and partially general admission. We just started doing this. Here's a link to one of the events: https://live.stanford.edu/calendar/march-2023/comedy-bing-suli-mccullough
Diana Burnell,
I would be curious as to how you are accomplishing that. Is that done via some JavaScript which forces a new link onto the GA area which is forcing the ?z=#### part of the URL or something else? I also happened to notice the production season ID is apparently "0"? I really like what you have done there, and am just curious about how it works.
John A. Moskal II
I really like this one. Thank you for this!
I did not build this, so am unsure of all the details. This is its own facility map. In the prices, we have two zones, one for Reserved and one for GA. with specific price types for each of those zones, with only those price types enabled for those zones (i.e. Reserved is enabled for the Reserved zone, but not the GA zone, and General Admission is enabled for the GA zone, but not the Reserved zone). We also assign the correct ticket type to each of those prices (reserved vs GA). I don't know about the URL questions or the production season question. Wish I could be more helpfull!
John A. Moskal II When the Production Season ID is unknown, a 0 can be used in its place: a single ID number preceded by a 0 is interpreted as a performance ID, and will load that performance. This is useful when the production season ID is unknown.Note: This link will not work if a customized URL Slug is set for the performance.For the GA link, this is actually something our Support team can assist with. Here's the note about how it functions:
I hope that helps!
Marley
That helps a lot. Thank you very much for the clarification. Somehow I missed that in the documentation.