[jira] [Comment Edited] (OFBIZ-7121) get-related-one element was not defined in file widget-form.xsd
[ https://issues.apache.org/jira/browse/OFBIZ-7121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970510#comment-15970510 ] Jacques Le Roux edited comment on OFBIZ-7121 at 4/16/17 9:01 PM: - Dalater was right, there is not widget-common.xsd in R13.07 and it's of course not included in widget.xsd. So I suggest all R13.07 users to update to more recent version R16.11 among them... was (Author: jacques.le.roux): Dalater was right, there is not widget-common.xsd in R13.07 and it's of course not included in widget.xsd. So I suggest all R13.07 to update to more recent version R16.11 among them... > get-related-one element was not defined in file widget-form.xsd > --- > > Key: OFBIZ-7121 > URL: https://issues.apache.org/jira/browse/OFBIZ-7121 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Release Branch 13.07 >Reporter: dalater >Assignee: Jacques Le Roux > > get-related-one element was not defined in file widget-form.xsd -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (OFBIZ-7375) Routing should not be allow to update with empty routing name
[ https://issues.apache.org/jira/browse/OFBIZ-7375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-7375. -- Resolution: Fixed Fix Version/s: (was: Trunk) Release Branch 13.07 Release Branch 14.12 Release Branch 15.12 16.11.02 Upcoming Release Thanks Ankit, Your patch is in trunk r1791634 R16.11 r1791635 R15.12 r1791636 R14.12 r1791637 R13.07 r1791638 > Routing should not be allow to update with empty routing name > - > > Key: OFBIZ-7375 > URL: https://issues.apache.org/jira/browse/OFBIZ-7375 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: Trunk >Reporter: Ankit Joshi >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Release, 16.11.02, Release Branch 15.12, > Release Branch 14.12, Release Branch 13.07 > > Attachments: OFBIZ-7375-trunk.patch > > > Steps to regenerate - > 1) Navigate to manufacturing -> Routing > 2) Press New Routing button. > 3) Try to create a routing without entering Routing Name. It will not allowed > to create the record as routing name is mandatory field. > 4) Create routing by adding proper details. > 5) Now, select newly create routing from manufacturing -> Routing > 6) Try to update selected routing with empty Routing Name. > Actual : Routing can be update with empty Routing Name. > Expected : Routing should not allow to update with empty Routing Name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-7375) Routing should not be allow to update with empty routing name
[ https://issues.apache.org/jira/browse/OFBIZ-7375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-7375: -- Assignee: Jacques Le Roux (was: Pierre Smits) > Routing should not be allow to update with empty routing name > - > > Key: OFBIZ-7375 > URL: https://issues.apache.org/jira/browse/OFBIZ-7375 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: Trunk >Reporter: Ankit Joshi >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-7375-trunk.patch > > > Steps to regenerate - > 1) Navigate to manufacturing -> Routing > 2) Press New Routing button. > 3) Try to create a routing without entering Routing Name. It will not allowed > to create the record as routing name is mandatory field. > 4) Create routing by adding proper details. > 5) Now, select newly create routing from manufacturing -> Routing > 6) Try to update selected routing with empty Routing Name. > Actual : Routing can be update with empty Routing Name. > Expected : Routing should not allow to update with empty Routing Name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9283) Remove code dependencies from application (at least product) to plugins (at least ecommerce)
[
https://issues.apache.org/jira/browse/OFBIZ-9283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-9283:
---
Issue Type: Sub-task (was: Bug)
Parent: OFBIZ-9322
> Remove code dependencies from application (at least product) to plugins (at
> least ecommerce)
>
>
> Key: OFBIZ-9283
> URL: https://issues.apache.org/jira/browse/OFBIZ-9283
> Project: OFBiz
> Issue Type: Sub-task
> Components: ecommerce, product
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
> Fix For: Upcoming Release
>
>
> Some applications have still references in code to plugins. I think it's only
> product to ecommerce but could be more...
> I did not try but I guess if you use only the framework (w/o plugins) and try
> the link in the catalog/control/EditProduct screen which leads to ecommerce
> ("Product Page") you will get an error, so it's a bug!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (OFBIZ-6650) Blank page when ordering an open-gismo-GZ-1006-p
[ https://issues.apache.org/jira/browse/OFBIZ-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970513#comment-15970513 ] Jacques Le Roux commented on OFBIZ-6650: bq. OK, I still reproduce, really weird stuff. I will debug it! One day (or another...) > Blank page when ordering an open-gismo-GZ-1006-p > > > Key: OFBIZ-6650 > URL: https://issues.apache.org/jira/browse/OFBIZ-6650 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: Upcoming Release > > Attachments: Image 095.png, Image 096.png, Image 097.png, Image > 098.png > > > This issue is also happenning in stable and old demo -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (OFBIZ-7121) get-related-one element was not defined in file widget-form.xsd
[ https://issues.apache.org/jira/browse/OFBIZ-7121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-7121. -- Resolution: Won't Fix Dalater was right, there is not widget-common.xsd in R13.07 and it's of course not included in widget.xsd. So I suggest all R13.07 to update to more recent version R16.11 among them... > get-related-one element was not defined in file widget-form.xsd > --- > > Key: OFBIZ-7121 > URL: https://issues.apache.org/jira/browse/OFBIZ-7121 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Release Branch 13.07 >Reporter: dalater >Assignee: Jacques Le Roux > > get-related-one element was not defined in file widget-form.xsd -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (OFBIZ-7265) Could not obtain Lock on lucene index Lock
[ https://issues.apache.org/jira/browse/OFBIZ-7265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-7265. -- Resolution: Fixed Assignee: Jacques Le Roux Fix Version/s: Release Branch 15.12 16.11.02 Upcoming Release Thanks a bunch Amardeep, well spotted! Your solution is in trunk r1791625 R16.11 and R15.12 r1791626 > Could not obtain Lock on lucene index Lock > -- > > Key: OFBIZ-7265 > URL: https://issues.apache.org/jira/browse/OFBIZ-7265 > Project: OFBiz > Issue Type: Bug > Components: lucene >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Release, 16.11.02, Release Branch 15.12 > > > I found this message in error.log > |xer_default_products |DocumentIndexer |E| Could not obtain > Lock on lucene index Lock held by this virtual machine: > C:\projectASF-Mars\ofbiz\runtime\indexes\products\write.lock > Here is Jacopo's answer: > bq. We should not worry (because the "lucene" component is just an > experimental one) but let's keep an eye on it: it is caused when two threads > are trying to update documents in the Lucene index; it may happen when two > events modify data that trigger the execution of the document update. We > could consider to enhance the DocumentIndexer to properly manage these > scenarios. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (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 ] Jacques Le Roux reopened OFBIZ-4502: I reopen this issue because, as I said in muy last comment: bq. We need instead to provide a migrateWebSitePathAlias migrating service. > 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: Trunk >Reporter: Martin Kreidenweis >Assignee: Jacques Le Roux > Fix For: 16.11.01 > > Attachments: CMS-Tree-Improvement-2.patch, > CMS-Tree-Improvement.patch, Image 109.png, OFBIZ-4502.patch, > OFBIZ-4502.showErrorTree.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 was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-6110) Move as much as possible demo data from ecommerce to product or order components
[ https://issues.apache.org/jira/browse/OFBIZ-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-6110: --- Issue Type: Sub-task (was: Improvement) Parent: OFBIZ-9322 > Move as much as possible demo data from ecommerce to product or order > components > > > Key: OFBIZ-6110 > URL: https://issues.apache.org/jira/browse/OFBIZ-6110 > Project: OFBiz > Issue Type: Sub-task > Components: ecommerce, order, product >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Release > > > It would be better if we have most of the demo product data in product or > maybe in order component. Because almost all what can be done concerning > ordering in ecommerce can also be done in order manager from which anyway > ecommerce depends on > More generally each component should have the data to be able to work as much > on its own as possible. Even if that means redundancy of some sorts. Most of > the time, we can avoid redudancy when there are components dependencies and > the component data are loaded after the main one. > This is when > https://cwiki.apache.org/confluence/display/OFBIZ/Component+and+Component+Set+Dependencies > helps and shows why it should be actively maintained! For instance I'm not > sure we show data loading order there... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-7532) Form Display Field improvement to manage multiple number format
[ https://issues.apache.org/jira/browse/OFBIZ-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970498#comment-15970498 ] Jacques Le Roux commented on OFBIZ-7532: Hi Charles, any chances? > Form Display Field improvement to manage multiple number format > --- > > Key: OFBIZ-7532 > URL: https://issues.apache.org/jira/browse/OFBIZ-7532 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Charles STELTZLEN >Assignee: Jacques Le Roux >Priority: Minor > Attachments: OFBIZ-7532.patch > > > On display field used in forms, there is a "type" "accounting-number" which > is used to format number like property configuration : > #,##0.;(#,##0.). > This JIRA propose to extend this idea by using a "type" "number" and an > additional attribute called "format-pattern". This field will be used by form > renderer to get the good property. It use FlexibleString to manage variable > in this field and so allow to have different format for the same column > according to some conditions. > example: format-pattern="accounting"/> > The "format-pattern" will be stored in arithmetic.properties. > example: > # the default number format > default.number.format = ##0.00 > accounting.number.format = #,##0.;(#,##0.) > quantity.number.format = ##0.00 > integer-quantity.number.format = #0 > percentage.number.format = ##.##% > export.number.format = #.00 > In ModelFormField.java, the system gets property using > EntityUtilProperties.getPropertyValue to ba able to quickly add a new format. > I think that it will require a discussion on Dev mailing-list to validate the > choices. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9323) Remove the birt.tld file and all related files and lines
[ https://issues.apache.org/jira/browse/OFBIZ-9323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970457#comment-15970457 ] Jacques Le Roux commented on OFBIZ-9323: Hi Taher, Yes indeed when I create the patch, either with ToirtoiseSvn (as here) or with Subclipse, or even svn di (which is actually used underneath by both before) the removed files are not in the patch. Why is explained here https://stackoverflow.com/questions/12124660/svn-diff-ignoring-deleted-files. But yes, as I have mentionned in the dev ML thread I intend to also remove all concernes files or folders (and their content), ie: birt/template birt/webapp/birt/WEB-INF/attachments birt.tld server-config.wsdd It would be great indeed if we could put back the Birt viewer. But is not the new POJO based API still using the EPL v1 license? Note though that if this is impossible, because of the license, we could still explain in a page in the wiki how to use the Birt viewer, even its both versions... I also read that the Eclipse fundation is working on a v2 of the EPL. But it's only to make it more compatible with the GPL not the ASL. So I see no chances with both EPL license versions to be integrated in an Apache released product. > Remove the birt.tld file and all related files and lines > > > Key: OFBIZ-9323 > URL: https://issues.apache.org/jira/browse/OFBIZ-9323 > Project: OFBiz > Issue Type: Task > Components: birt >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: Upcoming Release > > Attachments: OFBIZ-9323.patch > > > After LEGAL-296 and this thread https://s.apache.org/HdLV, it's clear we need > to clean Birt from wrong licensed files and related features. > Hopefully the same will apply to R16.11 branch. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9323) Remove the birt.tld file and all related files and lines
[ https://issues.apache.org/jira/browse/OFBIZ-9323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970326#comment-15970326 ] Taher Alkhateeb commented on OFBIZ-9323: Hello, I don't see the removal of the tld file in this patch? It's unfortunate that we are going to remove some of the best demonstration features of eclipse due to this licensing issue, it seems upgrading to the newest version of the viewer might resolve this because the new API is POJO based, but there is some work to do to implement this integration. > Remove the birt.tld file and all related files and lines > > > Key: OFBIZ-9323 > URL: https://issues.apache.org/jira/browse/OFBIZ-9323 > Project: OFBiz > Issue Type: Task > Components: birt >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: Upcoming Release > > Attachments: OFBIZ-9323.patch > > > After LEGAL-296 and this thread https://s.apache.org/HdLV, it's clear we need > to clean Birt from wrong licensed files and related features. > Hopefully the same will apply to R16.11 branch. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9323) Remove the birt.tld file and all related files and lines
[ https://issues.apache.org/jira/browse/OFBIZ-9323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-9323: --- Attachment: OFBIZ-9323.patch > Remove the birt.tld file and all related files and lines > > > Key: OFBIZ-9323 > URL: https://issues.apache.org/jira/browse/OFBIZ-9323 > Project: OFBiz > Issue Type: Task > Components: birt >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: Upcoming Release > > Attachments: OFBIZ-9323.patch > > > After LEGAL-296 and this thread https://s.apache.org/HdLV, it's clear we need > to clean Birt from wrong licensed files and related features. > Hopefully the same will apply to R16.11 branch. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9323) Remove the birt.tld file and all related files and lines
Jacques Le Roux created OFBIZ-9323: -- Summary: Remove the birt.tld file and all related files and lines Key: OFBIZ-9323 URL: https://issues.apache.org/jira/browse/OFBIZ-9323 Project: OFBiz Issue Type: Task Components: birt Affects Versions: Trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux Fix For: Upcoming Release After LEGAL-296 and this thread https://s.apache.org/HdLV, it's clear we need to clean Birt from wrong licensed files and related features. Hopefully the same will apply to R16.11 branch. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9225) Editing quantity of configurable products changes actual product
[ https://issues.apache.org/jira/browse/OFBIZ-9225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970264#comment-15970264 ] Jacques Le Roux commented on OFBIZ-9225: To completly close this subject: bq. I confused the ship group line and the quantity column :/ Maybe we could do a better UI and have the edit qty input field near the the ordered label Actually the quantity is by ship group and I even committed a way to dynamically edit the quantity by ship group with OFBIZ-5761 So this is only missing a columns separation but I'd not try that with an FTL file and I have not the guts to change EditOrderItems.ftl into a widget form... > Editing quantity of configurable products changes actual product > - > > Key: OFBIZ-9225 > URL: https://issues.apache.org/jira/browse/OFBIZ-9225 > Project: OFBiz > Issue Type: Bug > Components: product >Affects Versions: Trunk, 16.11.01, Release Branch 15.12 >Reporter: Suraj Khurana >Assignee: Deepak Dixit > Fix For: Release Branch 14.12, Release Branch 15.12, Upcoming > Release, 16.11.02 > > Attachments: EditOrderQty.png, Image 001.png, OFBIZ-9225.patch, > OFBIZ-9225.patch > > > Create an order by adding any configurable product. > Try to edit the quantity of configurable product. > Actual product changes in cart > Technical details: > Quantity changes successfully but actual sellable product which is of > "AGGREGATED_CONF" type changes with parent "AGGREGATED" type product. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9322) Remove all dependencies from OFBiz framework to plugins
Taher Alkhateeb created OFBIZ-9322: -- Summary: Remove all dependencies from OFBiz framework to plugins Key: OFBIZ-9322 URL: https://issues.apache.org/jira/browse/OFBIZ-9322 Project: OFBiz Issue Type: Improvement Affects Versions: Upcoming Release Reporter: Taher Alkhateeb Assignee: Taher Alkhateeb Priority: Minor The OFBiz [framework repository|http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk] fails to build and run tests unless the [plugins repository|http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk] is added first. The reason for this failure is mostly due to dependencies of some tests defined in the framework on data that is defined in the ecommerce plugin. The purpose of this JIRA is to completely remove all these dependencies and achieve a successful build of the framework using the command "./gradlew cleanAll loadDefault testIntegration" This task requires multiple different approaches including: - Moving some demo data from ecommerce to framework - Moving some tests where relevant from framework to ecommerce - Refactoring and/or removing some tests to disentangle the dependencies -- This message was sent by Atlassian JIRA (v6.3.15#6346)
