[
https://issues.apache.org/jira/browse/OFBIZ-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacques Le Roux closed OFBIZ-5850.
----------------------------------
Resolution: Fixed
Fix Version/s: 13.07.02
12.04.06
Upcoming Branch
Thanks Gareth well spotted,
Your slightly mofidied patch is in
trunk r1641066
R13.07 r1641068
R12.04 r1641069
I simply removed the line added in the block which remove the dot and 000 ms in date/time string. I did not see any reason why this was needed. I modified the comment on this block for faster understanding.
> <@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)
Locked
