0.4.0 2018-02-04
See the release blog post.
Note
Users of pretalx.com are already on the latest version of pretalx and have access to all of the listed new features and bugfixes. Administrators of self-hosted pretalx instances can find upgrade instructions here.
[Feature] A page in the organiser area lists and links all possible data exports in one export page.
[Feature] You may now import XML files to release a new schedule. (#322)
[Feature] We added a new team management interface to manage all team members and permissions in one place. (#292)
[Feature] The new init command for project setup adds the initial user, but in time it should ask for basic configuration, too.
[Feature] The rebuild command now supports a –clear flag to remove all static assets before rebuilding them.
[Feature] You can choose a pattern for the header hero strip in your event colour.
[Feature] You can now choose different deadlines per submission type, overriding the default deadline. (#320)
[Feature] All forms are instantly editable if you have edit permissions, and disabled otherwise. No more need to click “Edit”! (#325)
[Fixed bug] The schedule export could change project settings, requiring pretalx restart to reset the settings. Turning “Generate HTML export on schedule release” off was a workaround for this bug.
[Fixed bug] When running pretalx as (in-application) superuser, permission issues could arise. pretalx now warns and offers to migrate the account to an administrator account. (#259)
[Fixed bug] Frontend password validation was non-functional, and never displayed interactive password statistics. This was a display issue.
[Fixed bug] We removed the unused max_duration property of submission types. (#327)
[Fixed bug] Users always saw the default submission type instead of their chosen one. (#329)