2.3.0 2021-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] Pretalx now remembers the timezone you have selected on the schedule page across reloads.
[Feature] Schedules have better scroll behaviour on very wide and very narrow displays.
[Feature] Organisers can now disable audience feedback. (#1171)
[Feature] You can now link to specific days on the schedule again, as with our old schedule. The link is generated when you click the tabs leading to specific days. (#1163)
[Feature] If you attach ?lang=en to a request, pretalx will serve the page in the requested language (if active in the current event).
[Feature] On session detail pages, the event timezone is now noted next to the time.
[Fixed bug] Session detail pages did not use the full width of the page.
Call for Papers
[Feature] If you run a multi-lingual event, you don’t have to request the content locale in your CfP anymore.
Organiser backend
[Feature] Plugin selection is now available for all organisers, not just administrators.
[Fixed bug] When adding a new organisers to a team, email suggestions from known users did not work. (#1157)
Organiser backend: E-Mails
[Feature] Email signatures now look a lot better in HTML emails
[Feature] pretalx finally supports sending of emails based on templates, with a full template placeholder system. Hello, {name}! (#412)
[Feature] Email filters are now subtractive instead of additive, giving you more fine-grained control about your bulk emails. (#715)
[Fixed bug] Fixed an issue when rendering individual session times in emails.
[Fixed bug] pretalx now does not allow you to test your custom SMTP settings until you have actually configured them. (#1150)
Organiser backend: Session management
[Feature] Thanks to the new “pending state” feature, organisers and reviewers can mark proposals as accepted/rejected without letting speakers see the decision yet. (#667)
[Fixed bug] When adding a new speaker to a proposal, pretalx would suggest organiser accounts rather than speaker accounts. (#1157)
Organiser backend: Review process
[Feature] Tags are now shown in the reviewer dashboard and can be filtered for.
[Feature] Improved the tagging interface to be still useful with a large number of tags. (#976)
[Feature] Anonymisation for reviewers can now be switched on on a team level, overriding the general event settings.
[Fixed bug] Fixed a bug where abstaining during the review process was not possible while review scores were mandatory.
Organiser backend: Scheduling
[Feature] The schedule editor now polls changes, so if somebody else changes the schedule while you’re editing it, you will see the changes soon afterwards.
[Feature] Pretalx will now highlight overlapping sessions on the schedule editor, and will also warn you before you release a new schedule if sessions overlap in the same room.
[Feature] You can now change a session’s room and time in the session form, allowing for minute-level accuracy instead of our usual 5-minute intervals. (#933)
[Feature] As a reminder, the event timezone will be shown at the top of the schedule editor page.
[Fixed bug] When you clicked a talk in the schedule editor, it would open in a new window, but also stay in dragging mode in the editor page.
API
[Feature] You can filter submissions by multiple states in the API now. (#1232)
Languages and translations
[Feature] pretalx now comes with new translations, in Arabic, Spanish, and Brazilian Portuguese!
Administrators
[Feature] Media files are now excluded from crawlers via robots.txt.
[Announcement] When updating, please take care to update your plugins, as some interfaces have changed. Plugin authors, please refer to PR 1230 to see changed settings access.
Developers and plugins
[Feature] Plugin languages can now be either globally available or only for active events – plugin developers, please adjust your plugins!
[Feature] Plugins can now perform actions on every schedule release (for example, to trigger an update in external consumers to avoid polling).
[Feature] There is a new plugin hook that allows you to perform actions when a new schedule is released.