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

User can not change availability because its out of event timeframe #579

Closed
s-light opened this Issue Feb 1, 2019 · 3 comments

Comments

Projects
None yet
2 participants
@s-light
Copy link
Contributor

s-light commented Feb 1, 2019

Expected Behavior

Allow Orga to change event timeframe without getting users stuck

Current Behavior

If event timeframe is shortend and user had availability times set
he is not able to edit anything in his profile -as in this the old time is stored (but not shown)
and so triggers an The submitted availability is not within the event timeframe.validity error.

Steps to Reproduce

  1. Setup an event for two days
  2. user → submit talk and set your availability to all day for both days
  3. change event timeframe to one day only
  4. user can't change his availability or any other profile thing anymore.
  5. also he can't confirm submissions - seems to be similar bug. (but no error message)

Context

this just plopped up during testing and playing around..

Your Environment

  • Version used: v0.9.0-46-gce3f46d5 (current master / forked)
  • Environment name and version: Firefox 64.0 (64-bit)
  • Operating System and version: Kubuntu 18.10 64-bit
@rixx

This comment has been minimized.

Copy link
Member

rixx commented Feb 4, 2019

Arguably, availability not within the event time frame should just be discarded in all availability forms, instead of raising an error.

@s-light

This comment has been minimized.

Copy link
Contributor Author

s-light commented Feb 5, 2019

found yesterday: same bug happens for rooms too....

@rixx

This comment has been minimized.

Copy link
Member

rixx commented Feb 5, 2019

Availability forms are the same everyhwere, so seeing the same issue here is expected. Thanks for mentioning it, though, so we'll have another place to test the fix :)

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.