Bug #8797

Users can enter year '0000' for creation (and other?) events

Added by Mike Gale over 6 years ago. Updated over 5 years ago.

Status:NewStart date:08/11/2015
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Form validation
Target version:-
Google Code Legacy ID: Tested version:2.3
Sponsored:No Requires documentation:

Description

To reproduce:

1. Create an archival description
2. Set creation end date to 0000-00-00
3. Save

Result: An end date of 0000-00-00 is inserted into the MySQL database
Expected result: We should have validation in place to prevent year 0000, since such a year doesn't exist and doesn't really make sense.


Related issues

Related to Access to Memory (AtoM) - Bug #8796: Year 0000 event dates in MySQL crash ES when using search... Verified 08/11/2015

History

#1 Updated by Mike Gale over 6 years ago

  • Related to Bug #8796: Year 0000 event dates in MySQL crash ES when using search:populate added

#2 Updated by Mike Gale over 6 years ago

  • Assignee deleted (Jesús García Crespo)

#3 Updated by Mike Gale over 6 years ago

This might require significant work. E.g.:

  1. Identifying all date fields in AtoM where the user can enter year 0000 and where that doesn't make sense
  2. Creating validators for the dates entered in all templates (ISAD, RAD, etc.)

#5 Updated by Dan Gillean over 5 years ago

  • Target version deleted (Release 2.3.0)

Also available in: Atom PDF