* Autocheckin data model/cosmetics
* Expose automatically checked-in OrderPositions
* Expose automatically checked-in OrderPositions in CSV/PDF Exports
* Fix some tests, try to fix MultiStringField/CheckboxSelectMultiple
* Actually fix MultiStringField/CheckboxSelectMultiple.
(Not pretty, but it works)
* Fix more tests
* Squash migration
* Also fix CSV/nameparts-test
* Changes for Autocheckin code-review
* Perform Auto-Checkins through new core plugin
* Update config-doc to reflect also checkinlists
* Explicitly output AutoCheckin Yes/No for CSV-Export (+ fix test)
* Move autocheckin from plugin to service
* API-doc
* Fix API-doc spelling
* Checkinlist-API and autocheckin order tests
* Performance improvement when reading checkinlists for autocheckin
Co-Authored-By: Raphael Michel <michel@rami.io>
* Autocheckin test for order created through API
* Resolve migration conflict
* First tabs
* Convert more pages
* Convert question page
* Item form
* Add item_formsets signal
* Revert "Add new signal nav_item"
This reverts commit 1ce613ff89.
* Formset is a word!
* Initial work on seating
* Add seat guids
* Add product_list_top
* CartAdd: Ignore item when a seat is passed
* Cart display
* product_list_top → render_seating_plan
* Render seating plan in voucher redemption
* Fix failing tests
* Add tests for extending cart positions with seats
* Add subevent_forms to docs
* Update schema, migrations
* Dealing with expired orders
* steps to order change
* Change order positions
* Allow to add seats
* tests for ocm
* Fix things after rebase
* Seating plans API
* Add more tests for cart behaviour
* Widget support
* Adjust widget tests
* Re-enable CSP
* Update schema
* Api: position.seat
* Add guid to word list
* API: (sub)event.seating_plan
* Vali fixes
* Fix api
* Fix reference in test
* Fix test for real
* .
* Add a position detail page to the frontend
* Mail templates
* Send mails
* Send reminder email
* Add position support to sendmail plugin
* Add and fix some tests
* Fix failing test on real databases
* Change semantics of changing orders
This basically does two things to the "Change products" view of orders and the
OrderChangeManager program API:
1) It decouples changing items or subevents from changing prices.
OrderChangeManager.change_item() and .change_subevent() no longer
touch the price of a position. Instead .change_price() needs to be
called explicitly. However, a client-side JavaScript component now
*proposes* a new price based on the changed item or subevent.
2) The user interface now exposes the possibility of doing multiple
things at the same time, i.e. changing the item, subevent and price
in the same operation. OrderChangeManager already allowed this
before.
(1) is basically a consequence of (2), while (2) is a prerequesite for
e.g. the `seating` branch, where changing the subevent will always
require changing the seat.
* Add tests for price calculation API
