[ 
https://issues.apache.org/jira/browse/OFBIZ-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux closed OFBIZ-5382.
----------------------------------

       Resolution: Fixed
    Fix Version/s: Release Branch 13.07
                   Release Branch 12.04
                   SVN trunk
                   Release Branch 11.04
         Assignee: Jacques Le Roux

Thanks Christian,

Well spotted, always the 2 annoying 1st line from Eclipse (use project option 
not workspace when creating the patch)

Your patch is commited in trunk at r1539147
Backported in
R13.07 r1539150
R12.04 r1539151
R11.04 r1539152


> Additional ship group renderDateFields not created 
> ---------------------------------------------------
>
>                 Key: OFBIZ-5382
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5382
>             Project: OFBiz
>          Issue Type: Bug
>    Affects Versions: SVN trunk
>            Reporter: Christian Carlow
>            Assignee: Jacques Le Roux
>            Priority: Minor
>             Fix For: Release Branch 11.04, SVN trunk, Release Branch 12.04, 
> Release Branch 13.07
>
>         Attachments: ordershipinginfo.ftl.diff
>
>
> ShipBeforeDate/ShipAfterDate fields are not created as renderDateFields for 
> additional ship groups on orderview page.
> The problem is that additional ship groups share the same id as the first 
> ship group date fields.  The javascript renderDateField logic requires unique 
> ids the all fields that are supposed to be created by renderDateField.
> To reproduce:
> 1.  Create an order for DemoCustCompany
> 2.  Add 10 GZ-BASKET products to the order and click "Finalize Order"
> 3.  Add an additional ship group and click "Continue"
> 4.  Assign 5 of GZ-BASKET to second ship group and click "Continue"
> 5.  Complete the remaining steps required to complete the order 
> 6.  On the page after the "Create Order" link is clicked, notice the date 
> fields of the second ship group were not rendered with a calendar.  



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to