You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Jorge Alberto Londoño Giraldo (JIRA)" <ji...@apache.org> on 2017/03/24 23:04:42 UTC
[jira] [Updated] (OPENMEETINGS-1610) "'timepicker' is not a valid
LocalTime
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jorge Alberto Londoño Giraldo updated OPENMEETINGS-1610:
--------------------------------------------------------
Description: When selecting class schedule different from the current one, the format changes from 10:00 PM to 10:00 p. m. So an error message that says "'timepicker' is not a valid LocalTime ' .. .That is PM to p. m. Therefore the format is incorrect. (was: When selecting class schedule different from the current one, the format changes from 10:00 PM to 10:00 p. m. So an error message that says "'timepicker' is not a valid LocalTime ' .. .That is PM to p. M. Therefore the format is incorrect.)
> "'timepicker' is not a valid LocalTime
> ---------------------------------------
>
> Key: OPENMEETINGS-1610
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1610
> Project: Openmeetings
> Issue Type: Bug
> Components: HTML5/Calendar
> Affects Versions: 3.2.1
> Environment: Ubuntu 16.04
> Reporter: Jorge Alberto Londoño Giraldo
> Assignee: Maxim Solodovnik
> Labels: calendar, date, timepicker
> Attachments: Captura de pantalla 2017-03-23 a las 7.45.19 p.m..png
>
>
> When selecting class schedule different from the current one, the format changes from 10:00 PM to 10:00 p. m. So an error message that says "'timepicker' is not a valid LocalTime ' .. .That is PM to p. m. Therefore the format is incorrect.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)