Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-25719

Incorrect Date fieldValue when timestamp is set to 0

    Details

      Description

      If the Date field is set to 1970-01-01 in UTC, the REST API gives null as its fieldValue instead of

      {timestamp: 0}

      Steps to reproduce (setting 1970-01-01UTC might be tricky, the easiest way I found was to update directly data_int column in ezcontentobject_attribute)

      1. create a Content Type with a Date field definition
      2. create a Content and set the Date to 1970-01-01
      3. Load the Content in the REST API, the fieldValue is null

        Issue Links

          Activity

          Hide
          Yannick Roger (Inactive) added a comment -

          The kernel patch for EZP-25375 is the fix for the Time fieldtype with the same case (timestamp 0). The solution might be quite similar.

          Show
          Yannick Roger (Inactive) added a comment - The kernel patch for EZP-25375 is the fix for the Time fieldtype with the same case (timestamp 0). The solution might be quite similar.

            People

            • Assignee:
              Unassigned
              Reporter:
              Damien Pobel (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: