[jira] [Commented] (OFBIZ-6856) ContactMechs Label

[Julien NICOLAS (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15120344#comment-15120344
 ] 

Julien NICOLAS commented on OFBIZ-6856:
---

Issue fixed in release :
Trunk 1727207
13.07 1727212

> ContactMechs Label
> --
>
> Key: OFBIZ-6856
> URL: https://issues.apache.org/jira/browse/OFBIZ-6856
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk, 13.07.02
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
> Fix For: 13.07.03, Upcoming Branch
>
> Attachments: JIRA6856-1307.patch, JIRA6856.patch
>
>
> Is it normal that in facility, the label for contact information is named 
> "ContactMechs".
> I think it could be a mistake but I'm French and maybe I miss something.
> Anyway, I think this label must be "Contact Mechs" and if we want to 
> standardize the contact mech label, it must be "Contact Information"
> In the same way, if you select "ContactMechs", you can find the "New Contact 
> Mech" button that can be rename as "New contact information".
> What is your opinion ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6843) New theme Rainbow Stone

[Julien NICOLAS (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15120420#comment-15120420
 ] 

Julien NICOLAS commented on OFBIZ-6843:
---

Yes ! It sound good.

Thanks !

Unfortunately the next version I'll provide in the next minutes will not have 
it :D

> New theme Rainbow Stone
> ---
>
> Key: OFBIZ-6843
> URL: https://issues.apache.org/jira/browse/OFBIZ-6843
> Project: OFBiz
>  Issue Type: Improvement
>  Components: themes
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
>  Labels: features, theme
> Fix For: Trunk
>
> Attachments: patch2forRainbowstoneTheme.patch, screenshot-1.png
>
>
> I create a new theme based on Flat Grey.
> It's the beginning but already functional, my goal is to provide a new style 
> for OFBiz.
> This is my tastes, so don't hesitate to criticize :)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6843) New theme Rainbow Stone

[Julien NICOLAS (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julien NICOLAS updated OFBIZ-6843:
--
Attachment: (was: rainbowstone.tar.gz)

> New theme Rainbow Stone
> ---
>
> Key: OFBIZ-6843
> URL: https://issues.apache.org/jira/browse/OFBIZ-6843
> Project: OFBiz
>  Issue Type: Improvement
>  Components: themes
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
>  Labels: features, theme
> Fix For: Trunk
>
> Attachments: patch2forRainbowstoneTheme.patch, screenshot-1.png
>
>
> I create a new theme based on Flat Grey.
> It's the beginning but already functional, my goal is to provide a new style 
> for OFBiz.
> This is my tastes, so don't hesitate to criticize :)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6843) New theme Rainbow Stone

[Julien NICOLAS (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julien NICOLAS updated OFBIZ-6843:
--
Attachment: rainbowstone.tar.gz

I fix seed data and jquery call ;)
For the next version, I hope to use the new Nicolas's idea.

> New theme Rainbow Stone
> ---
>
> Key: OFBIZ-6843
> URL: https://issues.apache.org/jira/browse/OFBIZ-6843
> Project: OFBiz
>  Issue Type: Improvement
>  Components: themes
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
>  Labels: features, theme
> Fix For: Trunk
>
> Attachments: patch2forRainbowstoneTheme.patch, rainbowstone.tar.gz, 
> screenshot-1.png
>
>
> I create a new theme based on Flat Grey.
> It's the beginning but already functional, my goal is to provide a new style 
> for OFBiz.
> This is my tastes, so don't hesitate to criticize :)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6856) ContactMechs Label

[Julien NICOLAS (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julien NICOLAS updated OFBIZ-6856:
--
Attachment: JIRA6856.patch

Fix translation issue for contact Mech as Party contact Mech translation for 
trunk

> ContactMechs Label
> --
>
> Key: OFBIZ-6856
> URL: https://issues.apache.org/jira/browse/OFBIZ-6856
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk, 13.07.02
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
> Attachments: JIRA6856.patch
>
>
> Is it normal that in facility, the label for contact information is named 
> "ContactMechs".
> I think it could be a mistake but I'm French and maybe I miss something.
> Anyway, I think this label must be "Contact Mechs" and if we want to 
> standardize the contact mech label, it must be "Contact Information"
> In the same way, if you select "ContactMechs", you can find the "New Contact 
> Mech" button that can be rename as "New contact information".
> What is your opinion ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jira] [Closed] (OFBIZ-6760) Move all entity definitions from the applications components into a separate one

[gil portenseigne]

I like the idea.

Gil

On 27/01/2016 19:28, Jacques Le Roux wrote:

I have to think more about it, but my 1st feeling is the same

Jacques

Le 27/01/2016 05:59, Deepak Dixit a écrit :

Sounds good to me.

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Mon, Jan 25, 2016 at 6:52 PM, Nicolas Malin 


wrote:


Hi,

Now as the data-model is present and the task closed, can we 
continue to

move all crud on the same component and keep only service with business
oriented logic on the dedicate component ?

I think about service like
createProductCategory/updateProductCategory/deleteProductCategory 
and not

storeOrder ;)

Nicolas



Le 16/01/2016 12:49, Deepak Dixit (JIRA) a écrit :


   [
https://issues.apache.org/jira/browse/OFBIZ-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel 


]

Deepak Dixit closed OFBIZ-6760.
---

Move all entity definitions from the applications components into a

separate one

 



  Key: OFBIZ-6760
  URL: 
https://issues.apache.org/jira/browse/OFBIZ-6760

  Project: OFBiz
   Issue Type: Improvement
   Components: ALL APPLICATIONS
 Affects Versions: Trunk
 Reporter: Jacques Le Roux
 Assignee: Jacopo Cappellato
  Fix For: Upcoming Branch


See this thread for a previous discussion:
http://markmail.org/message/sfdm22wfy3fulpyb



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-6856) ContactMechs Label

[Julien NICOLAS (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julien NICOLAS closed OFBIZ-6856.
-

> ContactMechs Label
> --
>
> Key: OFBIZ-6856
> URL: https://issues.apache.org/jira/browse/OFBIZ-6856
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk, 13.07.02
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
> Fix For: 13.07.03, Upcoming Branch
>
> Attachments: JIRA6856-1307.patch, JIRA6856.patch
>
>
> Is it normal that in facility, the label for contact information is named 
> "ContactMechs".
> I think it could be a mistake but I'm French and maybe I miss something.
> Anyway, I think this label must be "Contact Mechs" and if we want to 
> standardize the contact mech label, it must be "Contact Information"
> In the same way, if you select "ContactMechs", you can find the "New Contact 
> Mech" button that can be rename as "New contact information".
> What is your opinion ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6856) ContactMechs Label

[Julien NICOLAS (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julien NICOLAS updated OFBIZ-6856:
--
Attachment: JIRA6856-1307.patch

Patch for 13.07

> ContactMechs Label
> --
>
> Key: OFBIZ-6856
> URL: https://issues.apache.org/jira/browse/OFBIZ-6856
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk, 13.07.02
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
> Attachments: JIRA6856-1307.patch, JIRA6856.patch
>
>
> Is it normal that in facility, the label for contact information is named 
> "ContactMechs".
> I think it could be a mistake but I'm French and maybe I miss something.
> Anyway, I think this label must be "Contact Mechs" and if we want to 
> standardize the contact mech label, it must be "Contact Information"
> In the same way, if you select "ContactMechs", you can find the "New Contact 
> Mech" button that can be rename as "New contact information".
> What is your opinion ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-6857) Add service crud for AgreementItemAttribute

[Nicolas Malin (JIRA)]

Nicolas Malin created OFBIZ-6857:


 Summary: Add service crud for AgreementItemAttribute
 Key: OFBIZ-6857
 URL: https://issues.apache.org/jira/browse/OFBIZ-6857
 Project: OFBiz
  Issue Type: New Feature
  Components: accounting
Affects Versions: Trunk
Reporter: Nicolas Malin
Assignee: Nicolas Malin
Priority: Trivial
 Fix For: Upcoming Branch


all on the subject



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-6857) Add service crud for AgreementItemAttribute

[Nicolas Malin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Malin closed OFBIZ-6857.

Resolution: Implemented

> Add service crud for AgreementItemAttribute
> ---
>
> Key: OFBIZ-6857
> URL: https://issues.apache.org/jira/browse/OFBIZ-6857
> Project: OFBiz
>  Issue Type: New Feature
>  Components: accounting
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Assignee: Nicolas Malin
>Priority: Trivial
>  Labels: crud
> Fix For: Upcoming Branch
>
>
> all on the subject



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6743) Error on the Split Payment button from the Quick Finalize Order screen

[Pierre Smits (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15119446#comment-15119446
 ] 

Pierre Smits commented on OFBIZ-6743:
-

So to understand this issue correctly the quick checkout process in the order 
component is missing a reference to the view-map 'checkoutpayment'?

Adding the view-map to the controller.xml of the ordermgr component is a good 
thing, but removing the screen and the associated .ftl from the ecommerce 
component isn't. 
The front-end side (from a webshop perspective) is often heavily modified, and 
having the screen and freemarker definition in a backend component shouldn't be 
happening.

> Error on the Split Payment button from the Quick Finalize Order screen
> --
>
> Key: OFBIZ-6743
> URL: https://issues.apache.org/jira/browse/OFBIZ-6743
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Release Branch 12.04, Release Branch 13.07, Release 
> Branch 14.12, Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
> Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch
>
>
> Error in trunk:
> ERROR rendering error page [/error/error.jsp], but here is the error text: 
> org.ofbiz.webapp.control.RequestHandlerException: No definition found for 
> view with name [checkoutpayment]
> Error in stable and old:
> org.ofbiz.webapp.control.RequestHandlerException: No definition found for 
> view with name [checkoutpayment]
> This is the same kind of error you got with OFBIZ-6741 before it was fixed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Triangular VAT in Europe ?

[Nicolas Malin]

Hello, In Europe with the B2B drop shipment process we have a specific 
rule to calculate the VAT. The particularity comes from the purchase 
order, applying the VAT of the product origin country if billing address 
OR shipping address is in the same country. 1. I'm a French society that 
ordered product from Italy to sale in Denmark -> No VAT 2. I'm a French 
society that ordered product from Italy to sale in Italy -> Italian VAT 
3. I'm a French society that ordered product from France to sale in 
Italy -> French VAT Currently to resolve the taxAuth in OFBiz we use the 
shipping address only, so we can see that the point 3. isn't covered 
because the product wasn't shipped in France. Does anyone ever met the 
same problem ? I propose to improve the taxAuth resolution with also the 
origin address and the billing address. After that, I have the problem 
to say when we need to check the origin instead of the shipping. H 
... my first idea would be to check if the payToPartyId is an internal 
organisation. If yes, resolve taxAuth with the shipping else, I check if 
the origin is the same country than the shipping or billing. After 
TaxAuth the rate resolved come without change. However, I suggest to add 
a customMethodId on taxAuthRateProduct to increase the configuration of 
complex cases.


Any suggest ?

--
#jeSuisCharlie
logoNrd 
Nicolas Malin
Ingénieur d'étude. Dernier sujet : "Les vaches portant un prénom pouvent 
trouver la sortie d'un labyrinthe en cas de toxoplasmose

informat...@nereide.fr
8 rue des Déportés 37000 TOURS, 02 47 50 30 54

Apache OFBiz  | ofbiz-fr 
 | | réseau LE 

Re: Triangular VAT in Europe ?

[Heidi Dehaes - Olagos]

Hello,

There exists also something like the refutation of the VAT (la réfutation
du TVA).
If a company in Belgium purchases a product or service in the Netherlands,
the company in the Netherlands can send an invoice to the Belgium company
without VAT by mentioning "refutation of VAT" and it is the Belgium company
who will have to pay the VAT afterwards to the VAT organisation.

Eric

Olagos bvba
Heidi Dehaes
Kerkstraat 34
2570 Duffel
Belgium
Tel. : 015/31 53 04
GSM :0485/22 35 80
E-mail : info.ola...@gmail.com
http://www.olagos.eu
http://www.olagos.com
http://www.olagos.be
http://www.olagos.nl



2016-01-27 16:37 GMT+01:00 Nicolas Malin :

> Hello, In Europe with the B2B drop shipment process we have a specific
> rule to calculate the VAT. The particularity comes from the purchase order,
> applying the VAT of the product origin country if billing address OR
> shipping address is in the same country. 1. I'm a French society that
> ordered product from Italy to sale in Denmark -> No VAT 2. I'm a French
> society that ordered product from Italy to sale in Italy -> Italian VAT 3.
> I'm a French society that ordered product from France to sale in Italy ->
> French VAT Currently to resolve the taxAuth in OFBiz we use the shipping
> address only, so we can see that the point 3. isn't covered because the
> product wasn't shipped in France. Does anyone ever met the same problem ? I
> propose to improve the taxAuth resolution with also the origin address and
> the billing address. After that, I have the problem to say when we need to
> check the origin instead of the shipping. H ... my first idea would be
> to check if the payToPartyId is an internal organisation. If yes, resolve
> taxAuth with the shipping else, I check if the origin is the same country
> than the shipping or billing. After TaxAuth the rate resolved come without
> change. However, I suggest to add a customMethodId on taxAuthRateProduct to
> increase the configuration of complex cases.
>
> Any suggest ?
>
> --
> #jeSuisCharlie
> [image: logoNrd] 
> Nicolas Malin
> Ingénieur d'étude. Dernier sujet : "Les vaches portant un prénom pouvent
> trouver la sortie d'un labyrinthe en cas de toxoplasmose
> informat...@nereide.fr
> 8 rue des Déportés 37000 TOURS, 02 47 50 30 54
> Apache OFBiz  |  ofbiz-fr
>  |  | réseau LE
> 
>

[jira] [Updated] (OFBIZ-6804) Add QuoteContent entity, service and screen : draft to use layered-modal link

[Jacques Le Roux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux updated OFBIZ-6804:
---
Attachment: Image 086.png

Hi Nicolas, 

I applied the patch, loaded the data. And got this screen. This error appears 
in both case (internal or external content)

Note that the content types dropdown are all empty and there are 2 in the 
external content case.

I did not went further

> Add QuoteContent entity, service and screen : draft to use layered-modal link
> -
>
> Key: OFBIZ-6804
> URL: https://issues.apache.org/jira/browse/OFBIZ-6804
> Project: OFBiz
>  Issue Type: New Feature
>  Components: order
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Priority: Minor
>  Labels: content, layered, quote, ux
> Attachments: Image 086.png, OFBIZ-6804.patch, Sélection_027.png
>
>
> To test the layered-model on actual context, I create a new screen from 
> nereide improvement and I select to add the management of content to the 
> quote entity.
> This patch is a working draft to improve the layered-model and if it's nice 
> for some people, try to convert some standard screen on this new vision 
> So feel free to test and sharing



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-6804) Add QuoteContent entity, service and screen : draft to use layered-modal link

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15120920#comment-15120920
 ] 

Jacques Le Roux edited comment on OFBIZ-6804 at 1/28/16 7:15 AM:
-

Hi Nicolas, 

I applied the patch, loaded the data. And got this screen. !Image 086.png!

This error appears in both case (internal or external content)

Note that the content types dropdown are all empty and there are 2 in the 
external content case.

I did not went further


was (Author: jacques.le.roux):
Hi Nicolas, 

I applied the patch, loaded the data. And got this screen. This error appears 
in both case (internal or external content)

Note that the content types dropdown are all empty and there are 2 in the 
external content case.

I did not went further

> Add QuoteContent entity, service and screen : draft to use layered-modal link
> -
>
> Key: OFBIZ-6804
> URL: https://issues.apache.org/jira/browse/OFBIZ-6804
> Project: OFBiz
>  Issue Type: New Feature
>  Components: order
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Priority: Minor
>  Labels: content, layered, quote, ux
> Attachments: Image 086.png, OFBIZ-6804.patch, Sélection_027.png
>
>
> To test the layered-model on actual context, I create a new screen from 
> nereide improvement and I select to add the management of content to the 
> quote entity.
> This patch is a working draft to improve the layered-model and if it's nice 
> for some people, try to convert some standard screen on this new vision 
> So feel free to test and sharing



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6802) be able to set accounting company in the header, remove from accounting, so other components can change it too.

[Parinya Wongjina (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Parinya Wongjina updated OFBIZ-6802:

Attachment: OFBIZ-6802-fix.patch

Add new patch file for fix some javascript line to prevent error when there're 
ID with some escape character

on listVisualThemes.ftl :
document.SetUserPreferences_${visualTheme.visualThemeId}.submit() --> 
document.forms['SetUserPreferences_${visualTheme.visualThemeId}'].submit()

on listCompanies.ftl :
document.SetUserPreferences_${company.partyId}.submit()" 
-->document.forms['SetUserPreferences_${company.partyId}'].submit()"

> be able to set accounting company in the header, remove from accounting, so 
> other components can change it too.
> ---
>
> Key: OFBIZ-6802
> URL: https://issues.apache.org/jira/browse/OFBIZ-6802
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting
>Affects Versions: Trunk
> Environment: any
>Reporter: Hans Bakker
> Attachments: OFBIZ-6802-fix.patch, OFBIZ-6802.patch
>
>
> Currently it is possible to set the current accounting company in the option 
> under organization GL settings and in party preferences.
> The proposal is to remove it from accounting and set it in the theme header 
> so it will be available in all components. In order to make the system not 
> more complicated, this setting is only available when there is more than a 
> single accounting company.
> Then replace the organization GL settings in accounting  by 
> {code}
> "${organization} setup' and '${organization} accounting where ${organization} 
> {code}
> is the current selected accounting company in the header.
> The global setting of the current organization is already done in the 
> application decorator in the commonext component.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6804) Add QuoteContent entity, service and screen : draft to use layered-modal link

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15120924#comment-15120924
 ] 

Jacques Le Roux commented on OFBIZ-6804:


Here is the error:
{code}
[java] 2016-01-28 08:08:20,399 |http-bio-8443-exec-4 |ServiceDispatcher 
|E| Incoming context (in runSync : uploadOrCreateQuoteContentFile) does 
not match expected requirements
[java] org.ofbiz.service.ServiceValidationException: Le paramÞtre requis 
suivant manque : [uploadOrCreateQuoteContentFile.quoteContentTypeId]
{code}

> Add QuoteContent entity, service and screen : draft to use layered-modal link
> -
>
> Key: OFBIZ-6804
> URL: https://issues.apache.org/jira/browse/OFBIZ-6804
> Project: OFBiz
>  Issue Type: New Feature
>  Components: order
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Priority: Minor
>  Labels: content, layered, quote, ux
> Attachments: Image 086.png, OFBIZ-6804.patch, Sélection_027.png
>
>
> To test the layered-model on actual context, I create a new screen from 
> nereide improvement and I select to add the management of content to the 
> quote entity.
> This patch is a working draft to improve the layered-model and if it's nice 
> for some people, try to convert some standard screen on this new vision 
> So feel free to test and sharing



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6804) Add QuoteContent entity, service and screen : draft to use layered-modal link

[Nicolas Malin (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15120956#comment-15120956
 ] 

Nicolas Malin commented on OFBIZ-6804:
--

oO strange, I did a quick check and the entity, data and dropdow are correct on 
this patch. If I unknow you I would response just run ant load-seed but the 
doubt inside me so, I will check more ! :)

> Add QuoteContent entity, service and screen : draft to use layered-modal link
> -
>
> Key: OFBIZ-6804
> URL: https://issues.apache.org/jira/browse/OFBIZ-6804
> Project: OFBiz
>  Issue Type: New Feature
>  Components: order
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Priority: Minor
>  Labels: content, layered, quote, ux
> Attachments: Image 086.png, OFBIZ-6804.patch, Sélection_027.png
>
>
> To test the layered-model on actual context, I create a new screen from 
> nereide improvement and I select to add the management of content to the 
> quote entity.
> This patch is a working draft to improve the layered-model and if it's nice 
> for some people, try to convert some standard screen on this new vision 
> So feel free to test and sharing



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6855) Getting fresh OFBIZ database in seconds.

[Kulwant Singh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15119812#comment-15119812
 ] 

Kulwant Singh commented on OFBIZ-6855:
--

The above link refers to some nginx docker image.
Can i share my experience of ofbiz and docker on above link ?

> Getting fresh OFBIZ database in seconds.
> 
>
> Key: OFBIZ-6855
> URL: https://issues.apache.org/jira/browse/OFBIZ-6855
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Kulwant Singh
>Assignee: Jacques Le Roux
>Priority: Minor
>  Labels: docker, entities
>
> Actually when setting up new database for testing and client-demo purposes It 
> takes around 15 - 20 minutes to create entities and put seed data into these 
> entities and this repetation of task with every new build/release wastes lots 
> of time and is also very frustrating because of doing same task again and 
> again.
> This problem can be solved by can using DOCKERS with image already having 
> OFBIZ entities created in them and it will make getting fresh database as 
> simple as just starting the new process(Docker container and forwarding ports 
> for database from host machine to docker container).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6743) Error on the Split Payment button from the Quick Finalize Order screen

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15119908#comment-15119908
 ] 

Jacques Le Roux commented on OFBIZ-6743:


That's not our problem OOTB. Everyone can copy and change in custom projects. 
We want to avoid duplication and separation OOTB. I thought this was obvious 
for a long time contributor like you :p

> Error on the Split Payment button from the Quick Finalize Order screen
> --
>
> Key: OFBIZ-6743
> URL: https://issues.apache.org/jira/browse/OFBIZ-6743
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Release Branch 12.04, Release Branch 13.07, Release 
> Branch 14.12, Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
> Fix For: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch
>
>
> Error in trunk:
> ERROR rendering error page [/error/error.jsp], but here is the error text: 
> org.ofbiz.webapp.control.RequestHandlerException: No definition found for 
> view with name [checkoutpayment]
> Error in stable and old:
> org.ofbiz.webapp.control.RequestHandlerException: No definition found for 
> view with name [checkoutpayment]
> This is the same kind of error you got with OFBIZ-6741 before it was fixed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6855) Getting fresh OFBIZ database in seconds.

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15119922#comment-15119922
 ] 

Jacques Le Roux commented on OFBIZ-6855:


Please (re?)-read my previous comment:
{quote}
Please create a Wiki page under 
https://cwiki.apache.org/confluence/display/OFBIZ/Home we will then discuss on 
the dev ML where to put it exactly. For that you need 1st to follow explanation 
at https://cwiki.apache.org/confluence/display/OFBIZ/No+Spam

Thanks!
{quote}
In a new wiki page indeed we could share our experiences with Docker, even if 
losely related with OFBiz, why not? Of course it's better if it closely related 
to OFBIz ;)

> Getting fresh OFBIZ database in seconds.
> 
>
> Key: OFBIZ-6855
> URL: https://issues.apache.org/jira/browse/OFBIZ-6855
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Kulwant Singh
>Assignee: Jacques Le Roux
>Priority: Minor
>  Labels: docker, entities
>
> Actually when setting up new database for testing and client-demo purposes It 
> takes around 15 - 20 minutes to create entities and put seed data into these 
> entities and this repetation of task with every new build/release wastes lots 
> of time and is also very frustrating because of doing same task again and 
> again.
> This problem can be solved by can using DOCKERS with image already having 
> OFBIZ entities created in them and it will make getting fresh database as 
> simple as just starting the new process(Docker container and forwarding ports 
> for database from host machine to docker container).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6858) Solr logging doesn't work

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15119914#comment-15119914
 ] 

Jacques Le Roux commented on OFBIZ-6858:


Nope, you did not read me right, I got there using the url you gave :p

> Solr logging doesn't work
> -
>
> Key: OFBIZ-6858
> URL: https://issues.apache.org/jira/browse/OFBIZ-6858
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/solr
>Affects Versions: Trunk, Release Branch 15.12
>Reporter: Pierre Smits
>
> When looking at the logging screen in demo-trunk 
> (https://demo-trunk-ofbiz.apache.org/solr/#/~logging) no logging results are 
> shown. Nor does https://demo-trunk-ofbiz.apache.org/solr/#/~logging/level 
> provide any insights.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-6858) Solr logging doesn't work

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15119914#comment-15119914
 ] 

Jacques Le Roux edited comment on OFBIZ-6858 at 1/27/16 6:26 PM:
-

Nope, you did not read me right, I got there using the 1st url you gave :p

The 2nd works as well for me


was (Author: jacques.le.roux):
Nope, you did not read me right, I got there using the url you gave :p

> Solr logging doesn't work
> -
>
> Key: OFBIZ-6858
> URL: https://issues.apache.org/jira/browse/OFBIZ-6858
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/solr
>Affects Versions: Trunk, Release Branch 15.12
>Reporter: Pierre Smits
>
> When looking at the logging screen in demo-trunk 
> (https://demo-trunk-ofbiz.apache.org/solr/#/~logging) no logging results are 
> shown. Nor does https://demo-trunk-ofbiz.apache.org/solr/#/~logging/level 
> provide any insights.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6859) searchContent generates an error

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15119942#comment-15119942
 ] 

Jacques Le Roux commented on OFBIZ-6859:


Same errors locally BTW

> searchContent generates an error
> 
>
> Key: OFBIZ-6859
> URL: https://issues.apache.org/jira/browse/OFBIZ-6859
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/ecommerce
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, 
> Release Branch 15.12
>Reporter: Pierre Smits
>  Labels: lucene, search
>
> Executing a content search in the ecommerce component generates an error.
> See: https://demo-stable-ofbiz.apache.org/ecommerce/control/searchContent 
> (r13.x)
> See: https://demo-trunk-ofbiz.apache.org/ecommerce/control/searchContent 
> (trunk)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6858) Solr logging doesn't work

[Pierre Smits (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15119996#comment-15119996
 ] 

Pierre Smits commented on OFBIZ-6858:
-

Can you upload a screenshot so I, and others, can get an impression?

> Solr logging doesn't work
> -
>
> Key: OFBIZ-6858
> URL: https://issues.apache.org/jira/browse/OFBIZ-6858
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/solr
>Affects Versions: Trunk, Release Branch 15.12
>Reporter: Pierre Smits
>
> When looking at the logging screen in demo-trunk 
> (https://demo-trunk-ofbiz.apache.org/solr/#/~logging) no logging results are 
> shown. Nor does https://demo-trunk-ofbiz.apache.org/solr/#/~logging/level 
> provide any insights.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6859) searchContent generates an error

[Pierre Smits (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15120002#comment-15120002
 ] 

Pierre Smits commented on OFBIZ-6859:
-

I typed in 'searchContent' after  
https://demo-trunk-ofbiz.apache.org/ecommerce/control

> searchContent generates an error
> 
>
> Key: OFBIZ-6859
> URL: https://issues.apache.org/jira/browse/OFBIZ-6859
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/ecommerce
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, 
> Release Branch 15.12
>Reporter: Pierre Smits
>  Labels: lucene, search
>
> Executing a content search in the ecommerce component generates an error.
> See: https://demo-stable-ofbiz.apache.org/ecommerce/control/searchContent 
> (r13.x)
> See: https://demo-trunk-ofbiz.apache.org/ecommerce/control/searchContent 
> (trunk)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jira] [Closed] (OFBIZ-6760) Move all entity definitions from the applications components into a separate one

[Jacques Le Roux]

I have to think more about it, but my 1st feeling is the same

Jacques

Le 27/01/2016 05:59, Deepak Dixit a écrit :

Sounds good to me.

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Mon, Jan 25, 2016 at 6:52 PM, Nicolas Malin 
wrote:


Hi,

Now as the data-model is present and the task closed, can we continue to
move all crud on the same component and keep only service with business
oriented logic on the dedicate component ?

I think about service like
createProductCategory/updateProductCategory/deleteProductCategory and not
storeOrder ;)

Nicolas



Le 16/01/2016 12:49, Deepak Dixit (JIRA) a écrit :


   [
https://issues.apache.org/jira/browse/OFBIZ-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Deepak Dixit closed OFBIZ-6760.
---

Move all entity definitions from the applications components into a

separate one



  Key: OFBIZ-6760
  URL: https://issues.apache.org/jira/browse/OFBIZ-6760
  Project: OFBiz
   Issue Type: Improvement
   Components: ALL APPLICATIONS
 Affects Versions: Trunk
 Reporter: Jacques Le Roux
 Assignee: Jacopo Cappellato
  Fix For: Upcoming Branch


See this thread for a previous discussion:
http://markmail.org/message/sfdm22wfy3fulpyb



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6861) AdminSearch generates an error

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15119940#comment-15119940
 ] 

Jacques Le Roux commented on OFBIZ-6861:


BTW, how did you get there from an UI POV (steps please)

> AdminSearch generates an error
> --
>
> Key: OFBIZ-6861
> URL: https://issues.apache.org/jira/browse/OFBIZ-6861
> Project: OFBiz
>  Issue Type: Bug
>  Components: content
>Affects Versions: Trunk, Release Branch 15.12
>Reporter: Pierre Smits
>  Labels: lucene, search
>
> In https://demo-trunk-ofbiz.apache.org/content/control/AdminSearch following 
> error is shown:
> {code}
> org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
> [component://lucene/widget/LuceneScreens.xml#AdminSearch]: 
> java.lang.IllegalArgumentException: Error running script at location 
> [component://lucene/webapp/content/WEB-INF/actions/Search.groovy]: 
> groovy.lang.MissingMethodException: No signature of method: static 
> org.apache.lucene.store.FSDirectory.open() is applicable for argument types: 
> (java.io.File) values: [runtime/indexes/content] Possible solutions: 
> open(java.nio.file.Path), open(java.nio.file.Path, 
> org.apache.lucene.store.LockFactory), grep(), grep(java.lang.Object), 
> use([Ljava.lang.Object;), wait() (Error running script at location 
> [component://lucene/webapp/content/WEB-INF/actions/Search.groovy]: 
> groovy.lang.MissingMethodException: No signature of method: static 
> org.apache.lucene.store.FSDirectory.open() is applicable for argument types: 
> (java.io.File) values: [runtime/indexes/content] Possible solutions: 
> open(java.nio.file.Path), open(java.nio.file.Path, 
> org.apache.lucene.store.LockFactory), grep(), grep(java.lang.Object), 
> use([Ljava.lang.Object;), wait())
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6861) AdminSearch generates an error

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15119937#comment-15119937
 ] 

Jacques Le Roux commented on OFBIZ-6861:


I can reproduce this error on trunk and locally

> AdminSearch generates an error
> --
>
> Key: OFBIZ-6861
> URL: https://issues.apache.org/jira/browse/OFBIZ-6861
> Project: OFBiz
>  Issue Type: Bug
>  Components: content
>Affects Versions: Trunk, Release Branch 15.12
>Reporter: Pierre Smits
>  Labels: lucene, search
>
> In https://demo-trunk-ofbiz.apache.org/content/control/AdminSearch following 
> error is shown:
> {code}
> org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
> [component://lucene/widget/LuceneScreens.xml#AdminSearch]: 
> java.lang.IllegalArgumentException: Error running script at location 
> [component://lucene/webapp/content/WEB-INF/actions/Search.groovy]: 
> groovy.lang.MissingMethodException: No signature of method: static 
> org.apache.lucene.store.FSDirectory.open() is applicable for argument types: 
> (java.io.File) values: [runtime/indexes/content] Possible solutions: 
> open(java.nio.file.Path), open(java.nio.file.Path, 
> org.apache.lucene.store.LockFactory), grep(), grep(java.lang.Object), 
> use([Ljava.lang.Object;), wait() (Error running script at location 
> [component://lucene/webapp/content/WEB-INF/actions/Search.groovy]: 
> groovy.lang.MissingMethodException: No signature of method: static 
> org.apache.lucene.store.FSDirectory.open() is applicable for argument types: 
> (java.io.File) values: [runtime/indexes/content] Possible solutions: 
> open(java.nio.file.Path), open(java.nio.file.Path, 
> org.apache.lucene.store.LockFactory), grep(), grep(java.lang.Object), 
> use([Ljava.lang.Object;), wait())
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6859) searchContent generates an error

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15119941#comment-15119941
 ] 

Jacques Le Roux commented on OFBIZ-6859:


I confirm both on demo server

Could you please give us the steps you used on UI to get to this URL, thanks!

> searchContent generates an error
> 
>
> Key: OFBIZ-6859
> URL: https://issues.apache.org/jira/browse/OFBIZ-6859
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/ecommerce
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, 
> Release Branch 15.12
>Reporter: Pierre Smits
>  Labels: lucene, search
>
> Executing a content search in the ecommerce component generates an error.
> See: https://demo-stable-ofbiz.apache.org/ecommerce/control/searchContent 
> (r13.x)
> See: https://demo-trunk-ofbiz.apache.org/ecommerce/control/searchContent 
> (trunk)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6858) Solr logging doesn't work

[Pierre Smits (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15120145#comment-15120145
 ] 

Pierre Smits commented on OFBIZ-6858:
-

Ahh. Now I see where the confusion is coming from. In the menu on the left 
you'll see 'Logging'. Please click that and watch the log results appear. That 
is what I am talking about.

> Solr logging doesn't work
> -
>
> Key: OFBIZ-6858
> URL: https://issues.apache.org/jira/browse/OFBIZ-6858
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/solr
>Affects Versions: Trunk, Release Branch 15.12
>Reporter: Pierre Smits
> Attachments: Image2.png
>
>
> When looking at the logging screen in demo-trunk 
> (https://demo-trunk-ofbiz.apache.org/solr/#/~logging) no logging results are 
> shown. Nor does https://demo-trunk-ofbiz.apache.org/solr/#/~logging/level 
> provide any insights.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6858) Solr logging doesn't work

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15120182#comment-15120182
 ] 

Jacques Le Roux commented on OFBIZ-6858:


OK, I got it, same locally

> Solr logging doesn't work
> -
>
> Key: OFBIZ-6858
> URL: https://issues.apache.org/jira/browse/OFBIZ-6858
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/solr
>Affects Versions: Trunk, Release Branch 15.12
>Reporter: Pierre Smits
> Attachments: Image2.png
>
>
> When looking at the logging screen in demo-trunk 
> (https://demo-trunk-ofbiz.apache.org/solr/#/~logging) no logging results are 
> shown. Nor does https://demo-trunk-ofbiz.apache.org/solr/#/~logging/level 
> provide any insights.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6858) Solr logging doesn't work

[Jacques Le Roux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux updated OFBIZ-6858:
---
Attachment: Image2.png

> Solr logging doesn't work
> -
>
> Key: OFBIZ-6858
> URL: https://issues.apache.org/jira/browse/OFBIZ-6858
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/solr
>Affects Versions: Trunk, Release Branch 15.12
>Reporter: Pierre Smits
> Attachments: Image2.png
>
>
> When looking at the logging screen in demo-trunk 
> (https://demo-trunk-ofbiz.apache.org/solr/#/~logging) no logging results are 
> shown. Nor does https://demo-trunk-ofbiz.apache.org/solr/#/~logging/level 
> provide any insights.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-6858) Solr logging doesn't work

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15120134#comment-15120134
 ] 

Jacques Le Roux edited comment on OFBIZ-6858 at 1/27/16 8:47 PM:
-

So you don't believe me? :/

!Image2.png!

Note "-javaagent:/home/ofbizDemo/trunk/contrast-rO0.jar" which is quite a 
proof, isn'it!

Can someone else please confirm it works for her/him also ?


was (Author: jacques.le.roux):
So you don't believe me? :/

!image2.png!

Note "-javaagent:/home/ofbizDemo/trunk/contrast-rO0.jar" which is quite a 
proof, isn'it!

Can someone else please confirm it works for her/him also ?

> Solr logging doesn't work
> -
>
> Key: OFBIZ-6858
> URL: https://issues.apache.org/jira/browse/OFBIZ-6858
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/solr
>Affects Versions: Trunk, Release Branch 15.12
>Reporter: Pierre Smits
> Attachments: Image2.png
>
>
> When looking at the logging screen in demo-trunk 
> (https://demo-trunk-ofbiz.apache.org/solr/#/~logging) no logging results are 
> shown. Nor does https://demo-trunk-ofbiz.apache.org/solr/#/~logging/level 
> provide any insights.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6858) Solr logging doesn't work

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15120134#comment-15120134
 ] 

Jacques Le Roux commented on OFBIZ-6858:


So you don't believe me? :/

!image2.png!

Note "-javaagent:/home/ofbizDemo/trunk/contrast-rO0.jar" which is quite a 
proof, isn'it!

Can someone else please confirm it works for her/him also ?

> Solr logging doesn't work
> -
>
> Key: OFBIZ-6858
> URL: https://issues.apache.org/jira/browse/OFBIZ-6858
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/solr
>Affects Versions: Trunk, Release Branch 15.12
>Reporter: Pierre Smits
> Attachments: Image2.png
>
>
> When looking at the logging screen in demo-trunk 
> (https://demo-trunk-ofbiz.apache.org/solr/#/~logging) no logging results are 
> shown. Nor does https://demo-trunk-ofbiz.apache.org/solr/#/~logging/level 
> provide any insights.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-6592) Add wiki documentation regarding the component

[Jacques Le Roux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux closed OFBIZ-6592.
--
   Resolution: Done
Fix Version/s: Upcoming Branch

Thanks Pierre,

Your patch is in trunk at r1727001

> Add wiki documentation regarding the component
> --
>
> Key: OFBIZ-6592
> URL: https://issues.apache.org/jira/browse/OFBIZ-6592
> Project: OFBiz
>  Issue Type: Improvement
>  Components: specialpurpose/solr
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-6592-Solr.patch
>
>
> Have documentation in the wiki to describe the component etc



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-6611) Incorporate the readme for the SOLR component

[Pierre Smits (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits closed OFBIZ-6611.
---
   Resolution: Fixed
Fix Version/s: Upcoming Branch

Done via OFBIZ-6592

> Incorporate the readme for the SOLR component
> -
>
> Key: OFBIZ-6611
> URL: https://issues.apache.org/jira/browse/OFBIZ-6611
> Project: OFBiz
>  Issue Type: Improvement
>  Components: specialpurpose/solr
>Affects Versions: Trunk
> Environment: A readme should be the first starting point of each 
> component for developers have references to the placeholder in the wiki, in 
> jira and in svn/viewvc
>Reporter: Pierre Smits
>Assignee: Pierre Smits
> Fix For: Upcoming Branch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-6611) Incorporate the readme for the SOLR component

[Pierre Smits (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits reassigned OFBIZ-6611:
---

Assignee: Pierre Smits

> Incorporate the readme for the SOLR component
> -
>
> Key: OFBIZ-6611
> URL: https://issues.apache.org/jira/browse/OFBIZ-6611
> Project: OFBiz
>  Issue Type: Improvement
>  Components: specialpurpose/solr
>Affects Versions: Trunk
> Environment: A readme should be the first starting point of each 
> component for developers have references to the placeholder in the wiki, in 
> jira and in svn/viewvc
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6858) Solr logging doesn't work

[Pierre Smits (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated OFBIZ-6858:

Description: When looking at the logging screen in demo-trunk 
(https://demo-trunk-ofbiz.apache.org/solr/#/~logging) no logging results are 
shown.

> Solr logging doesn't work
> -
>
> Key: OFBIZ-6858
> URL: https://issues.apache.org/jira/browse/OFBIZ-6858
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/solr
>Affects Versions: Trunk, Release Branch 15.12
>Reporter: Pierre Smits
>
> When looking at the logging screen in demo-trunk 
> (https://demo-trunk-ofbiz.apache.org/solr/#/~logging) no logging results are 
> shown.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-6592) Add wiki documentation regarding the component

[Pierre Smits (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits reassigned OFBIZ-6592:
---

Assignee: Pierre Smits

> Add wiki documentation regarding the component
> --
>
> Key: OFBIZ-6592
> URL: https://issues.apache.org/jira/browse/OFBIZ-6592
> Project: OFBiz
>  Issue Type: Improvement
>  Components: specialpurpose/solr
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
> Attachments: OFBIZ-6592-Solr.patch
>
>
> Have documentation in the wiki to describe the component etc



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6592) Add wiki documentation regarding the component

[Pierre Smits (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated OFBIZ-6592:

Attachment: OFBIZ-6592-Solr.patch

This patch addresses the issue.

> Add wiki documentation regarding the component
> --
>
> Key: OFBIZ-6592
> URL: https://issues.apache.org/jira/browse/OFBIZ-6592
> Project: OFBiz
>  Issue Type: Improvement
>  Components: specialpurpose/solr
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
> Attachments: OFBIZ-6592-Solr.patch
>
>
> Have documentation in the wiki to describe the component etc



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6592) Add wiki documentation regarding the component

[Pierre Smits (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15119118#comment-15119118
 ] 

Pierre Smits commented on OFBIZ-6592:
-

The patch addresses OFBIZ-6611. 

The wiki page has been made available via 
https://cwiki.apache.org/confluence/display/OFBIZ/Search+Integration

> Add wiki documentation regarding the component
> --
>
> Key: OFBIZ-6592
> URL: https://issues.apache.org/jira/browse/OFBIZ-6592
> Project: OFBiz
>  Issue Type: Improvement
>  Components: specialpurpose/solr
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-6592-Solr.patch
>
>
> Have documentation in the wiki to describe the component etc



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-6858) Solr logging doesn't work

[Pierre Smits (JIRA)]

Pierre Smits created OFBIZ-6858:
---

 Summary: Solr logging doesn't work
 Key: OFBIZ-6858
 URL: https://issues.apache.org/jira/browse/OFBIZ-6858
 Project: OFBiz
  Issue Type: Bug
  Components: specialpurpose/solr
Affects Versions: Release Branch 15.12, Trunk
Reporter: Pierre Smits






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6802) be able to set accounting company in the header, remove from accounting, so other components can change it too.

[Parinya Wongjina (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Parinya Wongjina updated OFBIZ-6802:

Attachment: (was: OFBIZ-6802.patch)

> be able to set accounting company in the header, remove from accounting, so 
> other components can change it too.
> ---
>
> Key: OFBIZ-6802
> URL: https://issues.apache.org/jira/browse/OFBIZ-6802
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting
>Affects Versions: Trunk
> Environment: any
>Reporter: Hans Bakker
> Attachments: OFBIZ-6802.patch
>
>
> Currently it is possible to set the current accounting company in the option 
> under organization GL settings and in party preferences.
> The proposal is to remove it from accounting and set it in the theme header 
> so it will be available in all components. In order to make the system not 
> more complicated, this setting is only available when there is more than a 
> single accounting company.
> Then replace the organization GL settings in accounting  by 
> {code}
> "${organization} setup' and '${organization} accounting where ${organization} 
> {code}
> is the current selected accounting company in the header.
> The global setting of the current organization is already done in the 
> application decorator in the commonext component.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6802) be able to set accounting company in the header, remove from accounting, so other components can change it too.

[Parinya Wongjina (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Parinya Wongjina updated OFBIZ-6802:

Attachment: OFBIZ-6802.patch

> be able to set accounting company in the header, remove from accounting, so 
> other components can change it too.
> ---
>
> Key: OFBIZ-6802
> URL: https://issues.apache.org/jira/browse/OFBIZ-6802
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting
>Affects Versions: Trunk
> Environment: any
>Reporter: Hans Bakker
> Attachments: OFBIZ-6802.patch
>
>
> Currently it is possible to set the current accounting company in the option 
> under organization GL settings and in party preferences.
> The proposal is to remove it from accounting and set it in the theme header 
> so it will be available in all components. In order to make the system not 
> more complicated, this setting is only available when there is more than a 
> single accounting company.
> Then replace the organization GL settings in accounting  by 
> {code}
> "${organization} setup' and '${organization} accounting where ${organization} 
> {code}
> is the current selected accounting company in the header.
> The global setting of the current organization is already done in the 
> application decorator in the commonext component.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-6861) AdminSearch generates an error

[Pierre Smits (JIRA)]

Pierre Smits created OFBIZ-6861:
---

 Summary: AdminSearch generates an error
 Key: OFBIZ-6861
 URL: https://issues.apache.org/jira/browse/OFBIZ-6861
 Project: OFBiz
  Issue Type: Bug
  Components: content
Affects Versions: Release Branch 15.12, Trunk
Reporter: Pierre Smits


In https://demo-trunk-ofbiz.apache.org/content/control/AdminSearch following 
error is shown:
{code}
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://lucene/widget/LuceneScreens.xml#AdminSearch]: 
java.lang.IllegalArgumentException: Error running script at location 
[component://lucene/webapp/content/WEB-INF/actions/Search.groovy]: 
groovy.lang.MissingMethodException: No signature of method: static 
org.apache.lucene.store.FSDirectory.open() is applicable for argument types: 
(java.io.File) values: [runtime/indexes/content] Possible solutions: 
open(java.nio.file.Path), open(java.nio.file.Path, 
org.apache.lucene.store.LockFactory), grep(), grep(java.lang.Object), 
use([Ljava.lang.Object;), wait() (Error running script at location 
[component://lucene/webapp/content/WEB-INF/actions/Search.groovy]: 
groovy.lang.MissingMethodException: No signature of method: static 
org.apache.lucene.store.FSDirectory.open() is applicable for argument types: 
(java.io.File) values: [runtime/indexes/content] Possible solutions: 
open(java.nio.file.Path), open(java.nio.file.Path, 
org.apache.lucene.store.LockFactory), grep(), grep(java.lang.Object), 
use([Ljava.lang.Object;), wait())
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6359) Improves dialog boxes generated by layered-modal link parameter

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15118867#comment-15118867
 ] 

Jacques Le Roux commented on OFBIZ-6359:


Thanks!

> Improves dialog boxes generated by layered-modal link parameter
> ---
>
> Key: OFBIZ-6359
> URL: https://issues.apache.org/jira/browse/OFBIZ-6359
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: framework
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
>
> There are few points I'd like to improve:
> * Add closeOnEscape (trivial)
> * Allow to pass parameters as hidden value
> * Consider also GET parameters put in the link target



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-6859) searchContent generates an error

[Pierre Smits (JIRA)]

Pierre Smits created OFBIZ-6859:
---

 Summary: searchContent generates an error
 Key: OFBIZ-6859
 URL: https://issues.apache.org/jira/browse/OFBIZ-6859
 Project: OFBiz
  Issue Type: Bug
  Components: specialpurpose/ecommerce
Affects Versions: Release Branch 15.12, Trunk, Release Branch 14.12, 
Release Branch 13.07
Reporter: Pierre Smits


Executing a content search in the ecommerce component generates an error.

See: https://demo-stable-ofbiz.apache.org/ecommerce/control/searchContent 
(r13.x)
See: https://demo-trunk-ofbiz.apache.org/ecommerce/control/searchContent (trunk)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-6860) ProductSearch generates an errorr

[Pierre Smits (JIRA)]

Pierre Smits created OFBIZ-6860:
---

 Summary: ProductSearch generates an errorr
 Key: OFBIZ-6860
 URL: https://issues.apache.org/jira/browse/OFBIZ-6860
 Project: OFBiz
  Issue Type: Bug
  Components: content
Affects Versions: Release Branch 15.12, Trunk
Reporter: Pierre Smits


When executing a product search in the content application an error is thrown.

In demo-trunk: https://demo-trunk-ofbiz.apache.org/content/control/ProductSearch
the following error is thrown:
{code}
org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
[component://lucene/widget/LuceneScreens.xml#ProductSearch]: 
java.lang.IllegalArgumentException: Error running script at location 
[component://lucene/webapp/content/WEB-INF/actions/SearchProducts.groovy]: 
groovy.lang.MissingMethodException: No signature of method: static 
org.apache.lucene.store.FSDirectory.open() is applicable for argument types: 
(java.io.File) values: [runtime/indexes/products] Possible solutions: 
open(java.nio.file.Path), open(java.nio.file.Path, 
org.apache.lucene.store.LockFactory), grep(), grep(java.lang.Object), 
use([Ljava.lang.Object;), wait() (Error running script at location 
[component://lucene/webapp/content/WEB-INF/actions/SearchProducts.groovy]: 
groovy.lang.MissingMethodException: No signature of method: static 
org.apache.lucene.store.FSDirectory.open() is applicable for argument types: 
(java.io.File) values: [runtime/indexes/products] Possible solutions: 
open(java.nio.file.Path), open(java.nio.file.Path, 
org.apache.lucene.store.LockFactory), grep(), grep(java.lang.Object), 
use([Ljava.lang.Object;), wait())
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6860) ProductSearch generates an errorr

[Pierre Smits (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated OFBIZ-6860:

Labels: lucene search  (was: )

> ProductSearch generates an errorr
> -
>
> Key: OFBIZ-6860
> URL: https://issues.apache.org/jira/browse/OFBIZ-6860
> Project: OFBiz
>  Issue Type: Bug
>  Components: content
>Affects Versions: Trunk, Release Branch 15.12
>Reporter: Pierre Smits
>  Labels: lucene, search
>
> When executing a product search in the content application an error is thrown.
> In demo-trunk: 
> https://demo-trunk-ofbiz.apache.org/content/control/ProductSearch
> the following error is thrown:
> {code}
> org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen 
> [component://lucene/widget/LuceneScreens.xml#ProductSearch]: 
> java.lang.IllegalArgumentException: Error running script at location 
> [component://lucene/webapp/content/WEB-INF/actions/SearchProducts.groovy]: 
> groovy.lang.MissingMethodException: No signature of method: static 
> org.apache.lucene.store.FSDirectory.open() is applicable for argument types: 
> (java.io.File) values: [runtime/indexes/products] Possible solutions: 
> open(java.nio.file.Path), open(java.nio.file.Path, 
> org.apache.lucene.store.LockFactory), grep(), grep(java.lang.Object), 
> use([Ljava.lang.Object;), wait() (Error running script at location 
> [component://lucene/webapp/content/WEB-INF/actions/SearchProducts.groovy]: 
> groovy.lang.MissingMethodException: No signature of method: static 
> org.apache.lucene.store.FSDirectory.open() is applicable for argument types: 
> (java.io.File) values: [runtime/indexes/products] Possible solutions: 
> open(java.nio.file.Path), open(java.nio.file.Path, 
> org.apache.lucene.store.LockFactory), grep(), grep(java.lang.Object), 
> use([Ljava.lang.Object;), wait())
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6859) searchContent generates an error

[Pierre Smits (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated OFBIZ-6859:

Labels: lucene search  (was: search)

> searchContent generates an error
> 
>
> Key: OFBIZ-6859
> URL: https://issues.apache.org/jira/browse/OFBIZ-6859
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/ecommerce
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, 
> Release Branch 15.12
>Reporter: Pierre Smits
>  Labels: lucene, search
>
> Executing a content search in the ecommerce component generates an error.
> See: https://demo-stable-ofbiz.apache.org/ecommerce/control/searchContent 
> (r13.x)
> See: https://demo-trunk-ofbiz.apache.org/ecommerce/control/searchContent 
> (trunk)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6858) Solr logging doesn't work

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15119161#comment-15119161
 ] 

Jacques Le Roux commented on OFBIZ-6858:


Are you sure? it works here. I get to 
https://demo-trunk-ofbiz.apache.org/solr/#/ after the login screen

> Solr logging doesn't work
> -
>
> Key: OFBIZ-6858
> URL: https://issues.apache.org/jira/browse/OFBIZ-6858
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/solr
>Affects Versions: Trunk, Release Branch 15.12
>Reporter: Pierre Smits
>
> When looking at the logging screen in demo-trunk 
> (https://demo-trunk-ofbiz.apache.org/solr/#/~logging) no logging results are 
> shown.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6858) Solr logging doesn't work

[Pierre Smits (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15119184#comment-15119184
 ] 

Pierre Smits commented on OFBIZ-6858:
-

You are using a different url than I provided.

> Solr logging doesn't work
> -
>
> Key: OFBIZ-6858
> URL: https://issues.apache.org/jira/browse/OFBIZ-6858
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/solr
>Affects Versions: Trunk, Release Branch 15.12
>Reporter: Pierre Smits
>
> When looking at the logging screen in demo-trunk 
> (https://demo-trunk-ofbiz.apache.org/solr/#/~logging) no logging results are 
> shown.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6858) Solr logging doesn't work

[Pierre Smits (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated OFBIZ-6858:

Description: When looking at the logging screen in demo-trunk 
(https://demo-trunk-ofbiz.apache.org/solr/#/~logging) no logging results are 
shown. Nor does https://demo-trunk-ofbiz.apache.org/solr/#/~logging/level 
provide any insights.  (was: When looking at the logging screen in demo-trunk 
(https://demo-trunk-ofbiz.apache.org/solr/#/~logging) no logging results are 
shown.)

> Solr logging doesn't work
> -
>
> Key: OFBIZ-6858
> URL: https://issues.apache.org/jira/browse/OFBIZ-6858
> Project: OFBiz
>  Issue Type: Bug
>  Components: specialpurpose/solr
>Affects Versions: Trunk, Release Branch 15.12
>Reporter: Pierre Smits
>
> When looking at the logging screen in demo-trunk 
> (https://demo-trunk-ofbiz.apache.org/solr/#/~logging) no logging results are 
> shown. Nor does https://demo-trunk-ofbiz.apache.org/solr/#/~logging/level 
> provide any insights.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)