date:20150529


[ 
https://issues.apache.org/jira/browse/OFBIZ-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564599#comment-14564599
 ] 

Pierre Smits commented on OFBIZ-6429:
-

This also applies when the start form uses an alt-target setting, as in e.g.:
{code}
form name=EditVendor type=single target=updateVendor title= 
default-map-name=vendor
actions
entity-one entity-name=Vendor value-field=vendor/
/actions
alt-target use-when=partyId==null target=createVendor/
alt-target use-when=partyId!=nullamp;amp;vendor!=null 
target=updateVendor/
   .
/form
{code}


 For lookup fields in sub forms (skip-start + skip-end), the value of the 
 form-name attribute should be dynamically rendered
 ---

 Key: OFBIZ-6429
 URL: https://issues.apache.org/jira/browse/OFBIZ-6429
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: Trunk
Reporter: Pierre Smits
  Labels: dynamic, forms
 Fix For: Upcoming Branch


 The solution in OFBIZ-6139 means hard-codedness of the value of the form-name 
 attribute of a field. 
 As shown in following example:
 {code}
 form name=RequestItemProduct type=single skip-start=true 
 skip-end=true
 field name=productId title=${uiLabelMap.CommonProduct} 
 form-name=EditCustRequestItem
 lookup target-form-name=LookupProduct 
 description-field-name=productName show-description=false/
 /field
 field name=productName form-name=EditCustRequestItem 
 position=2text read-only=true//field
 field name=quantity title=${uiLabelMap.CommonQuantity}text 
 size=10//field
 /form
 {code}
 However when the start form changes based on conditions in the screen 
 (parameters, etc), the lookup field won't work due to this hard-codedness.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6139) Lookup fields break when used with a form having skip-start=true


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

Jacques Le Roux updated OFBIZ-6139:
---
Description: 
We neglected this aspect so far. Adding a form-name attribute to the field 
element of the lookup fixes it. The value of form-name attribute must be the 
name of the parent form, ie the 1st form (the one with skip-end=true) which 
precedes the current form (with skip-start=true).

If you use a related description field (using the description-field-name 
attribute of the lookup element) you will need to put the form-name attribute 
in this field element too.

  was:
We neglected this aspect so far. Adding a form-name attribute to the field 
element of the lookup fixes it. The value of form-name attribute must be the 
name of 1st form (the one with skip-end=true) which precede the current form 
(with skip-start=true).

If you use a related description field (using the description-field-name 
attribute of the lookup element) you will need to put the form-name attribute 
in this field element too.


 Lookup fields break when used with a form having skip-start=true
 --

 Key: OFBIZ-6139
 URL: https://issues.apache.org/jira/browse/OFBIZ-6139
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Minor
  Labels: lookup
 Fix For: 14.12.01, 12.04.06, 13.07.02, Upcoming Branch


 We neglected this aspect so far. Adding a form-name attribute to the field 
 element of the lookup fixes it. The value of form-name attribute must be 
 the name of the parent form, ie the 1st form (the one with skip-end=true) 
 which precedes the current form (with skip-start=true).
 If you use a related description field (using the description-field-name 
 attribute of the lookup element) you will need to put the form-name 
 attribute in this field element too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6139) Lookup fields break when used with a form having skip-start=true


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

Jacques Le Roux updated OFBIZ-6139:
---
Description: 
We neglected this aspect so far. Adding a form-name attribute to the field 
element of the lookup fixes it. 

The value of form-name attribute must be the name of the parent form, ie 
the 1st form (the one with skip-end=true) which precedes the current form 
(which has skip-start=true).

If you use a related description field (using the description-field-name 
attribute of the lookup element) you need to put the form-name attribute in 
this field element too.

  was:
We neglected this aspect so far. Adding a form-name attribute to the field 
element of the lookup fixes it. The value of form-name attribute must be the 
name of the parent form, ie the 1st form (the one with skip-end=true) which 
precedes the current form (with skip-start=true).

If you use a related description field (using the description-field-name 
attribute of the lookup element) you will need to put the form-name attribute 
in this field element too.


 Lookup fields break when used with a form having skip-start=true
 --

 Key: OFBIZ-6139
 URL: https://issues.apache.org/jira/browse/OFBIZ-6139
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Minor
  Labels: lookup
 Fix For: 14.12.01, 12.04.06, 13.07.02, Upcoming Branch


 We neglected this aspect so far. Adding a form-name attribute to the field 
 element of the lookup fixes it. 
 The value of form-name attribute must be the name of the parent form, ie 
 the 1st form (the one with skip-end=true) which precedes the current form 
 (which has skip-start=true).
 If you use a related description field (using the description-field-name 
 attribute of the lookup element) you need to put the form-name attribute in 
 this field element too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-6429) For lookup fields in sub forms (skip-start + skip-end), the value of the form-name attribute should be dynamically rendered

Pierre Smits created OFBIZ-6429:
---

 Summary: For lookup fields in sub forms (skip-start + skip-end), 
the value of the form-name attribute should be dynamically rendered
 Key: OFBIZ-6429
 URL: https://issues.apache.org/jira/browse/OFBIZ-6429
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: Trunk
Reporter: Pierre Smits


The solution in OFBIZ-6139 means hard-codedness of the value of the form-name 
attribute of a field. 
As shown in following example:
{code}
form name=RequestItemProduct type=single skip-start=true skip-end=true
field name=productId title=${uiLabelMap.CommonProduct} 
form-name=EditCustRequestItem
lookup target-form-name=LookupProduct 
description-field-name=productName show-description=false/
/field
field name=productName form-name=EditCustRequestItem 
position=2text read-only=true//field
field name=quantity title=${uiLabelMap.CommonQuantity}text 
size=10//field
/form
{code}

However when the start form changes based on conditions in the screen 
(parameters, etc), the lookup field won't work due to this hard-codedness.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6429) For lookup fields in sub forms (skip-start + skip-end), the value of the form-name attribute should be dynamically rendered


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

Pierre Smits updated OFBIZ-6429:

Labels: dynamic forms  (was: )

 For lookup fields in sub forms (skip-start + skip-end), the value of the 
 form-name attribute should be dynamically rendered
 ---

 Key: OFBIZ-6429
 URL: https://issues.apache.org/jira/browse/OFBIZ-6429
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: Trunk
Reporter: Pierre Smits
  Labels: dynamic, forms
 Fix For: Upcoming Branch


 The solution in OFBIZ-6139 means hard-codedness of the value of the form-name 
 attribute of a field. 
 As shown in following example:
 {code}
 form name=RequestItemProduct type=single skip-start=true 
 skip-end=true
 field name=productId title=${uiLabelMap.CommonProduct} 
 form-name=EditCustRequestItem
 lookup target-form-name=LookupProduct 
 description-field-name=productName show-description=false/
 /field
 field name=productName form-name=EditCustRequestItem 
 position=2text read-only=true//field
 field name=quantity title=${uiLabelMap.CommonQuantity}text 
 size=10//field
 /form
 {code}
 However when the start form changes based on conditions in the screen 
 (parameters, etc), the lookup field won't work due to this hard-codedness.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6139) Lookup fields break when used with a form having skip-start=true


[ 
https://issues.apache.org/jira/browse/OFBIZ-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564542#comment-14564542
 ] 

Jacques Le Roux commented on OFBIZ-6139:


