Release 1.16.0 of pretix
Today, we are releasing the next monthly release of pretix. pretix 1.16 is one of the releases where we don't put out many large features, put polish lots of corners everywhere and are busy preparing some larger news in the background. There's still more than enough reason to upgrade! Big thanks go out to etiontdn, Felix Rindt, Jakob Schnell, Jochem van Kessel, Lorenzo Peña, luto, Maarten van den Berg, Maarten Visscher, Mason Mohkami, Mikkel Ricky, Pernille Thorsen, Pieter Roziers, robbi5, Sebastian Wallroth, and Wallaber Pinheiro, who contributed to this release. ❤️
pretix 1.16.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.
Multiple ticket designs
Starting with this version, you can not only have one single design for all your tickets, but you can create multiple layouts and then assign the layouts to your various products. This will come in useful if you have a range of widely varying products that should have visibly distinct ticket layouts.
OAuth support and new REST API features
We've got great news for everyone who wants to integrate their web service with our pretix API: You can now request access to an user's pretix account using OAuth2, removing any need to manually copy and paste API keys around. We're looking forward to the great applications you will build with and around pretix!
Our REST API has also been improved in other places (see below), but we've now added the one thing you've always asked for: It is now finally possible to create orders through the API, at least for the most common purposes.
Smaller changes and bugfixes
-
The Dutch language is now enabled.
-
An "original price" can now be set for products to show an explicit discount.
-
A bug leading to accidental deletion of PDF files has been fixed; affected files will automatically be regenerated.
-
Multiple crashes have been fixed that occur when a payment provider is disabled that has already been used.
-
Tickets can now show a second QR code with a pseudonymous "Lead Scanning ID" that can be used to integrate with Lead Scanning services (stay tuned for more info soon!).
-
Event organizers can now accept payments manually even if an event is sold out or all deadlines are over.
-
The default ordering of dates in an event series is now configurable.
-
The list of orders as well as the check-in list can now be searched for ticket secrets.
-
It is now possible to regenerate the ticket secret of a single ticket.
-
A faulty dependency specification has been fixed.
-
A display error in showing the paid tickets in the list of event has been fixed.
-
Serving of large files has been improved.
-
Long event names are now automatically shortened for invoices.
-
Consenting to confirm messages (i.e. terms of service) is now explicitly logged with timestamp.
-
The list of dates in an event series can now be filtered by weekday.
-
Dates in an event series can now be deleted in bulk.
-
Accessibility has been improved for screenreader users.
-
It is now possible to ask for only the name of the customer, not the full address.
-
Products and categories can now have "internal names" that are shown only in the backend, but not to ticket customers.
-
Some untranslated labels and error messages have been fixed.
-
An error message is now being shown if an event slug of more than 16 characters is chosen.
Updates to official plugins and tools
-
pretixdesk has been release in version 0.3.3 and can now show the add-ons that are booked for a scanned ticket.
-
The plugin versions pretix-wirecard 0.6.1, pretix-bounces 1.0.1, pretix-cartshare 1.3, pretix-newsletter-ml 1.2.1, pretix-pages 1.2.3, and pretix-servicefees 1.0.1 have been released to feature Dutch translation.
-
The pretix Enterprise plugin pretix-shipping has been released in a new stable version for compatibility with the new ticket PDF rendering.
-
The pretix Enterprise plugins pretix-campaigns, pretix-slack, and pretix-tracking have been released in a new stable version to feature Dutch translation.
REST API changes
-
Orders now have a
last_modified
property that can be used to only retrieve changed order from the API. -
It is now possible to create orders with the API (with some caveats).
-
Order positions have two new fields available:
pseudonymization_id
andpdf_data
. -
You can now mark orders as refunded through the API.
-
Many API endpoints now support conditional fetching.
-
The fields
internal_name
andoriginal_price
have been added to the Item resource. -
APIs for badge layouts and ticket layouts have been added.