* [WIP] add date/time question type
* Date/time questions python classes, types and form handling
* use own timepicker
* Fix argument naming
* Add css and js for datetimepickers
* remove not needed str call
* seperate splitdatetime widget template and fix date/time questions
* change date placeholder to dec 31
* do not show seconds in presale time pickers
* improve codestyle
* add new question types to api doc
* add test
* expand test to datetime question
* add new questiontypes to changelog
remove duplicate parens
* remove timezone from time only question answers
* improve codestyle
* Fix date and time formatting in control question overview
* Checking for the last date in the event series before deleting a date. Last date in a event series should never be delted.
* Adding check to ensure that last date in a event series is not deleted. Editing unit test around deleting subevent to assert on alert-danger
* Increasing the scope of test_delete. We are now creating 2 subevents and testing deleting one and ensuring that the last one is not deleted
* Fixing alert text. Removing a redundant if condition for checking subevent count
* Adding assert for second event to ensure its not deleted
* Minor fixes and rebase
* First stab at notification settings
* Add "global" setting for notification levels
* Trigger notification task
* Get users with permission for event
* Actually send notification emails
* More notifications
* Allow to turn off notifications
* Link in email to pause all notifications
* Add NotificationType to wordlist
* Add notification tests
* Add documentation
* Rebase fixes
* [WIP] Implement automatic spell-check for docs
fixes#663
The only thing unclear to me so far is how the output of `make spelling`
should be checked - is there a possibility to check for a file (i.e.
`_build/spelling/output.txt`) to be empty, and report a failed build
otherwise?
* fix typo in requirements.txt
* add enchant library
* travis should report errors, order spelling wordlist
* change travis.yml to easier troubleshoot build issues
* fixed more typos, added more words
* add more words, fix more typos
* added more words
* added more words
* revert changes to .travis.yml
* Data model and migration
* Some backwards compatibility
* CRUD for checkin lists
* Show and perform checkins
* Correct numbers in table and dashboard widget
* event creation and cloning
* Allow to link specific exports and pass options per query
* Play with the CSV export
* PDF export
* Collapse exports by default
* Improve PDF exporter
* Addon stuff
* Subevent stuff, pretixdroid tests
* pretixdroid tests
* Add CRUD API
* Test compatibility
* Fix test
* DB-independent sorting behavior
* Add CRUD and coyp tests
* Re-enable pretixdroid plugin
* pretixdroid config
* Tests & fixes
* Fix duplicate source string
* occured -> occurred
All resources I could find listed this as misspelled, but I wasn't too
sure…
Also, it should be checked if all changes to the .po-files are respected
in the corresponding src-files.
* Check that vouchers selected via API are for the correct event
* Choose different subject for reminder mails if auto-expiry is off
* correct english typos
As with PR #660, it should be checked whether the changes to the
.po-files are respected in the corresponding src-files.
* [WIP] manual check-in of attendees
This enables manual check-in of attendees. The post-code was heavily
copied from the APIRedeemView of the pretixdroid, thus so far this seems
to be working, but I have a few questions:
The checkin-Objects generated by the pretixdroid-app have a nonce.
Should the checkin object generated here have a nonce, too?
Should the result of the check-in be noted in any other way than by the
change of the status?
* addressed review comments
* implement unit test for manual checkin
* fix style-issues
* Slight layout change
* Log who did the manual check-in
* Improve unit test to check the result of the action
