pretix

Release 1.17.0 of pretix

July 8, 2018

Today, we are releasing the next monthly release of pretix. pretix 1.17 again is a mini-release with only a few number of changes, as we're preparing a big change to the way payments work for next month. Big thanks go out to Dimas Rivas, Pernille Thorsen, and Tobias Kunze, who contributed to this release. ❤️

pretix 1.17.0 is now available for installation via pip. The new docker images will appear on Docker Hub over the next few hours. All customers of pretix Hosted are already using the new version and do not need to take any action.

Manual payments

We've added a new core plugin, called "Manual payments". This adds a payment method that you can configure all on your own to match your specific process if you want to process payments manually, e.g. in cash in advance or via an external invoicing service. You can specify how the payment method should be called in the checkout process and you can add your own texts that will be shown to the customer during checkout.

Smaller changes and bugfixes

  • You can now enter a minimum/maximum amount for most payment providers.

  • You can now specify an email address that should receive all outgoing emails in Bcc.

  • A P3P header is now set to prevent problems in Internet Explorer.

  • In the pretix widget, the text "FREE" is now hidden if there is exactly one product and it is free.

  • A bug with changing answers to file-upload questions has been fixed.

  • The check-in list CSV export now always contains email addresses.

  • The check-in list CSV export can now be configured to use Excel's CSV dialect.

  • Badges can now be sorted by last name of attendee.

  • An error has been fixed that lead to download reminders being sent in wrong languages.

  • Links in item descriptions are now again working.

  • Duplicate [] in email prefixes are now prevented.

  • Problems have been solved that occur when a payment provider has been used and the respective plugin is them removed.

Updates to official plugins and tools

REST API changes

  • Creation and deletion of cart positions is now possible through the API.

  • When creating orders you can now specify carts that should be used for quota calculation and then "consumed". Additionally, error messages of this endpoint are now more specific and consistent.

Read more blog posts