Re: svn commit: r1573170 - /ofbiz/site/index.html
Inline Le 03/03/2014 08:51, Hans Bakker a écrit : I think that missing certificates are unprofessional and if it is not possible to add one (a wild card certificate on apache.org would do it, costs about 80$, or even two single ones can be had for 10$) then certainly I agree with Jacques a comment that it does not do any harm, would be useful. Your proposition makes sense Hans. I already suggested that 5 years ago http://markmail.org/message/jtrovomwpqrl4xan And I even made a request to infra: https://issues.apache.org/jira/browse/INFRA-2849 I have used StartSSL since for my own needs and it works quite well. But it's maybe not a money issue, rather that the infra team does not want to handle it... yearly... You can discuss the way it is shown. If someone wants to remove it, let's go. But the SSL certificate issues will remain... Regards, Hans On 03/03/14 14:17, Adrian Crum wrote: I agree with Jacopo. This change makes the site look unprofessional. What makes look us unprofessional is not to have a SSL certificate. It's easy to forget once you have accepted the exceptions (trunk, stable, old). Maybe the ASF and infra team policies in this regard is because we are a kind of an exception. I don't know if any other TLP has also demos like us? Adrian Crum Sandglass Software www.sandglass-software.com On 3/2/2014 10:29 PM, Jacopo Cappellato wrote: On Mar 2, 2014, at 7:47 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Maybe some not geeky users, not reading our MLs, could be frightened by the certificate warning. So this simple sentence to reassure them. In general, I would prefer to discuss and fix real issues rather than trying to imagine what they could be. Following the same pattern, in the past, I have seen pages in the wiki (e.g. the old mailing list pages) become very confusing and redundant because unnecessary information was added and added over time (often with not well written English sentences). I don't see any relation with wiki pages here (which I agree could be better if all committers would make their duty), but yes having a SSL certificate(s?) there would be better in my opinion. I don't see much cluttering adding this sentence. The sentence: you can trust certificates doesn't mean anything and when you see it in the right bar menu it looks a bit weird (especially for users that don't click on the demo links and don't see the certificate warning); the OFBiz web site should be kept as clean as possible. Yes the sentence should rather say Please accept exceptions for SSL certificates if you get to the backend demos but I found it a bit too long. I agree that the OFBiz web site should be kept as clean as possible, so should be the demos. What are the formatting issues? I did not create a CSS class to center the sentence, is that the problem? Does it look right to you? That sentence is not aligned with the demo links and it is difficult to understand it referred to them. I just centered it above the demo sections to make it clear it was related. As I said we can remove it, if really we can't convince infra to handle a yearly certificate for our demos, maybe you have better ideas for demos to look more clean? Once again L'enfer est pavé de bonnes intentions Jacques Jacopo Jacques Le 02/03/2014 18:12, Jacopo Cappellato a écrit : Is this really needed? I don't think the certificate warning is a major issue and we can easily explain in the user list just in case someone will complain... instead of cluttering the web site with unnecessary information (with some formatting issues). Jacopo On Mar 1, 2014, at 2:23 PM, jler...@apache.org wrote: Author: jleroux Date: Sat Mar 1 13:23:10 2014 New Revision: 1573170 URL: http://svn.apache.org/r1573170 Log: Add a centered line in the demos section: Official demos (you can trust certificates) Modified: ofbiz/site/index.html Modified: ofbiz/site/index.html URL: http://svn.apache.org/viewvc/ofbiz/site/index.html?rev=1573170r1=1573169r2=1573170view=diff == --- ofbiz/site/index.html (original) +++ ofbiz/site/index.html Sat Mar 1 13:23:10 2014 @@ -225,9 +225,7 @@ lia href=source-repositories.htmlSource Repository (SVN)/a/li lia href=https://issues.apache.org/jira/browse/OFBIZ; target=_blankIssue Tracker (Jira)/a/li lia href=http://ci.apache.org/projects/ofbiz/site/javadocs/; target=_blankAPI Reference (Javadoc)/a/li -!-- TODO: the format of the page is very old and some of the videos are unavailable: move the page to the Wiki and add the link to it to the documentation.html page -lia href=VideosConf.htmlConference Videos/a/li --- +p align=centerOfficial demos (you can trust certificates)/p li11.04 Release Branch Demo (stable) ul
[jira] [Reopened] (OFBIZ-5552) Problems in single form when use-when and position are used together
[ https://issues.apache.org/jira/browse/OFBIZ-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reopened OFBIZ-5552: I had to revert because it had some side effects, like hiding the top part of the product edit screen, reverted in trunk r1573498 R13.07 r1573500 R12.04 r1573501 R11.04 r1573502 Problems in single form when use-when and position are used together Key: OFBIZ-5552 URL: https://issues.apache.org/jira/browse/OFBIZ-5552 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Leila Mekika Assignee: Jacques Le Roux Priority: Minor Fix For: Release Branch 11.04, SVN trunk, Release Branch 12.04, Release Branch 13.07 Attachments: OFBIZ-5552.patch The service renderSingleFormString check the previous field position to see if the current field must be displayed after the previous field or on a new line. When the previous field has a use-when condition that is not valid, it remains as the currentFormField and the next field is compared with this not rendered field. If the position of this previous field is the same as the current field, the current is displayed on the next line. To reproduce, add in a single form the three fields below : field position=1 name=firstdisplay description=first//field field position=2 name=second use-when=truedisplay description=second//field field position=2 name=second use-when=falsedisplay description=second//field The field second is rendered on a new line -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OFBIZ-5473) Expense Declaration application
[ https://issues.apache.org/jira/browse/OFBIZ-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13918109#comment-13918109 ] simon maskell commented on OFBIZ-5473: -- Hi Pierre This is the current process we follow, a employee fills out an expenses form which has several categories e.g. Motor Expenses, Fuel, Parking, Travel, Subsistence, some of these categories are driven via a formula e.g. Fuel - Miles * pence per mile. Each one of this categories has an assigned GL Code and an employee is associated with a cost centre which in our case is made up of 3 levels(tags), we have started working on these tags with a PO system which is just about to go live and we are using the HR Structure to build the tags e.g. Company, IT, Service Delivery these tag the PO order and the accounting transaction. I would see this working the same for expenses. Once the expenses form has been filled out we attach all the receipts and it is sent to your manager for approval and then sent to Bought Ledger who enter the data into our AP for payment. The process using Ofbiz would need to be something like this Enter the information into Ofbiz once all information has been entered it would trigger an approval process to the manager, at this point we would need to print something off to attach to the receipts(not all our employee would be able to scan the receipts into the system). Bought Ledger would then check the information on Ofbiz and the send the expenses to our AP system for payment to be made, obviously other people would be using Ofbiz to make the payments. Hope this helps Simon Expense Declaration application --- Key: OFBIZ-5473 URL: https://issues.apache.org/jira/browse/OFBIZ-5473 Project: OFBiz Issue Type: New Feature Reporter: Pierre Smits Labels: Expense Attachments: Screen Shot 2014-02-26 at 16.33.11.png, Screen Shot 2014-02-26 at 16.33.43.png, Screen Shot 2014-02-26 at 16.35.47.png, Screen Shot 2014-02-26 at 16.51.38.png Have a new application to register expenses incurred by employees (and others) and have these reviewed for approval. This is the place holder issue for all sub issues. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OFBIZ-5552) Problems in single form when use-when and position are used together
[ https://issues.apache.org/jira/browse/OFBIZ-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13918300#comment-13918300 ] Leila Mekika commented on OFBIZ-5552: - ok, sorry Jacques. I ran tests through several screens but i didn't see this side effect. It seems to cause wrong display in product edit screen because the lastFormField is null so here is a new patch with a control of lastFormField before assignment. I hope this time it doesn't impact anything else... Problems in single form when use-when and position are used together Key: OFBIZ-5552 URL: https://issues.apache.org/jira/browse/OFBIZ-5552 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Leila Mekika Assignee: Jacques Le Roux Priority: Minor Fix For: Release Branch 11.04, SVN trunk, Release Branch 12.04, Release Branch 13.07 Attachments: OFBIZ-5552 v2.patch, OFBIZ-5552.patch The service renderSingleFormString check the previous field position to see if the current field must be displayed after the previous field or on a new line. When the previous field has a use-when condition that is not valid, it remains as the currentFormField and the next field is compared with this not rendered field. If the position of this previous field is the same as the current field, the current is displayed on the next line. To reproduce, add in a single form the three fields below : field position=1 name=firstdisplay description=first//field field position=2 name=second use-when=truedisplay description=second//field field position=2 name=second use-when=falsedisplay description=second//field The field second is rendered on a new line -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (OFBIZ-5552) Problems in single form when use-when and position are used together
[ https://issues.apache.org/jira/browse/OFBIZ-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-5552: Attachment: OFBIZ-5552 v2.patch Problems in single form when use-when and position are used together Key: OFBIZ-5552 URL: https://issues.apache.org/jira/browse/OFBIZ-5552 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Leila Mekika Assignee: Jacques Le Roux Priority: Minor Fix For: Release Branch 11.04, SVN trunk, Release Branch 12.04, Release Branch 13.07 Attachments: OFBIZ-5552 v2.patch, OFBIZ-5552.patch The service renderSingleFormString check the previous field position to see if the current field must be displayed after the previous field or on a new line. When the previous field has a use-when condition that is not valid, it remains as the currentFormField and the next field is compared with this not rendered field. If the position of this previous field is the same as the current field, the current is displayed on the next line. To reproduce, add in a single form the three fields below : field position=1 name=firstdisplay description=first//field field position=2 name=second use-when=truedisplay description=second//field field position=2 name=second use-when=falsedisplay description=second//field The field second is rendered on a new line -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (OFBIZ-4953) Order item status change issue.
[
https://issues.apache.org/jira/browse/OFBIZ-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-4953.
--
Resolution: Fixed
Fix Version/s: Release Branch 13.07
Assignee: Jacques Le Roux
Thanks Deepak for the patch, Sumit, Christian for your help!
Deepak, your (slightly modified) patch is in
trunk r1573639
R13.07 r1573640
R12.04 r1573641
R11.04 r1573642
Considering the current effort to remove Javolution use when possible, I have
replaced
FastList.EntityExprnewInstance();
by
new ArrayListEntityExpr();
and formatted to use {} around one-line-code
Trivial comment for future: when replacing a patch, don't change the name. Jira
will handle it by graying the older one with the same name, far easier to
follow for committers (when you when to do things quickly ;)
Order item status change issue.
---
Key: OFBIZ-4953
URL: https://issues.apache.org/jira/browse/OFBIZ-4953
Project: OFBiz
Issue Type: Bug
Components: order
Reporter: Deepak Dixit
Assignee: Jacques Le Roux
Fix For: Release Branch 11.04, SVN trunk, Release Branch 12.04,
Release Branch 13.07, Release 10.04
Attachments: OFBIZ-4953-R10.04.patch, OFBIZ-4953-R11.04-R12.04.patch,
OFBIZ-4953-Trunk.patch, Updated-OFBIZ-4953-R10.04.patch,
Updated-OFBIZ-4953-R11.04-R12.04.patch, Updated-OFBIZ-4953-Trunk.patch
Steps to regenerate issue:
- Crate an SO/PO with more then one line item.
- Partially ship/received any one order item.
- After partial ship/receive order should be in approve status, one order
item in in completed status and another one is in Approved status.
- Change order status to hold.
- Now again approve order.
- After approve all order order except Completed/cancelled item should go in
Approved status.
But as per the current behavior completed order item also change to approved
status.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OFBIZ-4953) Order item status change issue.
[ https://issues.apache.org/jira/browse/OFBIZ-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13918348#comment-13918348 ] Jacques Le Roux commented on OFBIZ-4953: Ha also, most of the time no needs to provide patches for releases, it's easy to handle that with merge tools when commiting Order item status change issue. --- Key: OFBIZ-4953 URL: https://issues.apache.org/jira/browse/OFBIZ-4953 Project: OFBiz Issue Type: Bug Components: order Reporter: Deepak Dixit Assignee: Jacques Le Roux Fix For: Release 10.04, Release Branch 11.04, SVN trunk, Release Branch 12.04, Release Branch 13.07 Attachments: OFBIZ-4953-R10.04.patch, OFBIZ-4953-R11.04-R12.04.patch, OFBIZ-4953-Trunk.patch, Updated-OFBIZ-4953-R10.04.patch, Updated-OFBIZ-4953-R11.04-R12.04.patch, Updated-OFBIZ-4953-Trunk.patch Steps to regenerate issue: - Crate an SO/PO with more then one line item. - Partially ship/received any one order item. - After partial ship/receive order should be in approve status, one order item in in completed status and another one is in Approved status. - Change order status to hold. - Now again approve order. - After approve all order order except Completed/cancelled item should go in Approved status. But as per the current behavior completed order item also change to approved status. -- This message was sent by Atlassian JIRA (v6.2#6252)
buildbot failure in ASF Buildbot on ofbiz-branch11
The Buildbot has detected a new failure on builder ofbiz-branch11 while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/ofbiz-branch11/builds/183 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: portunus_ubuntu Build Reason: scheduler Build Source Stamp: [branch ofbiz/branches/release11.04] 1573642 Blamelist: jleroux BUILD FAILED: failed compile_1 sincerely, -The Buildbot
[jira] [Created] (OFBIZ-5555) Approvals function doesn't work for first time
Rong Nguyen created OFBIZ-: -- Summary: Approvals function doesn't work for first time Key: OFBIZ- URL: https://issues.apache.org/jira/browse/OFBIZ- Project: OFBiz Issue Type: Bug Components: content Affects Versions: SVN trunk Reporter: Rong Nguyen Scenario: 1. Go to content webapp 2. Go to CompDoc 3. Find all record 4. Edit any record 5. Click Approvals tab -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (OFBIZ-5555) Approvals function doesn't work for first time
[ https://issues.apache.org/jira/browse/OFBIZ-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rong Nguyen updated OFBIZ-: --- Attachment: Bug-.patch Approvals function doesn't work for first time -- Key: OFBIZ- URL: https://issues.apache.org/jira/browse/OFBIZ- Project: OFBiz Issue Type: Bug Components: content Affects Versions: SVN trunk Reporter: Rong Nguyen Attachments: Bug-.patch Scenario: 1. Go to content webapp 2. Go to CompDoc 3. Find all record 4. Edit any record 5. Click Approvals tab -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (OFBIZ-5556) Tracking code report in Marketing doesn't work
[ https://issues.apache.org/jira/browse/OFBIZ-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rong Nguyen updated OFBIZ-5556: --- Attachment: Bug-5556.patch Tracking code report in Marketing doesn't work -- Key: OFBIZ-5556 URL: https://issues.apache.org/jira/browse/OFBIZ-5556 Project: OFBiz Issue Type: Bug Components: marketing Affects Versions: SVN trunk Reporter: Rong Nguyen Priority: Minor Attachments: Bug-5556.patch Scenario: 1. Go to marketing webapp 2. Go to Reports 3. In Tracking Code Report, select start data and thru data 4. Click Run Tracking code report -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (OFBIZ-5556) Tracking code report in Marketing doesn't work
Rong Nguyen created OFBIZ-5556: -- Summary: Tracking code report in Marketing doesn't work Key: OFBIZ-5556 URL: https://issues.apache.org/jira/browse/OFBIZ-5556 Project: OFBiz Issue Type: Bug Components: marketing Affects Versions: SVN trunk Reporter: Rong Nguyen Priority: Minor Attachments: Bug-5556.patch Scenario: 1. Go to marketing webapp 2. Go to Reports 3. In Tracking Code Report, select start data and thru data 4. Click Run Tracking code report -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OFBIZ-4953) Order item status change issue.
[ https://issues.apache.org/jira/browse/OFBIZ-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919008#comment-13919008 ] Deepak Dixit commented on OFBIZ-4953: - Thanks Jacques. I'll keep these thing in mind :) Order item status change issue. --- Key: OFBIZ-4953 URL: https://issues.apache.org/jira/browse/OFBIZ-4953 Project: OFBiz Issue Type: Bug Components: order Reporter: Deepak Dixit Assignee: Jacques Le Roux Fix For: Release 10.04, Release Branch 11.04, SVN trunk, Release Branch 12.04, Release Branch 13.07 Attachments: OFBIZ-4953-R10.04.patch, OFBIZ-4953-R11.04-R12.04.patch, OFBIZ-4953-Trunk.patch, Updated-OFBIZ-4953-R10.04.patch, Updated-OFBIZ-4953-R11.04-R12.04.patch, Updated-OFBIZ-4953-Trunk.patch Steps to regenerate issue: - Crate an SO/PO with more then one line item. - Partially ship/received any one order item. - After partial ship/receive order should be in approve status, one order item in in completed status and another one is in Approved status. - Change order status to hold. - Now again approve order. - After approve all order order except Completed/cancelled item should go in Approved status. But as per the current behavior completed order item also change to approved status. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OFBIZ-5556) Tracking code report in Marketing doesn't work
[ https://issues.apache.org/jira/browse/OFBIZ-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919017#comment-13919017 ] Rong Nguyen commented on OFBIZ-5556: The problem come from the current code use 'parameters.startDate'(so it will be converted to String), and the parameter should be only 'startDate' Tracking code report in Marketing doesn't work -- Key: OFBIZ-5556 URL: https://issues.apache.org/jira/browse/OFBIZ-5556 Project: OFBiz Issue Type: Bug Components: marketing Affects Versions: SVN trunk Reporter: Rong Nguyen Priority: Minor Attachments: Bug-5556.patch Scenario: 1. Go to marketing webapp 2. Go to Reports 3. In Tracking Code Report, select start data and thru data 4. Click Run Tracking code report -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OFBIZ-5555) Approvals function doesn't work for first time
[ https://issues.apache.org/jira/browse/OFBIZ-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919018#comment-13919018 ] Rong Nguyen commented on OFBIZ-: One parameter was not initiated so it caused the error for first time. Approvals function doesn't work for first time -- Key: OFBIZ- URL: https://issues.apache.org/jira/browse/OFBIZ- Project: OFBiz Issue Type: Bug Components: content Affects Versions: SVN trunk Reporter: Rong Nguyen Attachments: Bug-.patch Scenario: 1. Go to content webapp 2. Go to CompDoc 3. Find all record 4. Edit any record 5. Click Approvals tab -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (OFBIZ-5555) Approvals function doesn't work for first time
[ https://issues.apache.org/jira/browse/OFBIZ-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rong Nguyen updated OFBIZ-: --- Priority: Minor (was: Major) Approvals function doesn't work for first time -- Key: OFBIZ- URL: https://issues.apache.org/jira/browse/OFBIZ- Project: OFBiz Issue Type: Bug Components: content Affects Versions: SVN trunk Reporter: Rong Nguyen Priority: Minor Attachments: Bug-.patch Scenario: 1. Go to content webapp 2. Go to CompDoc 3. Find all record 4. Edit any record 5. Click Approvals tab -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (OFBIZ-5557) Render multiMenu problem when linktype=hidden-form
Rong Nguyen created OFBIZ-5557: -- Summary: Render multiMenu problem when linktype=hidden-form Key: OFBIZ-5557 URL: https://issues.apache.org/jira/browse/OFBIZ-5557 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Reporter: Rong Nguyen Scenario: 1. Go to Content webapp 2. Go to CompDoc menuitem 3. Search 4. Go to 'Tree' view 5. We can not use 'Up' and 'Down' function When menu with linktype=hidden-form was render for each menu, they has the same name for form element, so it cause error. My solution is add extra attribute(extra-index) for Menu, and then in menu definition we provide this attribute and the forms with different name will be rendered. My implement was tested in this bug for Content webapp -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (OFBIZ-5557) Render multiMenu problem when linktype=hidden-form
[ https://issues.apache.org/jira/browse/OFBIZ-5557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rong Nguyen updated OFBIZ-5557: --- Attachment: ModelMenu.java Render multiMenu problem when linktype=hidden-form Key: OFBIZ-5557 URL: https://issues.apache.org/jira/browse/OFBIZ-5557 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Reporter: Rong Nguyen Attachments: 0001-Content.patch, ModelMenu.java Scenario: 1. Go to Content webapp 2. Go to CompDoc menuitem 3. Search 4. Go to 'Tree' view 5. We can not use 'Up' and 'Down' function When menu with linktype=hidden-form was render for each menu, they has the same name for form element, so it cause error. My solution is add extra attribute(extra-index) for Menu, and then in menu definition we provide this attribute and the forms with different name will be rendered. My implement was tested in this bug for Content webapp -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (OFBIZ-5557) Render multiMenu problem when linktype=hidden-form
[ https://issues.apache.org/jira/browse/OFBIZ-5557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rong Nguyen updated OFBIZ-5557: --- Attachment: 0001-Content.patch Render multiMenu problem when linktype=hidden-form Key: OFBIZ-5557 URL: https://issues.apache.org/jira/browse/OFBIZ-5557 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Reporter: Rong Nguyen Attachments: 0001-Content.patch, ModelMenu.java Scenario: 1. Go to Content webapp 2. Go to CompDoc menuitem 3. Search 4. Go to 'Tree' view 5. We can not use 'Up' and 'Down' function When menu with linktype=hidden-form was render for each menu, they has the same name for form element, so it cause error. My solution is add extra attribute(extra-index) for Menu, and then in menu definition we provide this attribute and the forms with different name will be rendered. My implement was tested in this bug for Content webapp -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OFBIZ-5557) Render multiMenu problem when linktype=hidden-form
[ https://issues.apache.org/jira/browse/OFBIZ-5557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919023#comment-13919023 ] Rong Nguyen commented on OFBIZ-5557: My patch does not include some changes from ModelMenu.java, so we should apply patch with ModelMenu.java Render multiMenu problem when linktype=hidden-form Key: OFBIZ-5557 URL: https://issues.apache.org/jira/browse/OFBIZ-5557 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Reporter: Rong Nguyen Attachments: 0001-Content.patch, ModelMenu.java Scenario: 1. Go to Content webapp 2. Go to CompDoc menuitem 3. Search 4. Go to 'Tree' view 5. We can not use 'Up' and 'Down' function When menu with linktype=hidden-form was render for each menu, they has the same name for form element, so it cause error. My solution is add extra attribute(extra-index) for Menu, and then in menu definition we provide this attribute and the forms with different name will be rendered. My implement was tested in this bug for Content webapp -- This message was sent by Atlassian JIRA (v6.2#6252)
