1.1.0 2019-12-21

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 reduce scroll wheel abrasions, pretalx schedules are now tabbed with one tab per event day.

  • [Feature] pretalx has learned what breaks are. Organisers can create those in the schedule editor, and they will be shown in an appropriately muted way in the schedule. (#242)

  • [Feature] If you want to display your schedule on your own homepage, pretalx now offers you a schedule widget. You can generate the code for the widget in your organiser settings.

  • [Fixed bug] Deleted talks could still be shown with their previous title and speaker. Now they are always replaced with a box saying “[deleted]” with no further information. (#828)

Call for Papers

  • [Feature] Questions of the type “choose one from a list” are now shown as a list of radio input options instead of a single drop-down, if there are three or less options to choose from. (#814)

  • [Feature] Organisers can create access tokens that allow users to submit after the CfP deadline, or that give access to hidden tracks or submission types. (#324)

  • [Fixed bug] pretalx would show an error when users were asked to select their submission’s track during the CfP workflow.

Organiser backend

  • [Feature] pretalx now comes with a CfP editor that allows you to change the headline, text, and help texts on each of the CfP step pages. (#648)

Organiser backend: E-Mails

  • [Feature] Organisers can now send emails to all speakers who have not uploaded slides/files for their talk yet. (#432)

Organiser backend: Session management

  • [Feature] There is now a page that shows all feedback by attendees for any talk in the conference. (#794)

  • [Feature] There is now a CSV export for answered questions. (#792)

  • [Feature] The submission type list and the track list now list the numbers of submissions per entry.

Organiser backend: Review process

  • [Feature] You can now determine if the answers to talk questions should be visible to reviewers. This allows you to ask personal questions of your submitters, even when you are running an anonymous review process. (#638)

Organiser backend: Scheduling

  • [Feature] The static HTML export will now be triggered when talk or speaker data is changed (as long as it’s also generated on schedule release). To protect against high server load, it will still run at most once every hour. (#277)

  • [Fixed bug] Reducing the slot count of a submission where all slots had been scheduled would not remove spare slots. (#816)

API

  • [Feature] Speakers can now see and reset their API token in their profile page. (#760)

Administrators

  • [Feature] pretalx now comes with an update check, which will notify you when new pretalx or plugin versions are available. This check sends anonymous data to the pretalx.com server, which is run by the pretalx developer. The data consist of a random but stable ID, the number of total and public events, and the version of pretalx and all installed plugins. No identifying information will be retained, and there is a visible and persistent opt-out warning until acknowledged by an administrator.

  • [Feature] File attachments generated from user data are now generated to be in safe ASCII range, to avoid trouble with Unicode-sensitive gunicorn versions. (#841)

  • [Feature] pretalx now has pretty error pages for CSRF fails and 400 errors. Test error pages are located at /400, /403, /404, /500, and /403/csrf.

  • [Fixed bug] One broken task among the periodically executed task would prevent others from being executed.

  • [Announcement] We documented the implicit requirement that the filesystem pretalx accesses should work with non-ASCII file names. Please check the installation documentation if you want to make sure this is the case for you.

Developers and plugins

  • [Feature] Plugins can now add content to the top of the user profile pages and the user-private submission lists.

  • [Feature] Plugins can now implement the uninstalled method to perform actions when a user deactivates them for an event.

  • [Feature] pretalx has the new management command create_test_event, which creates a demo event in a stage of your choice (cfp, review, schedule or over). All user accounts are created with @example.org email addresses.

  • [Feature] If pretalx encounters an error it can’t recover from, the error page now shows a link to a partially filled GitHub issue.

  • [Announcement] We have added a couple of pages to the pretalx wiki on GitHub, most importantly a list of events using pretalx, and a list of available plugins. The wiki is world-writable, so please add to it if you have an event or plugin that has not been mentioned yet!