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

DateAndTime field doesn't accept "12:00 AM"

    Details

      Description

      Steps
      • Create a content type with a date time fieldtype
      • Create a content of the previous content type
      • On the date time fieldtype, fill in with "02/02/2015" and "12:00 AM"

      The fieldttype validation don't allow.
      If we replace the time by "12:01", then we are allowed to proceed.

        Issue Links

          Activity

          Paulo Nunes (Inactive) created issue -
          Paulo Nunes (Inactive) made changes -
          Field Original Value New Value
          Summary Datetime fieldtype don't accept 12:00 Am time Datetime fieldtype don't accept 12:00 Am
          Paulo Nunes (Inactive) made changes -
          Status Open [ 1 ] Confirmed [ 10037 ]
          Damien Pobel (Inactive) made changes -
          Summary Datetime fieldtype don't accept 12:00 Am DateAndTime field doesn't accept "12:00 AM"
          Damien Pobel (Inactive) made changes -
          Status Confirmed [ 10037 ] Open [ 1 ]
          Hide
          Damien Pobel (Inactive) added a comment -

          Do we support such input ? I mean as you reported in EZP-23925 (actually EZP-25180), the DateAndTime edit interface is "unfinished" in browsers not supporting "datetime" HTML input and I agree that what you should put in those inputs is far from being clear.

          I'd also like more details:

          • what is the error message in such case ?
          • does the "use seconds" option have an impact on that issue ?
          • does the "required" option have an impact on that issue ?
          Show
          Damien Pobel (Inactive) added a comment - Do we support such input ? I mean as you reported in EZP-23925 (actually EZP-25180 ), the DateAndTime edit interface is "unfinished" in browsers not supporting "datetime" HTML input and I agree that what you should put in those inputs is far from being clear. I'd also like more details: what is the error message in such case ? does the "use seconds" option have an impact on that issue ? does the "required" option have an impact on that issue ?
          Paulo Nunes (Inactive) made changes -
          Attachment timeError.png [ 25920 ]
          Hide
          Paulo Nunes (Inactive) added a comment - - edited

          Do we support such input ?

          That I cannot answer. Based on Time documentation, where it's said "The usage of 24h or 12AM/PM format is(...)" I would say yes. Otherwise, If not, I don't know how would we refer to midnight and noon. Roland Benedetti, can you please give us some input on this?

          what is the error message in such case ?

          "Time do not have a valid input". See image in attach

          does the "use seconds" option have an impact on that issue ?

          No. Having "12:00:00 AM" the validation fails.

          does the "required" option have an impact on that issue

          hmm. Yes it has. Having the "required" option, the validation passes and publishing is already possible.

          Show
          Paulo Nunes (Inactive) added a comment - - edited Do we support such input ? That I cannot answer. Based on Time documentation , where it's said "The usage of 24h or 12AM /PM format is(...) " I would say yes. Otherwise, If not, I don't know how would we refer to midnight and noon. Roland Benedetti , can you please give us some input on this? what is the error message in such case ? "Time do not have a valid input". See image in attach does the "use seconds" option have an impact on that issue ? No. Having "12:00:00 AM" the validation fails. does the "required" option have an impact on that issue hmm. Yes it has. Having the "required" option, the validation passes and publishing is already possible.
          Damien Pobel (Inactive) made changes -
          Priority High [ 3 ] Medium [ 4 ]
          Ricardo Correia (Inactive) made changes -
          Link This issue relates to EZP-25375 [ EZP-25375 ]
          Damien Pobel (Inactive) made changes -
          Link This issue relates to EZP-23925 [ EZP-23925 ]
          Hide
          Damien Pobel (Inactive) added a comment -

          This is happening because Firefox does not support the time HTML5 input. We have an improvement in jira for that EZP-23925 and the format "12:00 AM" is definitively something we should not accept.

          Show
          Damien Pobel (Inactive) added a comment - This is happening because Firefox does not support the time HTML5 input. We have an improvement in jira for that EZP-23925 and the format "12:00 AM" is definitively something we should not accept.
          Damien Pobel (Inactive) made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Resolution Invalid [ 6 ]
          Alex Schuster made changes -
          Workflow EZ* Development Workflow [ 96835 ] EZEE Development Workflow [ 125345 ]
          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open Confirmed Confirmed
          31s 1 Paulo Nunes 02/Dec/15 5:22 PM
          Confirmed Confirmed Open Open
          42m 14s 1 damien.pobel@ez.no 02/Dec/15 6:05 PM
          Open Open Closed Closed
          61d 20h 24m 1 damien.pobel@ez.no 02/Feb/16 2:29 PM

            People

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

              Dates

              • Created:
                Updated:
                Resolved: