Release 4.7.0 of pretix

Today's release is a maintenance release, fixing lots of bugs and improving on smaller features throughout the system. Big new features will be arriving next again soon!

Big thanks go to cpoisnel, Emanuele Signoretta, Felix Schäfer, Ismael Menéndez Fernández, Jonathan Weth, Jozsef Ebenspanger, kackey621, Maico Timmerman, MaLund13, Marco Giacopuzzi, Matthias Brück, Mauro Amico, and Miguel Magalhães who contributed to this release. ❤️

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

Smaller changes and bugfixes

Ticket shop and widget

• We've added a new section to the event email settings that allows you to put additional content in calendar invite files sent by pretix.

• We've fixed more edge case issues with self-service changing of add-on products.

• A bug has been fixed that caused internal product names to be shown to customers.

• A bug has been fixed that caused reply-to email addresses not to be used correctly.

• A bug preventing to load the widget in Internet Explorer has been fixed. Be aware that we'll stop caring about Internet Explorer bugs in a few months!

• We've added some basic validation on name fields, no longer allowing e.g. URLs in names to prevent common spam attacks.

• The standalone registration of new customer accounts independent of an actual order now features a very minimal CAPTCHA to prevent attraction of automated spam bots in search of contact forms.

• The placeholder name_for_salutation can now be used in customer account registration mail templates.

• A bug has been fixed that caused incorrect localization of names in customer account registration mails.

• A bug has been fixed that caused order confirmation mails not being sent to attendees if no order email address was set.

• A bug has been fixed that caused minimum distance between seats being handled inconsistently for some specific values.

• A style bug in the cookie consent dialog has been fixed.

• Possibly incorrect ordering of add-on products in email footers has been fixed.

Ticketing backend and configuration

• The product list now shows internal names of categories, not public names.

• The order data export now includes ticket secrets.

• When sending mass emails, you can now attach ticket files.

• Bulk-creation of more than 500 vouchers on MySQL-based setups has been fixed.

• You can now use the personal data shredder immediately after an event ended.

• Prices of variations are now shown with correct number formatting in the variation editor.

• It is no longer possible to set the maximum or minimum number a product may appear in an order to negative values.

• A bug has been fixed that prevented switching seating plans in more cases than really necessary.

• A bug has been fixed that prevented bulk-deletion of vouchers in some cases.

• Voucher tags with the same letters but different capitalization are now handled consistently.

• A bug has been fixed that caused the date picker to be shown behind the map controls when creating a new event.

• Restricted plugins can now be enabled and disabled by regular users, but need to be white-listed in organizer settings by a system administrator.

Runtime and server environment

No changes.

Updates to official plugins and tools

• pretix 4.7.0 adds compatibility with new features in pretixPOS 3.0.x.

• The BitPay plugin has been released in version 1.4.2 to allow customizing the public name of the payment method.

• The COVID Certificates plugin has been released in version 2.1.0 to allow disabling to store results and allow to customize the list of allowed vaccines.

• The pretixPOS backend plugin has been released in version 2.6.0 to support new features introduced in pretixPOS 3.0.0.

• The Tracking plugin has been released in version 2.3.2 to fix some CSP-related issues.

Plugin API changes

• Following this discussion a change has been made to how external authentication backends should create and fetch users in the database to reduce security risks. If you maintain such a plugin, please adjust it as soon as possible. The documentation has been updated and this PR shows typical changes required to a plugin.

• Receivers of the register_data_exporters signal are now allowed to return None.

REST API changes

• You can now submit require_approval when creating new orders through the API.

• You can now set send_email to null when creating new orders through the API to have email sending dependent on the event's default settings.

• A bug has been fixed that prevented passing required_membership_types directly when creating new items.