changelog.rst

Release Notes

• 775 When a speaker withdrew their already-accepted talk, the talk slot was not removed from the schedule editor. It did work when setting the state via the organiser interface.
• 774 The API endpoint for events always returned a 404 on the detail view, even when event was visible in the list view.
• - Speaker and talk detail pages now contain links to their respective API detail pages as alternate links.
• - The main schedule page now returns a 303 See Also redirect if accessed with JSON or XML accept headers.
• 773 In the /talks and /submissions endpoints, speaker biographies were not exposed. They were available in the /speakers endpoint as expected, so if you cannot currently upgrade, please be advised to use that endpoint.
• - Organisers can now disable/remove the profile picture input field if they don't want any speaker pictures at all.
• - The event creation assistant now suggests more sensible event slugs.
• - The time(s), date(s) and location(s) of scheduled talks were added to the private speaker pages of those talks, making it easier for speakers to find out when and where their talk is taking place.
• - The API is now also available as an HTML browsable API. Filters and searches should be working as well as just browsing around.
• - The events API endpoint now comes with a urls field exposing links to the schedule page, and the login page, among other things.
• 754 Reviews could be returned multiple times in the reviews API endpoint (though the total count returned was correct).
• 742 Organisers can now set a minimum or maximum length for submission titles.
• 743 If no schedule has been published but a sneak peek is available, the schedule page now redirects to the sneak peek page.
• - The pretalx markdown display now supports markdown tables.
• - Due to the powerful and hard-to-specify nature of the schedule HTML import, the frontend facing schedule xml import has been removed. Administrators can still import schedule files with the import_schedule command.
• 1.0.3 <2019-06-27>
• 730 The talk page of talks with multiple slots did not work and threw an error instead.
• 729 The “unscheduled talks” column in the schedule editor could overlap with the room columns on events with many rooms.
• 728 The “Invite reviewers” link on the main event dashboard led to an incorrect page.
• 732 Speaker availability is now included in the API for organizers.
• 475 Organisers can now regenerate the accept/reject emails from the review dashboard context menu.
• - To keep in line with our new database scoping, if you access the pretalx shell, you are now advised to use the shell_scoped command instead of the shell command, and call it with the flags for your event, like --event__slug=myevent (or an --override flag to access all events).
• 731 Users can now see (and potentially edit) their submission's submission type.
• - Some custom domains could not be set via the frontend.
• - Organisers can now also see unconfirmed talks in their preview of the public schedule page. The unconfirmed talks are clearly marked to avoid confusion.
• 1.0.2 <2019-06-07>
• - Organisers were able to see all emails sent to a user in their events, instead of only emails sent for the currently active event. This is a data leak. You can find more information on our blog.
• - We now add a hash to all uploaded file names to avoid collisions.
• 1.0.1 <2019-06-03>
• 719 In the submission process, file upload questions would not be saved correctly.
• 713 The sneak peek toggle in the submission list did not actually work due to a changed URL.
• 718 Regular installation from PyPI was broken due to an incorrect file reference.
• 1.0.0 <2019-06-02>
• 427 Organisers can now permit users to submit (and change) their own talk duration length.
• 700 Submitters can now choose to withdraw their talk even if it was accepted. When an accepted talk is withdrawn, the organisers will receive a notification email.
• - When using a command line client to access a schedule page, pretalx will now output ASCII tables or lists, depending on the format parameter.
• 402 Fields with markdown support now come with a preview next to the input field (if JavaScript is enabled).
• 669 Emails can now also be sent grouped by submission track or submission type.
• - You can now install pretalx[redis] if you use pretalx with a redis server for better caching and/or asynchronous task runners.
• - Our documentation now lists the tasks a pretalx instance should run periodically, namely runperiodic about once every five minutes, and clearsessions about once a month.
• - Administrators can now see a dashboard with relevant settings and current information, including documentation links.
• 689 In the (undocumented) review API, reviews of deleted submissions were shown, even though those submissions were not available anymore via the frontend.
• 688 pretalx was inconstent in its usage of email senders and reply-tos. Now, if there is a sender address configured, the reply-to is not explicitly set. pretalx falls back to the instance-global sender if there is no event sender address. A reply-to setting is available if the organisers wish to provide a separate address there.
• 682 The submission endpoint now provides a created field to organiser users.
• 326 During event creation, pretalx provides more critical feedback, such as asking if the event is supposed to take place in the past, or suggesting good slugs.
• 393 As an alternative to file uploads, organisers can now also provide their custom CSS directly as text.
• 360 Within the review dashboard, organisers can now accept and reject multiple submissions at the same time.
• 656 Instead of by average, review scores are now shown aggregated by the median.
• 655 Mails to submissions with titles near the length cap (of 200 characters) could not be created, since with the added "[event]" prefix the mail subject was too long to be saved.
• - Question pages now feature visual statistics where appropriate.
• - There now is a page for submission statistics.
• 628 Prefill CfP form with track and submission type if they are available in the query string.
• - pretalx is now able to run with Python 3.7 even when using Celery.
• 598 Via the new review phase settings, speakers can be allowed to modify their submissions while they are being reviewed.
• 641 At the undocumented URL /<event>/speaker/by-id/123/ there is now a redirect to the canonical speaker URL /<event>/speaker/CODE/ to work around export format restrictions.
• 565 When using the back button to return to the previous step in the submission workflow, the data from the current step had to be filled in to use the button, but was not saved. Now it will be saved, and the progress bar on top can be used for lossy (but quick) navigation to the previous step.
• 645 The rendering of the full submission content in the acknowledgment mail (upon submission) looked weird in HTML, due to missing line breaks.
• 646 On slow network connections, the login step of the CfP submission loaded in a suboptimal way, leaving users with a seemingly finished page but without the login/registration form. As a consequence, all page loads (but especially that one) were optimized.
• 642 Having only one submission type in the event showed a drop-down with submission types from ALL events, instead of hiding the submission type input completely as intended.
• 609 Organisers can now filter submissions and reviews by track.
• 634 The API now provides internal notes by speakers and organisers to requesting users with adequate permissions.
• - Organizers can now provide a header image instead of a header color and pattern for their events.
• 640 Instead of having to scroll with the mouse wheel or arrow keys when dragging a talk in the schedule editor, you can now just drag the talk to the upper or lower edge of the window instead.
• - In pretalx, emails the organisers send out are now connected with user accounts if the address matches anybody, allowing organisers and speakers to see which emails were sent to a speaker. This serves both as a help for organisers and speakers, in case emails get lost, email addresses are inaccessible, or any other issues occur.
• 637 pretalx will now display the schedule wider the more rooms are present, starting at four rooms and reaching maximum browser width for six rooms, to make schedules look less cramped and more readable.
• 620 Speakers can't invite other speakers any longer after the CfP is over.
• 606 Our documentation now explains which parts of pretalx to back up.
• 486 In the schedule editor, the room names and the current date are now fixed to the top when scrolling down.
• 618 Fix a bug where some fields in the schedule.xml export were rendered without their timezone offset (only day defintions, not the talk times).
• 532 Add a field for notes of the organisers for their own use which is not visible to the public and the speakers.
• - Reviewers are now shown a progress bar when going through submissions.
• 570 Submissions can now be scheduled multiple times, e.g. if a workshop will be held twice.
• - Changing the order of rooms made the schedule break.
• 433 Organisers can now view all reviews, except for their own submissions.
• 589 Before setting a new custom domain for an event, pretalx now checks if the domain has any nameserver records.
• - A dependency of ours introduced an XSS vulnerability, which organisers could use to execute JavaScript during the CfP workflow of speakers via question texts. We have added a fix against this behaviour, and submitted a report including a patch to the upstream library. To prevent issues like this one in the future, we've moved all remaining JavaScript sources to files, and set the according CSP header, so that execution of inline JavaScript will be disabled.
• 364 Speakers can now invite a co-speaker while in the submission process.
• 62 Exporters can now opt in to show a QR code to their location. The XML and iCal exporters show a QR code linking their location by default.
• 477 If you only noticed after releasing your schedule that you wanted to changes something in your speaker notifications, you can now generate those emails again from the schedule editor actions menu.
• 479 When telling speakers about their scheduled or rescheduled slots, a hidden mail template was used instead of the actual template visible to the organiser.
• 563 For later reference, the full submission is included in the confirmation mail sent to the speaker.
• 571 When adding a submission as organiser, pretalx did not validate the speaker email address and then tried to send them an email regardless of its validity.
• 403 Organisers can now choose question answers by speakers to be published on the talk/speaker pages. This setting cannot be changed on once the question has been answered, to make sure that speakers are informed about this.
• - Reviewer teams can now be restricted to one or multiple tracks. Reviewers will only see submissions and reviews from these tracks.
• - Teams settings are now located exclusively at the organiser level. The navigation entry in the event sidebar will take you there directly.
• 523 If you use tracks, you can now choose to make questions available only to submissions on certain tracks.
• 459 The speaker page in the organiser backend now has a direct link to send an email to that speaker.
• 457 You can now order submissions by the number of reviews they have received on the review page.
• 566 The Reply-To field now permits multiple email addresses.
• 579 When organisers changed the event timeframe, already submitted availabilites would have to be changed upon new submission.
• 577 You can now decide if text lengths should be counted in words or in characters when restricting how long they should be.
• 587 pretalx did not automtically update a talk's duration when it was changed via the submission type or directly. It was only changed when you moved the talk in the schedule editor.
• 594 pretalx did not display speaker availabilities during submission, even when they were required, breaking submission workflows.
• 346 Due to the generous sponsorship of JuliaCon, pretalx is now capable of blind reviews, i.e. making sure that reviewers cannot see speaker names.
• - The organiser area has now additional, event specific login pages (at /orga/event/<slug>/login/) which redirect by default to the event dashboard, and appear with the color and logo of the event in question.
• - The review settings have moved from the CfP page to their own settings page.
• - You can now decide to add the robots=noindex meta tag to prevent bots from crawling your event pages.
• - Plugin developers can now use the is_available hook to decide if their plugin should be shown on a per-event basis.
• - Speaker without an avatar and with gravatar disabled had a broken avatar-image in the speaker's view in the orga-backend.
• - The visual representation of a speaker's avatar is now consistent across all image-sizes and bio-texts.
• 583 When signing up with an email address with upper case letters included, pretalx only allowed to log in with a lower-cased email address.
• 572 People who had only deleted submissions in an event were still shown in the submitter list, which was unexpected and was since fixed.
• - If only one conference language is available, pretalx doesn't as speakers to choose it from a drop-down, as this behaviour is rather silly.
• - pretalx doesn't run regenerate_css on startup automatically any longer. This reduces startup times. If for any reason an event does not look as it should, you can fix it by running python -m pretalx regenerate_css. You will also need to execute this command on updates from now on.
• - You can now decide if you want to notify speakers about their changed talks when releasing a new schedule.
• - To help make other pretalx installations more secure, we've updated our proposed nginx configuration to include an attachment header for all files under /media, to prevent user uploaded data to be delivered directly to other users. If you host a pretalx instance, please make use of this option.
• - Since SVG files are nearly impossible to sanitize, pretalx has given up trying, and will no longer accept SVG files as image uploads.
• - The iCal export for speakers who had both scheduled and not-yet-scheduled talks was broken.
• 559 Organisers can download a list of speakers as a CSV file.
• - A couple of URLs now end in a trailing slash where they did not before – you will be automatically redirected, so you don't have to worry about it unless you integrate pretalx somewhere without following redirects.
• - You can set the URL of your static HTML export, if you're using one, and it will be used when generating absolute URLs, e.g. in exports or emails.
• 0.9.0 <2018-12-21>
• - pretalx can now group talks in tracks. Each talk can be assigned a track (either by the submitter, or by the organiser). Tracks will be displayed in configurable colors in the public schedule. The feature is entirely optional, and you can continue using pretalx without tracks without any problem.
• - We tuned pretalx performance to be faster when showing the schedules of large conferences with several hundreds of talks.
• 538 The sneak peek view will only feature talks that have been accepted.
• 440 Organisers can now follow an RSS feed to see new submissions – you'll have to provide your authentication token in the RSS request header to authenticate.
• - You can now set the default pretalx system wide time zone and locale (defaulting to UTC and en).
• 544 Organisers could see the titles of speaker information notes of all events, not just the currently active one (they could not see the details or edit them).
• 504 The schedule page is now better printable.
• - A bug <celery/celery#4878> in celery could make running pretalx with asynchronous workers impossible. We've pinned an earlier celery version that doesn't show this problem.
• - 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.)
• - Plugins can now provide recording iframes (via the new register_recording_provider signal and other mixins).
• - The new nav_event_settings plugin signal allows plugins to integrate their own settings pages next to the pretalx core pages.
• - pretalx now presents a colorpicker for your event primary color, including a hint on color suitability.
• - The new /api/me endpoint shows name, email address, locale, and timezone of the logged in user.
• - 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.
• - The API now provides a /rooms endpoint.
• 530 The API now provides a /reviews endpoint.
• 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.
• - 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.
• - 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:Therebuildcommand now comes with a lot more build output for ease of debugging. You can disable the build output with the new--silent/-s`` flag.
• 476 Administrators can now delete both events and organisers.
• 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.
• 512 You can now configure if speakers should provide their availability during talk submission.
• - Due to an updated Django version, pretalx has dropped support for PostgreSQL 9.3 and MySQL 5.5.
• 0.8.0 <2018-09-23>
• - 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.
• - 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.
• 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).
• 454 As an organizer, it's now possible to send an email to all reviewers in the Compose Mail section.
• 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.
• - 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.
• - 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.
• - The submission list now includes a graph of submissions over time.
• - You can now see the sneak peek / is_featured flag in the submissions and talk API endpoints.
• - 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.
• - All manage commands available in pretalx are now included in the documentation.
• 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.
• - You can now see warnings and what the public changelog will look like before releasing a new schedule.
• 214 The schedule editor shows warnings on scheduling conflicts, including live feedback on where you can schedule a talk.
• 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.
• - 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.
• 408 You can now add length restrictions to abstracts, descriptions, speaker biographies, and all text-based questions.
• - When linking to a talk on social media, those pages will show the talk image.
• - French translation
• - The event logo shows up larger and up to the full width of the document below. Please check that your event still looks as intended after upgrading.
• 149 Allow to order rooms manually.
• 149 Allow to order questions manually.
• - We now have tests to make sure all config options and plugin hooks are part of our documentation.
• - 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.
• - For organisers, the submission/talk API endpoints now contain the question answers given by the speakers.
• - Schedules now contain a search bar to filter talks by title or speaker.
• - Schedules now feature a sidebar navigation to jump directly to a selected day.
• - 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.
• - Prevent organisers from adding a non-localhost mail server without transport level security to make sure our Privacy Policy holds true.
• 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.
• 0.7.1 <2018-06-19>
• - 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.
• 0.7.0 <2018-06-19>
• 430 To maintain compatability with frab xml exports, the schedule xml export now contains a <url> tag.
• - When trying to register a user with a nick that already existed in a different capitalization, pretalx failed to show a clear error message.
• 128 An event's schedule is now available even if the browser has no internet connection, provided it has opened the schedule before.
• - Provide better upgrade documentation for administrators.
• - Add clever release notes.
• 443 (UI) The button colors when changing submission states were unintuitive.
• - You can now configure the configuration file with the PRETALX_CONFIG_FILE environment variable.
• - Some more context sensitive dashboard tiles include for example a countdown to the CfP end.
• - A navigation search allows you to go directly to a range of useful pages.
• 444 If two organisers set a submission to 'accepted' at the same time, two acceptance emails would show up in the outbox.
• - Removing a speaker from a submission could be impossible if their nick contained special characters.
• - Submitters can share a submission via a read-only link.
• - Organisers can configure a list of talks as "sneak peek" before they release the first schedule.
• 446 If an event had a custom domain configured, absolute urls would still use the instance's default domain.
• 441 The "Mark speaker arrived" button is now visible during and slightly before the event, but not during other times.
• - The API always showed the speaker biography as empty.
• - When accessing a confirmation link unauthenticated, a 404 page was visible instead of a login page.
• - The API now exports links to submission images and speaker avatars.
• - HTML exports failed if a speaker had canceled their talk.
• - Sometimes, empty HTML reports showed up with all talks missing.
• 0.6.1 <2018-05-15>
• - The "Copy to draft" button was missing when viewing a sent email.
• 431 Accepted, but unconfirmed talks showed up as "Other talks" on the public schedule once the speaker had confirmed one talk.
• 0.6.0 <2018-05-06>
• - New plugin hook: pretalx.submission.signals.submission_state_change will trigger on any state change by a submission.
• - The frab compatible xml now uses UUIDs, and includes an XML comment with a pretalx version string.
• - pretalx has a better general look and feel and colorscheme.
• - Organisers can make more changes to speaker profiles and submissions to ease event administration.
• - pretalx now has a concept of organisers and teams.
• - To avoid running into issues when uploading custom CSS, and ensuring smooth operations, custom colors and CSS is not used in the organiser area anymore.
• - You can now send mails from templates and use shortcuts from submissions to send mails to specific speakers.
• - Since different events have different needs, organisers can now choose if speakers have to provide submission abstracts, descriptions, and speaker biographies during the CfP.
• 375 Speakers could see their submission in the orga backend, but could access no information they did not put there themselves.
• - The API showed talks to organisers if no schedule was present yet. It did not show the information to unauthorised users.
• - There was no possibility to reset a user's API token.
• - If an organiser changed a speaker's email address, they could assign an address already in use in the pretalx instance, resulting in buggy behaviour all around.
• 0.5.0 <2018-03-07>
• - pretalx now features a Plugin API, allowing to install custom plugins. Plugins can add their own exporters, and hook into plugin hooks. You can enable or disable plugins per event. You can find the plugin developer documentation: https://docs.pretalx.org/en/latest/developer/plugins/index.html
• 340 Organisers can now decide if reviewers should have to submit a score or a text with their review.
• 93 Organisers can provide room-based information for speakers, and send it automatically in the emails about talk scheduling.
• 318 The list of submissions is now better searchable.
• 294 Speakers can now upload an image that will show up next to their talk information.
• - Reviewers can now also answer custom questions during their review, with all capabilities that speaker questions have.
• 352 There are now optional review deadlines, preventing users from adding, modifying or removing reviews after a certain date.
• - Individual directories for logs, media, and static files can now take their values from environment variables.
• 348 Organisers can now show information snippets to submitters, or speakers.
• - Allow to filter question statistics by speaker status.
• 344 In the dashboard, reviewers would see an incorrect link to add new reviewers.
• 341 The "save" button was missing on the mail settings page.
• 333 Users could not see (instead not change) their submissions after CfP end, until they were either rejected or accepted.
• - In the <title> tag, the event showed up twice, once properly and once in a technical representation.
• - Documentation fix: The environment variable for database passwords is PRETALX_DB_PASS, not PRETALX_DB_PASSWORD.
• - Unconfirmed talks showed up as empty boxes in the schedule editor.
• - Upgrading the privileges of an existing user did not result in an email, since it required no new account.
• 300 The Docker setup was non-functional. The documentation includes a notice of limited support.
• - The orga view now always uses the event timezone.
• 0.4.1 <2018-02-05>
• 335 CfP was uneditable due to missing "Save" button.
• 336 Organisers couldn't add new questions.
• 0.4.0 <2018-02-04>
• - A page in the organiser area lists and links all possible data exports in one export page.
• 322 You may now import XML files to release a new schedule.
• 292 We added a new team management interface to manage all team members and permissions in one place.
• - The new init command for project setup adds the initial user, but in time it should ask for basic configuration, aswell.
• - The rebuild command now supports a --clear flag to remove all static assets before rebuilding them.
• - You can choose a pattern for the header hero strip in your event color.
• 320 You can now choose different deadlines per submission type, overriding the default deadline.
• 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.
• 0.3.1 <2018-01-18>
• - Make 404 errors more helpful.
• - Re-introduce support for the documented PRETALX_DATA_DIR environment variable.
• - Leaving an optional choice question empty resulted in a server error.
• 0.3.0 <2018-01-17>
• 243 Organisers can mark speakers as "arrived".
• 67 Visitors can download an ical file containing all talks of a single speaker.
• - We have a new API for speakers.
• - The speaker biography is now visible in submissions in the API endpoint.
• - Non-superusers could not access the email sending form.
• - More than one event stage could be visible as active.
• - If a user without active log-in looked at entered submissions, they triggered a server error instead of a 404.
• - If notifications about new submissions were active, pretalx sent the mails to the submitter instead of the organizer.
• 0.2.2 <2017-12-11>
• - Reviewers could not view speaker pages.
• - Inviting somebody twice did not issue a second invitation object.
• - Somebody who was reviewer first could not join the organizer team.
• 0.2.1 <2017-12-06>
• 122 All HTML contains better meta tags, which leads to better display in social media.
• 289 Organisers could not delete inactive questions (making them active first worked as a workaround).
• 288 Organisers could not delete choice questions as long as they still had answer options.
• - Review team invitations sometimes failed, resulting in useless invitation objects.
• - Clicking the "Save & next" button when reviewing could result in an internal error, without any data loss.
• - Organisers could not remove reviewers from teams.
• - Absolute URLs always included 'localhost' as their host.
• - When adding a submission in the orga backend with an orga user as speaker, the orga user did not receive a speaker profile.
• 0.2.0 <2017-12-01>
• - The default value for email SSL usage is now False, permitting the default configuration of localhost:25 to work on more machines out of the box.
• 159 E-mails are now sent with a multipart/HTML version, featuring the mail's text in a box, styled with the event's primary color.
• 126 You can now choose to hide the public schedule (including talk pages and speaker pages, but excluding feedback pages and the schedule.xml export)
• 215 pretalx validates mail template placeholders, and prevents organisers from saving templates including invalid placeholders.
• 208 You can now ask questions that take an uploaded file as an answer.
• 209 Speakers can now upload files which will be visible on their talk page.
• 210, 195 The review interface has been rewritten to include fewer pages with more information relevant to the user, dependent on event stages and their role in the event.
• 38 pretalx can now run with celery (an asynchronous task scheduler) for long running tasks and tasks like email sending. The new config section is part of our documentation.
• - The new rebuild command recompiles all static assets.
• 207 Question answers now receive a nice evaluation, aggregating all given answers.
• 233 Organisers can mark questions as 'answers contain personal data'. When users delete their accounts, they also delete answers of these questions.
• 78 We moved to a new permission system that allows for more flexible roles. Please report any bugs that may relate to incorrect permissions.
• 171 You can now configure a custom domain to use with your event, in case you have an event specific domain for each of your events.
• 156 You can assign "override votes" to reviewers, which function like vetos (both positive and negative), on an individual basis.
• - The new read-only REST API supports resources for events and submissions.
• 304 pretalx crashed with incorrect invite keys, now it shows a 404 page.
• - When building absolute URLs for exports, emails, and RSS feeds, pretalx used 'localhost' instead of the actual configured URL.
• - If a user was both an orga member and a reviewer, they could encounter access rights issues.
• - When removing the custom event color, and then adding it again, caching issues could occur.
• - Inactive questions (questions not visible to speakers) were not editable.
• - In some places, gravatar images of the visiting user were visible instead of the speaker.
• - The event stage display could show conflicting phases as active.
• 287 The default submission type was not, in fact, suggested by default.
• 0.1.0 <2017-11-01>