Bug 293840 - Do not allow for the participants to enter an invalid arrival/departure date from the past.
Summary: Do not allow for the participants to enter an invalid arrival/departure date ...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: www.kde.org
Classification: Websites
Component: sprints.kde.org (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Emil Sedgh
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-11 13:59 UTC by Laszlo Papp
Modified: 2021-03-09 21:36 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Laszlo Papp 2012-02-11 13:59:37 UTC
Version:           unspecified
OS:                Linux

The arrival and departure date could be arranged at least to the future. It is currently possible to select date for those from the past. Meanwhile it does not take too much effect on the participants, it might be confusing for other volunteers who would like to sign-up which is the mistake: the mentioned date, or the selected by the user making the mistake. It is even more serious, if the sprint organizer opening the new sprint makes this mistake because there are no other volunteers at the time whose arrival and departure date could make it clear.

There are traveling or hotel booking pages where you cannot choose an earlier
arrival and departure date from the past.

Reproducible: Always

Steps to Reproduce:
1) http://sprints.kde.org
2) Try to participate to an event
3) You can select and set a leaving or/and arrival date in the past for instance




Expected Results:  
1) http://sprints.kde.org
2) Try to participate to an event
3) You cannot select and set a leaving or/and arrival date in the past for instance
Comment 1 Justin Zobel 2021-03-09 07:25:53 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 2 Justin Zobel 2021-03-09 21:36:00 UTC
Lydia Pintscher confirmed this subdomain no longer exists and that all bugs related to it can be closed.