diff --git a/doc/screens/event/subevent_create.png b/doc/screens/event/subevent_create.png new file mode 100644 index 0000000000..c200ee4c4c Binary files /dev/null and b/doc/screens/event/subevent_create.png differ diff --git a/doc/screens/event/subevent_detail.png b/doc/screens/event/subevent_detail.png new file mode 100644 index 0000000000..7df87a8d00 Binary files /dev/null and b/doc/screens/event/subevent_detail.png differ diff --git a/doc/screens/event/subevent_list.png b/doc/screens/event/subevent_list.png new file mode 100644 index 0000000000..b5249aa081 Binary files /dev/null and b/doc/screens/event/subevent_list.png differ diff --git a/doc/user/events/create.rst b/doc/user/events/create.rst index 2fb7bf9820..5054ba3a45 100644 --- a/doc/user/events/create.rst +++ b/doc/user/events/create.rst @@ -28,7 +28,7 @@ is useful if you have a large number of events that are very similar to each oth (i.e. users should be able to buy tickets for multiple events at the same time). Those single events can differ in available products, quotas, prices and some meta information, but most settings need to be the same for all of them. We recommend to use this feature only if you really know that you need it and if you really run a lot of events, not if -you run e.g. a yearly conference. +you run e.g. a yearly conference. You can read more on this feature :ref:`here `. Once you set these values, you can procede to the next step: diff --git a/doc/user/events/subevents.rst b/doc/user/events/subevents.rst new file mode 100644 index 0000000000..f745e1a271 --- /dev/null +++ b/doc/user/events/subevents.rst @@ -0,0 +1,111 @@ +.. _subevents: + +Event series +============ + +During creation of a new event, you can choose that you want to create this event as an event series. +By event series, we mean a group of events that are similar in their structure and that you want to +sell within a single shop. An event series consists of **dates**. Each date represents one "event" +within the series. + +For example, we think good examples to use the event series feature are: + +* A theater or theater group that shows the same play on five evenings. + +* A band on tour that hosts the same show in different locations. + +* A workshop that is given multiple times in different locations or at different times. + +We **don't** think that the feature is well-suited for events like the following: + +* Event series distributed over a large timescale like annual conferences. We suggest using multiple events in this + case. You can avoid having to configure everything twice since you can copy settings from an existing event during + creation of the new event. + +* Multiple parts of a conference or festival (e.g. different days) if a significant number of attendees will visit + more than one of them. We suggest just using different products in this case. + +When using an event series, the single dates of the series are using the same settings in most places. They can +**only** differ in the following aspects: + +* They can have different date, time, and location parameters. + +* They can use different text on the shop front page. + +* They can have different prices for the various products. + +* They always have distinct quotas, which allows you to assign different amounts of tickets or to enable or disable + some products completely. + +* They can have different rules for check-in. + +Therefore, if your events are likely to need more different settings, this is probably not the feature for you. The +benefits of using event series, on the other hand, are: + +* You only need to set most settings once, as the multiple dates live in the same shop. + +* Your customers can build mixed orders, i.e. they can order tickets for multiple dates at once. + + +Creating and modifying dates in the series +------------------------------------------ + +Click on "Dates" in the left navigation menu of your event. This page shows you the list of currently existing event +dates and allows you to create, edit, clone and delete them. + +If "Dates" is missing from the navigation menu, you have insufficient permission or your event has not been set up as +an event series and you need to create a new event. + +.. thumbnail:: ../../screens/event/subevent_list.png + :align: center + :class: screenshot + +If you click on one of them or create a new one, you will see the following form: + +.. thumbnail:: ../../screens/event/subevent_create.png + :align: center + :class: screenshot + +Here, you can make changes to the following fields, most of which are optional: + +Name + This is the public name of your date. It should be descriptive enough to tell the user which date to select in + a calendar. + +Active + This date will only show up for customers if you check this box. In this sense, it corresponds to the "live" setting + of events. + + +Event start time + The date and time that this date starts at. + +Event end time + The date and time this date ends at. + +Location + This is the location of your date in a human-readable format. We will show this on the ticket shop frontpage, but + it might also be used e.g. in Wallet tickets. + +Admission time + The admission date and time to show on the ticket shop page or on the tickets. + +Frontpage text + A text to show on the front page of the ticket shop for this date. + +Start of presale + If you set this, no ticket will be sold before the time you set. If you set this on event series level as well, + both dates must be in the past for the tickets to be available. + +End of presale + If you set this, no ticket will be sold after the time you set. If you set this on event series level as well, + both dates must be in the future for the tickets to be available. + +Quotas + As for all events, no tickets will be available unless there is a quota created for them that specifies the number + of tickets available. You can create multiple quotas that are assinged to this date directly from this interface. + +Item prices + This is a table of all products configured for your shop. If you want, you can enter a new price for each one of them + in the right column to make them cheaper or more expensive for this date. If you leave a field empty, the price will + follow the product's default price. diff --git a/doc/user/index.rst b/doc/user/index.rst index 06d51e4781..d933e48478 100644 --- a/doc/user/index.rst +++ b/doc/user/index.rst @@ -9,6 +9,7 @@ wanting to use pretix to sell tickets. organizers/index events/create + events/subevents events/taxes payments/index events/widget diff --git a/doc/user/payments/fees.rst b/doc/user/payments/fees.rst index 04b8e90e59..5a839bf8fe 100644 --- a/doc/user/payments/fees.rst +++ b/doc/user/payments/fees.rst @@ -18,6 +18,9 @@ might also decide to go for option one to make it easier for customers who don't legislation might already be in place or become relevant from January 2018 the latest. This is not legal advice. If in doubt, consult a lawyer or refrain from charging payment fees. +If you go for the first option (as you should in the EU), you can just leave the payment fee fields in pretix' settings +empty. + If you go for the second option, you can configure pretix to charge the payment method fees to your user. You can define both an absolute fee as well as a percental fee based on the order total. If you do so, there are two different ways in which pretix can calculate the fee. Normally, it is fine to just go with the default setting, but