-
-
Notifications
You must be signed in to change notification settings - Fork 346
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set Checkin-date on category #333
Comments
syjer
added a commit
that referenced
this issue
Sep 13, 2017
syjer
added a commit
that referenced
this issue
Sep 13, 2017
TODO:
|
syjer
added a commit
that referenced
this issue
Sep 13, 2017
syjer
added a commit
that referenced
this issue
Sep 14, 2017
syjer
added a commit
that referenced
this issue
Sep 14, 2017
…pport for set/update valid check in from/to
syjer
added a commit
that referenced
this issue
Sep 19, 2017
syjer
added a commit
that referenced
this issue
Sep 20, 2017
syjer
added a commit
that referenced
this issue
Sep 20, 2017
syjer
added a commit
that referenced
this issue
Sep 21, 2017
syjer
added a commit
that referenced
this issue
Sep 21, 2017
syjer
added a commit
that referenced
this issue
Sep 21, 2017
syjer
added a commit
that referenced
this issue
Sep 21, 2017
syjer
added a commit
that referenced
this issue
Sep 21, 2017
…pport for set/update valid check in from/to
syjer
added a commit
that referenced
this issue
Sep 21, 2017
syjer
added a commit
that referenced
this issue
Sep 21, 2017
syjer
added a commit
that referenced
this issue
Sep 21, 2017
syjer
added a commit
that referenced
this issue
Sep 22, 2017
* #333 checkin date for ticket category: db changes * #333 fix mysql * #333 valid checkin from/to: add property in java model * #333 valid checkin from/to: mysql fix take2 * #333 valid check-in from/to for ticket category: backend: add insert/update support * #333 valid check-in from/to for ticket category: admin web ui: add support for set/update valid check in from/to * #333 check-in: add date check range from ticket category * #333 add UPDATE_TICKET_CATEGORY event for auditing * #333 fix query for mysql/pgsql * #333 add valid check in from/to to offline payload * #333 fix conditions
should be implemented |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Full support for multi-day events will come with v2.0 (along with other things)
For now we must at least support limited check-in, so that organizers can create multi-day events with combi tickets, or they can just create a special ticket for a fraction of the day.
To do that we should add "check-in-from" (default to event start at 00:00) and "check-in-to" (default to event end) to each category
Example1: three days conference
Day1 (2017-09-11): workshops
Day2 (2017-09-12): main event
Day3 (2017-09-13): other workshops / unconference / whatever
in this case the organizer should define the following categories:
Example1: one day conference
Day1 - main event (2017-09-11 08:00 - 16:00)
Day1 - meet & greet (2017-09-11 16:00 - 20:00)
in this case the organizer should define the following categories:
The text was updated successfully, but these errors were encountered: