[jira] [Closed] (OFBIZ-10158) Find Employee Position does not allow "don't care" for boolean fields
[ https://issues.apache.org/jira/browse/OFBIZ-10158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Foxworthy closed OFBIZ-10158. -- > Find Employee Position does not allow "don't care" for boolean fields > - > > Key: OFBIZ-10158 > URL: https://issues.apache.org/jira/browse/OFBIZ-10158 > Project: OFBiz > Issue Type: Bug > Components: humanres >Affects Versions: Trunk >Reporter: Paul Foxworthy >Assignee: Paul Foxworthy >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10158_FindEmplPosition_booleans.patch > > > In the demo app, go to > https://demo-stable.ofbiz.apache.org/humanres/control/FindEmplPositions, > click on New Employee Position, and toggle one of the four flags, e.g. set > Temporary Flag to N. > Now on the Find screen, there is no way to find all employee positions: it > insists on a Yes or No for the flags. This patch allows a blank "don't care" > option. > Thanks to Larissa Zanoni at Blockfreight for discovering this issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10158) Find Employee Position does not allow "don't care" for boolean fields
[ https://issues.apache.org/jira/browse/OFBIZ-10158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16323630#comment-16323630 ] Paul Foxworthy commented on OFBIZ-10158: Fixed in r1820949 > Find Employee Position does not allow "don't care" for boolean fields > - > > Key: OFBIZ-10158 > URL: https://issues.apache.org/jira/browse/OFBIZ-10158 > Project: OFBiz > Issue Type: Bug > Components: humanres >Affects Versions: Trunk >Reporter: Paul Foxworthy >Assignee: Paul Foxworthy >Priority: Minor > Attachments: OFBIZ-10158_FindEmplPosition_booleans.patch > > > In the demo app, go to > https://demo-stable.ofbiz.apache.org/humanres/control/FindEmplPositions, > click on New Employee Position, and toggle one of the four flags, e.g. set > Temporary Flag to N. > Now on the Find screen, there is no way to find all employee positions: it > insists on a Yes or No for the flags. This patch allows a blank "don't care" > option. > Thanks to Larissa Zanoni at Blockfreight for discovering this issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-9501) Move all data in applications to the datamodel component
[ https://issues.apache.org/jira/browse/OFBIZ-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16323591#comment-16323591 ] Taher Alkhateeb edited comment on OFBIZ-9501 at 1/12/18 5:53 AM: - Hi Rishi It seems to me that maybe all demo data might be better placed in the datamodel component. I could be wrong but here are my thoughts: - first I think most of the demo data above populates entities defined in the data model component. It might be better for data to follow its entities location. - the reason why this JIRA was created is becauae I suffered while disentangling application dependencies on ecommerce. I think my life would have been easier if everything was in one place. - also demo data might be very useful even without the components. Demo data helps developers understand the entities by showing examples of populated data. Also if someone wants to develop their own custom accounting component for example then they can test it and check the interface using that demo data. Do I make sense? Or did I misunderstand something? Either way I'd love to hear your thoughts. And hats off for the great work you've done already. was (Author: taher): Hi Riahi It seems to me that maybe all demo data might be better placed in the datamodel component. I could be wrong but here are my thoughts: - first I think most of the demo data above populates entities defined in the data model component. It might be better for data to follow its entities location. - the reason why this JIRA was created is becauae I suffered while disentangling application dependencies on ecommerce. I think my life would have been easier if everything was in one place. - also demo data might be very useful even without the components. Demo data helps developers understand the entities by showing examples of populated data. Also if someone wants to develop their own custom accounting component for example then they can test it and check the interface using that demo data. Do I make sense? Or did I misunderstand something? Either way I'd love to hear your thoughts. And hats off for the great work you've done already. > Move all data in applications to the datamodel component > > > Key: OFBIZ-9501 > URL: https://issues.apache.org/jira/browse/OFBIZ-9501 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: 17.12.01 >Reporter: Taher Alkhateeb >Assignee: Rishi Solanki >Priority: Minor > Labels: application, data > Attachments: OFBIZ-9051-004.patch, OFBIZ-9501-001.patch, > OFBIZ-9501-002.patch, OFBIZ-9501-003.patch, > OFBIZ-9501-WorkEffortSeedData.patch, OFBIZ-9501_Consolidated-2.patch, > OFBIZ-9501_Consolidated.patch > > > As per a community [discussion > thread|https://lists.apache.org/thread.html/eb6ea79195204356a362dbf208c5dbb6d321d001bf2b79819dc45a24@%3Cdev.ofbiz.apache.org%3E] > we decided to move all data (seed, seed-initial, demo) to the datamodel > component. and to also reduce and cleanup this data to ease debugging and > maintenance. > After moving all the data, the directory and file structure would be similar > to the below: > data/ > ├── demo > │ ├── AccountingDemoData.xml > │ ├── CommonDemoData.xml > │ ├── ContentDemoData.xml > │ ├── HumanresDemo.xml > │ ├── ManufacturingDemoData.xml > │ ├── MarketingDemoData.xml > │ ├── OrderDemoData.xml > │ ├── PartyDemoData.xml > │ ├── ProductDemoData.xml > │ ├── ShipmentDemoData.xml > │ └── WorkEffortDemoData.xml > ├── seed > │ ├── AccountingSeedData.xml > │ ├── CommonSeedData.xml > │ ├── ContentSeedData.xml > │ ├── HumanresSeedData.xml > │ ├── ManufacturingSeedData.xml > │ ├── MarketingSeedData.xml > │ ├── OrderSeedData.xml > │ ├── PartySeedData.xml > │ ├── ProductSeedData.xml > │ ├── ShipmentSeedData.xml > │ └── WorkEffortSeedData.xml > └── seed-initial > ├── AccountingSeedInitialData.xml > ├── CommonSeedInitialData.xml > ├── ContentSeedInitialData.xml > ├── HumanresSeedInitialData.xml > ├── ManufacturingSeedInitialData.xml > ├── MarketingSeedInitialData.xml > ├── OrderSeedInitialData.xml > ├── PartySeedInitialData.xml > ├── ProductSeedInitialData.xml > ├── ShipmentSeedInitialData.xml > └── WorkEffortSeedInitialData.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9501) Move all data in applications to the datamodel component
[ https://issues.apache.org/jira/browse/OFBIZ-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16323591#comment-16323591 ] Taher Alkhateeb commented on OFBIZ-9501: Hi Riahi It seems to me that maybe all demo data might be better placed in the datamodel component. I could be wrong but here are my thoughts: - first I think most of the demo data above populates entities defined in the data model component. It might be better for data to follow its entities location. - the reason why this JIRA was created is becauae I suffered while disentangling application dependencies on ecommerce. I think my life would have been easier if everything was in one place. - also demo data might be very useful even without the components. Demo data helps developers understand the entities by showing examples of populated data. Also if someone wants to develop their own custom accounting component for example then they can test it and check the interface using that demo data. Do I make sense? Or did I misunderstand something? Either way I'd love to hear your thoughts. And hats off for the great work you've done already. > Move all data in applications to the datamodel component > > > Key: OFBIZ-9501 > URL: https://issues.apache.org/jira/browse/OFBIZ-9501 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: 17.12.01 >Reporter: Taher Alkhateeb >Assignee: Rishi Solanki >Priority: Minor > Labels: application, data > Attachments: OFBIZ-9051-004.patch, OFBIZ-9501-001.patch, > OFBIZ-9501-002.patch, OFBIZ-9501-003.patch, > OFBIZ-9501-WorkEffortSeedData.patch, OFBIZ-9501_Consolidated-2.patch, > OFBIZ-9501_Consolidated.patch > > > As per a community [discussion > thread|https://lists.apache.org/thread.html/eb6ea79195204356a362dbf208c5dbb6d321d001bf2b79819dc45a24@%3Cdev.ofbiz.apache.org%3E] > we decided to move all data (seed, seed-initial, demo) to the datamodel > component. and to also reduce and cleanup this data to ease debugging and > maintenance. > After moving all the data, the directory and file structure would be similar > to the below: > data/ > ├── demo > │ ├── AccountingDemoData.xml > │ ├── CommonDemoData.xml > │ ├── ContentDemoData.xml > │ ├── HumanresDemo.xml > │ ├── ManufacturingDemoData.xml > │ ├── MarketingDemoData.xml > │ ├── OrderDemoData.xml > │ ├── PartyDemoData.xml > │ ├── ProductDemoData.xml > │ ├── ShipmentDemoData.xml > │ └── WorkEffortDemoData.xml > ├── seed > │ ├── AccountingSeedData.xml > │ ├── CommonSeedData.xml > │ ├── ContentSeedData.xml > │ ├── HumanresSeedData.xml > │ ├── ManufacturingSeedData.xml > │ ├── MarketingSeedData.xml > │ ├── OrderSeedData.xml > │ ├── PartySeedData.xml > │ ├── ProductSeedData.xml > │ ├── ShipmentSeedData.xml > │ └── WorkEffortSeedData.xml > └── seed-initial > ├── AccountingSeedInitialData.xml > ├── CommonSeedInitialData.xml > ├── ContentSeedInitialData.xml > ├── HumanresSeedInitialData.xml > ├── ManufacturingSeedInitialData.xml > ├── MarketingSeedInitialData.xml > ├── OrderSeedInitialData.xml > ├── PartySeedInitialData.xml > ├── ProductSeedInitialData.xml > ├── ShipmentSeedInitialData.xml > └── WorkEffortSeedInitialData.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-10113) Replace Asm select plugin with Select2.
[ https://issues.apache.org/jira/browse/OFBIZ-10113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322338#comment-16322338 ] Aditya Sharma edited comment on OFBIZ-10113 at 1/12/18 5:08 AM: Replaced Asm select plugin with Select2 4.0.6 Added i18n support so added logic in JsLanguageFileMappingCreator and JsLanguageFilesMapping accordingly. Added some custom CSS as the Select2 seems to be too fancy in accordance with the current OFBiz themes Verify: Multiple drop-downs field in FormWidgetExamples. I have added multiple="true" with OFBIZ-10113_plugins.patch https://localhost:8443/example/control/FormWidgetExamples Find Request page with StatusId , CustRequestId https://localhost:8443/ordermgr/control/FindRequest I have replaced the plugins though I feel the implementation of select multiple js code is to be reviewed & refactored. I will pick when I am done with all my current tasks if I get some consensus. was (Author: aditya.sharma): Replaced Asm select plugin with Select2 4.0.6 Verify: Multiple drop-downs field in FormWidgetExamples. I have added multiple="true" with OFBIZ-10113_plugins.patch https://localhost:8443/example/control/FormWidgetExamples Find Request page with StatusId , CustRequestId https://localhost:8443/ordermgr/control/FindRequest I have replaced the plugins though I feel the implementation of select multiple js code is to be reviewed & refactored. I will pick when I am done with all my current tasks if I get some consensus. > Replace Asm select plugin with Select2. > --- > > Key: OFBIZ-10113 > URL: https://issues.apache.org/jira/browse/OFBIZ-10113 > Project: OFBiz > Issue Type: Sub-task > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: OFBIZ-10113.patch, OFBIZ-10113_plugins.patch, > select2.tar.gz > > > Current Asm Select Plugin > (http://www.ryancramer.com/journal/entries/asmselect_v104/) can be replaced > with Select2 (https://select2.org/). > * Select2 has much better community support on GitHub with 386 contributors > while Asm Select Plugin is handled by Ryan Cramer on > http://www.ryancramer.com/. > * Select2 has 37 releases while Asm select has very few releases yet. > * Both the plugin has MIT license. > Refer https://select2.org/ and https://github.com/select2/select2 for more > features and other information. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10158) Find Employee Position does not allow "don't care" for boolean fields
[ https://issues.apache.org/jira/browse/OFBIZ-10158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Foxworthy updated OFBIZ-10158: --- Description: In the demo app, go to https://demo-stable.ofbiz.apache.org/humanres/control/FindEmplPositions, click on New Employee Position, and toggle one of the four flags, e.g. set Temporary Flag to N. Now on the Find screen, there is no way to find all employee positions: it insists on a Yes or No for the flags. This patch allows a blank "don't care" option. Thanks to Larissa Zanoni at Blockfreight for discovering this issue. was: In the demo app, go to https://demo-stable.ofbiz.apache.org/humanres/control/FindEmplPositions, click on New Employee Position, and toggle one of the four flags, e.g. set Temporary Flag to N. Now on the Find screen, there is no way to find all employee positions: it insists on a Yes or No for the flags. This patch allows a blank "don't care" option. > Find Employee Position does not allow "don't care" for boolean fields > - > > Key: OFBIZ-10158 > URL: https://issues.apache.org/jira/browse/OFBIZ-10158 > Project: OFBiz > Issue Type: Bug > Components: humanres >Affects Versions: Trunk >Reporter: Paul Foxworthy >Assignee: Paul Foxworthy >Priority: Minor > > In the demo app, go to > https://demo-stable.ofbiz.apache.org/humanres/control/FindEmplPositions, > click on New Employee Position, and toggle one of the four flags, e.g. set > Temporary Flag to N. > Now on the Find screen, there is no way to find all employee positions: it > insists on a Yes or No for the flags. This patch allows a blank "don't care" > option. > Thanks to Larissa Zanoni at Blockfreight for discovering this issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-10158) Find Employee Position does not allow "don't care" for boolean fields
Paul Foxworthy created OFBIZ-10158: -- Summary: Find Employee Position does not allow "don't care" for boolean fields Key: OFBIZ-10158 URL: https://issues.apache.org/jira/browse/OFBIZ-10158 Project: OFBiz Issue Type: Bug Components: humanres Affects Versions: Trunk Reporter: Paul Foxworthy Assignee: Paul Foxworthy Priority: Minor In the demo app, go to https://demo-stable.ofbiz.apache.org/humanres/control/FindEmplPositions, click on New Employee Position, and toggle one of the four flags, e.g. set Temporary Flag to N. Now on the Find screen, there is no way to find all employee positions: it insists on a Yes or No for the flags. This patch allows a blank "don't care" option. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-10113) Replace Asm select plugin with Select2.
[ https://issues.apache.org/jira/browse/OFBIZ-10113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322338#comment-16322338 ] Aditya Sharma edited comment on OFBIZ-10113 at 1/12/18 3:57 AM: Replaced Asm select plugin with Select2 4.0.6 Verify: Multiple drop-downs field in FormWidgetExamples. I have added multiple="true" with OFBIZ-10113_plugins.patch https://localhost:8443/example/control/FormWidgetExamples Find Request page with StatusId , CustRequestId https://localhost:8443/ordermgr/control/FindRequest I have replaced the plugins though I feel the implementation of select multiple js code is to be reviewed & refactored. I will pick when I am done with all my current tasks if I get some consensus. was (Author: aditya.sharma): Replace Asm select plugin with Select2 4.0.6 Verify: Multiple drop-downs field in FormWidgetExamples. I have added multiple="true" with OFBIZ-10113_plugins.patch https://localhost:8443/example/control/FormWidgetExamples Find Request page with StatusId , CustRequestId https://localhost:8443/ordermgr/control/FindRequest I have replaced the plugins though I feel the implementation of select multiple js code is to be reviewed & refactored. I will pick when I am done with all my current tasks if I get some consensus. > Replace Asm select plugin with Select2. > --- > > Key: OFBIZ-10113 > URL: https://issues.apache.org/jira/browse/OFBIZ-10113 > Project: OFBiz > Issue Type: Sub-task > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: OFBIZ-10113.patch, OFBIZ-10113_plugins.patch, > select2.tar.gz > > > Current Asm Select Plugin > (http://www.ryancramer.com/journal/entries/asmselect_v104/) can be replaced > with Select2 (https://select2.org/). > * Select2 has much better community support on GitHub with 386 contributors > while Asm Select Plugin is handled by Ryan Cramer on > http://www.ryancramer.com/. > * Select2 has 37 releases while Asm select has very few releases yet. > * Both the plugin has MIT license. > Refer https://select2.org/ and https://github.com/select2/select2 for more > features and other information. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-10147) Buildbot script refactoring to put in a R17 branch build
[ https://issues.apache.org/jira/browse/OFBIZ-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-10147. --- Resolution: Done OK this is done, it seems also that INFRA-15829 has resolved by itself > Buildbot script refactoring to put in a R17 branch build > > > Key: OFBIZ-10147 > URL: https://issues.apache.org/jira/browse/OFBIZ-10147 > Project: OFBiz > Issue Type: Task > Components: BuildBot >Affects Versions: Trunk, 17.12.01 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > > Though I decided to let INFRA-15394 closed I found that the framework+plugins > build is not launched (as a dependence) after the framework build. > As we need the same pattern than the trunk for the R17 branch I will try to > fix this issue and then put in a R17 branch build > Then INFRA-15785 can be actionned -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10113) Replace Asm select plugin with Select2.
[ https://issues.apache.org/jira/browse/OFBIZ-10113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-10113: -- Attachment: OFBIZ-10113.patch OFBIZ-10113_plugins.patch select2.tar.gz Replace Asm select plugin with Select2 4.0.6 Verify: Multiple drop-downs field in FormWidgetExamples. I have added multiple="true" with OFBIZ-10113_plugins.patch https://localhost:8443/example/control/FormWidgetExamples Find Request page with StatusId , CustRequestId https://localhost:8443/ordermgr/control/FindRequest I have replaced the plugins though I feel the implementation of select multiple js code is to be reviewed & refactored. I will pick when I am done with all my current tasks if I get some consensus. > Replace Asm select plugin with Select2. > --- > > Key: OFBIZ-10113 > URL: https://issues.apache.org/jira/browse/OFBIZ-10113 > Project: OFBiz > Issue Type: Sub-task > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: OFBIZ-10113.patch, OFBIZ-10113_plugins.patch, > select2.tar.gz > > > Current Asm Select Plugin > (http://www.ryancramer.com/journal/entries/asmselect_v104/) can be replaced > with Select2 (https://select2.org/). > * Select2 has much better community support on GitHub with 386 contributors > while Asm Select Plugin is handled by Ryan Cramer on > http://www.ryancramer.com/. > * Select2 has 37 releases while Asm select has very few releases yet. > * Both the plugin has MIT license. > Refer https://select2.org/ and https://github.com/select2/select2 for more > features and other information. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9501) Move all data in applications to the datamodel component
[
https://issues.apache.org/jira/browse/OFBIZ-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322334#comment-16322334
]
Rishi Solanki commented on OFBIZ-9501:
--
[~taher] and all,
I'm looking into it further and check that as per review comment from Taher
that the data useless without that component then it should belongs to that
component only. On this we were agree to leave some data in the component
itself. Here I'm looking into demo data now and taking accounting component
example for now. Below are the demo data files in the accounting component and
I see most of the files data should belongs to component itself. So do we need
to proceed further with this ticket or we should discuss the accounting
component as example and try to move selective demo data as well. Like all
seed-initial data belongs to component as per last discussion.
I think demo fall in the same category so no movement required. Also I'm open
to discuss the part data which can be move and then will apply the patterns to
other components. Here is the quick reference;
{code}
{code}
> Move all data in applications to the datamodel component
>
>
> Key: OFBIZ-9501
> URL: https://issues.apache.org/jira/browse/OFBIZ-9501
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
>Affects Versions: 17.12.01
>Reporter: Taher Alkhateeb
>Assignee: Rishi Solanki
>Priority: Minor
> Labels: application, data
> Attachments: OFBIZ-9051-004.patch, OFBIZ-9501-001.patch,
> OFBIZ-9501-002.patch, OFBIZ-9501-003.patch,
> OFBIZ-9501-WorkEffortSeedData.patch, OFBIZ-9501_Consolidated-2.patch,
> OFBIZ-9501_Consolidated.patch
>
>
> As per a community [discussion
> thread|https://lists.apache.org/thread.html/eb6ea79195204356a362dbf208c5dbb6d321d001bf2b79819dc45a24@%3Cdev.ofbiz.apache.org%3E]
> we decided to move all data (seed, seed-initial, demo) to the datamodel
> component. and to also reduce and cleanup this data to ease debugging and
> maintenance.
> After moving all the data, the directory and file structure would be similar
> to the below:
> data/
> ├── demo
> │ ├── AccountingDemoData.xml
> │ ├── CommonDemoData.xml
> │ ├── ContentDemoData.xml
> │ ├── HumanresDemo.xml
> │ ├── ManufacturingDemoData.xml
> │ ├── MarketingDemoData.xml
> │ ├── OrderDemoData.xml
> │ ├── PartyDemoData.xml
> │ ├── ProductDemoData.xml
> │ ├── ShipmentDemoData.xml
> │ └── WorkEffortDemoData.xml
> ├── seed
> │ ├── AccountingSeedData.xml
> │ ├── CommonSeedData.xml
> │ ├── ContentSeedData.xml
> │ ├── HumanresSeedData.xml
> │ ├── ManufacturingSeedData.xml
> │ ├── MarketingSeedData.xml
> │ ├── OrderSeedData.xml
> │ ├── PartySeedData.xml
> │ ├── ProductSeedData.xml
> │ ├── ShipmentSeedData.xml
> │ └── WorkEffortSeedData.xml
> └── seed-initial
> ├── AccountingSeedInitialData.xml
> ├── CommonSeedInitialData.xml
> ├── ContentSeedInitialData.xml
> ├── HumanresSeedInitialData.xml
> ├── ManufacturingSeedInitialData.xml
> ├── MarketingSeedInitialData.xml
> ├── OrderSeedInitialData.xml
> ├── PartySeedInitialData.xml
> ├── ProductSeedInitialData.xml
> ├── ShipmentSeedInitialData.xml
> └── WorkEffortSeedInitialData.xml
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OFBIZ-10157) Performance optimization for entities in xml data export
[ https://issues.apache.org/jira/browse/OFBIZ-10157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kyra Pritzel-Hentley updated OFBIZ-10157: - Description: Suggested changes for XmlDsDump.groovy by [~mbecker]: - set parameter _distinct_ for new EntityFindOptions to false - when accessing values with delegator._find_() remove any sorting from parameters These changes allow and/or speed up export of large tables (e.g. for db migration) was: Suggested changes for XmlDsDump.groovy: - set parameter _distinct_ for new EntityFindOptions to false - when accessing values with delegator._find_() remove any sorting from parameters These changes allow and/or speed up export of large tables (e.g. for db migration) > Performance optimization for entities in xml data export > > > Key: OFBIZ-10157 > URL: https://issues.apache.org/jira/browse/OFBIZ-10157 > Project: OFBiz > Issue Type: Improvement > Components: framework >Reporter: Kyra Pritzel-Hentley >Priority: Minor > Attachments: OFBIZ-10157_XmlDsDump_performance_optimization.patch > > > Suggested changes for XmlDsDump.groovy by [~mbecker]: > - set parameter _distinct_ for new EntityFindOptions to false > - when accessing values with delegator._find_() remove any sorting from > parameters > These changes allow and/or speed up export of large tables (e.g. for db > migration) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10157) Performance optimization for entities in xml data export
[ https://issues.apache.org/jira/browse/OFBIZ-10157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kyra Pritzel-Hentley updated OFBIZ-10157: - Attachment: OFBIZ-10157_XmlDsDump_performance_optimization.patch This patch implements the suggested changes. > Performance optimization for entities in xml data export > > > Key: OFBIZ-10157 > URL: https://issues.apache.org/jira/browse/OFBIZ-10157 > Project: OFBiz > Issue Type: Improvement > Components: framework >Reporter: Kyra Pritzel-Hentley >Priority: Minor > Attachments: OFBIZ-10157_XmlDsDump_performance_optimization.patch > > > Suggested changes for XmlDsDump.groovy: > - set parameter _distinct_ for new EntityFindOptions to false > - when accessing values with delegator._find_() remove any sorting from > parameters > These changes allow and/or speed up export of large tables (e.g. for db > migration) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-10157) Performance optimization for entities in xml data export
Kyra Pritzel-Hentley created OFBIZ-10157: Summary: Performance optimization for entities in xml data export Key: OFBIZ-10157 URL: https://issues.apache.org/jira/browse/OFBIZ-10157 Project: OFBiz Issue Type: Improvement Components: framework Reporter: Kyra Pritzel-Hentley Priority: Minor Suggested changes for XmlDsDump.groovy: - set parameter _distinct_ for new EntityFindOptions to false - when accessing values with delegator._find_() remove any sorting from parameters These changes allow and/or speed up export of large tables (e.g. for db migration) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10156) Fix issues related to images paths
[
https://issues.apache.org/jira/browse/OFBIZ-10156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322120#comment-16322120
]
Jacques Le Roux commented on OFBIZ-10156:
-
Should also have been fixed with
trunk r1820862
R17.12 r1820867
I'll check before closing
> Fix issues related to images paths
> --
>
> Key: OFBIZ-10156
> URL: https://issues.apache.org/jira/browse/OFBIZ-10156
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL COMPONENTS
>Affects Versions: 17.12.01
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
>
> While working on OFBIZ-10128 I stumbled upon this issue found on trunk demo
> {code}
> 2018-01-11 09:30:28,159 |ajp-nio-8009-exec-4 |FOUserAgent
> |E| Image not found. URI:
> /example/control/qrcode;jsessionid=6E1C4C1E84C4C96F370B89A44201DEEC.jvm1?message=Example%201=bmp=UTF-8=true=20=20.
> (See position 47:77)
> 2018-01-11 09:30:29,183 |ajp-nio-8009-exec-4 |FOUserAgent
> |E| Image not found. URI:
> /example/control/qrcode;jsessionid=6E1C4C1E84C4C96F370B89A44201DEEC.jvm1?message=Example%201=bmp=UTF-8=true=20=20.
> (No context info available)
> 2018-01-11 09:35:08,370 |ajp-nio-8009-exec-8 |FOUserAgent
> |E| Image not found. URI: /images/ofbiz_logo.png. (See position 37:54)
> 2018-01-11 09:35:08,603 |ajp-nio-8009-exec-8 |FOUserAgent
> |E| Image not found. URI: /images/ofbiz_logo.png. (No context info available)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OFBIZ-10156) Fix issues related to images paths
Jacques Le Roux created OFBIZ-10156:
---
Summary: Fix issues related to images paths
Key: OFBIZ-10156
URL: https://issues.apache.org/jira/browse/OFBIZ-10156
Project: OFBiz
Issue Type: Sub-task
Components: ALL COMPONENTS
Affects Versions: 17.12.01
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Minor
While working on OFBIZ-10128 I stumbled upon this issue found on trunk demo
{code}
2018-01-11 09:30:28,159 |ajp-nio-8009-exec-4 |FOUserAgent
|E| Image not found. URI:
/example/control/qrcode;jsessionid=6E1C4C1E84C4C96F370B89A44201DEEC.jvm1?message=Example%201=bmp=UTF-8=true=20=20.
(See position 47:77)
2018-01-11 09:30:29,183 |ajp-nio-8009-exec-4 |FOUserAgent
|E| Image not found. URI:
/example/control/qrcode;jsessionid=6E1C4C1E84C4C96F370B89A44201DEEC.jvm1?message=Example%201=bmp=UTF-8=true=20=20.
(No context info available)
2018-01-11 09:35:08,370 |ajp-nio-8009-exec-8 |FOUserAgent
|E| Image not found. URI: /images/ofbiz_logo.png. (See position 37:54)
2018-01-11 09:35:08,603 |ajp-nio-8009-exec-8 |FOUserAgent
|E| Image not found. URI: /images/ofbiz_logo.png. (No context info available)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OFBIZ-10155) Error on ordermgr component for locale ar - Arabic
Aditya Sharma created OFBIZ-10155:
-
Summary: Error on ordermgr component for locale ar - Arabic
Key: OFBIZ-10155
URL: https://issues.apache.org/jira/browse/OFBIZ-10155
Project: OFBiz
Issue Type: Bug
Components: order
Affects Versions: Trunk, 17.12.01
Reporter: Aditya Sharma
Priority: Minor
Attachments: ErrorAr.png
Steps to regenerate:
1. Login to Order Manager
(https://demo-trunk.ofbiz.apache.org/ordermgr/control/main)
2. Click on change language link
(https://demo-trunk.ofbiz.apache.org/ordermgr/control/ListLocales)
3. Change locale to ar - العربية
(https://demo-trunk.ofbiz.apache.org/ordermgr/control/setSessionLocale?newLocale=ar)
{quote}ERROR rendering error page [/error/error.jsp], but here is the error
text: java.lang.RuntimeException: Error rendering widgets section [] in screen
named [GlobalDecorator]: freemarker.core.ParseException: Syntax error in
template
"org.apache.ofbiz.widget.renderer.macro.MacroMenuRenderer@296cd5b8_1000" in
line 1, column 185: Lexical error: encountered "\u0627" (1575), after
"\"\u0645\u062f\u064a\u0631 \u0623\u0645\u0631
\u0627\u0644\u0628\u064a\u0639\\".{quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OFBIZ-10128) Clean images, among them logos, in all locations used
[ https://issues.apache.org/jira/browse/OFBIZ-10128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322052#comment-16322052 ] Jacques Le Roux commented on OFBIZ-10128: - WIP, 1st commit at revision: 1820862 > Clean images, among them logos, in all locations used > - > > Key: OFBIZ-10128 > URL: https://issues.apache.org/jira/browse/OFBIZ-10128 > Project: OFBiz > Issue Type: Task >Reporter: Jacques Le Roux >Priority: Minor > > This is a copy of what [I said in dev > ML|http://markmail.org/message/ubx6he4z22vtat3r] > bq. It would be great if we could use the same logo everywhere and get rid of > old version at least in svn trunk It's a mess in general with images. There > are 3 locations: svn repo, main site and wiki. We should link as much as > possible from our svn repo. I even wonder if we should not ALWAYS link to it, > even from the main site! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9233) Enable a service to run by a specific service engine
[
https://issues.apache.org/jira/browse/OFBIZ-9233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shi Jinghai updated OFBIZ-9233:
---
Attachment: OFBIZ-9233-20180111.patch
In the OFBIZ-9233-20180111.patch, a new attribute "service-engine-name" is
introduced to service element in service define file, i.e. in
framework/service/servicedef/services_test_serviceengine_specific.xml:
{code:xml}
http://www.w3.org/2001/XMLSchema-instance;
xsi:noNamespaceSchemaLocation="../dtd/services.xsd">
Test services run on the "specific" service
engine
Test "specific" service engine.
{code}
This service-engine-name value will be set to every services defined in the
file, this makes it simple to change a service running pool dynamically in the
future.
When running an async service in scheduler, if the poolId is wrong configured
according to current service define, the poolId in JobSandbox can be
automatically changed. The sample is the jobId="TestJSSOnDefault" in
framework/service/testdef/data/MultiServiceEngineScheduledServiceData.xml.
> Enable a service to run by a specific service engine
>
>
> Key: OFBIZ-9233
> URL: https://issues.apache.org/jira/browse/OFBIZ-9233
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: Shi Jinghai
>Assignee: Shi Jinghai
>Priority: Minor
> Attachments: OFBIZ-9233-20170301.patch, OFBIZ-9233-20170413.patch,
> OFBIZ-9233-20180111.patch, OFBIZ-9233-MultiServiceEnginesEnv.png
>
>
> Currently, all of the services of OFBiz are run by the 'default' service
> engine.
> In a project, we have to make a service run by different service engines
> rather than the 'default' one, i.e. order services run by 'order' service
> engine and 'orderpool', shipment services run by 'shipment' service engine
> and 'shipmentpool'.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OFBIZ-10153) Shipping Label printing not working
[ https://issues.apache.org/jira/browse/OFBIZ-10153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322010#comment-16322010 ] Deepak Dixit commented on OFBIZ-10153: -- Let me check > Shipping Label printing not working > > > Key: OFBIZ-10153 > URL: https://issues.apache.org/jira/browse/OFBIZ-10153 > Project: OFBiz > Issue Type: Bug >Affects Versions: 16.11.04 >Reporter: Deepak Dixit >Assignee: Deepak Dixit > Fix For: 16.11.05 > > > As per changes done at OFBIZ-6849, shipping label printing not working. > If we use https url in FOP fo:external-graphics it check for valid cert and > if cert not found it throws exception. > Need to add viewShipmentLabel url in http.request-map.list so that it will > serve as http instead https -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10154) pagination errors in "KeywordSearch.ftl" and "ProductSearchSession.java"
[ https://issues.apache.org/jira/browse/OFBIZ-10154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karsten Tymann updated OFBIZ-10154: --- Attachment: OFBIZ-10154-pagination-keywordsearch.patch > pagination errors in "KeywordSearch.ftl" and "ProductSearchSession.java" > > > Key: OFBIZ-10154 > URL: https://issues.apache.org/jira/browse/OFBIZ-10154 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Karsten Tymann >Priority: Minor > Attachments: OFBIZ-10154-pagination-keywordsearch.patch > > > *pagination errors in keywordsearch in the Order->OrderEntry->Search-Screen* > With this patch I propose a fix for two bugs in the current OfBiz state. > 1. The pagination for the "Order Entry" Search in the "Order" component > has an error on the underlying FreemarkerTemplate. The .ftl displays all > potential pages, plus one. > For example, if you have 19 results with a ViewSize of 10, you should see > 2 pages, but in fact, 3 potential pages are shown. > This is a bug in the calculation of the pages on the .ftl. > The patch fixes the calculation by handling the variable "ListSize" as what it > is: the size of the list. There should be no subtraction for the listSize > provided by > the "KeywordSearch.groovy". > Note that this also adapts the file "KeywordSearch.ftl" to the equivalent > pagination > .ftl "CategoryDetail.ftl". In the patching process I also changed the > "TagSearch.ftl" to adapt to the correct calculation of pagination. > 2. The pagination for "KeywordSearch" triggers a completely new search if you > search for an order, change the > page, and then press the "Previous page" button. > This occurs because the method "processSearchParameters" in > "ProductSearchSession" > is called from the Groovy-Script of the Result-Screen > (check "KeywordSearch.groovy") > as well as from the method "checkDoKeywordOverride" which is triggered by > the Form-Submit-Search-Request "keywordsearch" (see controller.xml). > The additional call results in a new Search since the parameter > "clearSearchString" > is not send on the second occasion. Therefore one call should be eliminated. > I chose to remove the method call from within "checkDoKeywordOverride" > since it is unique to the component and is only triggered by this exact event. > "KeywordSearch.groovy", in multiple components, always triggers the > "ProductSearchSession.processSearchParameters(parameters, request)" > another call is just not needed. > Additionally I also removed the block of rechecking the set View and Index > size which > serves no purpose. Again, this block of actions is also not needed in similar > java classes such as "WorkEffortSearchSession.java". > To recreate the bug go to > Order->OrderEntry-> Search in the catalog for "g" -> check the amount of > shown pages and press "Next" -> press "back" -> note how many results you now > have, from 19 to 35 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-10154) pagination errors in "KeywordSearch.ftl" and "ProductSearchSession.java"
Karsten Tymann created OFBIZ-10154: -- Summary: pagination errors in "KeywordSearch.ftl" and "ProductSearchSession.java" Key: OFBIZ-10154 URL: https://issues.apache.org/jira/browse/OFBIZ-10154 Project: OFBiz Issue Type: Bug Components: order Affects Versions: Trunk Reporter: Karsten Tymann Priority: Minor *pagination errors in keywordsearch in the Order->OrderEntry->Search-Screen* With this patch I propose a fix for two bugs in the current OfBiz state. 1. The pagination for the "Order Entry" Search in the "Order" component has an error on the underlying FreemarkerTemplate. The .ftl displays all potential pages, plus one. For example, if you have 19 results with a ViewSize of 10, you should see 2 pages, but in fact, 3 potential pages are shown. This is a bug in the calculation of the pages on the .ftl. The patch fixes the calculation by handling the variable "ListSize" as what it is: the size of the list. There should be no subtraction for the listSize provided by the "KeywordSearch.groovy". Note that this also adapts the file "KeywordSearch.ftl" to the equivalent pagination .ftl "CategoryDetail.ftl". In the patching process I also changed the "TagSearch.ftl" to adapt to the correct calculation of pagination. 2. The pagination for "KeywordSearch" triggers a completely new search if you search for an order, change the page, and then press the "Previous page" button. This occurs because the method "processSearchParameters" in "ProductSearchSession" is called from the Groovy-Script of the Result-Screen (check "KeywordSearch.groovy") as well as from the method "checkDoKeywordOverride" which is triggered by the Form-Submit-Search-Request "keywordsearch" (see controller.xml). The additional call results in a new Search since the parameter "clearSearchString" is not send on the second occasion. Therefore one call should be eliminated. I chose to remove the method call from within "checkDoKeywordOverride" since it is unique to the component and is only triggered by this exact event. "KeywordSearch.groovy", in multiple components, always triggers the "ProductSearchSession.processSearchParameters(parameters, request)" another call is just not needed. Additionally I also removed the block of rechecking the set View and Index size which serves no purpose. Again, this block of actions is also not needed in similar java classes such as "WorkEffortSearchSession.java". To recreate the bug go to Order->OrderEntry-> Search in the catalog for "g" -> check the amount of shown pages and press "Next" -> press "back" -> note how many results you now have, from 19 to 35 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9413) Update Currency Uom data
[ https://issues.apache.org/jira/browse/OFBIZ-9413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16321912#comment-16321912 ] Deepak Dixit commented on OFBIZ-9413: - Hi Jacques, Yes I'll create new ticket for new amendment. Above comment is just a note for future reference that In this ticket we updated data till amendment_163. > Update Currency Uom data > - > > Key: OFBIZ-9413 > URL: https://issues.apache.org/jira/browse/OFBIZ-9413 > Project: OFBiz > Issue Type: Improvement >Reporter: Deepak Dixit >Assignee: Deepak Dixit > Fix For: Release Branch 14.12, Release Branch 15.12, 16.11.03 > > Attachments: OFBIZ-9413.patch, list_three.xls > > > While adding numericCode to currency UOM, I found that we need to update > some old currency UOM, as uomId has been updated. > https://www.currency-iso.org/en/home/tables/table-a1.html > https://www.currency-iso.org/en/home/amendments.html > Here is the short summary > *Following UomId not found* > * Santo Domiongo(CDP) > * Brazil (BRR) > * Argentinian Austral(ARA) > * Andoran peseta(ADP) > * Maltese Lira (MTL) > * Mexican Peso (old)(MXP) > * Peruvian Inti(PEI) > * Peruvian Sol(PES) > * Tadzhikistani Ruble(TJR) > *Following UOM using other currency* > Used Other > * ANDORRA == Euro > * Cyprus Pound(CYP) == Euro > * Ecuador Sucre(ECS) = USD > * Estonian Krone(EEK) = EURO > * Lithuanian Lita(LTL) == EURO > * Latvian Lat(LVL) == EURO > * Timor Escudo(TPE) == US Dollor > *Following UOM has been changed* > ||Old||New|| > |Belorussian Ruble(BYR)|Belarusian Ruble(BYN)| > |Bosnia-Herzogovinian Dinar(BAD)|Convertible Mark(BAM)| > |Azerbaijan Manat (AZM)|Azerbaijan Manat(AZN)| > |Angolan Kwanza (AOK)|Kwanza (AOA)| > |Afghani (AFA)|Afghani(AFN)| > |Dominican Republic Peso(DRP)|Dominican Peso (DOP)| > |Ghanian Cedi(GHC)|Ghana Cedi(GHS)| > |Guinea Peso(GWP)| Guinean Franc(GNF)| > |Kirghizstan Som(KIS)|KYRGYZSTAN Som (KGS)| > |Madagascan Franc(MGF)|Malagasy Ariary(MGA)| > |Mozambique Metical(MZM)|Mozambique Metical(MZN)| > |Nicaragua (NIC)|Cordoba Oro (NIO)| > |New Israeli Shekel(NIS)|New Israeli Sheqel (ILS)| > |Poland(PLZ)|Zloty (PLN)| > |Romanian Leu(ROL)|Romanian Leu(RON)| > |Russian Rouble(RUR)|Russian Ruble(RUB)| > |Sudanese Pound(SDP)|Sudanese Pound(SDG)| > |Peru (SOL)|Sol (PEN)| > |Surinam Guilder(SRG)|Surinam Dollar (SRD)| > |Turkmenistani Manat(TMM)|Turkmenistan New Manat(TMT)| > |Uganda Shilling(UGS)|Uganda Shilling(UGX)| > |Uruguayan New Peso(UYP)|Uruguay Peso en Unidades Indexadas (URUIURUI)(UYI)| > |Venezuelan Bolivar(VEB)|Bolívar(VEF)| > |Zambian Kwacha(ZMK)|Zambian Kwacha(ZMW)| > |Zimbabwean Dollar(ZWD)|Zimbabwe Dollar(ZWL)| > |Georgian Kupon (GEK)|GEORGIA Lari (GEL)| > Some currency codes moved to historic denominations, we can remove them from > data. > https://www.currency-iso.org/en/home/tables/table-a3.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10028) Update Geo information according to ISO notifications
[
https://issues.apache.org/jira/browse/OFBIZ-10028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyra Pritzel-Hentley updated OFBIZ-10028:
-
Attachment: OFBIZ-10028_ISO_Geo_Info_Notification_TG.patch
OFBIZ-10028_ISO_Geo_Info_Notification_TJ.patch
OFBIZ-10028_ISO_Geo_Info_Notification_UG.patch
Here are the last patches. For Uganda I really don't think we need info on all
121 Districts so I just recorded the four main regions.
Happy Commiting :)
> Update Geo information according to ISO notifications
> -
>
> Key: OFBIZ-10028
> URL: https://issues.apache.org/jira/browse/OFBIZ-10028
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Michael Brohl
>Priority: Minor
> Attachments: OFBIZ-10028_ISO_Geo_Info_Notification_CN.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_CY.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_CY.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_DE.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_EC.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_HU.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_ID.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_IS.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_KP.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_LA.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_MD.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_MH.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_ML.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_MX.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_NR.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_PA.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_PK.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_QA.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_TG.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_TJ.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_UG.patch
>
>
> This follows this discussion http://markmail.org/message/xn7f552qvtpua2uq,
> extract!
> bq. If someone is interested, the China changes are a bit to heavy for me,
> Here are the changes
> {quote}
> Country codes updated
> CN 2017-11-23 /China/
> CY 2017-11-23 /Cyprus/
> DE 2017-11-23 /Germany/
> EC 2017-11-23 /Ecuador/
> HK 2017-11-23 /Hong Kong/
> HU 2017-11-23 /Hungary/
> ID 2017-11-23 /Indonesia/
> IS 2017-11-23 /Iceland/
> KP 2017-11-23 /Korea (the
> Democratic People's Republic of)/
> LA 2017-11-23 /Lao
> People's Democratic Republic (the)/
> MD 2017-11-23 /Moldova
> (the Republic of)/
> MH 2017-11-23 /Marshall
> Islands (the)/
> ML 2017-11-23 /Mali/
> MO 2017-11-23 /Macao/
> MX 2017-11-23 /Mexico/
> NR 2017-11-23 /Nauru/
> PA 2017-11-23 /Panama/
> PK 2017-11-23 /Pakistan/
> QA 2017-11-23 /Qatar/
> TG 2017-11-23 /Togo/
> TJ 2017-11-23 /Tajikistan/
> UG 2017-11-23 /Uganda/
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OFBIZ-9413) Update Currency Uom data
[ https://issues.apache.org/jira/browse/OFBIZ-9413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16321890#comment-16321890 ] Jacques Le Roux commented on OFBIZ-9413: HI Deepak, Should we not create another Jira to handle this amendment? > Update Currency Uom data > - > > Key: OFBIZ-9413 > URL: https://issues.apache.org/jira/browse/OFBIZ-9413 > Project: OFBiz > Issue Type: Improvement >Reporter: Deepak Dixit >Assignee: Deepak Dixit > Fix For: Release Branch 14.12, Release Branch 15.12, 16.11.03 > > Attachments: OFBIZ-9413.patch, list_three.xls > > > While adding numericCode to currency UOM, I found that we need to update > some old currency UOM, as uomId has been updated. > https://www.currency-iso.org/en/home/tables/table-a1.html > https://www.currency-iso.org/en/home/amendments.html > Here is the short summary > *Following UomId not found* > * Santo Domiongo(CDP) > * Brazil (BRR) > * Argentinian Austral(ARA) > * Andoran peseta(ADP) > * Maltese Lira (MTL) > * Mexican Peso (old)(MXP) > * Peruvian Inti(PEI) > * Peruvian Sol(PES) > * Tadzhikistani Ruble(TJR) > *Following UOM using other currency* > Used Other > * ANDORRA == Euro > * Cyprus Pound(CYP) == Euro > * Ecuador Sucre(ECS) = USD > * Estonian Krone(EEK) = EURO > * Lithuanian Lita(LTL) == EURO > * Latvian Lat(LVL) == EURO > * Timor Escudo(TPE) == US Dollor > *Following UOM has been changed* > ||Old||New|| > |Belorussian Ruble(BYR)|Belarusian Ruble(BYN)| > |Bosnia-Herzogovinian Dinar(BAD)|Convertible Mark(BAM)| > |Azerbaijan Manat (AZM)|Azerbaijan Manat(AZN)| > |Angolan Kwanza (AOK)|Kwanza (AOA)| > |Afghani (AFA)|Afghani(AFN)| > |Dominican Republic Peso(DRP)|Dominican Peso (DOP)| > |Ghanian Cedi(GHC)|Ghana Cedi(GHS)| > |Guinea Peso(GWP)| Guinean Franc(GNF)| > |Kirghizstan Som(KIS)|KYRGYZSTAN Som (KGS)| > |Madagascan Franc(MGF)|Malagasy Ariary(MGA)| > |Mozambique Metical(MZM)|Mozambique Metical(MZN)| > |Nicaragua (NIC)|Cordoba Oro (NIO)| > |New Israeli Shekel(NIS)|New Israeli Sheqel (ILS)| > |Poland(PLZ)|Zloty (PLN)| > |Romanian Leu(ROL)|Romanian Leu(RON)| > |Russian Rouble(RUR)|Russian Ruble(RUB)| > |Sudanese Pound(SDP)|Sudanese Pound(SDG)| > |Peru (SOL)|Sol (PEN)| > |Surinam Guilder(SRG)|Surinam Dollar (SRD)| > |Turkmenistani Manat(TMM)|Turkmenistan New Manat(TMT)| > |Uganda Shilling(UGS)|Uganda Shilling(UGX)| > |Uruguayan New Peso(UYP)|Uruguay Peso en Unidades Indexadas (URUIURUI)(UYI)| > |Venezuelan Bolivar(VEB)|Bolívar(VEF)| > |Zambian Kwacha(ZMK)|Zambian Kwacha(ZMW)| > |Zimbabwean Dollar(ZWD)|Zimbabwe Dollar(ZWL)| > |Georgian Kupon (GEK)|GEORGIA Lari (GEL)| > Some currency codes moved to historic denominations, we can remove them from > data. > https://www.currency-iso.org/en/home/tables/table-a3.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10153) Shipping Label printing not working
[ https://issues.apache.org/jira/browse/OFBIZ-10153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16321867#comment-16321867 ] Jacques Le Roux commented on OFBIZ-10153: - Actually we could rather catch the exception and warn the developer (ie an OFBiz user) when still in development stage, no? > Shipping Label printing not working > > > Key: OFBIZ-10153 > URL: https://issues.apache.org/jira/browse/OFBIZ-10153 > Project: OFBiz > Issue Type: Bug >Affects Versions: 16.11.04 >Reporter: Deepak Dixit >Assignee: Deepak Dixit > Fix For: 16.11.05 > > > As per changes done at OFBIZ-6849, shipping label printing not working. > If we use https url in FOP fo:external-graphics it check for valid cert and > if cert not found it throws exception. > Need to add viewShipmentLabel url in http.request-map.list so that it will > serve as http instead https -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10028) Update Geo information according to ISO notifications
[
https://issues.apache.org/jira/browse/OFBIZ-10028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyra Pritzel-Hentley updated OFBIZ-10028:
-
Attachment: OFBIZ-10028_ISO_Geo_Info_Notification_MH.patch
OFBIZ-10028_ISO_Geo_Info_Notification_ML.patch
Small fix in ML and MH patches.
> Update Geo information according to ISO notifications
> -
>
> Key: OFBIZ-10028
> URL: https://issues.apache.org/jira/browse/OFBIZ-10028
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Michael Brohl
>Priority: Minor
> Attachments: OFBIZ-10028_ISO_Geo_Info_Notification_CN.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_CY.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_CY.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_DE.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_EC.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_HU.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_ID.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_IS.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_KP.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_LA.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_MD.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_MH.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_ML.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_MX.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_NR.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_PA.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_PK.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_QA.patch
>
>
> This follows this discussion http://markmail.org/message/xn7f552qvtpua2uq,
> extract!
> bq. If someone is interested, the China changes are a bit to heavy for me,
> Here are the changes
> {quote}
> Country codes updated
> CN 2017-11-23 /China/
> CY 2017-11-23 /Cyprus/
> DE 2017-11-23 /Germany/
> EC 2017-11-23 /Ecuador/
> HK 2017-11-23 /Hong Kong/
> HU 2017-11-23 /Hungary/
> ID 2017-11-23 /Indonesia/
> IS 2017-11-23 /Iceland/
> KP 2017-11-23 /Korea (the
> Democratic People's Republic of)/
> LA 2017-11-23 /Lao
> People's Democratic Republic (the)/
> MD 2017-11-23 /Moldova
> (the Republic of)/
> MH 2017-11-23 /Marshall
> Islands (the)/
> ML 2017-11-23 /Mali/
> MO 2017-11-23 /Macao/
> MX 2017-11-23 /Mexico/
> NR 2017-11-23 /Nauru/
> PA 2017-11-23 /Panama/
> PK 2017-11-23 /Pakistan/
> QA 2017-11-23 /Qatar/
> TG 2017-11-23 /Togo/
> TJ 2017-11-23 /Tajikistan/
> UG 2017-11-23 /Uganda/
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OFBIZ-10028) Update Geo information according to ISO notifications
[
https://issues.apache.org/jira/browse/OFBIZ-10028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyra Pritzel-Hentley updated OFBIZ-10028:
-
Attachment: (was: OFBIZ-10028_ISO_Geo_Info_Notification_MH.patch)
> Update Geo information according to ISO notifications
> -
>
> Key: OFBIZ-10028
> URL: https://issues.apache.org/jira/browse/OFBIZ-10028
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Michael Brohl
>Priority: Minor
> Attachments: OFBIZ-10028_ISO_Geo_Info_Notification_CN.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_CY.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_CY.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_DE.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_EC.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_HU.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_ID.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_IS.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_KP.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_LA.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_MD.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_MX.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_NR.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_PA.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_PK.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_QA.patch
>
>
> This follows this discussion http://markmail.org/message/xn7f552qvtpua2uq,
> extract!
> bq. If someone is interested, the China changes are a bit to heavy for me,
> Here are the changes
> {quote}
> Country codes updated
> CN 2017-11-23 /China/
> CY 2017-11-23 /Cyprus/
> DE 2017-11-23 /Germany/
> EC 2017-11-23 /Ecuador/
> HK 2017-11-23 /Hong Kong/
> HU 2017-11-23 /Hungary/
> ID 2017-11-23 /Indonesia/
> IS 2017-11-23 /Iceland/
> KP 2017-11-23 /Korea (the
> Democratic People's Republic of)/
> LA 2017-11-23 /Lao
> People's Democratic Republic (the)/
> MD 2017-11-23 /Moldova
> (the Republic of)/
> MH 2017-11-23 /Marshall
> Islands (the)/
> ML 2017-11-23 /Mali/
> MO 2017-11-23 /Macao/
> MX 2017-11-23 /Mexico/
> NR 2017-11-23 /Nauru/
> PA 2017-11-23 /Panama/
> PK 2017-11-23 /Pakistan/
> QA 2017-11-23 /Qatar/
> TG 2017-11-23 /Togo/
> TJ 2017-11-23 /Tajikistan/
> UG 2017-11-23 /Uganda/
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OFBIZ-10028) Update Geo information according to ISO notifications
[
https://issues.apache.org/jira/browse/OFBIZ-10028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyra Pritzel-Hentley updated OFBIZ-10028:
-
Attachment: (was: OFBIZ-10028_ISO_Geo_Info_Notification_ML.patch)
> Update Geo information according to ISO notifications
> -
>
> Key: OFBIZ-10028
> URL: https://issues.apache.org/jira/browse/OFBIZ-10028
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Michael Brohl
>Priority: Minor
> Attachments: OFBIZ-10028_ISO_Geo_Info_Notification_CN.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_CY.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_CY.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_DE.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_EC.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_HU.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_ID.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_IS.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_KP.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_LA.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_MD.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_MX.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_NR.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_PA.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_PK.patch,
> OFBIZ-10028_ISO_Geo_Info_Notification_QA.patch
>
>
> This follows this discussion http://markmail.org/message/xn7f552qvtpua2uq,
> extract!
> bq. If someone is interested, the China changes are a bit to heavy for me,
> Here are the changes
> {quote}
> Country codes updated
> CN 2017-11-23 /China/
> CY 2017-11-23 /Cyprus/
> DE 2017-11-23 /Germany/
> EC 2017-11-23 /Ecuador/
> HK 2017-11-23 /Hong Kong/
> HU 2017-11-23 /Hungary/
> ID 2017-11-23 /Indonesia/
> IS 2017-11-23 /Iceland/
> KP 2017-11-23 /Korea (the
> Democratic People's Republic of)/
> LA 2017-11-23 /Lao
> People's Democratic Republic (the)/
> MD 2017-11-23 /Moldova
> (the Republic of)/
> MH 2017-11-23 /Marshall
> Islands (the)/
> ML 2017-11-23 /Mali/
> MO 2017-11-23 /Macao/
> MX 2017-11-23 /Mexico/
> NR 2017-11-23 /Nauru/
> PA 2017-11-23 /Panama/
> PK 2017-11-23 /Pakistan/
> QA 2017-11-23 /Qatar/
> TG 2017-11-23 /Togo/
> TJ 2017-11-23 /Tajikistan/
> UG 2017-11-23 /Uganda/
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OFBIZ-10153) Shipping Label printing not working
[ https://issues.apache.org/jira/browse/OFBIZ-10153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16321864#comment-16321864 ] Jacques Le Roux commented on OFBIZ-10153: - Hi Deepak, Quoting you bq. If we use https url in FOP fo:external-graphics it check for valid cert and if cert not found it throws exception. Should this be OOTB w/o warning? In production people should use HTTPS with a cert, we know images are vulnerable. But I'm unsure how to warn people about using HTTPS there then (ie remove viewShipmentLabel from url.properties), puttin it in url.properties is not enough to warn I fear, any ideas? > Shipping Label printing not working > > > Key: OFBIZ-10153 > URL: https://issues.apache.org/jira/browse/OFBIZ-10153 > Project: OFBiz > Issue Type: Bug >Affects Versions: 16.11.04 >Reporter: Deepak Dixit >Assignee: Deepak Dixit > Fix For: 16.11.05 > > > As per changes done at OFBIZ-6849, shipping label printing not working. > If we use https url in FOP fo:external-graphics it check for valid cert and > if cert not found it throws exception. > Need to add viewShipmentLabel url in http.request-map.list so that it will > serve as http instead https -- This message was sent by Atlassian JIRA (v6.4.14#64029)
