Conversation
|
|
||
| **Copying rows** creates duplicate seat IDs as well as combination of zone, row number, and seat number. | ||
| Change the row number of the row you copied to an number that is not yet in use on the plan. | ||
| Then, activate the "Reversed" toggle and deactivate it again. |
There was a problem hiding this comment.
In my test, this step is not necessary if I already changed the row number.
There was a problem hiding this comment.
Changed the row number when?
Copying rows without this step results in failed validation for me every single time
There was a problem hiding this comment.
Not for me, if you want, we can do a quick screenshare session tomorrow
| 3. a custom string defined by you | ||
|
|
||
| The editor will assign seats the first option (UUID) during creation if you do not change any of the defaults (row or seat number). | ||
| If you change seat or row number, or if you use the "Reversed" toggle, the editor will assign the second option (zone, row number, and seat number, joined with dashes) as the seat ID. |
There was a problem hiding this comment.
Still not happy with the Reversed toggle as the trick here, without explaining that the Reversed toggle is actually for. But that might be a software UX issue, not a docs issue ;
There was a problem hiding this comment.
Is there a more straightforward way to do this?
There was a problem hiding this comment.
No, that's what I mean: I don't like it, but it's a problem of the software, not of your docs.
Jopretix
left a comment
Jopretix
left a comment
There was a problem hiding this comment.
Various comments on seating documentation
| It is not available on pretix Community. | ||
|
|
There was a problem hiding this comment.
In my experience this is a very complex subject for most of our customers. From a didactic point of view I would argue to first introduce the basic model and terms of pretix' seating right at the beginning of this article and then exploring the details of seating like in the rest of this documentation and how to set it up correctly. Maybe like this:
pretix' seating plans allows you to create seats and organize them in numbered rows. You can define multiple zones in pretix and assign those seats/rows accordingly. Zones can help your customers to find their seats more easily if your event space has a more complex layout like orchestra, mezzanine, balcony and a left and right side since these zones will be shown on the layout and the tickets. Furthermore you can introduce different categories to your seating plan since you might want to assign different products with different prices to your seats.
| In order to configure seating plan behavior for your singular event or event series, navigate to :navpath:Your event → :fa3-wrench: Settings → Seating plans:. | ||
| If you want your customers to be able to select their own seats, check the box next to "Customers can choose their own seats". |
There was a problem hiding this comment.
| In order to configure seating plan behavior for your singular event or event series, navigate to :navpath:Your event → :fa3-wrench: Settings → Seating plans:. | |
| If you want your customers to be able to select their own seats, check the box next to "Customers can choose their own seats". | |
| In order to configure the seating plan behavior for your singular event or event series, navigate to :navpath:Your event → :fa3-wrench: Settings → Seating plans:. | |
| If you want your customers to be able to select their own seats, check the box next to "Customers can choose their own seats". |
| The page will display an error message. | ||
|
|
||
| If the new plan fulfills both requirements, then the migration will be successful. | ||
|
|
There was a problem hiding this comment.
One advanced feature is missing: The optimizer hint. With this one can define which seats can be bought first. This comes in handy to decrease clusters in your seating array. I think we should at least mention it here, or don't we?
4 participants
Explain how to set up seating plans and layouts, and how to sell tickets that way