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

Cannot change 2nd date once a date has been picked #5

Closed
jeffreykemp opened this issue Nov 17, 2015 · 3 comments
Closed

Cannot change 2nd date once a date has been picked #5

jeffreykemp opened this issue Nov 17, 2015 · 3 comments
Assignees
Labels
Milestone

Comments

@jeffreykemp
Copy link

Case #1

  1. Enter a date for the 1st item, e.g. 10 Sep.
  2. Enter a date for the 2nd item, e.g. 11 Sep.
  3. Open the date picker on the 2nd item.

Expected: can select any date on or after 10 Sep.
Actual: can only select dates between 10 Sep and 11 Sep.
Workaround: clear the date from the item first

Case #2

  1. Enter a date for the 1st item, e.g. 10 Sep.
  2. Enter a date for the 2nd item, e.g. 11 Sep.
  3. Change the 1st date to an invalid date, e.g. 12 Sep.
  4. Attempt to change the 2nd date.

Expected: can select any date on or after 12 Sep.
Actual: cannot select any date at all, cannot navigate months.

Case #3

  1. Enter a date for the 1st item, e.g. 10 Sep.
  2. Enter a date for the 2nd item, e.g. 11 Sep.
  3. Attempt to change the 1st date.

Expected: can select any date not later than 11 Sep.
Actual: can select any date.

I suspect these issues are related.

@vincentmorneau
Copy link

+1

It was working fine in the pre-5.0 version: https://apex.oracle.com/pls/apex/f?p=45587:700:0

@martindsouza martindsouza self-assigned this Dec 13, 2015
@martindsouza
Copy link
Member

@jeffreykemp @vincentmorneau This is not a bug, rather a configuration option. You probably have the following setting for the TO_DATE item:

image

This does raise a good point, that the plugin should catch this issue as it can be very hard to debug. As such I will update the plugin to show an alert message on run time to let developers know right away:

image

As well, when the application is run in debug mode it will be obvious to developer and provide reference back to this issue:

image

martindsouza added a commit that referenced this issue Dec 13, 2015
Use ui._elements.$elementObj instead of local vars $this and $elementObj (minor)
@martindsouza martindsouza added this to the 2.1.0 milestone Dec 13, 2015
martindsouza added a commit that referenced this issue Dec 13, 2015
@martindsouza
Copy link
Member

Update: As they're other possible mis-configurations I have moved all the configurations into the plugin render function. As such these will now be PL/SQL errors that show up when the page is run if the item configuration is invalid.

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

No branches or pull requests

3 participants