Minor related patch after OFBIZ-4225 issue (Lookup target-parameter in form widget is not working) fixed
-------------------------------------------------------------------------------------------------------- Key: OFBIZ-4228 URL: https://issues.apache.org/jira/browse/OFBIZ-4228 Project: OFBiz Issue Type: Bug Components: order Affects Versions: SVN trunk Reporter: Leon Priority: Minor Fix For: SVN trunk Attachments: ordermgrLookupScreensParm0.patch In https://issues.apache.org/jira/browse/OFBIZ-4225, Deepak Dixit fixed a bug in fieldlookup.js which caused "Lookup target-parameter in form widget is not working"。 Now the form widget framework behaves same as widget-form.xsd specifies: using parameters.parmI (where I is the position number in the "target-parameter" list) in the related lookup screen. The position number in the list begins from 1. That implictes "parm0" is invalid. So I search the whole project to look up whether there's "parm0" left out. That's what this patch for. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira |
[ https://issues.apache.org/jira/browse/OFBIZ-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leon updated OFBIZ-4228: ------------------------ Attachment: ordermgrLookupScreensParm0.patch update "parameters.parm0" to "parameters.parm1" > Minor related patch after OFBIZ-4225 issue (Lookup target-parameter in form widget is not working) fixed > -------------------------------------------------------------------------------------------------------- > > Key: OFBIZ-4228 > URL: https://issues.apache.org/jira/browse/OFBIZ-4228 > Project: OFBiz > Issue Type: Bug > Components: order > Affects Versions: SVN trunk > Reporter: Leon > Priority: Minor > Fix For: SVN trunk > > Attachments: ordermgrLookupScreensParm0.patch > > > In https://issues.apache.org/jira/browse/OFBIZ-4225, Deepak Dixit fixed a bug in fieldlookup.js which caused "Lookup target-parameter in form widget is not working"。 > Now the form widget framework behaves same as widget-form.xsd specifies: using parameters.parmI (where I is the position number in the "target-parameter" list) in the related lookup screen. The position number in the list begins from 1. That implictes "parm0" is invalid. > So I search the whole project to look up whether there's "parm0" left out. That's what this patch for. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-4228. ---------------------------------- Resolution: Fixed Fix Version/s: Release Branch 10.04 Assignee: Jacques Le Roux Thanks Leon, I thought about the xsd, but bypassed your search, well spotted! Your patch is in trunk at r1084855, I have applied it also to R10.04 at r1084856. > Minor related patch after OFBIZ-4225 issue (Lookup target-parameter in form widget is not working) fixed > -------------------------------------------------------------------------------------------------------- > > Key: OFBIZ-4228 > URL: https://issues.apache.org/jira/browse/OFBIZ-4228 > Project: OFBiz > Issue Type: Bug > Components: order > Affects Versions: SVN trunk > Reporter: Leon > Assignee: Jacques Le Roux > Priority: Minor > Fix For: Release Branch 10.04, SVN trunk > > Attachments: ordermgrLookupScreensParm0.patch > > > In https://issues.apache.org/jira/browse/OFBIZ-4225, Deepak Dixit fixed a bug in fieldlookup.js which caused "Lookup target-parameter in form widget is not working"。 > Now the form widget framework behaves same as widget-form.xsd specifies: using parameters.parmI (where I is the position number in the "target-parameter" list) in the related lookup screen. The position number in the list begins from 1. That implictes "parm0" is invalid. > So I search the whole project to look up whether there's "parm0" left out. That's what this patch for. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011098#comment-13011098 ] Deepak Dixit commented on OFBIZ-4228: ------------------------------------- Thanks Leon I missed it, my apologies. > Minor related patch after OFBIZ-4225 issue (Lookup target-parameter in form widget is not working) fixed > -------------------------------------------------------------------------------------------------------- > > Key: OFBIZ-4228 > URL: https://issues.apache.org/jira/browse/OFBIZ-4228 > Project: OFBiz > Issue Type: Bug > Components: order > Affects Versions: SVN trunk > Reporter: Leon > Assignee: Jacques Le Roux > Priority: Minor > Fix For: Release Branch 10.04, SVN trunk > > Attachments: ordermgrLookupScreensParm0.patch > > > In https://issues.apache.org/jira/browse/OFBIZ-4225, Deepak Dixit fixed a bug in fieldlookup.js which caused "Lookup target-parameter in form widget is not working"。 > Now the form widget framework behaves same as widget-form.xsd specifies: using parameters.parmI (where I is the position number in the "target-parameter" list) in the related lookup screen. The position number in the list begins from 1. That implictes "parm0" is invalid. > So I search the whole project to look up whether there's "parm0" left out. That's what this patch for. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira |
Free forum by Nabble | Edit this page |