-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Date Picker crashing CMS in list widget #1113
Comments
Error message being thrown when a date is selected:
|
Tracing the error, the last This means that for some reason when the date field is changed, |
@thebetternewt I have a fix for the crashing issue in the linked PR, it should be merged as soon as another maintainer can review. I think the weirdness of only the last date field showing a default should be a separate issue, would you wind splitting that out? The bug only happens if a date field is the first field under a list item. As a workaround until it is fixed, if you don't have any string fields that you have first, you can add a hidden field before the date fields, like so:
|
@tech4him1 Thanks! That seems to work. I decided to add a string label for each date range anyway for reference purposes, so good to know my code works. I'll put in a separate request for the default date not showing up. |
- Do you want to request a feature or report a bug?
- What is the current behavior?
- If the current behavior is a bug, please provide the steps to reproduce.
- What is the expected behavior?
- Please mention your CMS, node.js, and operating system version.
- Please link or paste your
config.yml
below if applicable.I am trying to add a list widget with multiple date fields. However, the first field in the list crashes the CMS when I pick a date from the datepicker widget. With multiple date fields present, the last one also seems to be the only one showing today's date as default. Fields do not seem to be responding to default values described in config.yml.
Here is my config file:
config.yml
The list is under the "date_settings" file declaration, under "blackout_dates".
Thanks!
The text was updated successfully, but these errors were encountered: