Bugfix release 1.10.1

The current stable release 1.10.0 contained a few little errors that we fix in this follow-up release 1.10.1. In particular:

• In emails for orders paid via bank transfer, the banking information was formatted incorrectly.

• Question answers attached to add-on products have not been saved correctly.

• Login with an U2F device is now compatible with the U2F implementation of Firefox 57.

• Sorting the list of events, orders, dates or organizers was only possible for ascending values, not for descending.

• A change in the Dockerfile was made to work around a problem with reportlab 3.4.0.

• The list of check-in lists was displayed incorrectly if a check-in list was limited to multiple products.

• The dependencies celery and kombu are now upgraded to version 4.1.0 to mitigate a compatibility issue with Python 3.6.

• A bug in the documentation of docker installs has been fixed. If you are using a docker-based setup based on that documentation, please make sure you read the section below.

pretix 1.10.1 is now available for installation via pip. The new docker images will appear on Docker Hub over the next few hours. We apologize for any caused inconvenience.

Documentation bug in the Docker installation tutorial

The tutorial "Small-scale deployment with Docker" contained an error in the recommended layout of the service file. The wrong version looks like this:

[Unit]
Description=pretix
After=docker.service
Requires=docker.service

[Service]
TimeoutStartSec=0
ExecStartPre=-/usr/bin/docker kill %n
ExecStartPre=-/usr/bin/docker rm %n
ExecStart=/usr/bin/docker run --name %n -p 8345:80 \
    -v /var/pretix-data:/data \
    -v /etc/pretix:/etc/pretix \
    -v /var/run/redis:/var/run/redis \
    -v /var/run/mysqld:/var/run/mysqld \
    pretix/standalone all
ExecStop=/usr/bin/docker stop %n

[Install]
WantedBy=multi-user.target

The correct version looks like this:

[Unit]
Description=pretix
After=docker.service
Requires=docker.service

[Service]
TimeoutStartSec=0
ExecStartPre=-/usr/bin/docker kill %n
ExecStartPre=-/usr/bin/docker rm %n
ExecStart=/usr/bin/docker run --name %n -p 8345:80 \
    -v /var/pretix-data:/data \
    -v /etc/pretix:/etc/pretix \
    -v /var/run/redis:/var/run/redis \
    -v /var/run/mysqld:/var/run/mysqld \
    pretix/standalone:stable all
ExecStop=/usr/bin/docker stop %n

[Install]
WantedBy=multi-user.target

The difference is in the pretix/standalone:stable all line that previously missed the :stable tag specifier. Therefore, even though the tutorial recommended to execute docker pull pretix/standalone:stable beforehand, Docker would apparently download the latest build of pretix' master branch and starting this container. You can check your installed version at https://my-pretix-domain.example.com/control/global/update/. If this shows 1.11.0.dev0 instead of 1.10.0, you are affected by this problem.

Our master branch as of today is currently considered to be relatively stable and also fixes the bugs listed above, so this is not directly a problem. We are strongly recommending not to try to downgrade, as it might give you problems with conflicting versions of the database schema. Instead, we suggest that you follow the following path to get back into the stable release cycle:

• Download to the image of the master branch as of today by executing docker pull pretix/standalone@sha256:04c15d3b668fe865d4a6adf0fcaa871a001de02128d25e084db2bc473c6846f9

• Pin this version by changing the line in the service file to pretix/standalone@sha256:04c15d3b668fe865d4a6adf0fcaa871a001de02128d25e084db2bc473c6846f9 all

• Restart pretix.service to upgrade to that version (systemctl restart pretix.service).

• Execute docker exec -it pretix.service pretix upgrade.

• Once pretix 1.11.0 is release (early January), change the line in the service file to pretix/standalone:stable and follow the usual upgrade procedure.

If you are using a custom Dockerfile, i.e. to install additional plugins, all of this applies to the FROM: line of your Dockerfile instead of the service file. If you already had the :stable tag there, you should not be affected.