Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Requiring availability during submission prevents submissions due to deadlock. #594

Closed
MacLemon opened this Issue Feb 14, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@MacLemon
Copy link
Contributor

MacLemon commented Feb 14, 2019

Current Behavior

CfP Settings are configured to require availability, like in this screenshot.

screen_shot_2019-02-14_at_14_38_10

When a user wants to enter CfP with a submission, they're asked to fill in multiple forms. On the profile step, they're not asked to fill in their availability during the conference. The form validation enforces the filling of a non-displayed, and for the user non-existing field.
This results in a dead-lock situation since the submitter cannot advance past this step.

Expected Behavior

Display all required fields to the submitter so they can advance and complete their submission.
Alternatively, postpone the requirement for availability for the confirmation step, so they can only confirm their their talk when they also fill in the required availability.

Steps to Reproduce

  1. Configure CfP to require Availability
  2. Start a submission, advance until the speaker's profile step
  3. Hit a deadlock since pretalx is complaining about “This field must be filled out” where there is no marked field to give a hint which field is required. This is because the required availability field isn't displayed at all.

Context

A friendly speaker contacted us that they have a problem finishing their submission.

wbvuixcvaeubacjntkacwgej-2

Current workaround: Remove the requirement for availability during submission. (Confirmed working, by said speaker.)

Your Environment

  • Version used: pretalx 0.9.0
  • Environment name and version (e.g. Chrome 39, python 3.5): Browser independent
  • Operating System and version (desktop or mobile): Speaker's Desktop OS is some Linux.
  • Link to your instance, if in production: https://cfp.privacyweek.at/
@rixx

This comment has been minimized.

Copy link
Member

rixx commented Feb 14, 2019

Thank you for the report! Definitely a bug, and once it's closed, it might make a fine reason to release v0.10.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.