due date fields allow non-sane due dates

Bug #1016102 reported by Joseph on 2012-06-21
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Medium
Unassigned

Bug Description

Evergreen Version 2.0.3+

On IRC bshum reports ' 3402-01-06 23:59:59-05' was an allowed due date, we may want dojo to check for unreasonable due dates before allowing them.

<bshum> '3402-01-06 23:59:59-05' for a due date. That looks almost like someone might have scanned an item barcode into a due date field? 34020 could be the prefix for items from a lib in our system.

Michael Peters (mrpeters) wrote :

Tested and confirmed in master (2506f44).

You can set a specific due date in the year 3402 and perform a checkout (technically valid, I guess) but the actual due date gets displayed as 13/31/69 10:59PM, however, which is strange.

Changed in evergreen:
status: New → Confirmed
importance: Undecided → Medium
Andrea Neiman (aneiman) wrote :

Not just a dojo thing, I was able to successfully check out an item in the web client on a 3.1.5 test system with a specific due date of 3028-04-04, which the web client happily accepted & displayed normally.

tags: added: checkout webstaffclient
removed: dojo
Rogan Hamby (rogan-hamby) wrote :

Do we want to put a cap on future checkouts? I.e. you can't set a custom due date more than 1 year in the future and control it via YAOUS?

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

Other bug subscribers