Re: Multi-tenant ecommerce

Hi Gareth, IMO, I would not like to see that a (potential) customer would be required to enter the tenant ID, as this would surely deminish user satisfaction. And on the other hand passing the tenant ID in a url would also not be preferable regarding security issues. I can imagine that the

Re: Multi-tenant ecommerce

Hi Gareth, IMO, I would not like to see that a (potential) customer would be required to enter the tenant ID, as this would surely deminish user satisfaction. And on the other hand passing the tenant ID in a url would also not be preferable regarding security issues. I can imagine that the

[jira] [Closed] (OFBIZ-4463) Reference to datetimepicker is wrong in CommonScreens.xml

[ https://issues.apache.org/jira/browse/OFBIZ-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-4463. -- Resolution: Fixed Fix Version/s: SVN trunk Release Branch 11.04

RE: Multi-tenant ecommerce

Pierre, I'm getting stuck into the code to get a better understanding of how it all hangs together. In the market we're addressing there is a degree of paranoia about competitors being able to see one's prices, so it is not unusual to hide the entire web store behind a login and use a

[jira] [Created] (OFBIZ-4466) Chart of accounts isn't sorted properly

Chart of accounts isn't sorted properly --- Key: OFBIZ-4466 URL: https://issues.apache.org/jira/browse/OFBIZ-4466 Project: OFBiz Issue Type: Sub-task Components: accounting Affects Versions:

[jira] [Updated] (OFBIZ-4466) Chart of accounts isn't sorted properly

[ https://issues.apache.org/jira/browse/OFBIZ-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-4466: Attachment: ofbiz-4466-glaccount-sorting.patch This patch provides the fix Chart

Re: Multi-tenant ecommerce

https://issues.apache.org/jira/browse/OFBIZ-3579 if you add something. tenant was designed to get ID from login. so for ecommerce you need to have separated webapps like eccomerclone, and put the tenantID in the web.xml. the problems I believe is how do you select which webapplication is selected

fieldlookup.gif background transparent

Hi, At r1181878, I have made the fieldlookup.gif background transparent. This should have been done far earlier :/ If nobody disagree, I will backport to releases in few days... Jacques

Re: fieldlookup.gif background transparent

fieldlookup.gif isn't deprecated ? Le 11/10/2011 18:32, Jacques Le Roux a écrit : Hi, At r1181878, I have made the fieldlookup.gif background transparent. This should have been done far earlier :/ If nobody disagree, I will backport to releases in few days... Jacques -- Nicolas MALIN

Re: fieldlookup.gif background transparent

Not at all, try the new Flat Grey theme. It's also used in (at least) 3 places by other themes Jacques From: Nicolas Malin malin.nico...@librenberry.net fieldlookup.gif isn't deprecated ? Le 11/10/2011 18:32, Jacques Le Roux a écrit : Hi, At r1181878, I have made the fieldlookup.gif

[jira] [Created] (OFBIZ-4467) Improve auto-fields-entity (select include field and auto drop-down)

Improve auto-fields-entity (select include field and auto drop-down) Key: OFBIZ-4467 URL: https://issues.apache.org/jira/browse/OFBIZ-4467 Project: OFBiz Issue Type:

[jira] [Updated] (OFBIZ-4467) Improve auto-fields-entity (select include field and auto drop-down)

[ https://issues.apache.org/jira/browse/OFBIZ-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Malin updated OFBIZ-4467: - Attachment: OFBIZ-4467.png OFBIZ-4467.patch Improve auto-fields-entity

[jira] [Created] (OFBIZ-4468) After login it shows error 'Product not found!'

After login it shows error 'Product not found!' --- Key: OFBIZ-4468 URL: https://issues.apache.org/jira/browse/OFBIZ-4468 Project: OFBiz Issue Type: Bug Components: framework,

Should loadSalesInvoiceFact be run on return instead of commit?

Hi all, Last year the SECA that runs loadSalesInvoiceFact was changed to run async. See https://fisheye6.atlassian.com/browse/ofbiz/trunk/applications/accounting/servicedef/secas_olap.xml?hb=true#to29 . That makes sense to me, but it's run on commit, (that is, prior to the commit) and I'm

Re: Should loadSalesInvoiceFact be run on return instead of commit?

+1 Regards Scott On 12/10/2011, at 12:09 PM, Paul Foxworthy wrote: Hi all, Last year the SECA that runs loadSalesInvoiceFact was changed to run async. See https://fisheye6.atlassian.com/browse/ofbiz/trunk/applications/accounting/servicedef/secas_olap.xml?hb=true#to29 . That makes

[jira] [Created] (OFBIZ-4469) Load product dimension when and only when the product is created successfully

Load product dimension when and only when the product is created successfully - Key: OFBIZ-4469 URL: https://issues.apache.org/jira/browse/OFBIZ-4469 Project: OFBiz

[jira] [Created] (OFBIZ-4470) Append order item overrides the exist one if the last order item is canceled

Append order item overrides the exist one if the last order item is canceled -- Key: OFBIZ-4470 URL: https://issues.apache.org/jira/browse/OFBIZ-4470 Project: OFBiz

[jira] [Updated] (OFBIZ-4470) Append order item overrides the exist one if the last order item is canceled

[ https://issues.apache.org/jira/browse/OFBIZ-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leon updated OFBIZ-4470: Attachment: OFBIZ-4470.patch set the correct nextItemSeq of shopping cart. It the next item sequence id, not the