[
https://issues.apache.org/jira/browse/OFBIZ-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222158#comment-14222158
]
Gareth Carter commented on OFBIZ-5850:
--------------------------------------
Thanks Jacques.
The code to remove the ms was something else I was testing and snuck into that
patch, apologies for that.
However, I do believe removing the ms is valid because it prevents the jquery
datetimepicker from setting the time in the popup from an existing value. For
this I will create another jira.
> <@htmlTemplate.renderDateTimeField does not parse date string based on input
> format
> -----------------------------------------------------------------------------------
>
> Key: OFBIZ-5850
> URL: https://issues.apache.org/jira/browse/OFBIZ-5850
> Project: OFBiz
> Issue Type: Bug
> Affects Versions: Release Branch 13.07, Trunk
> Reporter: Gareth Carter
> Assignee: Jacques Le Roux
> Priority: Critical
> Fix For: Upcoming Branch, 12.04.06, 13.07.02
>
> Attachments: 1637919.patch
>
>
> Commit 1626419 changed htmlFormMacroLibrary.ftl renderDateTimeField to use
> Date.parse instead of Date.parseExact.
> https://code.google.com/p/datejs/wiki/APIDocumentation states Date.parse will
> use current CultureInfo for formats but for parsing ISO yyyy-MM-dd from
> hidden field, need to use parseExact.
> I spotted this when CultureInfo was en-GB and selecting 2014-11-01 on any
> date field (i18n field displays 11/01/2014 instead of 01/11/2014)
> For November all days after the 12th display correctly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
