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

          Joaquim Cavalleri (Inactive) created issue -
          Joaquim Cavalleri (Inactive) made changes -
          Field Original Value New Value
          Description if one has an ezdatetime as Required, no content can be created using 00:00 as the time part.

          h5.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
          {quote}
          {
              "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",
          ....
              }
          }
          {quote}
          if one has an ezdatetime as Required, no content can be created using 00:00 as the time part.

          h5.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
          {code}
          {
              "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",
          ....
              }
          }
          {code}
          Joaquim Cavalleri (Inactive) made changes -
          Status Open [ 1 ] Confirmed [ 10037 ]
          Joaquim Cavalleri (Inactive) made changes -
          Component/s Studio UI [ 13545 ]
          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.
          Łukasz Serwatka made changes -
          Project eZ Studio [ 11800 ] eZ Publish / Platform [ 10401 ]
          Key EZS-482 EZP-25375
          Component/s Platform UI (Admin UI & Content UI) [ 10301 ]
          Component/s Studio UI [ 13545 ]
          Affects Version/s 2015.12 [ 14489 ]
          Affects Version/s 2015.12 [ 14504 ]
          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?
          Ricardo Correia (Inactive) made changes -
          Fix Version/s Customer request [ 11018 ]
          Ricardo Correia (Inactive) made changes -
          Link This issue relates to EZP-25179 [ EZP-25179 ]
          Ricardo Correia (Inactive) made changes -
          Link This issue relates to EZP-23925 [ EZP-23925 ]
          Ricardo Correia (Inactive) made changes -
          Status Confirmed [ 10037 ] InputQ [ 10001 ]
          Damien Pobel (Inactive) made changes -
          Component/s Platform/REST API v2 [ 10310 ]
          Yannick Roger (Inactive) made changes -
          Assignee Yannick Roger [ yannick.roger@ez.no ]
          Yannick Roger (Inactive) made changes -
          Status InputQ [ 10001 ] Development [ 3 ]
          Yannick Roger (Inactive) made changes -
          Summary Setting time to 00h00 invalidates Required date/time fields' value Impossible to store time with value 00:00 on required fields
          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
          Yannick Roger (Inactive) made changes -
          Remote Link This issue links to "PR on Platform UI (Web Link)" [ 16128 ]
          Yannick Roger (Inactive) made changes -
          Description if one has an ezdatetime as Required, no content can be created using 00:00 as the time part.

          h5.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
          {code}
          {
              "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",
          ....
              }
          }
          {code}
          if one has an ezdatetime as Required, no content can be created using 00:00 as the time part.

          h5.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
          {code}
          {
              "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",
          ....
              }
          }
          {code}

          *The same problems happens on Time fields*
          Yannick Roger (Inactive) made changes -
          Description if one has an ezdatetime as Required, no content can be created using 00:00 as the time part.

          h5.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
          {code}
          {
              "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",
          ....
              }
          }
          {code}

          *The same problems happens on Time fields*
          if one has an ezdatetime as Required, no content can be created using 00:00 as the time part.

          h5.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
          {code}
          {
              "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",
          ....
              }
          }
          {code}

          *The same problems happens on Time fields (actually that's even worse because the kernel also has a bug on handling this case)*
          Yannick Roger (Inactive) made changes -
          Status Development [ 3 ] Development Review [ 10006 ]
          Yannick Roger (Inactive) made changes -
          Link This issue testing discovered EZP-25424 [ EZP-25424 ]
          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.
          Yannick Roger (Inactive) made changes -
          Link This issue relates to EZP-25270 [ EZP-25270 ]
          Yannick Roger (Inactive) made changes -
          Description if one has an ezdatetime as Required, no content can be created using 00:00 as the time part.

          h5.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
          {code}
          {
              "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",
          ....
              }
          }
          {code}

          *The same problems happens on Time fields (actually that's even worse because the kernel also has a bug on handling this case)*
          if one has an ezdatetime as Required, no content can be created using 00:00 as the time part.

          h5.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
          {code}
          {
              "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",
          ....
              }
          }
          {code}

          *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
          Yannick Roger (Inactive) made changes -
          Summary Impossible to store time with value 00:00 on required fields Timestamps 0 are not handled properly
          Yannick Roger (Inactive) made changes -
          Link This issue testing discovered EZP-25459 [ EZP-25459 ]
          Damien Pobel (Inactive) made changes -
          Environment eZ Studio 15.12 eZ Platform 15.12
          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
          Yannick Roger (Inactive) made changes -
          Fix Version/s 2016.02 [ 14501 ]
          Yannick Roger (Inactive) made changes -
          Status Development Review [ 10006 ] Documentation Review done [ 10011 ]
          Assignee Yannick Roger [ yannick.roger@ez.no ]
          Rui Silva (Inactive) made changes -
          Status Documentation Review done [ 10011 ] QA [ 10008 ]
          Rui Silva (Inactive) made changes -
          Flagged Impediment [ 10000 ]
          Paulo Nunes (Inactive) made changes -
          Link This issue relates to EZP-25276 [ EZP-25276 ]
          Rui Silva (Inactive) made changes -
          Status QA [ 10008 ] InputQ [ 10001 ]
          Assignee Rui Silva [ rui.silva@ez.no ]
          Yannick Roger (Inactive) made changes -
          Status InputQ [ 10001 ] Development [ 3 ]
          Assignee Yannick Roger [ yannick.roger@ez.no ]
          André Rømcke made changes -
          Fix Version/s 2016.02.1 [ 14515 ]
          Fix Version/s 2016.02 [ 14501 ]
          André Rømcke made changes -
          Fix Version/s 2016.02 [ 14501 ]
          Fix Version/s 2016.02.1 [ 14515 ]
          André Rømcke made changes -
          Fix Version/s 2016.02.1 [ 14516 ]
          Fix Version/s 2016.02 [ 14501 ]
          Yannick Roger (Inactive) made changes -
          Epic Link EZP-25545 [ 53511 ]
          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.
          Yannick Roger (Inactive) made changes -
          Status Development [ 3 ] Development Review [ 10006 ]
          Yannick Roger (Inactive) made changes -
          Status Development Review [ 10006 ] Documentation Review done [ 10011 ]
          Fix Version/s 16.02 [ 14501 ]
          Fix Version/s 16.02.1 [ 14516 ]
          Assignee Yannick Roger [ yannick.roger@ez.no ]
          Rui Silva (Inactive) made changes -
          Status Documentation Review done [ 10011 ] QA [ 10008 ]
          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.
          Rui Silva (Inactive) made changes -
          Assignee Rui Silva [ rui.silva@ez.no ]
          Status QA [ 10008 ] Closed [ 6 ]
          Resolution Fixed [ 1 ]
          Yannick Roger (Inactive) made changes -
          Link This issue relates to EZP-25719 [ EZP-25719 ]
          Alex Schuster made changes -
          Workflow EZ* Development Workflow [ 97398 ] EZEE Development Workflow [ 125470 ]
          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open Confirmed Confirmed
          5m 47s 1 joaquim.cavalleri@ez.no 12/Jan/16 4:34 PM
          Confirmed Confirmed InputQ InputQ
          20h 27m 1 ricardo.correia@ez.no 13/Jan/16 1:01 PM
          QA QA InputQ InputQ
          3d 22h 25m 1 rui.silva@ez.no 29/Feb/16 9:10 AM
          InputQ InputQ Development Development
          12d 3h 8m 2 yannick.roger@ez.no 29/Feb/16 10:17 AM
          Development Development Development Review Development Review
          9d 5h 23m 2 yannick.roger@ez.no 08/Mar/16 3:22 PM
          Development Review Development Review Documentation Review done Documentation Review done
          29d 18h 37m 2 yannick.roger@ez.no 08/Mar/16 3:23 PM
          Documentation Review done Documentation Review done QA QA
          1h 55m 2 rui.silva@ez.no 08/Mar/16 4:32 PM
          QA QA Closed Closed
          2m 5s 1 rui.silva@ez.no 08/Mar/16 4:34 PM

            People

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

              Dates

              • Created:
                Updated:
                Resolved: