[jira] [Closed] (OFBIZ-10008) Add mechanism to prevent the usage of EntitySyncRemove
[ https://issues.apache.org/jira/browse/OFBIZ-10008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit closed OFBIZ-10008. Resolution: Fixed Fixed at Trunk [https://github.com/apache/ofbiz-framework/commit/574bf8fa3181fc79a190d165105019e0b461412e/] R18.12 https://github.com/apache/ofbiz-framework/commit/4d689bdfb439170fa4460c21273bb4e6c90318f7/ > Add mechanism to prevent the usage of EntitySyncRemove > -- > > Key: OFBIZ-10008 > URL: https://issues.apache.org/jira/browse/OFBIZ-10008 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Chandan Khandelwal >Assignee: Deepak Dixit >Priority: Major > Fix For: 18.12.01 > > Attachments: OFBIZ-10008.patch > > > No configurations is available to disable usage of EntitySyncRemove. And it's > creating problems when having a large database and frequent delete operations. > saveEntitySyncRemoveInfo is used to create EntitySyncRemove records in > GenericDelegator.removeValue() and removeByPrimaryKey(). > The idea is to add a mechanism to prevent the usage of EntitySyncRemove by > adding a property in general.properties file used to configure in > entityengine.xml > Tenants should be considered, OFBIZ-10468 has been created for that. > Also I wondered if the test/filter should be part of > saveEntitySyncRemoveInfo() (comment "don't store remove info on entities > where it is disabled") but it would be diluted and is more appropriate at a > higher level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10008) Add mechanism to prevent the usage of EntitySyncRemove
[ https://issues.apache.org/jira/browse/OFBIZ-10008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285666#comment-17285666 ] ASF subversion and git services commented on OFBIZ-10008: - Commit 4d689bdfb439170fa4460c21273bb4e6c90318f7 in ofbiz-framework's branch refs/heads/release18.12 from Deepak Dixit [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=4d689bd ] Fixed: Corrected property name as defined in general.properties (OFBIZ-10008) > Add mechanism to prevent the usage of EntitySyncRemove > -- > > Key: OFBIZ-10008 > URL: https://issues.apache.org/jira/browse/OFBIZ-10008 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Chandan Khandelwal >Assignee: Deepak Dixit >Priority: Major > Fix For: 18.12.01 > > Attachments: OFBIZ-10008.patch > > > No configurations is available to disable usage of EntitySyncRemove. And it's > creating problems when having a large database and frequent delete operations. > saveEntitySyncRemoveInfo is used to create EntitySyncRemove records in > GenericDelegator.removeValue() and removeByPrimaryKey(). > The idea is to add a mechanism to prevent the usage of EntitySyncRemove by > adding a property in general.properties file used to configure in > entityengine.xml > Tenants should be considered, OFBIZ-10468 has been created for that. > Also I wondered if the test/filter should be part of > saveEntitySyncRemoveInfo() (comment "don't store remove info on entities > where it is disabled") but it would be diluted and is more appropriate at a > higher level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10008) Add mechanism to prevent the usage of EntitySyncRemove
[ https://issues.apache.org/jira/browse/OFBIZ-10008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285662#comment-17285662 ] ASF subversion and git services commented on OFBIZ-10008: - Commit 574bf8fa3181fc79a190d165105019e0b461412e in ofbiz-framework's branch refs/heads/trunk from Deepak Dixit [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=574bf8f ] Fixed: Corrected property name as defined in general.properties (OFBIZ-10008) > Add mechanism to prevent the usage of EntitySyncRemove > -- > > Key: OFBIZ-10008 > URL: https://issues.apache.org/jira/browse/OFBIZ-10008 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Chandan Khandelwal >Assignee: Deepak Dixit >Priority: Major > Fix For: 18.12.01 > > Attachments: OFBIZ-10008.patch > > > No configurations is available to disable usage of EntitySyncRemove. And it's > creating problems when having a large database and frequent delete operations. > saveEntitySyncRemoveInfo is used to create EntitySyncRemove records in > GenericDelegator.removeValue() and removeByPrimaryKey(). > The idea is to add a mechanism to prevent the usage of EntitySyncRemove by > adding a property in general.properties file used to configure in > entityengine.xml > Tenants should be considered, OFBIZ-10468 has been created for that. > Also I wondered if the test/filter should be part of > saveEntitySyncRemoveInfo() (comment "don't store remove info on entities > where it is disabled") but it would be diluted and is more appropriate at a > higher level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (OFBIZ-10008) Add mechanism to prevent the usage of EntitySyncRemove
[ https://issues.apache.org/jira/browse/OFBIZ-10008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit reopened OFBIZ-10008: -- Assignee: Deepak Dixit (was: Jacques Le Roux) Inconsistency in config name. > Add mechanism to prevent the usage of EntitySyncRemove > -- > > Key: OFBIZ-10008 > URL: https://issues.apache.org/jira/browse/OFBIZ-10008 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Chandan Khandelwal >Assignee: Deepak Dixit >Priority: Major > Fix For: 18.12.01 > > Attachments: OFBIZ-10008.patch > > > No configurations is available to disable usage of EntitySyncRemove. And it's > creating problems when having a large database and frequent delete operations. > saveEntitySyncRemoveInfo is used to create EntitySyncRemove records in > GenericDelegator.removeValue() and removeByPrimaryKey(). > The idea is to add a mechanism to prevent the usage of EntitySyncRemove by > adding a property in general.properties file used to configure in > entityengine.xml > Tenants should be considered, OFBIZ-10468 has been created for that. > Also I wondered if the test/filter should be part of > saveEntitySyncRemoveInfo() (comment "don't store remove info on entities > where it is disabled") but it would be diluted and is more appropriate at a > higher level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12171) Handling the JCenter shutdown
[ https://issues.apache.org/jira/browse/OFBIZ-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285536#comment-17285536 ] Michael Brohl commented on OFBIZ-12171: --- The migration for r17.12 is going to be tough. If I update to the lowest Gradle version supporting metadataSources (4.5.1) we need to change the build.gradle as well. There seem to be incompatibilities with the clean* tasks. I am also currently facing this bug: https://www.jfrog.com/jira/browse/RTFACT-24621 causing compile errors because UOUtils cannot be found. I'm at it but it won't go as fast as I'd wish it would. > Handling the JCenter shutdown > - > > Key: OFBIZ-12171 > URL: https://issues.apache.org/jira/browse/OFBIZ-12171 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS >Affects Versions: Release Branch 18.12, Trunk, 17.12.05 >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Major > Labels: backport-needed > Fix For: Upcoming Branch > > > Citing Taher's message at [2]: > Hello Everyone, > > I received emails and checked resources [1] that seem to confirm JCenter from > JFrog is going down and that the last day of operation for the repository is > going to be May 1st 2021. > > This is a big deal as many running instances will crash unless updated, so > not only do future versions of OFBiz need to adapt, but also existing > installations. > > I'm not sure how to best handle this? Especially for production instances out > there on older versions of OFBiz. Maybe one solution is to host the existing > libraries in some temporary location or try to migrate them to MavenCentral > ... Whatever is the solution I think we should make a fast move. > > [1] > [https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter] > > [https://www.infoq.com/news/2021/02/jfrog-jcenter-bintray-closure] > [2] > [https://lists.apache.org/thread.html/rf8e883ca8b90d51ad9d6d48c46f8f1fcc1cb82cce802daeeab0b910a%40%3Cdev.ofbiz.apache.org%3E] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12171) Handling the JCenter shutdown
[ https://issues.apache.org/jira/browse/OFBIZ-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285468#comment-17285468 ] ASF subversion and git services commented on OFBIZ-12171: - Commit 8a3d230ba6add546356b617c7a4f94ba183d6563 in ofbiz-plugins's branch refs/heads/trunk from Michael Brohl [ https://gitbox.apache.org/repos/asf?p=ofbiz-plugins.git;h=8a3d230 ] Improved: Removes obsolete comment (OFBIZ-12171) > Handling the JCenter shutdown > - > > Key: OFBIZ-12171 > URL: https://issues.apache.org/jira/browse/OFBIZ-12171 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS >Affects Versions: Release Branch 18.12, Trunk, 17.12.05 >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Major > Labels: backport-needed > Fix For: Upcoming Branch > > > Citing Taher's message at [2]: > Hello Everyone, > > I received emails and checked resources [1] that seem to confirm JCenter from > JFrog is going down and that the last day of operation for the repository is > going to be May 1st 2021. > > This is a big deal as many running instances will crash unless updated, so > not only do future versions of OFBiz need to adapt, but also existing > installations. > > I'm not sure how to best handle this? Especially for production instances out > there on older versions of OFBiz. Maybe one solution is to host the existing > libraries in some temporary location or try to migrate them to MavenCentral > ... Whatever is the solution I think we should make a fast move. > > [1] > [https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter] > > [https://www.infoq.com/news/2021/02/jfrog-jcenter-bintray-closure] > [2] > [https://lists.apache.org/thread.html/rf8e883ca8b90d51ad9d6d48c46f8f1fcc1cb82cce802daeeab0b910a%40%3Cdev.ofbiz.apache.org%3E] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-12178) ModelInduceFromDb does not show entity relations.
[ https://issues.apache.org/jira/browse/OFBIZ-12178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-12178: -- Summary: ModelInduceFromDb does not show entity relations. (was: ModelInduceFromDb does not show realtions.) > ModelInduceFromDb does not show entity relations. > - > > Key: OFBIZ-12178 > URL: https://issues.apache.org/jira/browse/OFBIZ-12178 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Release Branch 18.12, Trunk >Reporter: Benjamin Jugl >Assignee: Benjamin Jugl >Priority: Minor > > As encountered in OFBIZ-6510, the ModelInduceFromDb does currently not > include entity relations and foreign key constraints. Since they are an > important part of the database model, we should fix that. > I could track down the problem to an incomplete invocation of the ModelEntity > through the constructor used in the DatabaseUtil.induceModelFromDb() Methods. > This constructor does not initialize the Relations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12166) Default ordering of webapps titles in main menu
[ https://issues.apache.org/jira/browse/OFBIZ-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285231#comment-17285231 ] Jacques Le Roux commented on OFBIZ-12166: - Hi Michael, I did in my last message: https://markmail.org/message/bvox3y4y4rfcwsp3 > Default ordering of webapps titles in main menu > --- > > Key: OFBIZ-12166 > URL: https://issues.apache.org/jira/browse/OFBIZ-12166 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: 18.12.01, Upcoming Branch > > > This follows https://markmail.org/message/ftgfpwztflty7klb, excerpt: > bq. [...] having more important apps in 1st places would be better [...] the > feature should be easily changed by custom projects [...] documentation for > that would be enough. > I propose this order: > 1. partymgr(because you need parties to do anything) > 2. catalog (because you need products to do anything) > 3. facility (because you need to store products to do anything) > 4. order (because it's there that things begin to "move") > 5. accounting (because it's there that things "end"; ar & ap should > disappear) > 6. content (because you need to associate contents to make things better) > 7. manufacturing (because OFBiz is also an ERP) > 8. sfa (because people are often looking for a CRM, BTW most them don't know > what SFA is) > 9. workeffort (this one could be above, but it's not obvious for most people) > 10. humanres (more important than below IMO) > 11. marketing (not sure about the place of this one) > 12. webtools (maybe higher?) > - (plugins start below) > 1. rest (could be named api soon) > 2. projectmgr > 3. webpos > 4. bi > 5. birt > 6. myportal > 7. assetmaint > 8. ismgr > 9. scrum > 10. solr > 11. ebay > 12. firstdata > 13. - (those are special, maybe above?) > 14. example > 15. exampleext > - (those plugins don't show atm but exist, maybe need more info > from backend menu?) > 1. ecommerce > 2. ecomseo > 3. multiflex > 4. cmssite > 5. ebaystore > 6. ldap > 7. lucene > 8. passport > 9. pricat > 10. msggateway -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-12178) ModelInduceFromDb does not show realtions.
[ https://issues.apache.org/jira/browse/OFBIZ-12178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Jugl reassigned OFBIZ-12178: - Assignee: Benjamin Jugl > ModelInduceFromDb does not show realtions. > -- > > Key: OFBIZ-12178 > URL: https://issues.apache.org/jira/browse/OFBIZ-12178 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Release Branch 18.12, Trunk >Reporter: Benjamin Jugl >Assignee: Benjamin Jugl >Priority: Minor > > As encountered in OFBIZ-6510, the ModelInduceFromDb does currently not > include entity relations and foreign key constraints. Since they are an > important part of the database model, we should fix that. > I could track down the problem to an incomplete invocation of the ModelEntity > through the constructor used in the DatabaseUtil.induceModelFromDb() Methods. > This constructor does not initialize the Relations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-11202) Issue in validating date of format yyyy-MM-dd'T'HH:mm:ss
[ https://issues.apache.org/jira/browse/OFBIZ-11202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl closed OFBIZ-11202. - Resolution: Invalid > Issue in validating date of format -MM-dd'T'HH:mm:ss > > > Key: OFBIZ-11202 > URL: https://issues.apache.org/jira/browse/OFBIZ-11202 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Release Branch 16.11, Release Branch 18.12, Release > Branch 17.12, Trunk >Reporter: Lalit Dashora >Assignee: Michael Brohl >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11202) Issue in validating date of format yyyy-MM-dd'T'HH:mm:ss
[ https://issues.apache.org/jira/browse/OFBIZ-11202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285146#comment-17285146 ] Lalit Dashora commented on OFBIZ-11202: --- Yes, Please close this one, this is not valid. > Issue in validating date of format -MM-dd'T'HH:mm:ss > > > Key: OFBIZ-11202 > URL: https://issues.apache.org/jira/browse/OFBIZ-11202 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Release Branch 16.11, Release Branch 18.12, Release > Branch 17.12, Trunk >Reporter: Lalit Dashora >Assignee: Michael Brohl >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10791) Unable to add product (of ASSET_USAGE type) in order
[ https://issues.apache.org/jira/browse/OFBIZ-10791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-10791: -- Fix Version/s: (was: Release Branch 17.12) 17.12.06 > Unable to add product (of ASSET_USAGE type) in order > > > Key: OFBIZ-10791 > URL: https://issues.apache.org/jira/browse/OFBIZ-10791 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 16.11, Release Branch 18.12, Release > Branch 17.12, Trunk >Reporter: Praveen Sharma >Assignee: Michael Brohl >Priority: Major > Labels: ASSET_USAGE, CONTRACT_RENEWAL, PURCHASE_RENTAL, > SALES_RENTAL > Fix For: 18.12.01, Upcoming Branch, 17.12.06 > > Attachments: OFBIZ-10791.patch, OFBIZ-10791.patch, Screenshot from > 2019-03-09 11-05-31.png, Screenshot from 2019-03-09 11-06-20.png, Screenshot > from 2019-03-09 11-06-36.png, asset-addtocart.png > > > Steps to regenerate: > # Login to URL: [https://demo-trunk.ofbiz.apache.org/ordermgr/control/main] > # Click on order entry > # Set customer and click on continue > # Click continue on Enter Order Currency, Agreements, and Ship Dates page > (Please refer attachment: 2-Continue) > # Try to add product from Quick Lookup. > Actual: Unable to add product for order. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10308) Financial account transaction --> accounting transaction
[ https://issues.apache.org/jira/browse/OFBIZ-10308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-10308: -- Fix Version/s: (was: Release Branch 17.12) 17.12.06 > Financial account transaction --> accounting transaction > > > Key: OFBIZ-10308 > URL: https://issues.apache.org/jira/browse/OFBIZ-10308 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Release Branch 13.07, Release Branch 14.12, Release > Branch 15.12, Release Branch 16.11, Release Branch 18.12, Release Branch > 17.12, Trunk >Reporter: Ingo Wolfmayr >Assignee: Michael Brohl >Priority: Major > Fix For: 18.12.01, Upcoming Branch, 17.12.06 > > Attachments: ofbiz.patch > > > When creating a financial account transaction some of the accounting > transaction are in the wrong direction. > 1) Withdraw 10$: > DEBIT 00 General Checking Account (10$) --> CREDIT 649000 Other > Consulting Fees (10$) > 2) Debit 10$: > *DEBIT 00 General Checking Account (10$) --> CREDIT 649000 Other > Consulting Fees (10$) (WRONG)* > 3) Adjustment +10$: > DEBIT 00 General Checking Account (10$) --> CREDIT 649000 Other > Consulting Fees (10$) > 4) Adjustment -10$: > *CREDIT 00 General Checking Account (-10$) -->DEBIT 649000 Other > Consulting Fees (-10$) (WRONG)* > 2) should be: > DEBIT 649000 Other Consulting Fees --> CREDIT 00 General Checking > Account (10$) > 4) should be: > CREDIT 00 General Checking Account (++*10$) -->DEBIT 649000 Other > Consulting Fees (+*+10$) > > The attached patch fixes the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11680) ViewQuoteProfit shows fields in wrong order
[ https://issues.apache.org/jira/browse/OFBIZ-11680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-11680: -- Fix Version/s: (was: 17.12.05) 17.12.06 > ViewQuoteProfit shows fields in wrong order > --- > > Key: OFBIZ-11680 > URL: https://issues.apache.org/jira/browse/OFBIZ-11680 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Pierre Smits >Assignee: Suraj Khurana >Priority: Major > Labels: quote > Fix For: 18.12.01, 17.12.06 > > Attachments: OFBIZ-11680.patch, Screen Shot 2020-05-09 at 10.40.39.png > > > See attached image. > Total amount (of the quote) should be before total cost. > On line items, the quoteUnitPrice should be before averageCost -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-12173) Visit disabling causes NullPointerException on ecomm groovy script
[ https://issues.apache.org/jira/browse/OFBIZ-12173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-12173: -- Fix Version/s: (was: Release Branch 17.12) 17.12.06 > Visit disabling causes NullPointerException on ecomm groovy script > -- > > Key: OFBIZ-12173 > URL: https://issues.apache.org/jira/browse/OFBIZ-12173 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Release Branch 18.12, Trunk, 17.12.05 > Environment: Linux Ubuntu 18.04 LTS, Apache OFBiz v13.07.03 >Reporter: Giulio Speri >Assignee: Pawan Verma >Priority: Blocker > Labels: visit > Fix For: 18.12.01, 17.12.06 > > Attachments: > OFBIZ-12173_Visit_disabling_causes_NullPointerException.patch, > newcustomer_error.jpg > > > Disable tracking of Visits and Visitors, setting false the value of > stats.persist.visit stats.persist.visitor in serverstats.properties file, > causes a NullPointerException in the groovy script > ecommerce/groovyScript/customer/NewCustomer.groovy. > Attached here below a screenshot of the error. > !newcustomer_error.jpg! > This error also afflicts older version of OFBiz (the screenshot is taken from > an ecommerce site running on OFBiz 13.07.03) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11684) Form to add an employee position doesn't function properly when invoked from Humanres tree
[ https://issues.apache.org/jira/browse/OFBIZ-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285133#comment-17285133 ] Sebastian Berg commented on OFBIZ-11684: This seems to be the same problem. The solution suggested in OFBIZ-11685 also fixes this issue. > Form to add an employee position doesn't function properly when invoked from > Humanres tree > -- > > Key: OFBIZ-11684 > URL: https://issues.apache.org/jira/browse/OFBIZ-11684 > Project: OFBiz > Issue Type: Bug > Components: humanres >Affects Versions: Release Branch 18.12, 18.12.01, Release Branch 17.12, > 17.12.03, Trunk, 17.12.04 >Reporter: Pierre Smits >Priority: Major > Labels: usability > > Selecting Add Employee Position or Add Person from the context menu opens the > corresponding edit forms with calendar lookup fields. > The calendar form does no open when the lookup icon is clicked. > Expected calendar to open on click. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11685) Form to add an employee doesn't function properly when invoked from Humanres tree
[ https://issues.apache.org/jira/browse/OFBIZ-11685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285132#comment-17285132 ] Sebastian Berg commented on OFBIZ-11685: After some investigating I noticed, that if I remove line 125 '' in 'common-theme/widget/CommonScreens#GlobalActions' the dateTimePicker works fine. In the trunk version CommonScreens#GlobalActions got refactored and the line was removed. Maybe that's why its working fine in trunk. Maybe someone with more knowledge on the subject can tell why we need line 125, otherwise I would suggest to remove it. > Form to add an employee doesn't function properly when invoked from Humanres > tree > - > > Key: OFBIZ-11685 > URL: https://issues.apache.org/jira/browse/OFBIZ-11685 > Project: OFBiz > Issue Type: Bug > Components: humanres >Affects Versions: Release Branch 18.12, 18.12.01, Release Branch 17.12, > 17.12.03, Trunk, 17.12.04 >Reporter: Pierre Smits >Assignee: Sebastian Berg >Priority: Major > Labels: usability > > Selecting 'Add Person' from the context menu (on the 'Employment Position' > element opens the corresponding edit forms with calendar lookup fields. > The calendar form does no open when the lookup icon is clicked. > Expected calendar to open on click. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-6510) Replace webtools/control/view/ModelInduceFromDb with widgets
[ https://issues.apache.org/jira/browse/OFBIZ-6510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285092#comment-17285092 ] Benjamin Jugl commented on OFBIZ-6510: -- Created OFBIZ-12178 to tackle this. > Replace webtools/control/view/ModelInduceFromDb with widgets > > > Key: OFBIZ-6510 > URL: https://issues.apache.org/jira/browse/OFBIZ-6510 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Release Branch 18.12, Trunk >Reporter: Christian Carlow >Assignee: Michael Brohl >Priority: Major > Labels: backport-needed > Fix For: 18.12.01, Upcoming Branch > > Attachments: OFBIZ-6510.patch, OFBIZ-6510.patch, OFBIZ-6510.patch, > OFBIZ-6510.patch > > > The page is written in JSP probably from very long ago when FTL and widgets > didn't even exist yet. It should be implemented in widgets now that they are > available. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-12178) ModelInduceFromDb does not show realtions.
Benjamin Jugl created OFBIZ-12178: - Summary: ModelInduceFromDb does not show realtions. Key: OFBIZ-12178 URL: https://issues.apache.org/jira/browse/OFBIZ-12178 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Trunk, Release Branch 18.12 Reporter: Benjamin Jugl As encountered in OFBIZ-6510, the ModelInduceFromDb does currently not include entity relations and foreign key constraints. Since they are an important part of the database model, we should fix that. I could track down the problem to an incomplete invocation of the ModelEntity through the constructor used in the DatabaseUtil.induceModelFromDb() Methods. This constructor does not initialize the Relations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