While testing the feature, Pierre Smits wanted to have form-name dynamic (using 
form-name=${name}). Then the form-name attrbute should support 
FlexibleStringExpander. This could be another Jira...

 Lookup fields break when used with a form having skip-start=true
 --

 Key: OFBIZ-6139
 URL: https://issues.apache.org/jira/browse/OFBIZ-6139
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Minor
  Labels: lookup
 Fix For: 14.12.01, 12.04.06, 13.07.02, Upcoming Branch


 We neglected this aspect so far. Adding a form-name attribute to the field 
 element of the lookup fixes it. 
 The value of form-name attribute must be the name of the parent form, ie 
 the 1st form (the one with skip-end=true) which precedes the current form 
 (which has skip-start=true).
 If you use a related description field (using the description-field-name 
 attribute of the lookup element) you need to put the form-name attribute in 
 this field element too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-6139) Lookup fields break when used with a form having skip-start=true


[ 
https://issues.apache.org/jira/browse/OFBIZ-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564542#comment-14564542
 ] 

Jacques Le Roux edited comment on OFBIZ-6139 at 5/29/15 10:31 AM:
--

While testing the feature, Pierre Smits wanted to have form-name dynamic by 
using {code}form-name=${name}{code}. Then the form-name attrbute should 
support FlexibleStringExpander. This could be another Jira...


was (Author: jacques.le.roux):
While testing the feature, Pierre Smits wanted to have form-name dynamic 
{code}(using form-name=${name}){code}. Then the form-name attrbute should 
support FlexibleStringExpander. This could be another Jira...

 Lookup fields break when used with a form having skip-start=true
 --

 Key: OFBIZ-6139
 URL: https://issues.apache.org/jira/browse/OFBIZ-6139
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Minor
  Labels: lookup
 Fix For: 14.12.01, 12.04.06, 13.07.02, Upcoming Branch


 We neglected this aspect so far. Adding a form-name attribute to the field 
 element of the lookup fixes it. 
 The value of form-name attribute must be the name of the parent form, ie 
 the 1st form (the one with skip-end=true) which precedes the current form 
 (which has skip-start=true).
 If you use a related description field (using the description-field-name 
 attribute of the lookup element) you need to put the form-name attribute in 
 this field element too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-6139) Lookup fields break when used with a form having skip-start=true


[ 
https://issues.apache.org/jira/browse/OFBIZ-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564549#comment-14564549
 ] 

Pierre Smits edited comment on OFBIZ-6139 at 5/29/15 10:39 AM:
---

Having to have the form name hard coded in the field as in:
{code}
form name=RequestItemProduct type=single skip-start=true skip-end=true
field name=productId title=${uiLabelMap.CommonProduct} 
form-name=EditCustRequestItem
lookup target-form-name=LookupProduct 
description-field-name=productName show-description=false/
/field
field name=productName form-name=EditCustRequestItem 
position=2text read-only=true//field
field name=quantity title=${uiLabelMap.CommonQuantity}text 
size=10//field
/form
leads to a degradation in functionality. Such a form can be used only with one 
start form.

With dynamic form building whereby the start-form might be conditionally 
defined (based on parameter values), the form name required in the lookup 
fields of the injectable sub-forms should change accordingly.



was (Author: pfm.smits):
Having to have the form name hard coded in the field as in:
{code}
form name=RequestItemProduct type=single skip-start=true skip-end=true
field name=productId title=${uiLabelMap.CommonProduct}
lookup target-form-name=LookupProduct 
description-field-name=productName show-description=false/
/field
field name=productName form-name=EditCustRequestItem 
position=2text read-only=true//field
field name=quantity title=${uiLabelMap.CommonQuantity}text 
size=10//field
 /form
{code}
leads to a degradation in functionality.

With dynamic form building whereby the start-form might be conditionally 
defined (based on parameter values), the form name required in the lookup 
fields of the injectable sub-forms should change accordingly.


 Lookup fields break when used with a form having skip-start=true
 --

 Key: OFBIZ-6139
 URL: https://issues.apache.org/jira/browse/OFBIZ-6139
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Minor
  Labels: lookup
 Fix For: 14.12.01, 12.04.06, 13.07.02, Upcoming Branch


 We neglected this aspect so far. Adding a form-name attribute to the field 
 element of the lookup fixes it. 
 The value of form-name attribute must be the name of the parent form, ie 
 the 1st form (the one with skip-end=true) which precedes the current form 
 (which has skip-start=true).
 If you use a related description field (using the description-field-name 
 attribute of the lookup element) you need to put the form-name attribute in 
 this field element too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-6139) Lookup fields break when used with a form having skip-start=true


[ 
https://issues.apache.org/jira/browse/OFBIZ-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564549#comment-14564549
 ] 

Pierre Smits edited comment on OFBIZ-6139 at 5/29/15 10:40 AM:
---

Having to have the form name hard coded in the field as in:
{code}
form name=RequestItemProduct type=single skip-start=true skip-end=true
field name=productId title=${uiLabelMap.CommonProduct} 
form-name=EditCustRequestItem
lookup target-form-name=LookupProduct 
description-field-name=productName show-description=false/
/field
field name=productName form-name=EditCustRequestItem 
position=2text read-only=true//field
field name=quantity title=${uiLabelMap.CommonQuantity}text 
size=10//field
/form
{code}
leads to a degradation in functionality. Such a form can be used only with one 
start form.

With dynamic form building whereby the start-form might be conditionally 
defined (based on parameter values), the form name required in the lookup 
fields of the injectable sub-forms should change accordingly.



was (Author: pfm.smits):
Having to have the form name hard coded in the field as in:
{code}
form name=RequestItemProduct type=single skip-start=true skip-end=true
field name=productId title=${uiLabelMap.CommonProduct} 
form-name=EditCustRequestItem
lookup target-form-name=LookupProduct 
description-field-name=productName show-description=false/
/field
field name=productName form-name=EditCustRequestItem 
position=2text read-only=true//field
field name=quantity title=${uiLabelMap.CommonQuantity}text 
size=10//field
/form
leads to a degradation in functionality. Such a form can be used only with one 
start form.

With dynamic form building whereby the start-form might be conditionally 
defined (based on parameter values), the form name required in the lookup 
fields of the injectable sub-forms should change accordingly.


 Lookup fields break when used with a form having skip-start=true
 --

 Key: OFBIZ-6139
 URL: https://issues.apache.org/jira/browse/OFBIZ-6139
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Minor
  Labels: lookup
 Fix For: 14.12.01, 12.04.06, 13.07.02, Upcoming Branch


 We neglected this aspect so far. Adding a form-name attribute to the field 
 element of the lookup fixes it. 
 The value of form-name attribute must be the name of the parent form, ie 
 the 1st form (the one with skip-end=true) which precedes the current form 
 (which has skip-start=true).
 If you use a related description field (using the description-field-name 
 attribute of the lookup element) you need to put the form-name attribute in 
 this field element too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (OFBIZ-6229) Can't create a geo without providing a geoID

2015-05-29 Thread Taher Alkhateeb (JIRA)


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

Taher Alkhateeb resolved OFBIZ-6229.

   Resolution: Fixed
Fix Version/s: Trunk

fixed in r1682415

 Can't create a geo without providing a geoID
 

 Key: OFBIZ-6229
 URL: https://issues.apache.org/jira/browse/OFBIZ-6229
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02
Reporter: Pierre Smits
Assignee: Taher Alkhateeb
Priority: Minor
  Labels: geodata
 Fix For: Trunk


 Currently the process of creating a geo fails when a geoId is not provided. 
 The process should self-provide the geoId if it isn't provided by the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6139) Lookup fields break when used with a form having skip-start=true


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

