web client serials: create subscriptions fails silently unless date is YYYY-MM-DD

Bug #1731010 reported by Andrea Neiman
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Medium
Unassigned

Bug Description

Web Client 3.0

Create Subscription wants you to use the date picker for subscription start & end date. It does not check any date entry preference setting.

You can type in the date as YYYY-MM-DD (which is what the picker will enter the date as) but any other typed entry will result in the subscription silently failing to save.

There is an error message in console, but no user-visible message that the subscription has failed to save, or why it has failed to save.

Revision history for this message
Remington Steed (rjs7) wrote :

Very closely related, trying to save a subscription with a blank Start Date also fails silently, except for errors in the console.

Revision history for this message
Remington Steed (rjs7) wrote :

For the record, the empty start date field causes this error:

ERROR: null value in column "start_date" violates not-null constraint

Revision history for this message
John Amundson (jamundson) wrote :

Tested in Web Client 3.0.3.
Subscription fails to save unless date in YYYY-MM-DD format. Fails without user-visible message. Tested both blank date and wrong format.

Changed in evergreen:
status: New → Confirmed
Revision history for this message
John Amundson (jamundson) wrote :

Update to this bug with a little clarification.

The subscription will fail to save if the date is blank or NOT in the date format defined by the library setting for "Deprecated:Format Dates with this pattern".

We updated the Format Dates settings to MM-dd-yyyy, and the subscription now needs the date in this format.

There should definitely be some form of visual indication why the subscription fails to save, (i.e. the date box could become yellow similar to date fields in Patron Registration).

tags: removed: webstaffclient
Revision history for this message
Erica Rohlfs (erohlfs) wrote :

I just tested in version 3.7 and see the behavior Andrea describes. I adjusted the date format to MM-dd-yyyy in the library settings, and that didn't appear to affect the need to use a YYYY-MM-DD when creating a subscription on this sandbox. I'm wondering if the format issue is partially related to https://bugs.launchpad.net/evergreen/+bug/1843917

Changed in evergreen:
importance: Undecided → Medium
tags: added: needsdiscussion
Revision history for this message
Chrisy Schroth (cschroth) wrote (last edit ):

Just tested on Bug Squashing Week test server Blake's test server, bugsquash.mobiusconsortium.org, Evergreen version "HEAD".

Attempted to create a subscription on TCN 237 to test another bug, and decided to try entering MM-DD-YYYY instead of YYYY-MM-DD to test this one as well. Subscription creation failed silently, just sits there as if waiting for you to do/click something else.

Used the calendar to pick the correct date format and clicked Save again so I could proceed with creating the subscription and test the other bug. It appeared to fail silently, as again there was no change to the screen and I was able to continue to click Save multiple times and a new subscription was not visible in the list at the bottom of the page. When I refreshed the page to start over again, it had actually created 2 subscriptions, although I was unable to see/use/interact with either of them without refreshing.

Deleted both those subscriptions and tried to duplicate the previous exercise, but I changed the Distribution Label each time I clicked Save. It created 3 different, nearly identical subscriptions which never appeared on the screen until after reloading the Manage Subscriptions interface.

**Edit to say that this actually might be something with this server. I just tried to create a Prediction Pattern for the subscription that I left and it wouldn't allow me to create one. I deleted the whole whole subscription and started over, creating it correctly the first time, and it again failed silently, but was there when I refreshed the Manage Subscriptions window.

Revision history for this message
Terran McCanna (tmccanna) wrote :

Chrisy - there was another patch on that test server that was causing problems if you want to try this one again

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.