You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Adrian Crum (JIRA)" <ji...@apache.org> on 2013/11/04 12:51:17 UTC

[jira] [Commented] (OFBIZ-5382) Additional ship group renderDateFields not created

    [ https://issues.apache.org/jira/browse/OFBIZ-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812781#comment-13812781 ] 

Adrian Crum commented on OFBIZ-5382:
------------------------------------

Patch file names should end with .patch or .diff.

https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Contributors+Best+Practices


> 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
>            Priority: Minor
>         Attachments: ordershipinginfo.ftl
>
>
> 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)