Jacques Le Roux updated OFBIZ-6139:
---
Description: 
We neglected this aspect so far. Adding a form-name attribute to the field 
element of the lookup fixes it. The value of form-name attribute must be the 
name of 1st form (the one with skip-end=true) which precede the current form 
(with 
If you use a related description field (using the description-field-name 
attribute of the lookup element) you will need to put the form-name attribute 
in this field element too.

  was:We neglected this aspect so far, adding a form-name attribute to the 
lookup element fixes it. You then need also to set the correct id-name value on 
field element.


 Lookup fields break when used with a form having skip-start=true
 --

 Key: OFBIZ-6139
 URL: https://issues.apache.org/jira/browse/OFBIZ-6139
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Minor
  Labels: lookup
 Fix For: 14.12.01, 12.04.06, 13.07.02, Upcoming Branch


 We neglected this aspect so far. Adding a form-name attribute to the field 
 element of the lookup fixes it. The value of form-name attribute must be 
 the name of 1st form (the one with skip-end=true) which precede the current 
 form (with 
 If you use a related description field (using the description-field-name 
 attribute of the lookup element) you will need to put the form-name 
 attribute in this field element too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-6139) Lookup fields break when used with a form having skip-start=true


[ 
https://issues.apache.org/jira/browse/OFBIZ-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564542#comment-14564542
 ] 

Jacques Le Roux edited comment on OFBIZ-6139 at 5/29/15 10:30 AM:
--

While testing the feature, Pierre Smits wanted to have form-name dynamic 
{code}(using form-name=${name}){code}. Then the form-name attrbute should 
support FlexibleStringExpander. This could be another Jira...


was (Author: jacques.le.roux):
While testing the feature, Pierre Smits wanted to have form-name dynamic (using 
form-name=${name}). Then the form-name attrbute should support 
FlexibleStringExpander. This could be another Jira...

 Lookup fields break when used with a form having skip-start=true
 --

 Key: OFBIZ-6139
 URL: https://issues.apache.org/jira/browse/OFBIZ-6139
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Minor
  Labels: lookup
 Fix For: 14.12.01, 12.04.06, 13.07.02, Upcoming Branch


 We neglected this aspect so far. Adding a form-name attribute to the field 
 element of the lookup fixes it. 
 The value of form-name attribute must be the name of the parent form, ie 
 the 1st form (the one with skip-end=true) which precedes the current form 
 (which has skip-start=true).
 If you use a related description field (using the description-field-name 
 attribute of the lookup element) you need to put the form-name attribute in 
 this field element too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6139) Lookup fields break when used with a form having skip-start=true


[ 
https://issues.apache.org/jira/browse/OFBIZ-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564549#comment-14564549
 ] 

Pierre Smits commented on OFBIZ-6139:
-

Having to have the form name hard coded in the field as in:
{code}
form name=RequestItemProduct type=single skip-start=true skip-end=true
field name=productId title=${uiLabelMap.CommonProduct}
lookup target-form-name=LookupProduct 
description-field-name=productName show-description=false/
/field
field name=productName form-name=EditCustRequestItem 
position=2text read-only=true//field
field name=quantity title=${uiLabelMap.CommonQuantity}text 
size=10//field
 /form
{code}
leads to a degradation in functionality.

With dynamic form building whereby the start-form might be conditionally 
defined (based on parameter values), the form name required in the lookup 
fields of the injectable sub-forms should be change accordingly.


 Lookup fields break when used with a form having skip-start=true
 --

 Key: OFBIZ-6139
 URL: https://issues.apache.org/jira/browse/OFBIZ-6139
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Minor
  Labels: lookup
 Fix For: 14.12.01, 12.04.06, 13.07.02, Upcoming Branch


 We neglected this aspect so far. Adding a form-name attribute to the field 
 element of the lookup fixes it. 
 The value of form-name attribute must be the name of the parent form, ie 
 the 1st form (the one with skip-end=true) which precedes the current form 
 (which has skip-start=true).
 If you use a related description field (using the description-field-name 
 attribute of the lookup element) you need to put the form-name attribute in 
 this field element too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-6139) Lookup fields break when used with a form having skip-start=true


[ 
https://issues.apache.org/jira/browse/OFBIZ-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564549#comment-14564549
 ] 

Pierre Smits edited comment on OFBIZ-6139 at 5/29/15 10:38 AM:
---

Having to have the form name hard coded in the field as in:
{code}
form name=RequestItemProduct type=single skip-start=true skip-end=true
field name=productId title=${uiLabelMap.CommonProduct}
lookup target-form-name=LookupProduct 
description-field-name=productName show-description=false/
/field
field name=productName form-name=EditCustRequestItem 
position=2text read-only=true//field
field name=quantity title=${uiLabelMap.CommonQuantity}text 
size=10//field
 /form
{code}
leads to a degradation in functionality.

With dynamic form building whereby the start-form might be conditionally 
defined (based on parameter values), the form name required in the lookup 
fields of the injectable sub-forms should change accordingly.



was (Author: pfm.smits):
Having to have the form name hard coded in the field as in:
{code}
form name=RequestItemProduct type=single skip-start=true skip-end=true
field name=productId title=${uiLabelMap.CommonProduct}
lookup target-form-name=LookupProduct 
description-field-name=productName show-description=false/
/field
field name=productName form-name=EditCustRequestItem 
position=2text read-only=true//field
field name=quantity title=${uiLabelMap.CommonQuantity}text 
size=10//field
 /form
{code}
leads to a degradation in functionality.

With dynamic form building whereby the start-form might be conditionally 
defined (based on parameter values), the form name required in the lookup 
fields of the injectable sub-forms should be change accordingly.


 Lookup fields break when used with a form having skip-start=true
 --

 Key: OFBIZ-6139
 URL: https://issues.apache.org/jira/browse/OFBIZ-6139
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Minor
  Labels: lookup
 Fix For: 14.12.01, 12.04.06, 13.07.02, Upcoming Branch


 We neglected this aspect so far. Adding a form-name attribute to the field 
 element of the lookup fixes it. 
 The value of form-name attribute must be the name of the parent form, ie 
 the 1st form (the one with skip-end=true) which precedes the current form 
 (which has skip-start=true).
 If you use a related description field (using the description-field-name 
 attribute of the lookup element) you need to put the form-name attribute in 
 this field element too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6139) Lookup fields break when used with a form having skip-start=true


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

Jacques Le Roux updated OFBIZ-6139:
---
Description: 
We neglected this aspect so far. Adding a form-name attribute to the field 
element of the lookup fixes it. The value of form-name attribute must be the 
name of 1st form (the one with skip-end=true) which precede the current form 
(with skip-start=true).

If you use a related description field (using the description-field-name 
attribute of the lookup element) you will need to put the form-name attribute 
in this field element too.

  was:
We neglected this aspect so far. Adding a form-name attribute to the field 
element of the lookup fixes it. The value of form-name attribute must be the 
name of 1st form (the one with skip-end=true) which precede the current form 
(with 
If you use a related description field (using the description-field-name 
attribute of the lookup element) you will need to put the form-name attribute 
in this field element too.


 Lookup fields break when used with a form having skip-start=true
 --

 Key: OFBIZ-6139
 URL: https://issues.apache.org/jira/browse/OFBIZ-6139
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Minor
  Labels: lookup
 Fix For: 14.12.01, 12.04.06, 13.07.02, Upcoming Branch


 We neglected this aspect so far. Adding a form-name attribute to the field 
 element of the lookup fixes it. The value of form-name attribute must be 
 the name of 1st form (the one with skip-end=true) which precede the current 
 form (with skip-start=true).
 If you use a related description field (using the description-field-name 
 attribute of the lookup element) you will need to put the form-name 
 attribute in this field element too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6229) Can't create a geo without providing a geoID


[ 
https://issues.apache.org/jira/browse/OFBIZ-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564720#comment-14564720
 ] 

Jacques Le Roux commented on OFBIZ-6229:


Thanks Pierre, Taher,

After r1682444 where I commited 
{quote}
Replaces by better labels, stumbled upon it while backporting r1682415 for 
OFBIZ-6229. I missed it when committing r1667969 
{quote}

I backported to
R14.12 at r1682445
R13.07 at r1682446
R12.04 at r1682447



 Can't create a geo without providing a geoID
 

 Key: OFBIZ-6229
 URL: https://issues.apache.org/jira/browse/OFBIZ-6229
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02
Reporter: Pierre Smits
Assignee: Taher Alkhateeb
Priority: Minor
  Labels: geodata
 Fix For: Trunk


 Currently the process of creating a geo fails when a geoId is not provided. 
 The process should self-provide the geoId if it isn't provided by the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6229) Can't create a geo without providing a geoID


[ 
https://issues.apache.org/jira/browse/OFBIZ-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564754#comment-14564754
 ] 

Pierre Smits commented on OFBIZ-6229:
-

Thanks Taher and Jacques.

 Can't create a geo without providing a geoID
 

 Key: OFBIZ-6229
 URL: https://issues.apache.org/jira/browse/OFBIZ-6229
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02
Reporter: Pierre Smits
Assignee: Taher Alkhateeb
Priority: Minor
  Labels: geodata
 Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch


 Currently the process of creating a geo fails when a geoId is not provided. 
 The process should self-provide the geoId if it isn't provided by the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jira] [Closed] (OFBIZ-5679) Functionality to add WebSitePathAlias records is missing

2015-05-29 Thread Michael Brohl


Jacques,

one followup question regarding freezed release branches: what about 
missing translations? Are they considered bugfixes or improvements and 
should they be backported or not?


Thanks and regards,

Michael

Am 29.05.15 um 15:31 schrieb Michael Brohl:

Reverted in r1682457

Thanks and regards,

Michael

Am 29.05.15 um 00:05 schrieb Jacques Le Roux:
Normally not, the branch is freezed as we call that, there are 
exceptions but must be by consensus. I guess here it's easier to 
simply revert ;)


Jacques

Le 28/05/2015 20:29, Michael Brohl a écrit :
Should have asked this before but missed it in the heat of the 
battle: This was an improvement not a bugfix and I have backported 
in the unreleased branch 14.12. Is this ok for unreleased branches 
to bring in improvements or is this restricted to bugfixes and 
security fixes?


Thanks for your advise,

Michael






smime.p7s
Description: S/MIME Cryptographic Signature

[jira] [Comment Edited] (OFBIZ-6427) Implement FindService record grouping/summarization functionality


[ 
https://issues.apache.org/jira/browse/OFBIZ-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564824#comment-14564824
 ] 

Christian Carlow edited comment on OFBIZ-6427 at 5/29/15 1:43 PM:
--

Here is an updated list of the group functions that seem worthy of implementing 
for form widget find fields: sum, avg, min, max, first, last, count, 
countDistinct

The group functions listed for each find field as table rows with a sequence 
dropdown cell to control the order in which the function values should appear 
and a text box to control the actual text that should be rendered.  The 
sequence dropdown will be set to blank by default which will prevent 
processing.  The text field will be set to a default value indicating the group 
function and the function value using FlexibleStringExpander such as 
{code}
Avg ${funcValue}, Min ${funcValue}.
{code}


was (Author: ofbizzer):
Here is an updated list of the group functions that seem worthy of implementing 
for form widget find fields: sum, avg, min, max, first, last, count, 
countDistinct

The group functions listed for each find field as table rows with a sequence 
dropdown cell to control the order in which the function values should appear 
and a text box to control the actual text that should be rendered.  The 
sequence dropdown will be set to blank by default which will prevent 
processing.  The text field will be set to a default value indicating the group 
function and the function value using FlexibleStringExpander such as Avg 
${funcValue}, Min ${funcValue}.

 Implement FindService record grouping/summarization functionality
 -

 Key: OFBIZ-6427
 URL: https://issues.apache.org/jira/browse/OFBIZ-6427
 Project: OFBiz
  Issue Type: Improvement
  Components: framework
Affects Versions: Trunk
Reporter: Christian Carlow

 Just as sortSeq and sortDir will be added to find fields like ignoreCase is 
 available, groupBy check box would also enhance user query capabilities.  
 FindService would have to be extended to process the list and create 
 group/summary records.
 For example, if a grid/form lists customer orders and the user wants to 
 determine the total quantity and price of products ordered between a date 
 range, then check marking the groupBy for productId would insert a grouping 
 record before the details containing totals.
 This issue is primarily meant to handle reports for which pagination isn't 
 used because all records are displayed.  For these reports queries, group 
 totals can simply be calculated by looping each detail record.  But if 
 pagination is used, the method of calculating totals for grouping records 
 becomes more complicated because if detail records exist outside of the 
 current page but are part of a group being summarized then they will be 
 excluded from the group total unless implemented some other way.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

buildbot failure in ASF Buildbot on ofbiz-trunk

The Buildbot has detected a new failure on builder ofbiz-trunk while building 
ASF Buildbot. Full details are available at:
http://ci.apache.org/builders/ofbiz-trunk/builds/915

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit' 
triggered this build
Build Source Stamp: [branch ofbiz/trunk] 1682462
Blamelist: jleroux,nmalin

BUILD FAILED: failed

Sincerely,
 -The Buildbot

[jira] [Closed] (OFBIZ-6417) renderDateFindField doesn't reselect operation


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

Nicolas Malin closed OFBIZ-6417.


 renderDateFindField doesn't reselect operation
 --

 Key: OFBIZ-6417
 URL: https://issues.apache.org/jira/browse/OFBIZ-6417
 Project: OFBiz
  Issue Type: Improvement
  Components: framework
Affects Versions: Trunk
Reporter: Christian Carlow
Assignee: Nicolas Malin
 Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch

 Attachments: OFBIZ-6417.patch






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6229) Can't create a geo without providing a geoID

2015-05-29 Thread Taher Alkhateeb (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564732#comment-14564732
 ] 

Taher Alkhateeb commented on OFBIZ-6229:


Thank you Jacques, next time I will make sure to label it as Upcoming Branch.

How do you link the commit to the JIRA? or does it happen automatically if you 
put the HTML link to the JIRA in the commit message?

 Can't create a geo without providing a geoID
 

 Key: OFBIZ-6229
 URL: https://issues.apache.org/jira/browse/OFBIZ-6229
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02
Reporter: Pierre Smits
Assignee: Taher Alkhateeb
Priority: Minor
  Labels: geodata
 Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch


 Currently the process of creating a geo fails when a geoId is not provided. 
 The process should self-provide the geoId if it isn't provided by the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-6430) date-find in form widget does not persist value


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

Nicolas Malin closed OFBIZ-6430.


 date-find in form widget does not persist value
 ---

 Key: OFBIZ-6430
 URL: https://issues.apache.org/jira/browse/OFBIZ-6430
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Release Branch 13.07
Reporter: Nicolas Malin
Assignee: Nicolas Malin
Priority: Minor
 Fix For: 13.07.03


 I open an issue related to OFBIZ-5074 for the branch 13.07
 When you realize a performFind search with date-find field, the given dates 
 has been lost when the page reloaded with search result.
 You can try with the screen : 
 http://demo-stable-ofbiz.apache.org/accounting/control/findInvoices



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-6305) German translations for various applications

2015-05-29 Thread Michael Brohl (JIRA)


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

Michael Brohl reassigned OFBIZ-6305:


Assignee: Michael Brohl  (was: Christian Geisert)

 German translations for various applications
 

 Key: OFBIZ-6305
 URL: https://issues.apache.org/jira/browse/OFBIZ-6305
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL APPLICATIONS
Affects Versions: Upcoming Branch
Reporter: Martin Becker
Assignee: Michael Brohl
 Attachments: OFBIZ-6305-PartyComponent.patch, 
 OFBIZ-6305-ProductEntityLabels.patch, OFBIZ-6305-ProductErrorUiLabels.patch, 
 OFBIZ-6305-ProductUiLabels.patch


 We would like to contribute missing german translations for the OFBiz 
 applications based on the current trunk. There will arrive patches for this 
 per application within this ticket.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6427) Implement FindService record grouping/summarization functionality


[ 
https://issues.apache.org/jira/browse/OFBIZ-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564824#comment-14564824
 ] 

Christian Carlow commented on OFBIZ-6427:
-

Here is an updated list of the group functions that seem worthy of implementing 
for form widget find fields: sum, avg, min, max, first, last, count, 
countDistinct

The group functions listed for each find field as table rows with a sequence 
dropdown cell to control the order in which the function values should appear 
and a text box to control the actual text that should be rendered.  The 
sequence dropdown will be set to blank by default which will prevent 
processing.  The text field will be set to a default value indicating the group 
function and the function value using FlexibleStringExpander such as Avg 
${funcValue}, Min ${funcValue}.

 Implement FindService record grouping/summarization functionality
 -

 Key: OFBIZ-6427
 URL: https://issues.apache.org/jira/browse/OFBIZ-6427
 Project: OFBiz
  Issue Type: Improvement
  Components: framework
Affects Versions: Trunk
Reporter: Christian Carlow

 Just as sortSeq and sortDir will be added to find fields like ignoreCase is 
 available, groupBy check box would also enhance user query capabilities.  
 FindService would have to be extended to process the list and create 
 group/summary records.
 For example, if a grid/form lists customer orders and the user wants to 
 determine the total quantity and price of products ordered between a date 
 range, then check marking the groupBy for productId would insert a grouping 
 record before the details containing totals.
 This issue is primarily meant to handle reports for which pagination isn't 
 used because all records are displayed.  For these reports queries, group 
 totals can simply be calculated by looping each detail record.  But if 
 pagination is used, the method of calculating totals for grouping records 
 becomes more complicated because if detail records exist outside of the 
 current page but are part of a group being summarized then they will be 
 excluded from the group total unless implemented some other way.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

buildbot failure in ASF Buildbot on ofbiz-branch13

The Buildbot has detected a new failure on builder ofbiz-branch13 while 
building ASF Buildbot. Full details are available at:
http://ci.apache.org/builders/ofbiz-branch13/builds/319

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz13-commit' 
triggered this build
Build Source Stamp: [branch ofbiz/branches/release13.07] 1682460
Blamelist: nmalin

BUILD FAILED: failed

Sincerely,
 -The Buildbot

[jira] [Updated] (OFBIZ-6229) Can't create a geo without providing a geoID


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

Jacques Le Roux updated OFBIZ-6229:
---
Fix Version/s: (was: Trunk)
   Upcoming Branch
   13.07.03
   12.04.06
   14.12.01

Taher, I just changed it for you: you fix only unreleased versions, so it's not 
trunk to put in Fix Version/s field but Upcoming Branch. We use that to 
automatically generate releases changelogs from Jira, thank!

 Can't create a geo without providing a geoID
 

 Key: OFBIZ-6229
 URL: https://issues.apache.org/jira/browse/OFBIZ-6229
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02
Reporter: Pierre Smits
Assignee: Taher Alkhateeb
Priority: Minor
  Labels: geodata
 Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch


 Currently the process of creating a geo fails when a geoId is not provided. 
 The process should self-provide the geoId if it isn't provided by the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-6430) date-find in form widget does not persist value

Nicolas Malin created OFBIZ-6430:


 Summary: date-find in form widget does not persist value
 Key: OFBIZ-6430
 URL: https://issues.apache.org/jira/browse/OFBIZ-6430
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Release Branch 13.07
Reporter: Nicolas Malin
Assignee: Nicolas Malin
Priority: Minor


I open an issue related to OFBIZ-5074 for the branch 13.07

When you realize a performFind search with date-find field, the given dates has 
been lost when the page reloaded with search result.

You can try with the screen : 
http://demo-stable-ofbiz.apache.org/accounting/control/findInvoices



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jira] [Closed] (OFBIZ-5679) Functionality to add WebSitePathAlias records is missing

2015-05-29 Thread Michael Brohl


Reverted in r1682457

Thanks and regards,

Michael

Am 29.05.15 um 00:05 schrieb Jacques Le Roux:
Normally not, the branch is freezed as we call that, there are 
exceptions but must be by consensus. I guess here it's easier to 
simply revert ;)


Jacques

Le 28/05/2015 20:29, Michael Brohl a écrit :
Should have asked this before but missed it in the heat of the 
battle: This was an improvement not a bugfix and I have backported in 
the unreleased branch 14.12. Is this ok for unreleased branches to 
bring in improvements or is this restricted to bugfixes and security 
fixes?


Thanks for your advise,

Michael

Am 28.05.15 um 20:20 schrieb Michael Brohl (JIRA):
  [ 
https://issues.apache.org/jira/browse/OFBIZ-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel 
]


Michael Brohl closed OFBIZ-5679.

Resolution: Implemented
 Fix Version/s: Release Branch 14.12
Upcoming Branch

Thanks Pierre and Willem,

your changes are in
trunk at r1682295
release branch 14.12 at r1682298

I had to manually apply some changes and correct some issues with 
whitespaces to get this in. Please be careful with the encoding 
settings of your IDE.











smime.p7s
Description: S/MIME Cryptographic Signature

[jira] [Resolved] (OFBIZ-6430) date-find in form widget does not persist value


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

Nicolas Malin resolved OFBIZ-6430.
--
   Resolution: Fixed
Fix Version/s: 13.07.03

 date-find in form widget does not persist value
 ---

 Key: OFBIZ-6430
 URL: https://issues.apache.org/jira/browse/OFBIZ-6430
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Release Branch 13.07
Reporter: Nicolas Malin
Assignee: Nicolas Malin
Priority: Minor
 Fix For: 13.07.03


 I open an issue related to OFBIZ-5074 for the branch 13.07
 When you realize a performFind search with date-find field, the given dates 
 has been lost when the page reloaded with search result.
 You can try with the screen : 
 http://demo-stable-ofbiz.apache.org/accounting/control/findInvoices



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6430) date-find in form widget does not persist value


[ 
https://issues.apache.org/jira/browse/OFBIZ-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564813#comment-14564813
 ] 

Nicolas Malin commented on OFBIZ-6430:
--

Done at revision 1682460 on 13.07

 date-find in form widget does not persist value
 ---

 Key: OFBIZ-6430
 URL: https://issues.apache.org/jira/browse/OFBIZ-6430
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Release Branch 13.07
Reporter: Nicolas Malin
Assignee: Nicolas Malin
Priority: Minor
 Fix For: 13.07.03


 I open an issue related to OFBIZ-5074 for the branch 13.07
 When you realize a performFind search with date-find field, the given dates 
 has been lost when the page reloaded with search result.
 You can try with the screen : 
 http://demo-stable-ofbiz.apache.org/accounting/control/findInvoices



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6305) German translations for various applications

