Recent releases for pretalx

pretalx v0.1.0

2017-11-07T13:52:30+00:00

*Released on 2017-11-01.* As this is the first release, there are neither new features, nor fixed bugs, nor relevant release notes. All of those are to follow! pretalx releases will be signed by PGP key ``F0DAD3990F9C816CFD30F8F329C085265D94C052``. Further details, including the PGP key, can be found at https://pretalx.org/security.

pretalx v0.2.0

2017-12-01T12:19:22+00:00

# v0.2.0 *Released on 2017-12-01* ## Breaking Changes - 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. ## Features - 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. (#159) - You can now choose to hide the public schedule (including talk pages and speaker pages, but excluding feedback pages and the schedule.xml export) (#126) - Mail template placeholders are now validated so that templates including invalid placeholders cannot be saved at all. (#215) - You can now ask questions that take an uploaded file as an answer. (#208) - Speakers can now upload files which will be shown on their talk page. (#209) - 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. (#195, #210) - pretalx can now be configured to run with celery (an asynchronous task scheduler) for long running tasks and tasks like email sending. A new config section was added, and usage has been documented. (#38) - A ``rebuild`` command was introduced that recompiles all static assets. - Question answers now receive a nice evaluation, aggregating all given answers. (#207) - Questions may now be marked as 'answers contain personal data'. Answers of these questions are deleted when users delete their accounts. (#233) - We moved to a new permission system that allows for more flexible roles. Please report any bugs that may relate to incorrect permissions. (#78) - 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. (#171) - You can assign "override votes" to reviewers, which function like vetos (both positive and negative), on an individual basis. (#156) - A read only REST API was introduced. At the moment, it only supports resources for events and submissions. ## Fixed bugs - pretalx crashed when an incorrect invite key was used, now it shows a 404 page (#304). - When building absolute URLs for exports, emails, and RSS feeds, 'localhost' was used instead of the actual configured URL. - If an account was configured to be both an orga member and a reviewer, it encountered access rights issues. - When removing the custom event color, and then adding it again, caching issues could be encountered. - Inactive questions (questions not shown to speakers) could not be edited. - In some places, gravatar images of the visiting user were shown instead of the speaker. - The event stage display could show several conflicting phases as active. - The default submission type was not, in fact, suggested by default. (#287)

pretalx v0.2.1

2017-12-06T01:00:51+00:00

# v0.2.1 *Released on 2017-12-06* ## Features - Added better meta tags, which leads to better display in social media. (#122) ## Fixed bugs - Inactive questions could not be deleted (making them active first worked as a workaround). (#289) - Choice questions could not be deleted as long as they still had answer options. (#288) - Review team invitations sometimes failed, resulting in useless invitation objects. - When clicking the "Save & next" button when reviewing, an internal error was encountered after the review was saved. - Reviewers could not be removed from their team. - URLs were always generated with '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.

pretalx v0.2.2

2017-12-11T13:04:01+00:00

# v0.2.2 *Released on 2017-12-11* ## Fixed bugs - Reviewers could not view speaker pages. - Inviting somebody twice did not issue a second invitation object. - Somebody who was reviewer first could not be added to the organizer team.

pretalx v0.3.0

2018-01-16T23:27:57+00:00

*Released on 2018-01-17* ## Breaking Changes None. ## Features - Speakers can now be marked as "arrived". (#243) - Visitors can download an ical file containing all talks of a single speaker (#67) - There is now an API for speakers. - The speaker biography is now shown in submissions in the API endpoint. ## Fixed bugs - Non-superusers could not access the email sending form. - More than one event stage could be shown as active. - Trying to look at entered submissions without being logged in produced a server error instead of a 404. - If notifications about new submissions were turned on, they were sent to the submitter instead of the organizer.

pretalx v03.1

2018-01-18T08:54:00+00:00

*Released on 2018-01-18* ## Breaking Changes None. ## Features None. ## Fixed bugs - Make various 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.

pretalx v0.4.0

2018-02-04T15:27:26+00:00

# v0.4.0 *Released on 2018-02-04* This release removes the dependecy `django-zxcvbn-password`. Depending on your setup, you can remove it with `pip uninstall django-zxcvbn-password` or a similar command. This release also expanded the `rebuild` command to take a flag `--clear`, which discards all existing compiled static files and rebuilds them from scratch. This command invocation is encouraged after an update if any event on the instance uses custom styling or custom colors. ## Features - There is now a page in the organiser area listing and linking all currently possible data exports in one export page. - You may now import XML files to release a new schedule. (#322) - We added a new team management interface to manage all team members and permissions in one place. (#292) - There is an `init` command for project setup. Currently it only 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 prior to the rebuild. - You can choose a pattern for the header hero strip in your event color. - You can now choose different deadlines per submission type, overriding the default deadline. (#320) - All forms are instantly editable if you are allowed to edit them, and disabled otherwise. No more need to click "Edit"! (#325) ## Fixed bugs - The schedule export could change project settings, requiring pretalx to be restarted to reset the settings. This could be avoided by unchecking "Generate HTML export on schedule release". - When running pretalx as (in-application) superuser, permission issues could arise. pretalx now warns and offers to migrate the account to an administrator account. (#259) - Frontend password validation was broken, and never displayed interactive password statistics. This was a display issue only. - We removed the unused `max_duration` property of submission types. (#327) - Users always saw the default submission type instead of their chosen one. (#329)

pretalx v0.4.1

2018-02-05T13:22:19+00:00

v0.4.1 ------ *Released on 2018-02-05* Many thanks to @Rafiot for the timely bug reports. ## Fixed bugs - CfP was uneditable due to missing "Save" button. (#335) - No new questions could be added due to the wront template being loaded. (#336)

pretalx v0.5.0

2018-03-07T00:12:35+00:00

