0.2.0 2017-12-01

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] E-mails are now sent with a multipart/HTML version, featuring the mail’s text in a box, styled with the event’s primary colour. (#159)

  • [Feature] You can now choose to hide the public schedule (including talk pages and speaker pages, but excluding feedback pages and the schedule XML export) (#126)

  • [Feature] pretalx validates mail template placeholders, and prevents organisers from saving templates including invalid placeholders. (#215)

  • [Feature] You can now ask questions that take an uploaded file as an answer. (#208)

  • [Feature] Speakers can now upload files which will be visible on their talk page. (#209)

  • [Feature] , [Feature] The review interface has been rewritten to include fewer pages with more information relevant to the user, dependent on event stages and their role in the event. (#210)

  • [Feature] pretalx can now run with celery (an asynchronous task scheduler) for long running tasks and tasks like email sending. The new config section is part of our documentation. (#38)

  • [Feature] The new rebuild command will recompile all static assets.

  • [Feature] Question answers now receive a nice evaluation, aggregating all given answers. (#207)

  • [Feature] Organisers can mark questions as “answers contain personal data”. When users delete their accounts, they also delete answers of these questions. (#233)

  • [Feature] We moved to a new permission system that allows for more flexible roles. Please report any bugs that may relate to incorrect permissions. (#78)

  • [Feature] You can now configure a custom domain to use with your event, in case you have an event specific domain for each of your events. (#171)

  • [Feature] You can assign “override votes” to reviewers, which function like vetoes (both positive and negative), on an individual basis. (#156)

  • [Feature] The new read-only REST API supports resources for events and submissions.

  • [Fixed bug] The default value for email SSL usage is now False, permitting the default configuration of localhost:25 to work on more machines out of the box.

  • [Fixed bug] pretalx crashed with incorrect invite keys, now it shows a 404 page. (#304)

  • [Fixed bug] When building absolute URLs for exports, emails, and RSS feeds, pretalx used “localhost” instead of the actual configured URL.

  • [Fixed bug] If a user was both an organiser member and a reviewer, they could encounter access rights issues.

  • [Fixed bug] When removing the custom event colour, and then adding it again, caching issues could occur.

  • [Fixed bug] Inactive questions (questions not visible to speakers) were not editable.

  • [Fixed bug] The event stage display could show conflicting phases as active.

  • [Fixed bug] The default submission type was not, in fact, suggested by default. (#287)