2015-05-29 Thread Michael Brohl (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564834#comment-14564834
 ] 

Michael Brohl commented on OFBIZ-6305:
--

Thanks Martin, your patch is in r1682466.

 German translations for various applications
 

 Key: OFBIZ-6305
 URL: https://issues.apache.org/jira/browse/OFBIZ-6305
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL APPLICATIONS
Affects Versions: Upcoming Branch
Reporter: Martin Becker
Assignee: Michael Brohl
 Attachments: OFBIZ-6305-PartyComponent.patch, 
 OFBIZ-6305-ProductEntityLabels.patch, OFBIZ-6305-ProductErrorUiLabels.patch, 
 OFBIZ-6305-ProductUiLabels.patch


 We would like to contribute missing german translations for the OFBiz 
 applications based on the current trunk. There will arrive patches for this 
 per application within this ticket.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

buildbot failure in ASF Buildbot on ofbiz-branch14

The Buildbot has detected a new failure on builder ofbiz-branch14 while 
building ASF Buildbot. Full details are available at:
http://ci.apache.org/builders/ofbiz-branch14/builds/140

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz14-commit' 
triggered this build
Build Source Stamp: [branch ofbiz/branches/release14.12] 1682463
Blamelist: nmalin

BUILD FAILED: failed

Sincerely,
 -The Buildbot

buildbot success in ASF Buildbot on ofbiz-trunk

The Buildbot has detected a restored build on builder ofbiz-trunk while 
building ASF Buildbot. Full details are available at:
http://ci.apache.org/builders/ofbiz-trunk/builds/916

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit' 
triggered this build
Build Source Stamp: [branch ofbiz/trunk] 1682466
Blamelist: mbrohl

Build succeeded!

Sincerely,
 -The Buildbot

[jira] [Closed] (OFBIZ-6229) Can't create a geo without providing a geoID


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

Pierre Smits closed OFBIZ-6229.
---

 Can't create a geo without providing a geoID
 

 Key: OFBIZ-6229
 URL: https://issues.apache.org/jira/browse/OFBIZ-6229
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02
Reporter: Pierre Smits
Assignee: Taher Alkhateeb
Priority: Minor
  Labels: geodata
 Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch


 Currently the process of creating a geo fails when a geoId is not provided. 
 The process should self-provide the geoId if it isn't provided by the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6229) Can't create a geo without providing a geoID


[ 
https://issues.apache.org/jira/browse/OFBIZ-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14565572#comment-14565572
 ] 

Pierre Smits commented on OFBIZ-6229:
-

I will close this issue. 

 Can't create a geo without providing a geoID
 

 Key: OFBIZ-6229
 URL: https://issues.apache.org/jira/browse/OFBIZ-6229
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02
Reporter: Pierre Smits
Assignee: Taher Alkhateeb
Priority: Minor
  Labels: geodata
 Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch


 Currently the process of creating a geo fails when a geoId is not provided. 
 The process should self-provide the geoId if it isn't provided by the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6229) Can't create a geo without providing a geoID

2015-05-29 Thread Taher Alkhateeb (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14565536#comment-14565536
 ] 

Taher Alkhateeb commented on OFBIZ-6229:


Thank you Jacques for the feedback. For the record this was my first commit so 
I was a bit terrified and I can now release a sigh of relief.

Who should close this issue and when? Is it Pierre as the reporter or is it 
when someone validates with a test (I tested already)? And when should it be 
closed, does some time have to pass?

 Can't create a geo without providing a geoID
 

 Key: OFBIZ-6229
 URL: https://issues.apache.org/jira/browse/OFBIZ-6229
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02
Reporter: Pierre Smits
Assignee: Taher Alkhateeb
Priority: Minor
  Labels: geodata
 Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch


 Currently the process of creating a geo fails when a geoId is not provided. 
 The process should self-provide the geoId if it isn't provided by the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-5949) ofbizsetup create product store cause exception, remove use of temp file to load entity data

2015-05-29 Thread Wai (JIRA)

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

Wai updated OFBIZ-5949:
---
Attachment: OFBIZ-5949.patch

OFBIZ-6216 solved the foreign key violation issue related to NEXT_DAY_AIR in
the template file ProductStoreData.xml.
Now this patch contains only the modifications related to a multitenant
friendly way of loading data from a template file (eg. ProductStoreData.xml).

ofbizsetup create product store cause exception, remove use of temp file to
load entity data

Key: OFBIZ-5949
URL: https://issues.apache.org/jira/browse/OFBIZ-5949
Project: OFBiz
Issue Type: Bug
Components: commonext/setup
Affects Versions: Trunk
Reporter: Wai
Assignee: Jacques Le Roux
Attachments: OFBIZ-5949.patch, OFBIZ-5949.patch, OFBIZ-5949.patch

The exception is caused by foreign key constraint violation between
ShipmentCostEstimate and CarrierShipmentMethod entities.
Currently, when creating a new product store using ofbizsetup component
default data associated with the product store is loaded into the database
using the following steps.
1. read default data from entity xml file and replace specific items in the
read data and write to temp file.
2. use service=parseEntityXmlFile to load the processed file into database.
The issue with this method is that the temp file can present a problem when
ofbiz is operating in multitenant mode.
The solution is to modify the relevant services so that no temp file needs
generated.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-6431) Error on Sending confirm email from newly created quote, Quote without Terms

Forrest Rae created OFBIZ-6431:
--

 Summary: Error on Sending confirm email from newly created quote, 
Quote without Terms
 Key: OFBIZ-6431
 URL: https://issues.apache.org/jira/browse/OFBIZ-6431
 Project: OFBiz
  Issue Type: Bug
  Components: order
 Environment: 
http://demo-trunk-ofbiz.apache.org/ordermgr/control/sendQuoteReportMail
Reporter: Forrest Rae


Error on Sending confirm email from newly created quote

http://demo-trunk-ofbiz.apache.org/ordermgr/control/sendQuoteReportMail



The Following Errors Occurred:

Error rendering screen for email: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteSimple]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null) (Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null)) (Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null) (Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null))) (Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null) (Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null)) (Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null) (Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6431) Error on Sending confirm email from newly created quote, Quote without Terms


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

Forrest Rae updated OFBIZ-6431:
---
Description: 
I cloned this bug, since I couldn't reopen.  Create a quote with items and a 
QuoteTerm, and try sending the quote by email.  When you try to send the report 
via email, you'll get a NullPointerException.  I traced this done to the fact 
that ListQuoteInfo use a screenlet.  
org.ofbiz.widget.screen.ModelScreenWidget.Screenlet.renderWidgetString() calls 
org.ofbiz.widget.html.HtmlScreenRenderer.renderScreenletBegin() which calls 
org.ofbiz.base.util.UtilHttp.isJavaScriptEnabled().  The exception is thrown 
because there is no Request or Response context, as these screens are being 
generated via a service call.

===
Error on Sending confirm email from newly created quote

http://demo-trunk-ofbiz.apache.org/ordermgr/control/sendQuoteReportMail



The Following Errors Occurred:

Error rendering screen for email: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteSimple]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null) (Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null)) (Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null) (Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null))) (Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null) (Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null)) (Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null) (Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null


  was:
Error on Sending confirm email from newly created quote

http://demo-trunk-ofbiz.apache.org/ordermgr/control/sendQuoteReportMail



The Following Errors Occurred:

Error rendering screen for email: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteSimple]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null) (Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null)) (Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null) (Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null))) (Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
java.lang.NullPointerException (null) (Error

Re: [jira] [Closed] (OFBIZ-5679) Functionality to add WebSitePathAlias records is missing

2015-05-29 Thread Jacques Le Roux


Missing translations are fine to be backported w/o consensus as long as they 
don't break the Label Manager. I keep an eye on this anyway...

Jacques

Le 29/05/2015 15:39, Michael Brohl a écrit :

Jacques,

one followup question regarding freezed release branches: what about missing translations? Are they considered bugfixes or improvements and should 
they be backported or not?


Thanks and regards,

Michael

Am 29.05.15 um 15:31 schrieb Michael Brohl:

Reverted in r1682457

Thanks and regards,

Michael

Am 29.05.15 um 00:05 schrieb Jacques Le Roux:

Normally not, the branch is freezed as we call that, there are exceptions but 
must be by consensus. I guess here it's easier to simply revert ;)

Jacques

Le 28/05/2015 20:29, Michael Brohl a écrit :
Should have asked this before but missed it in the heat of the battle: This was an improvement not a bugfix and I have backported in the 
unreleased branch 14.12. Is this ok for unreleased branches to bring in improvements or is this restricted to bugfixes and security fixes?


Thanks for your advise,

Michael

[jira] [Comment Edited] (OFBIZ-6431) Error on Sending confirm email from newly created quote, Quote without Terms


[ 
https://issues.apache.org/jira/browse/OFBIZ-6431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14565351#comment-14565351
 ] 

Christian Carlow edited comment on OFBIZ-6431 at 5/29/15 8:33 PM:
--

Hey Forrest,

This is related or a duplicate: https://issues.apache.org/jira/browse/OFBIZ-6360


was (Author: ofbizzer):
Hey Forrest,

This is related: https://issues.apache.org/jira/browse/OFBIZ-6360

 Error on Sending confirm email from newly created quote, Quote without Terms
 

 Key: OFBIZ-6431
 URL: https://issues.apache.org/jira/browse/OFBIZ-6431
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk
 Environment: 
 http://demo-trunk-ofbiz.apache.org/ordermgr/control/sendQuoteReportMail
Reporter: Forrest Rae

 I cloned this bug, since I couldn't reopen.  Create a quote with items and a 
 QuoteTerm, and try sending the quote by email.  When you try to send the 
 report via email, you'll get a NullPointerException.  I traced this done to 
 the fact that ListQuoteInfo use a screenlet.  
 org.ofbiz.widget.screen.ModelScreenWidget.Screenlet.renderWidgetString() 
 calls org.ofbiz.widget.html.HtmlScreenRenderer.renderScreenletBegin() which 
 calls org.ofbiz.base.util.UtilHttp.isJavaScriptEnabled().  The exception is 
 thrown because there is no Request or Response context, as these screens are 
 being generated via a service call.
 ===
 Error on Sending confirm email from newly created quote
 http://demo-trunk-ofbiz.apache.org/ordermgr/control/sendQuoteReportMail
 The Following Errors Occurred:
 Error rendering screen for email: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteSimple]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null)) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null))) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null)) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6431) Error on Sending confirm email from newly created quote, Quote without Terms


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

Forrest Rae updated OFBIZ-6431:
---
Affects Version/s: Release Branch 13.07
   Release Branch 14.12
   Trunk

 Error on Sending confirm email from newly created quote, Quote without Terms
 

 Key: OFBIZ-6431
 URL: https://issues.apache.org/jira/browse/OFBIZ-6431
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk
 Environment: 
 http://demo-trunk-ofbiz.apache.org/ordermgr/control/sendQuoteReportMail
Reporter: Forrest Rae

 Error on Sending confirm email from newly created quote
 http://demo-trunk-ofbiz.apache.org/ordermgr/control/sendQuoteReportMail
 The Following Errors Occurred:
 Error rendering screen for email: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteSimple]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null)) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null))) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null)) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6431) Error on Sending confirm email from newly created quote, Quote without Terms


[ 
https://issues.apache.org/jira/browse/OFBIZ-6431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14565351#comment-14565351
 ] 

Christian Carlow commented on OFBIZ-6431:
-

Hey Forrest,

This is related: https://issues.apache.org/jira/browse/OFBIZ-6360

 Error on Sending confirm email from newly created quote, Quote without Terms
 

 Key: OFBIZ-6431
 URL: https://issues.apache.org/jira/browse/OFBIZ-6431
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk
 Environment: 
 http://demo-trunk-ofbiz.apache.org/ordermgr/control/sendQuoteReportMail
Reporter: Forrest Rae

 I cloned this bug, since I couldn't reopen.  Create a quote with items and a 
 QuoteTerm, and try sending the quote by email.  When you try to send the 
 report via email, you'll get a NullPointerException.  I traced this done to 
 the fact that ListQuoteInfo use a screenlet.  
 org.ofbiz.widget.screen.ModelScreenWidget.Screenlet.renderWidgetString() 
 calls org.ofbiz.widget.html.HtmlScreenRenderer.renderScreenletBegin() which 
 calls org.ofbiz.base.util.UtilHttp.isJavaScriptEnabled().  The exception is 
 thrown because there is no Request or Response context, as these screens are 
 being generated via a service call.
 ===
 Error on Sending confirm email from newly created quote
 http://demo-trunk-ofbiz.apache.org/ordermgr/control/sendQuoteReportMail
 The Following Errors Occurred:
 Error rendering screen for email: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteSimple]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null)) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null))) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null)) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6431) Error on Sending confirm email from newly created quote, Quote without Terms


[ 
https://issues.apache.org/jira/browse/OFBIZ-6431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14565419#comment-14565419
 ] 

Jacques Le Roux commented on OFBIZ-6431:


Christian use rather OFBIZ-6360, when it will be closed the above will not 
reflect, this one will (Jira infers), thanks!

 Error on Sending confirm email from newly created quote, Quote without Terms
 

 Key: OFBIZ-6431
 URL: https://issues.apache.org/jira/browse/OFBIZ-6431
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk
 Environment: 
 http://demo-trunk-ofbiz.apache.org/ordermgr/control/sendQuoteReportMail
Reporter: Forrest Rae

 I cloned this bug, since I couldn't reopen.  Create a quote with items and a 
 QuoteTerm, and try sending the quote by email.  When you try to send the 
 report via email, you'll get a NullPointerException.  I traced this done to 
 the fact that ListQuoteInfo use a screenlet.  
 org.ofbiz.widget.screen.ModelScreenWidget.Screenlet.renderWidgetString() 
 calls org.ofbiz.widget.html.HtmlScreenRenderer.renderScreenletBegin() which 
 calls org.ofbiz.base.util.UtilHttp.isJavaScriptEnabled().  The exception is 
 thrown because there is no Request or Response context, as these screens are 
 being generated via a service call.
 ===
 Error on Sending confirm email from newly created quote
 http://demo-trunk-ofbiz.apache.org/ordermgr/control/sendQuoteReportMail
 The Following Errors Occurred:
 Error rendering screen for email: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteSimple]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null)) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null))) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null)) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6229) Can't create a geo without providing a geoID


[ 
https://issues.apache.org/jira/browse/OFBIZ-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14565440#comment-14565440
 ] 

Jacques Le Roux commented on OFBIZ-6229:


