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

CCX: Conflicting start and end dates do not show an error #39

Open
carsongee opened this issue Aug 13, 2015 · 1 comment
Open

CCX: Conflicting start and end dates do not show an error #39

carsongee opened this issue Aug 13, 2015 · 1 comment

Comments

@carsongee
Copy link

Tested on sandbox2o.

I noticed that conflicting start and end dates do not provide an error message and can go unnoticed. Changes can be saved as well. I'm not sure if an error message is desired. I provided two examples of conflicting dates below.

screen shot 2015-08-04 at 10 47 41 am

When a course is scheduled in studio, conflicting dates will produce an error message and changes cannot be saved.
screen shot 2015-08-05 at 10 27 41 am
screen shot 2015-08-05 at 10 29 22 am

However, individual subsections can be scheduled with conflicting dates and changes can be saved.
screen shot 2015-08-05 at 10 38 24 am

@pdpinch
Copy link
Member

pdpinch commented Nov 25, 2015

@amir-qayyum-khan I've verified https://github.com/edx/edx-platform/issues/10538 and it addresses this issue in the sidebar. But I think it still exists in the main schedule tree. Steps to reproduce:

  1. Add a Chapter to a CCX.
  2. In the schedule tree, click on the start date. Set it to be a date in the future.
  3. For the same chapter, set the due date to be in the past.

Expected behavior:

An error message, like "Due date cannot be before start date.'

Actual behavior:

Date is accepted and can also be saved.

Work on this should probably wait for the schedule.js refactor, #146

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants