* standardize use of check-in
* split on occurrence of "checkin_*"
Instead of skipping when encountering "checkin_*", we now split and only
pass the second part to the spell-checker. This fixes the aforementioned
problem.
* fix spelling issue with checkins
* [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
* mention CoC in README.md
According to the discussion in #689, the Code of Conduct gets directly
referenced in the README-file, instead of linking to the
CODE_OF_CONDUCT-file
* undo whitespace-change
* 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
* [WIP] Failed Payment error handling
When finished, this should fix#248
* rename PaymentFailedException to PaymentException\nimported Exception where neccessary
* comments fixed
* minor style fixes
* Fixed a name error