Putting the OFBIZ- ref as you did for r1682415 is enough. I often put the 
complete URL, most env allow you to simply click then to get there. It's also 
good to put a word about the contributor (the person who reported/created the 
Jira), even id this person did not provide a patch. Remember you can always 
update svn commits comments ;)

 Can't create a geo without providing a geoID
 

 Key: OFBIZ-6229
 URL: https://issues.apache.org/jira/browse/OFBIZ-6229
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02
Reporter: Pierre Smits
Assignee: Taher Alkhateeb
Priority: Minor
  Labels: geodata
 Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch


 Currently the process of creating a geo fails when a geoId is not provided. 
 The process should self-provide the geoId if it isn't provided by the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-6431) Error on Sending confirm email from newly created quote, Quote without Terms


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

Forrest Rae closed OFBIZ-6431.
--
Resolution: Fixed

 Error on Sending confirm email from newly created quote, Quote without Terms
 

 Key: OFBIZ-6431
 URL: https://issues.apache.org/jira/browse/OFBIZ-6431
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk
 Environment: 
 http://demo-trunk-ofbiz.apache.org/ordermgr/control/sendQuoteReportMail
Reporter: Forrest Rae

 I cloned this bug, since I couldn't reopen.  Create a quote with items and a 
 QuoteTerm, and try sending the quote by email.  When you try to send the 
 report via email, you'll get a NullPointerException.  I traced this done to 
 the fact that ListQuoteInfo use a screenlet.  
 org.ofbiz.widget.screen.ModelScreenWidget.Screenlet.renderWidgetString() 
 calls org.ofbiz.widget.html.HtmlScreenRenderer.renderScreenletBegin() which 
 calls org.ofbiz.base.util.UtilHttp.isJavaScriptEnabled().  The exception is 
 thrown because there is no Request or Response context, as these screens are 
 being generated via a service call.
 ===
 Error on Sending confirm email from newly created quote
 http://demo-trunk-ofbiz.apache.org/ordermgr/control/sendQuoteReportMail
 The Following Errors Occurred:
 Error rendering screen for email: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteSimple]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null)) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null))) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null)) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6360) Form widget rendering broken for EmailServices.java


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

Forrest Rae updated OFBIZ-6360:
---
Attachment: OFBIZ-6360-release13.07.patch

I attached a patch for release13.07.  Please updated the affected versions to 
also 14.12, and 13.07.

 Form widget rendering broken for EmailServices.java
 ---

 Key: OFBIZ-6360
 URL: https://issues.apache.org/jira/browse/OFBIZ-6360
 Project: OFBiz
  Issue Type: Improvement
  Components: framework
Affects Versions: Trunk
Reporter: Christian Carlow
 Fix For: Trunk

 Attachments: OFBIZ-6360-release13.07.patch, OFBIZ-6360.patch


 Currently only FTL files are rendered by EmailServices.java because 
 formStringRenderer is null for 
 HtmlScreenRenderer.java#renderScreenletSubWidget which is supposed to be 
 extracted from the context parameter, previously from the request parameter, 
 which never exists for the emailing service.  This issue was encountered when 
 testing the sendQuoteReportMail service for the form widget that replaced the 
 FTL for OFBIZ-6349.  
 EmailServices.java is still using the deprecated HtmlScreenRenderer and 
 FoScreenRenderer which should both be replaced by MacroScreenRenderer.  This 
 made me realize I left out the new header rendering functionality for patch 
 OFBIZ-6354 for these two deprecated classes which probably need to be 
 provided along with the existing patch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (OFBIZ-6431) Error on Sending confirm email from newly created quote, Quote without Terms


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

Jacques Le Roux reopened OFBIZ-6431:


 Error on Sending confirm email from newly created quote, Quote without Terms
 

 Key: OFBIZ-6431
 URL: https://issues.apache.org/jira/browse/OFBIZ-6431
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk
 Environment: 
 http://demo-trunk-ofbiz.apache.org/ordermgr/control/sendQuoteReportMail
Reporter: Forrest Rae

 I cloned this bug, since I couldn't reopen.  Create a quote with items and a 
 QuoteTerm, and try sending the quote by email.  When you try to send the 
 report via email, you'll get a NullPointerException.  I traced this done to 
 the fact that ListQuoteInfo use a screenlet.  
 org.ofbiz.widget.screen.ModelScreenWidget.Screenlet.renderWidgetString() 
 calls org.ofbiz.widget.html.HtmlScreenRenderer.renderScreenletBegin() which 
 calls org.ofbiz.base.util.UtilHttp.isJavaScriptEnabled().  The exception is 
 thrown because there is no Request or Response context, as these screens are 
 being generated via a service call.
 ===
 Error on Sending confirm email from newly created quote
 http://demo-trunk-ofbiz.apache.org/ordermgr/control/sendQuoteReportMail
 The Following Errors Occurred:
 Error rendering screen for email: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteSimple]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null)) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null))) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null)) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-6431) Error on Sending confirm email from newly created quote, Quote without Terms


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

Jacques Le Roux closed OFBIZ-6431.
--
Resolution: Duplicate

 Error on Sending confirm email from newly created quote, Quote without Terms
 

 Key: OFBIZ-6431
 URL: https://issues.apache.org/jira/browse/OFBIZ-6431
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk
 Environment: 
 http://demo-trunk-ofbiz.apache.org/ordermgr/control/sendQuoteReportMail
Reporter: Forrest Rae

 I cloned this bug, since I couldn't reopen.  Create a quote with items and a 
 QuoteTerm, and try sending the quote by email.  When you try to send the 
 report via email, you'll get a NullPointerException.  I traced this done to 
 the fact that ListQuoteInfo use a screenlet.  
 org.ofbiz.widget.screen.ModelScreenWidget.Screenlet.renderWidgetString() 
 calls org.ofbiz.widget.html.HtmlScreenRenderer.renderScreenletBegin() which 
 calls org.ofbiz.base.util.UtilHttp.isJavaScriptEnabled().  The exception is 
 thrown because there is no Request or Response context, as these screens are 
 being generated via a service call.
 ===
 Error on Sending confirm email from newly created quote
 http://demo-trunk-ofbiz.apache.org/ordermgr/control/sendQuoteReportMail
 The Following Errors Occurred:
 Error rendering screen for email: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteSimple]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null)) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null))) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteTemplate]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null)) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ViewQuoteInfo]: 
 org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null) (Error rendering screen 
 [component://order/widget/ordermgr/QuoteScreens.xml#ListQuoteInfo]: 
 java.lang.NullPointerException (null



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-6349) Replace ViewQuoteItems.ftl with form widgets


[ 
https://issues.apache.org/jira/browse/OFBIZ-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542477#comment-14542477
 ] 

Jacques Le Roux edited comment on OFBIZ-6349 at 5/29/15 9:43 PM:
-

I just realized the currency needs to be set to 
{code}${quote.currencyUomId}{code} to match ViewQuoteItems.ftl which will be 
applied to the replacement currency fields of OFBIZ-5428.  I'm not sure if its 
necessary to repatch this if OFBIZ-5428 will override that will be patched but 
will if requested.


was (Author: ofbizzer):
I just realized the currency needs to be set to ${quote.currencyUomId} to match 
ViewQuoteItems.ftl which will be applied to the replacement currency fields of 
OFBIZ-5428.  I'm not sure if its necessary to repatch this if OFBIZ-5428 will 
override that will be patched but will if requested.

 Replace ViewQuoteItems.ftl with form widgets
 

 Key: OFBIZ-6349
 URL: https://issues.apache.org/jira/browse/OFBIZ-6349
 Project: OFBiz
  Issue Type: Improvement
  Components: order
Affects Versions: Trunk
Reporter: Christian Carlow
 Attachments: OFBIZ-6349.patch






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6404) Allow form/grid widget hyperlinks to be grouped into a single column