0.6.0 2018-05-06

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] New plugin hook: pretalx.submission.signals.submission_state_change will trigger on any state change by a submission.

  • [Feature] The frab compatible XML now uses UUIDs, and includes an XML comment with a pretalx version string.

  • [Feature] pretalx has a better general look and feel and colour scheme.

  • [Feature] Organisers can make more changes to speaker profiles and submissions to ease event administration.

  • [Feature] pretalx now has a concept of organisers and teams.

  • [Feature] To avoid running into issues when uploading custom CSS, and ensuring smooth operations, custom colours and CSS is not used in the organiser area anymore.

  • [Feature] You can now send mails from templates and use shortcuts from submissions to send mails to specific speakers.

  • [Feature] Since different events have different needs, organisers can now choose if speakers have to provide submission abstracts, descriptions, and speaker biographies during the CfP.

  • [Fixed bug] Speakers could see their submission in the organiser backend, but could access no information they did not put there themselves. (#375)

  • [Fixed bug] The API showed talks to organisers if no schedule was present yet. It did not show the information to unauthorised users.

  • [Fixed bug] There was no possibility to reset a user’s API token.

  • [Fixed bug] If an organiser changed a speaker’s email address, they could assign an address already in use in the pretalx instance, resulting in buggy behaviour all around.