[
https://issues.apache.org/jira/browse/OPENMEETINGS-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940902#comment-15940902
]
Jorge Alberto Londoño Giraldo edited comment on OPENMEETINGS-1610 at 3/24/17
6:38 PM:
--------------------------------------------------------------------------------------
Hello, in the system configuration America/Bogota an user America/Bogota I also
tried Etc / GMT+5, As I see it is not by the user's timezone it is by the
format changing from (AM / PM) to (a.m. p.m.) Lowercase and those points do
not accept them.
was (Author: jorgelondo):
Hello, in the system configuration America/Bogota an user America/Bogota I also
tried Etc / GMT-5, As I see it is not by the user's timezone it is by the
format changing from (AM / PM) to (a.m. p.m.) Lowercase and those points do
not accept them.
> "'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)
