:support:`-` A new pretalx plugin adds media.ccc.de as a recording provider – this plugin replaces the previously inbuilt capacity of pretalx to provide recording iframes. (This functionality was never directly exposed and only accessible via the pretalx shell. It is now deprecated and will be removed in a later version.)
:feature:`-` Plugins can now provide recording iframes (via the new register_recording_provider signal and other mixins).
:feature:`-` The new nav_event_settings plugin signal allows plugins to integrate their own settings pages next to the pretalx core pages.
:feature:`-` pretalx now presents a colorpicker for your event primary color, including a hint on color suitability.
:feature:`-` The new /api/me endpoint shows name, email address, locale, and timezone of the logged in user.
:feature:`-` The nav_event plugin signal has changed to expect a list instead of a dictionary response. The dictionary response will be supported for one more version, and raises a deprecation warning.
:feature:`-` The API now provides a /rooms endpoint – this endpoint is public, so upgrading will publish which rooms you have configured in your conferences!
🐛`529` When trying to review their own submission, a user would see a 404 not found error instead of an explanation that this was a forbidden action.
🐛`-` The password reset form told users if they had already tried to reset their password in the last 24 hours. While this is helpful, it also allows user discovery via password reset. Instead, the user now sees a more generic message.
:feature:`-` While filling out the submission form wizard, submitters see a top bar telling them where they are in the submission process.
🐛`-` The event dashboard showed a wrong countdown towards the CfP end while the CfP end was between three and one day away.
:feature:`-` The new event dropdown helps you find your event, even if you have access to many events.
🐛`-` The organiser login page did not strip whitespace from login credentials.
🐛`524` Review settings contained the setting "Force data entry" twice, referring to the score and text, respectively.
🐛`522` If a speaker did not check a mandatory checkbox, they could not submit the form (as intended), but could see no feedback explaining the issue.
:feature:`` The rebuild command now comes with a lot more build output for ease of debugging. You can disable the build output with the new --silent/-s flag.
:feature:`476` Administrators can now delete both events and organisers.
:feature:`493` Speaker email addresses are now available via the API for users with access permissions.
🐛`515` Under rare circumstances, the pretalx database could reach a state pretalx couldn't cope with due to duplicate schedule versions.
:feature:`512` You can now configure if speakers should provide their availability during talk submission.
:support:`-` Due to an updated Django version, pretalx has dropped support for PostgreSQL 9.3 and MySQL 5.5.
🐛`-` When a user removed a submission containing an answered choice question, pretalx removed the selected answer option, too.
🐛`501` When a speaker held more than two talks, their related talks did not show up.
🐛`505` Custom CSS may now also include media queries.
🐛`500` Display of times could be off in the static HTML export.
:support:`-` The URLs for schedule exports have changed from /myevent/schedule/export?exporter=exportername to /myevent/schedule/export/exportername – if you have hardcoded links to schedule exporters, please update them accordingly.
:feature:`213` A human-readable time until the CfP closes now shows up next to the end time.
🐛`503` Not all current TLDs did end up included as URLs when processing markdown input to build links.
🐛`-` The schedule import in the organiser backend never worked (while the manage command for administrators did work).
:feature:`454` As an organizer, it's now possible to send an email to all reviewers in the Compose Mail section.
:feature:`492` In exports, HTTP Etags are now supported to allow for more aggressive caching on clients.
🐛`-` If a review question was mandatory while submission questions were active, they would block the submission process.
:feature:`-` Organisers can now also reset the password for the speakers they have access to.
🐛`488` The HTML export contained media files (not other content) from all conferences on an instance, instead of the exported conference.
:feature:`-` Present a public list of talks and a list of speakers.
🐛`478` The behaviour of pressing enter in multi-step forms was unintuitive in some places.
:feature:`-` The submission list now includes a graph of submissions over time.
:feature:`-` You can now see the sneak peek / is_featured flag in the submissions and talk API endpoints.
:feature:`-` You can now use your authentication token to access all pages you have access to, as you already could for the API. This makes integration of exports much easier.
:support:`-` All manage commands available in pretalx are now included in the documentation.
:feature:`240` When using paper cards to build a schedule, each card comes with a QR code link to a quick scheduling form for that submission.
:feature:`-` You can now see warnings and what the public changelog will look like before releasing a new schedule.
:feature:`214` The schedule editor shows warnings on scheduling conflicts, including live feedback on where you can schedule a talk.
:feature:`474` The review dashboard now features the same search and filter options as the submission list.
🐛`473` Following the revamp of team permissions, override votes were missing from the settings. We re-introduced the settings, and improved the general handling of override votes.
:support:`-` pretalx now doesn't support usernames any longer – as all users had to have email addresses already, you will now have to provide an email address to log in. This may confuse users – as an administrator, you can look up users' email addresses if they don't remember them, or change them, if necessary.
🐛`-` You could make questions inactive, but not delete them.
:feature:`408` You can now add length restrictions to abstracts, descriptions, speaker biographies, and all text-based questions.
:feature:`-` When linking to a talk on social media, those pages will show the talk image.
:support:`-` We now have tests to make sure all config options and plugin hooks are part of our documentation.
:feature:`-` Instead of setting a flag somewhere, pretalx now has an explicit "go live" button. Plugins can listen to the corresponding signal (please refer to the plugin documentation for further information).
🐛`463` Don't show a 404 error if a reviewer tries to review their own submission, but show an error message instead.
:feature:`-` For organisers, the submission/talk API endpoints now contain the question answers given by the speakers.
:feature:`-` Schedules now contain a search bar to filter talks by title or speaker.
:feature:`-` Schedules now feature a sidebar navigation to jump directly to a selected day.
:feature:`-` Allow organisers to configure which of the default CfP fields to request and require. Please check your settings after updating, as the migration is not guaranteed to work as expected.
:feature:`415` Allow organisers to trigger a password reset for team members.
🐛`451` Don't crash during pretalx init if no conference organiser slug is present.
🐛`-` The new read-only links for submissions received the same secret token when migrating the database. pretalx leaked no data, as this made using the read-only links impossible. When upgrading to the next release, all read-only link addresses will be reset.
🐛`-` A one-character-oversight led to issues with the new navigation search with certain user permissions.
:feature:`-` A page in the organiser area lists and links all possible data exports in one export page.
:feature:`322` You may now import XML files to release a new schedule.
:feature:`292` We added a new team management interface to manage all team members and permissions in one place.
:feature:`-` The new init command for project setup adds the initial user, but in time it should ask for basic configuration, aswell.
:feature:`-` The rebuild command now supports a --clear flag to remove all static assets before rebuilding them.
:feature:`-` You can choose a pattern for the header hero strip in your event color.
:feature:`320` You can now choose different deadlines per submission type, overriding the default deadline.
:feature:`325` All forms are instantly editable if you have edit permissions, and disabled otherwise. No more need to click "Edit"!
🐛`-` The schedule export could change project settings, requiring pretalx restart to reset the settings. Unchecking the "Generate HTML export on schedule release" settings was a workaround for this bug.
🐛`259` When running pretalx as (in-application) superuser, permission issues could arise. pretalx now warns and offers to migrate the account to an administrator account.
🐛`-` Frontend password validation was non-functional, and never displayed interactive password statistics. This was a display issue.
🐛`327` We removed the unused max_duration property of submission types.
🐛`329` Users always saw the default submission type instead of their chosen one.