2.0.0 2020-12-24

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] Instead of being unsorted as before, the list of talks on the schedule page is now sorted alphabetically. (#934)

• [Feature] Organisers can now choose how to display their schedule. Currently, the only two options are the previous grid display, or a list with talks and times.

• [Announcement] Pretalx has a new schedule, with a new widget. The old widget is deprecated and will be removed in the next release. Please migrate all of your widgets to the new widget code. You can generate it in your event’s settings.

Call for Papers

• [Feature] pretalx now limits file uploads to 10MB.

• [Feature] Tracks now have a description attached to them which is shown to the user in the CfP, if specified. This can be used to further explain an otherwise very short track name. (#915)

• [Feature] Questions can now be limited by submission type.

• [Feature] The help text for questions can now be 800 characters long instead of 200.

• [Fixed bug] It was not possible to hide a submission type unless accessed with an access token. (Or, well, it was possible, but the possibility was hidden.)

• [Fixed bug] The frontend markdown preview would not render all line breaks as line breaks (only two line breaks in a row), but the server rendered version did. (#877)

Organiser backend

• [Feature] pretalx now shows the complete history of logged changes to organisers.

• [Feature] pretalx now prevents you from creating multiple tracks or submission types with the same name. (#907)

• [Feature] If you go to a login page while you are logged in (e.g. because it was still open in another tab), you are now redirected instead of being prompted to log in.

• [Feature] Now, event organisers can activate and deactivate plugins for their events. Previously this was restricted to administrators.

• [Feature] The submission statistics now ignore deleted submissions. (#880)

• [Feature] If you create a new event and copy an old event’s configuration, pretalx will now also copy tracks and questions. (#873)

• [Fixed bug] The link to the team settings on the review settings page was incorrect. (#951)

• [Fixed bug] When updating the settings for an event with a custom domain, pretalx would mistakenly show an error message that this domain was already in use for another event.

Organiser backend: E-Mails

• [Feature] When you send out reminders about unanswered questions, you can now target specific questions, or tracks, or submission types.

• [Feature] Schedule notifications for speakers are now properly connected to the speaker accounts, instead of just referencing them by email addresses.

• [Fixed bug] Using custom mail servers worked, but testing the connection in the settings page showed an error (incorrectly).

• [Fixed bug] If incorrect variables were used in the schedule update email template, pretalx did not catch this mistake ahead of time, and instead just refused to release a new schedule. (#863)

Organiser backend: Speaker management

• [Feature] The filtered list of speakers in the organiser area now contains only people with confirmed or accepted talks, and is also better at showing the filter currently applied. (#855)

Organiser backend: Session management

• [Feature] You can now filter the submission list by specific question answers. (#882)

• [Feature] People without edit or delete permissions are not shown the edit or delete buttons on submissions anymore.

Organiser backend: Review process

• [Feature] Reviewers can now tag reviews while reviewing, and later filter for those tags.

• [Feature] Reviewers can now be asked to rate a proposal in several categories, with a total score calculated automatically.

• [Feature] In addition to anonymising proposals, you can now also anonymise reviewers towards other reviewers.

• [Feature] Questions that are visible to reviewers now also show up on the review page, to avoid having to switch to the full submission view in the review process.

• [Feature] Organisers can now anonymise submission content for reviewers, if they choose to do anonymised reviews. They can redact or edit any part of the submission for the reviewers’ view of it to remove identifying information.

• [Feature] Review scores are now consistently shown as numbers, and the text representation/meaning of those numbers is shown on hover.

• [Feature] Reviewers can now see both their own score and the median score in the review dashboard.

• [Fixed bug] In some settings combinations, reviewers were unable to change or even see their own reviews after submitting them. (#923)

• [Fixed bug] Firefox has a bug in their form caching. If you reviewed a submission, clicked “Save and next”, then went back and reloaded the page, Firefox would incorrectly fill your review form with the choice one point worse than your original selection. If you then chose “Save and next” again, this value would be saved.

• [Announcement] The essentially unused override score feature has been removed.

Organiser backend: Scheduling

• [Feature] In the schedule editor, you can now search for talks by speaker name. (#979)

• [Feature] Organisers can now leave a public comment when they release a new schedule. It will be visible in the changelog and the schedule RSS feed. (#772)

• [Feature] If you move your event dates, the schedule is moved too, and you can send notifications to your speakers by releasing a new schedule version.

API

• [Feature] There are two new API endpoints, /questions/ and /answers/, that incidentally are our first writable API endpoints. The API docs have been updated.

• [Feature] In the API, the event list is now sorted so that the oldest event comes last, not first as it was before.

• [Fixed bug] Reviewers had access to question answers that were not explicitly visible to reviewers by way of the API. (#928)

• [Fixed bug] The submission API returned a duration in formatted time, like “00:30”, but the API documentation claimed it was a number of minutes. pretalx now returns the number of minutes as promised. (#936)

Languages and translations

• [Feature] In all exporters, you can now select the export language with the ?lang= query parameter. If you don’t supply the parameter, pretalx will continue to guess your locale as before. If you provide the parameter without a value, the default event locale will be used. (#947)

• [Feature] If your event has only a single language configured, pretalx won’t show the language flag in the input fields anymore.

• [Feature] pretalx now comes with an updated French translation, and a brand new Chinese community translation!

• [Fixed bug] Internationalised strings were not always shown as such in the API, sometimes they were instead returned as plain strings. (#945)

• [Announcement] To make translation contributions more accessible, you can now improve translations (or add new ones!) at translate.pretalx.com

General

• [Feature] A lot of minor UI improvements, a re-work of the colours and fonts in use, as well as improvements of mobile and responsive pages.

Administrators

• [Feature] Email error reporting (sent to instance administrators) now includes a short explanation and a link to the pretalx issue tracker.

• [Feature] pretalx will no longer make alarmist noises about missing migrations.

• [Feature] Redirects to an event domain now include CORS headers to permit access from any client, to make pretalx integration in other websites easier.

• [Feature] Administrators can now configure static and media files to be under different URLs than static and media. (#830)

• [Fixed bug] Under specific circumstances, the django_sessions table could bloat a lot. This is fixed with the next release and the table will shrink over time as long as you regularly run the clearsessions command.

• [Announcement] Remember to check your access logs before upgrading to v2.1 to warn users about failing widgets.

• [Announcement] This version of pretalx has higher database version requirements. We now support PostgreSQL 9.6+, MariaDB 10.1+, MySQL 5.6+, and SQLite 3.8.3+.

Developers and plugins

• [Feature] Exporters can now supply the CORS header they want to send. All exporters provided by pretalx directly now allow access from all origins by default.

• [Feature] Plugin developers can now add content to the HTML head area with the new pretalx.cfp.signals.html_head signal.

• [Feature] The test event creation command now allows you to specify the event slug. This allows you to generate multiple test events in various event stages.

• [Feature] The new signal pretalx.common.signals.activitylog_display allows plugins to change how entries in the pretalx activity log are displayed.

• [Feature] The new signal pretalx.orga.signals.event_copy_data allows plugins to transfer data from one event to the next at event creation time.

• [Fixed bug] A bug in our permission checks made pretalx unable to run on Windows.

• [Announcement] If you have a plugin that listens to the footer_link signal, please change it so that it returns a list of dictionaries instead of a single dictionary. The dictionary-only return value is deprecated and support will be removed in a future pretalx version.