Issue Bug Closed

#92306Field with dbType = 'time' and eval 'time' not saved correctly to the database

Thorben Nissen 09/14/20, 21:11 updated 07/27/24, 16:10

Description

When using native timefield in database and input with eval ‘time’, the entered value is not correctly saved in the database. When showing the form again, that wrong value from the database is shown.

When the field is changed, the new value is internally stored as an integer in the backend interface. When submitted it is then used as date string, when converting the field value to a timestamp, which leads to a wrong datetime.

To reproduce configure a field as follows:
  • database field is set to time
  • field TCA type set to input
  • field TCA dbType set to time
  • field TCA eval set to time

This behaviour is present in v9, v10 and master.

Reviews 1

History 27

  1. Gerrit Code Review pushed patch set 1 for master to change 65735 status New Under Review 09/14/20, 21:33

  2. Gerrit Code Review pushed patch set 2 for master to change 65735 11/18/21, 10:36

  3. Gerrit Code Review pushed patch set 3 for master to change 65735 11/25/21, 20:50

  4. Gerrit Code Review pushed patch set 4 for main to change 65735 11/29/21, 14:06

  5. Gerrit Code Review pushed patch set 5 for main to change 65735 05/03/23, 09:18

  6. Benni Mack commented and changed status Under Review Needs Feedback 07/04/23, 20:28

    Can you check if the problem still exists in v12+ ?

  7. Georg Ringer commented and changed status Needs Feedback Closed 07/27/24, 16:10

    closing cause lack of feedback. a lot changed in latest version.

    if still valid in v13, please open a new issue and reference this one or contact me on slack. thanks