[jira] [Created] (OFBIZ-4602) Null values are not synchronized in http mode
Null values are not synchronized in http mode - Key: OFBIZ-4602 URL: https://issues.apache.org/jira/browse/OFBIZ-4602 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release 10.04, Release 09.04.01, Release 09.04, Release 4.0, SVN trunk Environment: Using entity synchronization trough HTTP Reporter: Patrick Antivackis In order to send over http the values to create, store and remove, Ofbiz is Xml serializing the values. GenericValue xml serialization is managed in GenericEntity.makeXmlElement, unfortunately this method just don't serialized null valued fields. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4602) Null values are not synchronized in http mode
[ https://issues.apache.org/jira/browse/OFBIZ-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Antivackis updated OFBIZ-4602: -- Environment: Using entity synchronization over HTTP (not RMI) (was: Using entity synchronization trough HTTP) Null values are not synchronized in http mode - Key: OFBIZ-4602 URL: https://issues.apache.org/jira/browse/OFBIZ-4602 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release 4.0, Release 09.04, Release 09.04.01, Release 10.04, SVN trunk Environment: Using entity synchronization over HTTP (not RMI) Reporter: Patrick Antivackis In order to send over http the values to create, store and remove, Ofbiz is Xml serializing the values. GenericValue xml serialization is managed in GenericEntity.makeXmlElement, unfortunately this method just don't serialized null valued fields. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4602) Null values are not synchronized in http mode
[ https://issues.apache.org/jira/browse/OFBIZ-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Antivackis updated OFBIZ-4602: -- Attachment: patch-OFBIZ-4602.txt To solve this issue, I managed null value the same way GenericEntity.setString (which is used for the Xml deserializing). I only managed until case 10, because i'm not sure the setString for the cases 11 to 15 are well managed (not taking care of null value) Null values are not synchronized in http mode - Key: OFBIZ-4602 URL: https://issues.apache.org/jira/browse/OFBIZ-4602 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release 4.0, Release 09.04, Release 09.04.01, Release 10.04, SVN trunk Environment: Using entity synchronization over HTTP (not RMI) Reporter: Patrick Antivackis Attachments: patch-OFBIZ-4602.txt In order to send over http the values to create, store and remove, Ofbiz is Xml serializing the values. GenericValue xml serialization is managed in GenericEntity.makeXmlElement, unfortunately this method just don't serialized null valued fields. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-4599) Product NOTFOUND causes java.lang.NullPointerException, ugly screen, and excessive logging
[ https://issues.apache.org/jira/browse/OFBIZ-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13161487#comment-13161487 ] mz4wheeler commented on OFBIZ-4599: --- It looks like trunk and 11.04 act differently when a non-existent product is accessed. Trunk shows: 404. That's an error. The requested URL /ecommerce/dropship1-dropShip1-px was not found on this server. That's all we know. 11.04 shows the red rectangle with the java error. I seem to remember a recent Jira related to /error which may have not been pushed to 11.04. Even so, Product.groovy should be fixed to handle the java.lang.NullPointerException exception. Less logging will occur (saves disk IO). Product NOTFOUND causes java.lang.NullPointerException, ugly screen, and excessive logging -- Key: OFBIZ-4599 URL: https://issues.apache.org/jira/browse/OFBIZ-4599 Project: OFBiz Issue Type: Bug Components: specialpurpose/ecommerce Affects Versions: Release Branch 11.04, SVN trunk Environment: Any Reporter: mz4wheeler Priority: Minor Attachments: OFBIZ-4599.patch If you manually enter a URL (or via search engine) for a non-existing product, the following (annoying) long java exception is logged. 2011-11-30 20:56:35,431 (TP-Processor3) [ModelScreen.java:401:ERROR] Error rendering screen [component://ecommerce/widget/CatalogScreens.xml#product]: java.lang.NullPointerException: Cannot get property 'isVirtual' on null object. Rolling back transaction. 2011-11-30 20:56:35,436 (TP-Processor3) [TransactionUtil.java:349:INFO ] [TransactionUtil.rollback] transaction rolled back 2011-11-30 20:56:35,437 (TP-Processor3) [TransactionUtil.java:274:WARN ] [TransactionUtil.commit] Not committing transaction, status is No Transaction (6) 2011-11-30 20:56:35,446 (TP-Processor3) [ ControlServlet.java:227:ERROR] exception report -- Error in request handler: Exception: org.ofbiz.widget.screen.ScreenRenderException Message: Error rendering screen [component://ecommerce/widget/CatalogScreens.xml#product]: java.lang.NullPointerException: Cannot get property 'isVirtual' on null object (Cannot get property 'isVirtual' on null object) cause - Exception: java.lang.NullPointerException Message: Cannot get property 'isVirtual' on null object stack trace --- java.lang.NullPointerException: Cannot get property 'isVirtual' on null object org.codehaus.groovy.runtime.NullObject.getProperty(NullObject.java:56) org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:156) org.codehaus.groovy.runtime.callsite.NullCallSite.getProperty(NullCallSite.java:44) org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:235) Product.run(Product.groovy:48) etc ... etc ... etc ... org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690) java.lang.Thread.run(Thread.java:662) 2011-11-30 20:56:35,449 (TP-Processor3) [ ControlServlet.java:243:ERROR] An error occurred, going to the errorPage: /error/error.jsp 2011-11-30 20:56:35,450 (TP-Processor3) [ ControlServlet.java:250:ERROR] Including errorPage: /error/error.jsp 2011-11-30 20:56:37,437 (TP-Processor3) [ ControlServlet.java:324:INFO ] [[[product] Request Done- total:6.14,since last([product] Request...):6.14]] On top of this, the following (BIG RED) error screen is shown to the user: :ERROR MESSAGE: org.ofbiz.widget.screen.ScreenRenderException: Error rendering screen [component://ecommerce/widget/CatalogScreens.xml#product]: java.lang.NullPointerException: Cannot get property 'isVirtual' on null object (Cannot get property 'isVirtual' on null object) This is caused by Product.groovy performing a search for a product (which fails) and then trying to reference product.isVariant, which doesn't exist. After the simple patch, the store now shows the default ecommerce screen, with the following message in the main ecommerce area: RESULT: Product not found for Product ID 1001JAPANCROS! Much better. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (OFBIZ-4600) When i used Person Tabel For new Record Creation
[ https://issues.apache.org/jira/browse/OFBIZ-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-4600. -- Assignee: Hans Bakker When i used Person Tabel For new Record Creation Key: OFBIZ-4600 URL: https://issues.apache.org/jira/browse/OFBIZ-4600 Project: OFBiz Issue Type: Bug Reporter: Dhiraj Gupta Assignee: Hans Bakker I have Developed new module enquiry in ofbiz. I created a form. I am trying to create record using person table through form . It gives the following Error. Message: Error while inserting: [GenericEntity:Person][createdStamp,2011-12-10 12:24:58.963(java.sql.Timestamp)][createdTxStamp,2011-12-10 12:24:58.207(java.sql.Timestamp)][firstName,ghjghj(java.lang.String)][lastName,jghjghj(java.lang.String)][lastUpdatedStamp,2011-12-10 12:24:58.963(java.sql.Timestamp)][lastUpdatedTxStamp,2011-12-10 12:24:58.207(java.sql.Timestamp)][partyId,10040(java.lang.String)][salutation,hjghjg(java.lang.String)] (SQL Exception while executing the following:INSERT INTO OFBIZ.PERSON (PARTY_ID, SALUTATION, FIRST_NAME, MIDDLE_NAME, LAST_NAME, PERSONAL_TITLE, SUFFIX, NICKNAME, FIRST_NAME_LOCAL, MIDDLE_NAME_LOCAL, LAST_NAME_LOCAL, OTHER_LOCAL, MEMBER_ID, GENDER, BIRTH_DATE, DECEASED_DATE, HEIGHT, WEIGHT, MOTHERS_MAIDEN_NAME, MARITAL_STATUS, SOCIAL_SECURITY_NUMBER, PASSPORT_NUMBER, PASSPORT_EXPIRE_DATE, TOTAL_YEARS_WORK_EXPERIENCE, COMMENTS, EMPLOYMENT_STATUS_ENUM_ID, RESIDENCE_STATUS_ENUM_ID, OCCUPATION, YEARS_WITH_EMPLOYER, MONTHS_WITH_EMPLOYER, EXISTING_CUSTOMER, CARD_ID, LAST_UPDATED_STAMP, LAST_UPDATED_TX_STAMP, CREATED_STAMP, CREATED_TX_STAMP) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (INSERT on table 'PERSON' caused a violation of foreign key constraint 'PERSON_PARTY' for key (10040). The statement has been rolled back.)) please Sort out this error Thanks Dhiraj -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OFBIZ-4603) Minor fix for Manage Picklist tab in Facility
Minor fix for Manage Picklist tab in Facility - Key: OFBIZ-4603 URL: https://issues.apache.org/jira/browse/OFBIZ-4603 Project: OFBiz Issue Type: Bug Components: ALL APPLICATIONS Affects Versions: Release 10.04, Release Branch 11.04, SVN trunk Reporter: Ankit Jain Priority: Minor On this page https://demo-trunk.ofbiz.apache.org/facility/control/PicklistManage?facilityId=WebStoreWarehouse the table header is not correct the orderId is showing above. It has a minor fix the the tr tag is not closed that's why its not displaying correctly, its a minor fix so I am not creating any patch please go to PickListManage.ftl in facility and on line no 126 close this tag tr class=header-row and its fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4604) French translation correction for ListWorkEffortTimeEntries label
[ https://issues.apache.org/jira/browse/OFBIZ-4604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-4604: -- Attachment: WorkEffortLabel.patch path for workEffortUiLabel.xml file French translation correction for ListWorkEffortTimeEntries label - Key: OFBIZ-4604 URL: https://issues.apache.org/jira/browse/OFBIZ-4604 Project: OFBiz Issue Type: Improvement Components: workeffort Reporter: Olivier Heintz Priority: Minor Attachments: WorkEffortLabel.patch Previous translation was Planifications horaires de la tâche I propose Détails des temps passés sur la tâche TimeEntries is more used for history not for schedule -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OFBIZ-4604) French translation correction for ListWorkEffortTimeEntries label
French translation correction for ListWorkEffortTimeEntries label - Key: OFBIZ-4604 URL: https://issues.apache.org/jira/browse/OFBIZ-4604 Project: OFBiz Issue Type: Improvement Components: workeffort Reporter: Olivier Heintz Priority: Minor Attachments: WorkEffortLabel.patch Previous translation was Planifications horaires de la tâche I propose Détails des temps passés sur la tâche TimeEntries is more used for history not for schedule -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4603) Minor fix for Manage Picklist tab in Facility
[ https://issues.apache.org/jira/browse/OFBIZ-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker reassigned OFBIZ-4603: -- Assignee: Hans Bakker Minor fix for Manage Picklist tab in Facility - Key: OFBIZ-4603 URL: https://issues.apache.org/jira/browse/OFBIZ-4603 Project: OFBiz Issue Type: Bug Components: ALL APPLICATIONS Affects Versions: Release 10.04, Release Branch 11.04, SVN trunk Reporter: Ankit Jain Assignee: Hans Bakker Priority: Minor On this page https://demo-trunk.ofbiz.apache.org/facility/control/PicklistManage?facilityId=WebStoreWarehouse the table header is not correct the orderId is showing above. It has a minor fix the the tr tag is not closed that's why its not displaying correctly, its a minor fix so I am not creating any patch please go to PickListManage.ftl in facility and on line no 126 close this tag tr class=header-row and its fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (OFBIZ-4603) Minor fix for Manage Picklist tab in Facility
[ https://issues.apache.org/jira/browse/OFBIZ-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker closed OFBIZ-4603. -- Resolution: Fixed Fix Version/s: SVN trunk thank you for reporting: revision 1209413 Minor fix for Manage Picklist tab in Facility - Key: OFBIZ-4603 URL: https://issues.apache.org/jira/browse/OFBIZ-4603 Project: OFBiz Issue Type: Bug Components: ALL APPLICATIONS Affects Versions: Release 10.04, Release Branch 11.04, SVN trunk Reporter: Ankit Jain Assignee: Hans Bakker Priority: Minor Fix For: SVN trunk On this page https://demo-trunk.ofbiz.apache.org/facility/control/PicklistManage?facilityId=WebStoreWarehouse the table header is not correct the orderId is showing above. It has a minor fix the the tr tag is not closed that's why its not displaying correctly, its a minor fix so I am not creating any patch please go to PickListManage.ftl in facility and on line no 126 close this tag tr class=header-row and its fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-4603) Minor fix for Manage Picklist tab in Facility
[ https://issues.apache.org/jira/browse/OFBIZ-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13161552#comment-13161552 ] Ankit Jain commented on OFBIZ-4603: --- Thanks Hans, please also apply this change in release10.04 , 11.04. Minor fix for Manage Picklist tab in Facility - Key: OFBIZ-4603 URL: https://issues.apache.org/jira/browse/OFBIZ-4603 Project: OFBiz Issue Type: Bug Components: ALL APPLICATIONS Affects Versions: Release 10.04, Release Branch 11.04, SVN trunk Reporter: Ankit Jain Assignee: Hans Bakker Priority: Minor Fix For: SVN trunk On this page https://demo-trunk.ofbiz.apache.org/facility/control/PicklistManage?facilityId=WebStoreWarehouse the table header is not correct the orderId is showing above. It has a minor fix the the tr tag is not closed that's why its not displaying correctly, its a minor fix so I am not creating any patch please go to PickListManage.ftl in facility and on line no 126 close this tag tr class=header-row and its fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4502) Improved CMS tree: more functionality and faster for large trees
[ https://issues.apache.org/jira/browse/OFBIZ-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christoph Neuroth updated OFBIZ-4502: - Attachment: CMS-Tree-Improvement-2.patch New version of our patch, applied against current trunk. Improved CMS tree: more functionality and faster for large trees Key: OFBIZ-4502 URL: https://issues.apache.org/jira/browse/OFBIZ-4502 Project: OFBiz Issue Type: Improvement Components: content Affects Versions: SVN trunk Reporter: Martin Kreidenweis Attachments: CMS-Tree-Improvement-2.patch, CMS-Tree-Improvement.patch We here at [Lusini|http://www.lusini.de/] did several improvements to the CMS backend to make it more useable for large CMS installations. * Improved performance of CMS tree ** loading nodes dynamically using AJAX *** Created ContentJsonEvents to handle the JSON calls ** use OFBiz entity caches ** removed duplicate execution of WebSitePublishPoint.groovy *** removed reference from controller.xml as it is not used anywhere * Moving nodes in CMS tree possible now using drag'n'drop ** ContentJsonEvents returns updated node attributes ** Adjusted WebSiteCMSNav.ftl to update the moved node with the data from the ajax request ** Needed to replace the jstree jQuery plugin by the current version available on the jstree website * Made nodes deleteable ** added remove to context menu ** We did not want to delete the WebSitePathAlias entities right away, so we added a fromDate and thruDate to it. *** extended WebSitePathAlias entity definition: added fromDate and thruDate *** now checking for date range everywhere when accessing path aliases *** This also allows users to publish or unpublish contents under a certain URL automatically at some time in the future. ** created event to delete a node *** thruDate of all assocs pointing to this node are set to current timestamp *** thruDate of WebSitePathAliases pointing to this content or any contents below are set to current timestamp *** this way nothing is actually removed from the DB and a undo would be possible if necessary ** extracted context menu to variable so it can be reused for all trees * fixed missing references to uiLabels in CMS menu bar * Activated cookie plugin so the selected node is remembered To migrate existing path aliases the following SQL statements can be used: BEGIN; UPDATE web_site_path_alias SET from_date=w.created_stamp FROM web_site_path_alias w WHERE w.path_alias=web_site_path_alias.path_alias; ALTER TABLE web_site_path_alias DROP CONSTRAINT pk_web_site_path_alias, ADD CONSTRAINT pk_web_site_path_alias PRIMARY KEY (web_site_id, path_alias, from_date); COMMIT; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-4502) Improved CMS tree: more functionality and faster for large trees
[ https://issues.apache.org/jira/browse/OFBIZ-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13161691#comment-13161691 ] Christoph Neuroth commented on OFBIZ-4502: -- We further improved the CMS Tree patch - it will now automatically open the parent of the new content and select it. What's your opinion on the patch? Any problems that block integrating our changes? Improved CMS tree: more functionality and faster for large trees Key: OFBIZ-4502 URL: https://issues.apache.org/jira/browse/OFBIZ-4502 Project: OFBiz Issue Type: Improvement Components: content Affects Versions: SVN trunk Reporter: Martin Kreidenweis Attachments: CMS-Tree-Improvement-2.patch, CMS-Tree-Improvement.patch We here at [Lusini|http://www.lusini.de/] did several improvements to the CMS backend to make it more useable for large CMS installations. * Improved performance of CMS tree ** loading nodes dynamically using AJAX *** Created ContentJsonEvents to handle the JSON calls ** use OFBiz entity caches ** removed duplicate execution of WebSitePublishPoint.groovy *** removed reference from controller.xml as it is not used anywhere * Moving nodes in CMS tree possible now using drag'n'drop ** ContentJsonEvents returns updated node attributes ** Adjusted WebSiteCMSNav.ftl to update the moved node with the data from the ajax request ** Needed to replace the jstree jQuery plugin by the current version available on the jstree website * Made nodes deleteable ** added remove to context menu ** We did not want to delete the WebSitePathAlias entities right away, so we added a fromDate and thruDate to it. *** extended WebSitePathAlias entity definition: added fromDate and thruDate *** now checking for date range everywhere when accessing path aliases *** This also allows users to publish or unpublish contents under a certain URL automatically at some time in the future. ** created event to delete a node *** thruDate of all assocs pointing to this node are set to current timestamp *** thruDate of WebSitePathAliases pointing to this content or any contents below are set to current timestamp *** this way nothing is actually removed from the DB and a undo would be possible if necessary ** extracted context menu to variable so it can be reused for all trees * fixed missing references to uiLabels in CMS menu bar * Activated cookie plugin so the selected node is remembered To migrate existing path aliases the following SQL statements can be used: BEGIN; UPDATE web_site_path_alias SET from_date=w.created_stamp FROM web_site_path_alias w WHERE w.path_alias=web_site_path_alias.path_alias; ALTER TABLE web_site_path_alias DROP CONSTRAINT pk_web_site_path_alias, ADD CONSTRAINT pk_web_site_path_alias PRIMARY KEY (web_site_id, path_alias, from_date); COMMIT; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OFBIZ-4605) Use-when not working on multi-forms submit button
Use-when not working on multi-forms submit button - Key: OFBIZ-4605 URL: https://issues.apache.org/jira/browse/OFBIZ-4605 Project: OFBiz Issue Type: Bug Components: framework Reporter: Leila Mekika Priority: Minor The submit button of a form multi is rendered event if we had a use-when condition -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4605) Use-when not working on multi-forms submit button
[ https://issues.apache.org/jira/browse/OFBIZ-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-4605: Description: The submit button of a form multi is rendered even if we add a use-when condition (was: The submit button of a form multi is rendered event if we had a use-when condition) Use-when not working on multi-forms submit button - Key: OFBIZ-4605 URL: https://issues.apache.org/jira/browse/OFBIZ-4605 Project: OFBiz Issue Type: Bug Components: framework Reporter: Leila Mekika Priority: Minor The submit button of a form multi is rendered even if we add a use-when condition -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4605) Use-when not working on multi-forms submit button
[ https://issues.apache.org/jira/browse/OFBIZ-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-4605: Attachment: OFBIZ-4605.patch Use-when not working on multi-forms submit button - Key: OFBIZ-4605 URL: https://issues.apache.org/jira/browse/OFBIZ-4605 Project: OFBiz Issue Type: Bug Components: framework Reporter: Leila Mekika Priority: Minor Attachments: OFBIZ-4605.patch The submit button of a form multi is rendered even if we add a use-when condition -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-4390) Ecommerce Error Page Does Not Work
[ https://issues.apache.org/jira/browse/OFBIZ-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13161956#comment-13161956 ] mz4wheeler commented on OFBIZ-4390: --- Can this be back ported to 11.04 as well? Ecommerce Error Page Does Not Work -- Key: OFBIZ-4390 URL: https://issues.apache.org/jira/browse/OFBIZ-4390 Project: OFBiz Issue Type: Bug Components: specialpurpose/ecommerce Reporter: Sam Hamilton Assignee: Hans Bakker Priority: Minor Fix For: SVN trunk Attachments: OFBIZ-4390-error.txt, OFBIZ-4390.patch If you are using the ecommerce app and you force it to generate a 404 error page it redirects back to /control/main. You can test the 404 error out here - http://demo-trunk.ofbiz.apache.org/ecommerce/please-give-me-an-error/ This default behaviour will confuse search engines as they expect to get a 404 error if a pages does not exist on a website. As pointed out by Bilgin on the mailing list adding the following code into web.xml should resolve the problem however it just generates more errors due to the redirect to /control/main is in place. error-page error-code404/error-code location/error/error.jsp/location /error-page -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4502) Improved CMS tree: more functionality and faster for large trees
[ https://issues.apache.org/jira/browse/OFBIZ-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker reassigned OFBIZ-4502: -- Assignee: Hans Bakker Improved CMS tree: more functionality and faster for large trees Key: OFBIZ-4502 URL: https://issues.apache.org/jira/browse/OFBIZ-4502 Project: OFBiz Issue Type: Improvement Components: content Affects Versions: SVN trunk Reporter: Martin Kreidenweis Assignee: Hans Bakker Attachments: CMS-Tree-Improvement-2.patch, CMS-Tree-Improvement.patch We here at [Lusini|http://www.lusini.de/] did several improvements to the CMS backend to make it more useable for large CMS installations. * Improved performance of CMS tree ** loading nodes dynamically using AJAX *** Created ContentJsonEvents to handle the JSON calls ** use OFBiz entity caches ** removed duplicate execution of WebSitePublishPoint.groovy *** removed reference from controller.xml as it is not used anywhere * Moving nodes in CMS tree possible now using drag'n'drop ** ContentJsonEvents returns updated node attributes ** Adjusted WebSiteCMSNav.ftl to update the moved node with the data from the ajax request ** Needed to replace the jstree jQuery plugin by the current version available on the jstree website * Made nodes deleteable ** added remove to context menu ** We did not want to delete the WebSitePathAlias entities right away, so we added a fromDate and thruDate to it. *** extended WebSitePathAlias entity definition: added fromDate and thruDate *** now checking for date range everywhere when accessing path aliases *** This also allows users to publish or unpublish contents under a certain URL automatically at some time in the future. ** created event to delete a node *** thruDate of all assocs pointing to this node are set to current timestamp *** thruDate of WebSitePathAliases pointing to this content or any contents below are set to current timestamp *** this way nothing is actually removed from the DB and a undo would be possible if necessary ** extracted context menu to variable so it can be reused for all trees * fixed missing references to uiLabels in CMS menu bar * Activated cookie plugin so the selected node is remembered To migrate existing path aliases the following SQL statements can be used: BEGIN; UPDATE web_site_path_alias SET from_date=w.created_stamp FROM web_site_path_alias w WHERE w.path_alias=web_site_path_alias.path_alias; ALTER TABLE web_site_path_alias DROP CONSTRAINT pk_web_site_path_alias, ADD CONSTRAINT pk_web_site_path_alias PRIMARY KEY (web_site_id, path_alias, from_date); COMMIT; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
