Details

      Description

      if one has an ezdatetime as Required, no content can be created using 00:00 as the time part.

      Steps to reproduce:
      • create a custom Content Type
      • add an ezdatetime, marked as Required with Empty as default value
      • attempt to create content, setting the value as 1/1/1990 00:00 (for instance)
        => Publishing operation will fail with the following error message

        {
            "ErrorMessage": {
                "_media-type": "application\/vnd.ez.api.ErrorMessage+json",
                "errorCode": 400,
                "errorMessage": "Bad Request",
                "errorDescription": "Value for required field definition 'my_date_time_field' with language 'eng-GB' is empty",
        ....
            }
        }
        

      The same problems happens on Time fields (actually that's even worse because the kernel also has a bug on handling this case)

      Also the display of empty Time and date and Time fields must be fixed (as explained in EZP-25270).

      • Create a ContentType with a "Time" a "Date and Time" field.
      • Create a new content based on this content type.
      • As time use 00:00
      • As dateandtime use 01/01/1970 00:00 on UTC time. So consider your timezone while entering, for example on my timezone (France in daylight saving time) I had to enter 01/01/1970 01:00

        Issue Links

          Activity

          Hide
          Rui Silva (Inactive) added a comment -

          Closing as fixed, as most time/date-related issues will be taken care of on the epic EZP-25545, as per [~yannick.roger@ez.no]'s instruction.

          Show
          Rui Silva (Inactive) added a comment - Closing as fixed, as most time/date-related issues will be taken care of on the epic EZP-25545 , as per [~yannick.roger@ez.no] 's instruction.
          Hide
          Yannick Roger (Inactive) added a comment -

          The behavior that is blocking this issue is actually EZP-23925.
          Most of the time related issues you are talking about have been added in a new EPIC ( EZP-25545 ) and should be tackled very soon.
          If you don't find anything new on this one you can mark it as fixed.

          Show
          Yannick Roger (Inactive) added a comment - The behavior that is blocking this issue is actually EZP-23925 . Most of the time related issues you are talking about have been added in a new EPIC ( EZP-25545 ) and should be tackled very soon. If you don't find anything new on this one you can mark it as fixed.
          Show
          Yannick Roger (Inactive) added a comment - - edited Fix on Platform UI: https://github.com/ezsystems/PlatformUIBundle/commit/0491f9137f61ab4475df201352f3e5fe694c4558 Fix on kernel: https://github.com/ezsystems/ezpublish-kernel/commit/2883bced3ceae1ca1ee8798990e3370d347e2eed
          Hide
          Yannick Roger (Inactive) added a comment -

          EZP-25270 use case should also be considered during this fix.

          Show
          Yannick Roger (Inactive) added a comment - EZP-25270 use case should also be considered during this fix.
          Show
          Yannick Roger (Inactive) added a comment - - edited PR on Platform UI: https://github.com/ezsystems/PlatformUIBundle/pull/501 PR on the kernel: https://github.com/ezsystems/ezpublish-kernel/pull/1565
          Hide
          Joaquim Cavalleri (Inactive) added a comment - - edited

          In my opinion, Paulo Nunes, these issues seem definitely related. However, if I understood correctly, the use cases in the other issues are not dumping an "is empty" error result, are they?

          Show
          Joaquim Cavalleri (Inactive) added a comment - - edited In my opinion, Paulo Nunes , these issues seem definitely related. However, if I understood correctly, the use cases in the other issues are not dumping an "is empty" error result, are they?
          Hide
          Paulo Nunes (Inactive) added a comment - - edited

          [~joaquim.cavalleri@ez.no] Please evaluate if this customer issue is not within EZP-25179 or EZP-23925 scope.

          Show
          Paulo Nunes (Inactive) added a comment - - edited [~joaquim.cavalleri@ez.no] Please evaluate if this customer issue is not within EZP-25179 or EZP-23925 scope.

            People

            • Assignee:
              Unassigned
              Reporter:
              Joaquim Cavalleri (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: