* MKBDIGI-183: Added quotas API write methods
* MKBDIGI-183: Fixed code formatting
* MKBDIGI-183: Added test for permission requirements
* MKBDIGI-183: Documentation corrections
* MKBDIGI-183: Removed redundant create/update locks
* MKBDIGI-183: Added quota validation to check that items and variations corresponds to each other
* MKBDIGI-183: Added quota validation to check that item belong to the same event as the endpoint
* MKBDIGI-183: Added subevent validation to check that subevent belong to the same event as the endpoint
* MKBDIGI-183: Added subevent validation to check that subevent is null for non-series events
* MKBDIGI-183: Changed validation error text
* MKBDIGI-183: Added logging for subevents
* MKBDIGI-183: Fixed code formatting
* MKBDIGI-183: Fixed validation error in API test
* MKBDIGI-183: Fixed documentation errors
* MKBDIGI-183: Fixed typos in validation messages
* MKBDIGI-183: Refactored validation loop vars check
* MKBDIGI-183: Updated error strings in test assersions
* MKBDIGI-183: Fixed logging for API quota update to account changing subevents
* 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.
I think the only "critical" fix here is the change from "Zahlmethoden"
to "Zahlungsmethoden", but that is the word used in the rest of the
translations, so I figured it should be changed here as well.
* [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