# v0.5.0 *Released on 2018-03-07* If you use postgresql, please use the package ``psycopg2-binary`` instead of ``psycopg2``, which is now also noted in the dependencies for postgresql. ## Features - pretalx now features a Plugin API, allowing to install custom plugins. Plugins can add their own exporters, and hook into various plugin hooks to be expanded over the course of this year. Plugins can be enabled or disabled per event. Documentation can be found here: https://docs.pretalx.org/en/latest/developer/plugins/index.html - Organisers can now decide if reviewers should be required to submit a score or a text with their review. (#340) - Organisers can provide room-based information for speakers, which will be provided in emails about talk scheduling. (#93) - The list of submissions is now better searchable. (#318) - Speakers can now upload an image that will be displayed next to their talk information. (#294) - Reviewers can now also be asked custom questions during their review, with all capabilities that speaker questions have. - There are now optional review deadlines, preventing reviews to be added, modified, or removed after a certain date. (#352) - Individual directories for logs, media, and static files can now be configured via environment variables. - Organisers can now show information snippets to submitters, or speakers. (#348) - Allow to filter question statistics by speaker status. ## Fixed bugs - In the dashboard, an incorrect link was given to add new reviewers. (#344) - The "save" button was missing on the mail settings page. (#341) - Users could not see (instead not change) their submissions after CfP end, until they were either rejected or accepted. (#333) - In the tag, the event was displayed 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 no invitation was required. - The Docker setup was broken. It is fixed, and a notice of limited support was added to the documentation. (#300) - The orga view now always uses the event timezone. </article> <article> <h1>pretalx v0.6.0</h1> <p>2018-05-06T16:39:26+00:00</p> # v0.6.0 *Released on 2018-05-06* ## Breaking Changes None. ## Features - New plugin hook: ``pretalx.submission.signals.submission_state_change`` is triggered on any state change by a submission. - The frab compatible xml was improved by using correct UUIDs, and includes an XML comment with a pretalx version string. - The general look and feel and colorscheme has been improved. - 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 submission abstracts, descriptions, and speaker biographies are required for their event. ## Fixed bugs - Speakers could see their submission in the orga backend, but could access no information they did not put there themselves. (#375) - The API showed talks to organisers if no schedule had been released 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. </article> <article> <h1>pretalx v0.6.1</h1> <p>2018-05-15T06:27:55+00:00</p> # v0.6.1 *Released on 2018-05-15* ## Fixed bugs - The "Copy to draft" button was missing when viewing a sent email. - Accepted, but unconfirmed talks were listed as "Other talks" publicly once the speaker had confirmed one talk and the first schedule was released. (#431) </article> <article> <h1>pretalx v0.7.0</h1> <p>2018-06-19T14:39:09+00:00</p> [Release Notes](https://docs.pretalx.org/en/latest/changelog.html) </article> <article> <h1>pretalx v0.7.1</h1> <p>2018-06-19T20:51:44+00:00</p> </article> <article> <h1>pretalx v0.8.0</h1> <p>2018-09-23T21:38:53+00:00</p> *Released n 2018-09-23* ## Breaking changes - 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. - pretalx now doesn't support usernames any longer – as email addresses were already required for accounts, they are now the only means of logging in. This may confuse a few users – as an administrator, you can look up users' email addresses if they don't remember them, or change them, if necessary. ## New features - A human-readable time until the CfP closes is now displayed next to the end time. (#213) - As an organizer, it is now possible to send an email to all reviewers in the Compose Mail section. (#454) - In exports, HTTP Etags are now supported to allow for more aggressive caching on clients. (#492) - Organisers can now also reset the password for the speakers they have access to. - Present a public list of talks and a list of speakers. - The submission list now includes a graph of submissions over time. - The sneak peek / is_featured flag is now shown in the submissions and talk API endpoints. - You can now use your authentication token to access all pages you have access to, not only the API. This makes integration of exports much easier. - When using paper cards to build a schedule, each card comes with a QR code link to a quick scheduling form for that submission. (#240) - Before releasing a new schedule, the user is now shown any warnings and what the public changelog will look like. - The schedule editor shows warnings on scheduling conflicts, including live feedback on where a talk can be placed. (#214) - The review dashboard now features the same search and filter options as the submission list. (#474) - You can now add minimum or maximum length restrictions to abstracts, descriptions, speaker biographies, and all text-based questions. (#408) - When linking to a talk on social media, the talk image is now shown. - French translation - The event logo is displayed larger and up to the full width of the document below. Please check that your event still looks as intended after upgrading. - Allow to order rooms manually. (#149) - Allow to order questions manually. (#149) - Instead of setting a flag somewhere, pretalx now has an explicit "go live" button. There is also a corresponding signal plugins can listen to (please refer to the plugin documentation for further information). - 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. - Allow organisers to trigger a password reset for team members. (#415) - We now have tests to make sure all config options and plugin hooks are documented. - All manage commands available in pretalx are now included in the documentation. ## Fixed bugs - When a submission was removed that contained an answered (multiple-) choice question, the selected answer option was removed, too. - When a speaker held more than two talks, their related talks were not linked correctly. (#501) - Custom CSS may now also include media queries. (#505) - Display of times could be off in the static HTML export. (#500) - Not all current TLDs were used when processing markdown input to build links. (#503) - The schedule import in the organiser backend never worked (while the manage command for administrators did work). - If a review question was mandatory while submission questions were active, they would block the submission process. - The HTML export contained media files (not other content) from all conferences on an instance, instead of only the exported conference. (#488) - The behaviour of pressing enter in multi-step forms was unintuitive in some places. (#478) - Following the revamp of team permissions, override votes could no longer be configured. This has been corrected, and the general handling of override votes was improved. (#473) - Questions couldn't be deleted, only made inactive. - Don't show a 404 error if a reviewer tries to review their own submission, but show an error message instead. (#463) - Don't crash during ``pretalx init`` if no conference organiser slug is given. (#451) </article> <article> <h1>pretalx v1.0.0</h1> <p>2019-06-02T16:03:00+00:00</p> Please check the [release blog post](https://pretalx.com/p/news/drum-roll-for-pretalx-10/) and [our changelog](https://docs.pretalx.org/en/latest/changelog.html#changelog) for details. </article> <article> <h1>pretalx v1.0.1</h1> <p>2019-06-03T16:52:12+00:00</p> This bugfix releases closes issues #713, #718, and #719. </article> <article> <h1>pretalx v1.0.2</h1> <p>2019-06-26T22:35:30+00:00</p> </article> <article> <h1>pretalx v1.0.3</h1> <p>2019-06-26T22:37:46+00:00</p> Fixes bugs #728, #729, #730, and an issue with saving an event's custom domain. </article> <article> <h1>pretalx v1.1.0</h1> <p>2019-12-21T08:07:16+00:00</p> </article> <article> <h1>pretalx v1.1.1</h1> <p>2020-01-09T23:41:12+00:00</p> </article> <article> <h1>pretalx v1.1.2</h1> <p>2020-01-10T12:35:55+00:00</p> </article> <article> <h1>pretalx v2.0.0</h1> <p>2020-12-24T00:29:50+00:00</p> </article> <article> <h1>pretalx v2.1.1</h1> <p>2021-01-16T14:10:54+00:00</p> </article> <article> <h1>pretalx v2.2.0</h1> <p>2021-08-15T10:27:56+00:00</p> </article> <article> <h1>pretalx v2.3.0</h1> <p>2021-12-25T23:56:43+00:00</p> </article> <article> <h1>pretalx v2.3.1</h1> <p>2021-12-26T00:11:25+00:00</p> </article> <article> <h1>pretalx v2.3.2</h1> <p>2023-03-07T12:22:25+00:00</p> Fixes a path traversal vulnerability in the static HTML exporter. </article> <article> <h1>pretalx v2023.1.0</h1> <p>2023-08-30T16:06:53+00:00</p> [Release blog post](https://pretalx.com/p/news/releasing-pretalx-2023-1-0/) </article> <article> <h1>pretalx v2023.1.3</h1> <p>2023-09-17T10:39:00+00:00</p> [Blog post](https://pretalx.com/p/news/releasing-pretalx-2023-1-3/) </article> </main></body></html>