Bugfix release 2025.7.1 of pretix

On Wednesday (2025-08-20) we released pretix 2025.7.0. Unfortunately, the migration of data in 2025.7.0 contained a critical bug that could cause data loss.

Specifically, after the migration, some events have lost their event-specific settings. We have removed the release 2025.7.0 from the PyPI and Docker Hub servers and published 2025.7.1 instead which does not contain the bug. Customers of pretix Hosted are not affected by the issue.

If you have already upgraded to 2025.7.0 between Wednesday and today, please verify if you are affected.

If you use redis, and do not have a current backup of your pretix database from before the update, we recommend to save a copy of your redis cache before you continue, as you might be able to recover data from the cache. You can use one of the below methods to dump the cache:

redis-cli SAVE
redis-cli CONFIG GET dir
# copy dump.db from directory returned by last command

# or
for key in $(redis-cli KEYS "*hierarkey*"); do echo -n "$key ";  redis-cli DUMP "$key" | base64 -w 0 ; echo ; done > redis_hierarkey_dump.txt

After that, to be able to verify if you are affected, we recommend to clear the settings cache (if using redis):

redis-cli KEYS "*hierarkey*" | xargs redis-cli DEL

Then, check if all your events have still the correct settings in place.

If they don't, we recommend to restore the database tables pretixbase_event_settingsstore and pretixbase_organizer_settingsstore to the latest backup you have from before the upgrade. As these tables are not referred to by other tables, restoring them individually is possible.

To do so, first delete the tables entirely:

TRUNCATE pretixbase_event_settingsstore;
TRUNCATE pretixbase_organizer_settingsstore;

If you use pg_dump for creating your backups as .sql files, you can open the SQL file in a text editor and delete everything except the blocks that look like this:

--
-- Data for Name: pretixbase_event_settingsstore; Type: TABLE DATA; Schema: public; Owner: pretix
--

COPY public.pretixbase_event_settingsstore (id, key, value, object_id) FROM stdin;
…
\.

and

--
-- Data for Name: pretixbase_organizer_settingsstore; Type: TABLE DATA; Schema: public; Owner: pretix
--

COPY public.pretixbase_organizer_settingsstore (id, key, value, object_id) FROM stdin;
…
\.

Then, load the SQL file with psql.

When restoring with a pg_restore format, use the the options like this:

pg_restore --data-only -t pretixbase_organizer_settingsstore -t pretixbase_event_settingsstore --verbose -d DATABASE_NAME < backup_file.dump

After the restore, clear your settings cache again:

redis-cli KEYS "*hierarkey*" | xargs redis-cli DEL

In addition to the bug mentioned above, the release 2025.7.1 also fixes one minor display issue in the new organizer-level plugin feature released in 2025.7.0.

We apologize deeply for this incident. We are reviewing our internal processes to figure out how this bug slipped through during testing. If you have any questions, please let us know.

Special thanks go out to Felix Schäfer who noticed the issue and was an excellent help during debugging.