2.2.0 2021-08-15

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.

Schedule

  • [Feature] To improve performance, the NoJS schedule is now located on a separate page.

  • [Feature] Event header images are now scaled down to a height of 150px. (#1082)

  • [Feature] pretalx has better rendering for multi-line code blocks (\`\`\`) in markdown elements and supports code highlighting.

  • [Feature] The talk feedback page is now available once a talk has started, not once it is over. (#1036)

  • [Fixed bug] The display of external videos in pretalx was broken due to a security header being set too strictly.

  • [Fixed bug] Sessions without speakers were displayed weirdly in the “featured sessions” page.

  • [Fixed bug] The display of large talk images was off, extending them too far to the right.

  • [Fixed bug] The HTML export did not work with the new schedule page.

Call for Papers

  • [Feature] You can freeze a question after a certain date, prohibiting users from changing their answers after the deadline. (#1069)

  • [Feature] You can now attach deadlines to questions, making them optional before the deadline and mandatory afterwards. (#1069)

  • [Feature] The availability widget now shows day names in your locale instead of always using English.

  • [Feature] pretalx will resize uploaded images down to 1920x1080 (by default).

  • [Feature] pretalx now removes EXIF metadata from all uploaded images.

  • [Fixed bug] In the CfP editor, when a step description was only given in a language that was not currently active, you could not change it any longer.

  • [Fixed bug] When your default submission type had a deadline prior to the event-wide deadline, the CfP form would not accept new proposals past the earlier deadline.

  • [Fixed bug] If you used links to fill in parts of the CfP form, you sometimes could not get part the first page. (#1023)

Organiser backend

  • [Feature] If you use custom domains, pretalx will automatically redirect the domain to the most recent event that uses this domain. This also means that you can configure multiple events with the same custom domain!

  • [Feature] Organisers can now create custom proposal and speaker exports (as either CSV or JSON), including any data they need. (#313)

  • [Feature] Added a password reset link to the page where you accept invitations to organiser teams. (#1048)

  • [Fixed bug] The statistics page did not work for events with just a single submission type.

Organiser backend: E-Mails

  • [Feature] To prevent emails getting recorded as spam, the custom sender address is now only used when you are using a custom email server. You can still set the reply-to address.

  • [Feature] In addition to sending either all emails or a single email, organisers can now also send only the currently selected emails. This is particularly helpful with an email provider (cough google) who starts rejecting emails when bulk-sending, halfway through your sending process.

  • [Fixed bug] pretalx would send multiple emails for proposals with multiple speakers. (#1111)

  • [Fixed bug] pretalx sometimes over-reported the number of emails generated when bulk-sending emails. (#1093)

Organiser backend: Speaker management

  • [Feature] You can now search speakers by specific given answers, as you could already search proposals and sessions.

  • [Feature] Speaker information will now be copied when cloning an event.

  • [Feature] Speaker information can now be created for specific tracks or proposal types.

Organiser backend: Session management

  • [Feature] You can now get a list of proposals or speakers that are still missing the answer to a given question. (#1092)

  • [Feature] The review statistics timeline chart now includes the total submitted proposals to the given date, in addition to the proposals submitted on the given date. (#1047)

  • [Fixed bug] When you created a session as organiser, you could choose a content language that was not supposed to be available in the active event.

  • [Fixed bug] The tag creation page is now hidden for users who don’t have permission to create tags. (#1049)

Organiser backend: Review process

  • [Feature] You can now choose if you want to compare the median of review scores or the average/mean. (#656)

  • [Feature] You can mark review score categories as independent. They won’t be part of the total calculation, and instead show up as their own column in the review dashboard.

  • [Feature] In the review dashboard, you can now filter the list of proposals by how many reviews they have.

  • [Fixed bug] Not all existing review scores were recalculated when review score weights were changed during a review phase.

  • [Fixed bug] Reviewers without further permissions could not create tags, even when they had the necessary permissions. (#1049)

  • [Fixed bug] Improved review interface so that long or complex scores don’t break the interface when editing an existing review.

Organiser backend: Scheduling

  • [Feature] You can now filter talks by track and type in the schedule editor. (#735)

  • [Feature] Room availabilities are now more fine-grained, you can set them on a 15-minute basis instead of 30-minutes as before.

  • [Fixed bug] pretalx would sometimes show unnecessary warnings in the talk editor when talks were scheduled across day breaks. (#1087)

  • [Fixed bug] A bug led to the first schedule release of every event being empty, sometimes, since all talks were treated as unconfirmed.

API

  • [Feature] With the anon query parameter, you can request anonymised proposal data from the API, even when you have permission to see the full data.

  • [Feature] Tags are now exposed in the API.

  • [Fixed bug] In the submission API view, the end time of a slot was sometimes empty.

  • [Fixed bug] The API would return errors in some edge cases when used by unauthenticated users.

Administrators

  • [Feature] pretalx will no longer send emails to localhost addresses, as those are used for deleted users. Please get in touch if this is a problem for you.

  • [Feature] If you run pretalx with --no-pretalx-information, it will not print the pretalx information header.

  • [Feature] You can now use the --silent flag with the regenerate_css command to reduce build verbosity.

  • [Announcement] If you use PostgreSQL, please make sure to be on at least PostgreSQL 10.

Developers and plugins

  • [Feature] On self-hosted pretalx instances, you can now configure pretalx to include additional CSP headers, especially of interest for plugin developers. (#1143)

  • [Feature] The event activation signal can now return a string to be shown as success message.