[jira] [Updated] (OFBIZ-9258) Render form values from pulled data
[ https://issues.apache.org/jira/browse/OFBIZ-9258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Yong updated OFBIZ-9258: -- Attachment: OFBIZ-9258.patch A patch is provided as POC. Currently, only implemented for the text fields. To test it, append '&pullData=true' to the url and call the form page again. > Render form values from pulled data > --- > > Key: OFBIZ-9258 > URL: https://issues.apache.org/jira/browse/OFBIZ-9258 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Upcoming Release >Reporter: James Yong >Assignee: James Yong >Priority: Minor > Attachments: OFBIZ-9258.patch > > > Currently, form data is being rendered together with the form widgets. To > better facilitate the use of Single Page or Mobile Application in the future, > it would be better to let the form widgets pull data from the server instead. > An initial discussion was made at > http://ofbiz.135035.n4.nabble.com/Render-table-rows-from-pulled-data-td4703142.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9258) Render form values from pulled data
James Yong created OFBIZ-9258: - Summary: Render form values from pulled data Key: OFBIZ-9258 URL: https://issues.apache.org/jira/browse/OFBIZ-9258 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Upcoming Release Reporter: James Yong Assignee: James Yong Priority: Minor Currently, form data is being rendered together with the form widgets. To better facilitate the use of Single Page or Mobile Application in the future, it would be better to let the form widgets pull data from the server instead. An initial discussion was made at http://ofbiz.135035.n4.nabble.com/Render-table-rows-from-pulled-data-td4703142.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (OFBIZ-9257) various problems in SFA
[ https://issues.apache.org/jira/browse/OFBIZ-9257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker closed OFBIZ-9257. -- Resolution: Fixed Committed revision 1786622 > various problems in SFA > --- > > Key: OFBIZ-9257 > URL: https://issues.apache.org/jira/browse/OFBIZ-9257 > Project: OFBiz > Issue Type: Bug > Components: marketing >Affects Versions: Trunk >Reporter: Hans Bakker >Priority: Critical > Attachments: sfa.diff > > > several problems in SFA fixed: > 1. leads without contactmech not show in my leads > 2. converted leads not show in contacts > 3. expired leads and contacts still show > 4. various other problems -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9257) various problems in SFA
[ https://issues.apache.org/jira/browse/OFBIZ-9257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker updated OFBIZ-9257: --- Attachment: sfa.diff this patch fixes these issues > various problems in SFA > --- > > Key: OFBIZ-9257 > URL: https://issues.apache.org/jira/browse/OFBIZ-9257 > Project: OFBiz > Issue Type: Bug > Components: marketing >Affects Versions: Trunk >Reporter: Hans Bakker >Priority: Critical > Attachments: sfa.diff > > > several problems in SFA fixed: > 1. leads without contactmech not show in my leads > 2. converted leads not show in contacts > 3. expired leads and contacts still show > 4. various other problems -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9257) various problems in SFA
Hans Bakker created OFBIZ-9257: -- Summary: various problems in SFA Key: OFBIZ-9257 URL: https://issues.apache.org/jira/browse/OFBIZ-9257 Project: OFBiz Issue Type: Bug Components: marketing Affects Versions: Trunk Reporter: Hans Bakker Priority: Critical several problems in SFA fixed: 1. leads without contactmech not show in my leads 2. converted leads not show in contacts 3. expired leads and contacts still show 4. various other problems -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9182) Create a separate svn repository for OFBiz official plugins
[ https://issues.apache.org/jira/browse/OFBIZ-9182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906509#comment-15906509 ] Jacques Le Roux commented on OFBIZ-9182: Done > Create a separate svn repository for OFBiz official plugins > --- > > Key: OFBIZ-9182 > URL: https://issues.apache.org/jira/browse/OFBIZ-9182 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Release >Reporter: Taher Alkhateeb >Priority: Minor > Labels: gradle, plugins, subversion > Attachments: OFBIZ-9182-subversion-embedded.patch, pluginsList.txt, > pullAllPluginsSource.log > > > This issue is related to the discussion found in [this > thread|https://s.apache.org/aohk] in which the community approved > restructuring our repositories. To achieve this task the following needs to > be done (in this order) > # Update the gradle scripts to assume that no plugins exist in the plugins > directory by default and no component-load.xml exists. It should follow the > same logic in loading the components as found in the ComponentContainer > class. Also the activation and deactivation of plugins happens in > ofbiz-component.xml, not in component-load.xml > # Add a new task to gradle called pullPluginSource that retrieves a plugin > from subversion and defaults to the official plugins repository of Apache > OFBiz. This task mostly serve "Trunk" because it always needs the latest > source code of the plugins. > # delete plugins/component-load.xml > # move all plugins to a new repository called > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins > # move the core framework to a new repository called > http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework > # fix buildbot to point to the new framework location > # update documentation where applicable including README.md -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9256) Split the tools folder from the trunk and put it in another branch
Jacques Le Roux created OFBIZ-9256: -- Summary: Split the tools folder from the trunk and put it in another branch Key: OFBIZ-9256 URL: https://issues.apache.org/jira/browse/OFBIZ-9256 Project: OFBiz Issue Type: Task Reporter: Jacques Le Roux The tools folder contains only tools used by the OFBiz team and is of no help for OFBiz users and could even be confusing. So this should not be delivered with the OFBiz trunk, plugins or releases. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9182) Create a separate svn repository for OFBiz official plugins
[ https://issues.apache.org/jira/browse/OFBIZ-9182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906489#comment-15906489 ] Jacques Le Roux commented on OFBIZ-9182: bq. if you use pullPluginSource, then each pulled plugin will have its own .svn. If on the other hand you use pullAllPluginsSource then you will have a single .svn for all plugins I think we need to document this technical aspect in the README. I'll use your sentence. bq. The no install task defined for plugin means there is nothing to do. To make it more clear, we can simply add the words "nothing to do" to make it clear that nothing went wrong. This is a minor issue as far as I'm concerned though. Yes sounds good to me, I'd add ". Nothing to do and worry about, see the documentation for more" > Create a separate svn repository for OFBiz official plugins > --- > > Key: OFBIZ-9182 > URL: https://issues.apache.org/jira/browse/OFBIZ-9182 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Release >Reporter: Taher Alkhateeb >Priority: Minor > Labels: gradle, plugins, subversion > Attachments: OFBIZ-9182-subversion-embedded.patch, pluginsList.txt, > pullAllPluginsSource.log > > > This issue is related to the discussion found in [this > thread|https://s.apache.org/aohk] in which the community approved > restructuring our repositories. To achieve this task the following needs to > be done (in this order) > # Update the gradle scripts to assume that no plugins exist in the plugins > directory by default and no component-load.xml exists. It should follow the > same logic in loading the components as found in the ComponentContainer > class. Also the activation and deactivation of plugins happens in > ofbiz-component.xml, not in component-load.xml > # Add a new task to gradle called pullPluginSource that retrieves a plugin > from subversion and defaults to the official plugins repository of Apache > OFBiz. This task mostly serve "Trunk" because it always needs the latest > source code of the plugins. > # delete plugins/component-load.xml > # move all plugins to a new repository called > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins > # move the core framework to a new repository called > http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework > # fix buildbot to point to the new framework location > # update documentation where applicable including README.md -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9182) Create a separate svn repository for OFBiz official plugins
[ https://issues.apache.org/jira/browse/OFBIZ-9182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906488#comment-15906488 ] Taher Alkhateeb commented on OFBIZ-9182: To answer quickly: - if you use pullPluginSource, then each pulled plugin will have its own .svn. If on the other hand you use pullAllPluginsSource then you will have a single .svn for all plugins - The no install task defined for plugin means there is nothing to do. To make it more clear, we can simply add the words "nothing to do" to make it clear that nothing went wrong. This is a minor issue as far as I'm concerned though. > Create a separate svn repository for OFBiz official plugins > --- > > Key: OFBIZ-9182 > URL: https://issues.apache.org/jira/browse/OFBIZ-9182 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Release >Reporter: Taher Alkhateeb >Priority: Minor > Labels: gradle, plugins, subversion > Attachments: OFBIZ-9182-subversion-embedded.patch, pluginsList.txt, > pullAllPluginsSource.log > > > This issue is related to the discussion found in [this > thread|https://s.apache.org/aohk] in which the community approved > restructuring our repositories. To achieve this task the following needs to > be done (in this order) > # Update the gradle scripts to assume that no plugins exist in the plugins > directory by default and no component-load.xml exists. It should follow the > same logic in loading the components as found in the ComponentContainer > class. Also the activation and deactivation of plugins happens in > ofbiz-component.xml, not in component-load.xml > # Add a new task to gradle called pullPluginSource that retrieves a plugin > from subversion and defaults to the official plugins repository of Apache > OFBiz. This task mostly serve "Trunk" because it always needs the latest > source code of the plugins. > # delete plugins/component-load.xml > # move all plugins to a new repository called > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins > # move the core framework to a new repository called > http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework > # fix buildbot to point to the new framework location > # update documentation where applicable including README.md -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9182) Create a separate svn repository for OFBiz official plugins
[
https://issues.apache.org/jira/browse/OFBIZ-9182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906485#comment-15906485
]
Jacques Le Roux commented on OFBIZ-9182:
Thanks Taher great work!
I'll answer to your last related message in the dev ML. To not make my answer
too verbose there, I have a question here.
Maybe I read it wrong but reading the documentation I thought we would have a
.svn directory in each plugin
bq. Download all officially supported plugins from source control (currently
subversion) and place them inclusive of *their ".svn" directory* in /plugins.
Actually we have only one . svn for all plugins, and I very like it like it
like that, much easier for maintenance, thanks! So maybe we should make the
documentation more clear?
Also when I run pullAllPluginsSource I get
{code}
C:\projectsASF\ofbiz-framework>gradlew pullAllPluginsSource
:pullPluginsFromSvn
:pullAllPluginsSource
:installAllPlugins
No install task defined for plugin assetmaint
No install task defined for plugin bi
No install task defined for plugin birt
No install task defined for plugin cmssite
No install task defined for plugin ebay
No install task defined for plugin ecommerce
No install task defined for plugin example
No install task defined for plugin exampleext
No install task defined for plugin hhfacility
No install task defined for plugin ldap
No install task defined for plugin lucene
No install task defined for plugin myportal
No install task defined for plugin passport
No install task defined for plugin pricat
No install task defined for plugin projectmgr
No install task defined for plugin scrum
No install task defined for plugin solr
No install task defined for plugin webpos
{code}
I guess it's OK (no specific tasks to do OOTB in each plugins) but maybe we
should document that in the the README? To avoid questions on this subject
(and prevent my RTFM reflex ;)) or make answers easier by pointing to the
documentation
> Create a separate svn repository for OFBiz official plugins
> ---
>
> Key: OFBIZ-9182
> URL: https://issues.apache.org/jira/browse/OFBIZ-9182
> Project: OFBiz
> Issue Type: Improvement
>Affects Versions: Upcoming Release
>Reporter: Taher Alkhateeb
>Priority: Minor
> Labels: gradle, plugins, subversion
> Attachments: OFBIZ-9182-subversion-embedded.patch, pluginsList.txt,
> pullAllPluginsSource.log
>
>
> This issue is related to the discussion found in [this
> thread|https://s.apache.org/aohk] in which the community approved
> restructuring our repositories. To achieve this task the following needs to
> be done (in this order)
> # Update the gradle scripts to assume that no plugins exist in the plugins
> directory by default and no component-load.xml exists. It should follow the
> same logic in loading the components as found in the ComponentContainer
> class. Also the activation and deactivation of plugins happens in
> ofbiz-component.xml, not in component-load.xml
> # Add a new task to gradle called pullPluginSource that retrieves a plugin
> from subversion and defaults to the official plugins repository of Apache
> OFBiz. This task mostly serve "Trunk" because it always needs the latest
> source code of the plugins.
> # delete plugins/component-load.xml
> # move all plugins to a new repository called
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins
> # move the core framework to a new repository called
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework
> # fix buildbot to point to the new framework location
> # update documentation where applicable including README.md
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (OFBIZ-9133) catalog/control/FindReviews does not render proper column data
[ https://issues.apache.org/jira/browse/OFBIZ-9133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906466#comment-15906466 ] Jacques Le Roux commented on OFBIZ-9133: Hi Wai, It seems to me that this issue was specific to this form. Feel free to open new issues if you want to review or know other related cases. I guess if after reviewing few forms using ignore-when and you don't find any issues it not worth reviewning all(!) forms ;) Thanks to care! > catalog/control/FindReviews does not render proper column data > -- > > Key: OFBIZ-9133 > URL: https://issues.apache.org/jira/browse/OFBIZ-9133 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Wai >Assignee: Jacques Le Roux > Fix For: Release Branch 13.07, Release Branch 14.12, Release > Branch 15.12, Upcoming Release, 16.11.02 > > Attachments: ofbiz-9133.patch, ofbiz-9133-Problem1.png, > ofbiz-9133-Problem2.png, ofbiz-9133-Solution.png > > > -go to https://localhost:8443/catalog/control/FindReviews > -find productId=GZ-2644 > -notice the table columns do not match the data -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9182) Create a separate svn repository for OFBiz official plugins
[ https://issues.apache.org/jira/browse/OFBIZ-9182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906447#comment-15906447 ] Taher Alkhateeb commented on OFBIZ-9182: Committed in r1786562 the implementation of the new task "pullAllPluginsSource" which delete the /plugins directory and replaces it with the plugins repository and for each plugin it executes the "install" task if it exists. The only thing left aside from general documentation is to create two separate buildbot scripts. One for ofbiz-framework and one for ofbiz-plugins to separate the two projects from each other. > Create a separate svn repository for OFBiz official plugins > --- > > Key: OFBIZ-9182 > URL: https://issues.apache.org/jira/browse/OFBIZ-9182 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Release >Reporter: Taher Alkhateeb >Priority: Minor > Labels: gradle, plugins, subversion > Attachments: OFBIZ-9182-subversion-embedded.patch, pluginsList.txt, > pullAllPluginsSource.log > > > This issue is related to the discussion found in [this > thread|https://s.apache.org/aohk] in which the community approved > restructuring our repositories. To achieve this task the following needs to > be done (in this order) > # Update the gradle scripts to assume that no plugins exist in the plugins > directory by default and no component-load.xml exists. It should follow the > same logic in loading the components as found in the ComponentContainer > class. Also the activation and deactivation of plugins happens in > ofbiz-component.xml, not in component-load.xml > # Add a new task to gradle called pullPluginSource that retrieves a plugin > from subversion and defaults to the official plugins repository of Apache > OFBiz. This task mostly serve "Trunk" because it always needs the latest > source code of the plugins. > # delete plugins/component-load.xml > # move all plugins to a new repository called > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins > # move the core framework to a new repository called > http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework > # fix buildbot to point to the new framework location > # update documentation where applicable including README.md -- This message was sent by Atlassian JIRA (v6.3.15#6346)
