We recently upgraded from atom 2.6 to 2.6.4 and have run into a show stopping bug.
The first screenshot shows the focus on a date field in a test record. The sidebar indicates that YYYY is a valid date and year is what we typically use, as anything else would be misleading.
When I enter the date 1988 and click save I get a 500 internal server error (see screenshot 2)
It appears to be trying to insert the date 1988-0-0, which is of course an invalid date. Checking the webserver logs confirms this:2022/08/13 19:19:06 [error] 242#242: *1654 FastCGI sent in stderr: "PHP message: Unable to execute INSERT statement. [wrapped: SQLSTATE: Invalid datetime format: 1292 Incorrect date value: '1988-0-0' for column 'start_date' at row 1]" while reading response header from upstream, client: 127.0.0.1, server: _, request: "POST /index.php/test/edit HTTP/1.1", upstream: "fastcgi://unix:/run/php7.2-fpm.atom.sock:", host: "erap-atx:8084", referrer: "http://catalog.episcopalarchives.org/index.php/test/edit"
The problem is really in the database schema: Given that this field is set to datetime format, one cannot
enter just a year. See the mysql documentation for details: https://dev.mysql.com/doc/refman/8.0/en/datetime.html
Let me stress that we can't use atom if it becomes impossible to specify things like Creation time as a year only. Putting in a precise date would be misleading to our users when often we don't have this information.