[
https://issues.apache.org/jira/browse/OFBIZ-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Gray reassigned OFBIZ-694:
Assignee: Scott Gray
> Select Standard by default instead of distinguishing
> --
[
https://issues.apache.org/jira/browse/OFBIZ-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Gray closed OFBIZ-702.
Resolution: Fixed
Hi Andrew
I checked the ASF svn history and no changes have been made that would have
ca
[
https://issues.apache.org/jira/browse/OFBIZ-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471595
]
Scott Gray commented on OFBIZ-693:
--
Hi Anil
Two points on this one:
1. Wouldn't it be better to use ATP rather than
[
https://issues.apache.org/jira/browse/OFBIZ-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471593
]
Scott Gray commented on OFBIZ-309:
--
Hi Leon
Could you please confirm if this is an still an issue? There was a comm
Just a quick note on this: my personal opinion is that it is a bad
idea to use startsWith() instead of equals() for this sort of thing.
The problem is that it is more error prone in the future. Someone may
create a new type with the same prefix but a totally different
intent, and then hav
Set default warehouse for a User In the warehouse tab in Asset Maint component
--
Key: OFBIZ-706
URL: https://issues.apache.org/jira/browse/OFBIZ-706
Project: OFBiz (The Open
[
https://issues.apache.org/jira/browse/OFBIZ-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anil K Patel updated OFBIZ-705:
---
Attachment: AssetMaintNoBar.patch
Fix the No tabbar bug.
> No Tab bar is shown when New FixedAssetMai
No Tab bar is shown when New FixedAssetMaint is created in Asset Maint
component and also when TimeEntry is deleted.
Key: OFBIZ-705
URL: https://i
[
https://issues.apache.org/jira/browse/OFBIZ-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471530
]
Jacques Le Roux commented on OFBIZ-703:
---
Andrew,
This documentation came from http://ofbiz.apache.org/docs/mini
[
https://issues.apache.org/jira/browse/OFBIZ-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reassigned OFBIZ-703:
-
Assignee: Jacques Le Roux
> calcop attribute definition conflict
> ---
Nah, that's too much overhead, this isn't really a killer issue. I'm fine with
the status quo. This idea sort of came up and I put it on the table, but
perhaps the includes directive is more useful for organizing requests inside an
application than anything.
Inter-app includes sounds fishy a
That still doesn't answer the question that brings out the problem
with the idea: where do we put it?
-David
On Feb 8, 2007, at 4:23 PM, Leon Torres wrote:
Well, the current situation isn't any more "modular" or "natural".
We have to specify a LookupProduct that points to the product
A compromise solution: have the request-uri in it's "native" app..and
then duplicate those request-uris in a specialized app that centralizes
those lookup screens. I don't think there would be much worry about
the request-uri/view-map definitions changing all too often, while the
underlying screen
Well, the current situation isn't any more "modular" or "natural". We have to
specify a LookupProduct that points to the product lookup screen in
applications/product/ in a bunch of different web apps that need it.
The only difference of putting them in one controller.xml is that it will cut
I agree with what Adrian wrote on this one...
The lookup screens should be defined in their most natural component.
If we were to have an include file for lookups across many
components, which component would be put it in?
-David
On Feb 8, 2007, at 12:57 PM, Adrian Crum wrote:
At first
[
https://issues.apache.org/jira/browse/OFBIZ-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471486
]
Adrian Crum commented on OFBIZ-666:
---
COMMITTERS: Could we get this added to the project please?
It has been tested
[
https://issues.apache.org/jira/browse/OFBIZ-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrian Crum updated OFBIZ-633:
--
Attachment: experimental_4.patch
experimental_4.patch builds upon experimental_3.patch. This patch will
It should be that if you create a request-uri with the same name lower
in the file than the element, your request-uri should
override the one from the included document. And if you're never
calling the request-uri from components you haven't loaded, then you'll
never have the error.
--- Adrian
At first glance this would seem like a logical thing to do. The downside is you
would lose modularity. In other words, there may be complications with
installations that don't mount all components.
Leon Torres wrote:
Hi folks, I saw that an directive is possible in
controller.xml and was won
[
https://issues.apache.org/jira/browse/OFBIZ-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471464
]
Si Chen commented on OFBIZ-677:
---
If there are no objections I'll commit this
> Patch to add RunService feature to /webt
[
https://issues.apache.org/jira/browse/OFBIZ-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Vijaywargiya updated OFBIZ-694:
--
Attachment: Selectable_Feature.patch
Thx Scott for your comments.
Here is the updated pa
Like it. Ready to help also.
+1
Anil Patel
On 2/8/07, Leon Torres <[EMAIL PROTECTED]> wrote:
Hi folks, I saw that an directive is possible in controller.xmland
was wondering if we should put all the Lookups like LookupProduct in one
xml for
convenience. This will allow applications to take
Hi folks, I saw that an directive is possible in controller.xml and
was wondering if we should put all the Lookups like LookupProduct in one xml for
convenience. This will allow applications to take advantage of all available
lookups in the system without having to duplicate the request and vi
[
https://issues.apache.org/jira/browse/OFBIZ-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471423
]
Chris Howe commented on OFBIZ-704:
--
Is this the best way to model it? fromString, toString and ccString seem to be
[
https://issues.apache.org/jira/browse/OFBIZ-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Si Chen reassigned OFBIZ-704:
-
Assignee: Si Chen
> Add CommunicationEvent.fromString, toString, ccString, headerString
>
Add CommunicationEvent.fromString, toString, ccString, headerString
---
Key: OFBIZ-704
URL: https://issues.apache.org/jira/browse/OFBIZ-704
Project: OFBiz (The Open for Business Project)
[
https://issues.apache.org/jira/browse/OFBIZ-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471419
]
Yinghui Chen commented on OFBIZ-701:
Hello, Si Chen,
Thanks for your advice. I will create a request in sourceforg
[
https://issues.apache.org/jira/browse/OFBIZ-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471416
]
Yinghui Chen commented on OFBIZ-701:
Hello, Jacques,
Thanks for your instruction. I have got advice from Si Chen
[
https://issues.apache.org/jira/browse/OFBIZ-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Si Chen closed OFBIZ-701.
-
Resolution: Invalid
If you want to contribute to opentaps crm follow the instructions here:
http://sourceforge.net
calcop attribute definition conflict
Key: OFBIZ-703
URL: https://issues.apache.org/jira/browse/OFBIZ-703
Project: OFBiz (The Open for Business Project)
Issue Type: Bug
Components: framework
[
https://issues.apache.org/jira/browse/OFBIZ-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471364
]
Jacques Le Roux commented on OFBIZ-701:
---
Sorry typos :(
PLease read : "can't mix licences" and especially "Ho
approveOrder is connected to nothing
Key: OFBIZ-702
URL: https://issues.apache.org/jira/browse/OFBIZ-702
Project: OFBiz (The Open for Business Project)
Issue Type: Bug
Components: ecommerce
[
https://issues.apache.org/jira/browse/OFBIZ-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471363
]
Jacques Le Roux commented on OFBIZ-701:
---
Yinghui,
Beware that the CRM/SFA module is GPL licenced and we can't
[
https://issues.apache.org/jira/browse/OFBIZ-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471354
]
Chris Howe commented on OFBIZ-71:
-
To note, that's a screen shot of Google Checkout's Sandbox showing what the
custome
translate opensourcestrategies' CRM/SFA into simplified chinese
---
Key: OFBIZ-701
URL: https://issues.apache.org/jira/browse/OFBIZ-701
Project: OFBiz (The Open for Business Project)
[
https://issues.apache.org/jira/browse/OFBIZ-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacopo Cappellato closed OFBIZ-505.
---
> Wrong target of lookupPartyAndUserLoginAndPerson form
>
The lookup in UserLogin screen excludes logins not associated to a Party.
-
Key: OFBIZ-700
URL: https://issues.apache.org/jira/browse/OFBIZ-700
Project: OFBiz (The Open for Busine
[
https://issues.apache.org/jira/browse/OFBIZ-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacopo Cappellato closed OFBIZ-104.
---
> Re-factor PaymentGatewayServices processCaptureResult
>
[
https://issues.apache.org/jira/browse/OFBIZ-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacopo Cappellato closed OFBIZ-45.
--
> availableLocales property does not handle country_code during parsing
> ---
[
https://issues.apache.org/jira/browse/OFBIZ-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacopo Cappellato closed OFBIZ-699.
---
Resolution: Fixed
Thanks Rupert,
I've fixed the link in rev. 504850
The update will go live s
[
https://issues.apache.org/jira/browse/OFBIZ-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacopo Cappellato reassigned OFBIZ-699:
---
Assignee: Jacopo Cappellato
> Marketing page not found from OFBiz home page
>
Marketing page not found from OFBiz home page
-
Key: OFBIZ-699
URL: https://issues.apache.org/jira/browse/OFBIZ-699
Project: OFBiz (The Open for Business Project)
Issue Type: Bug
Componen
[
https://issues.apache.org/jira/browse/OFBIZ-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Al Byers resolved OFBIZ-697.
Resolution: Fixed
I committed fix.
> ServiceMultiEvent does not handle ServiceAuthException
>
[
https://issues.apache.org/jira/browse/OFBIZ-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Al Byers resolved OFBIZ-696.
Resolution: Fixed
Committed fix.
> The ModelService.evalPermission method does not test for
> permissionRe
44 matches
Mail list logo
