You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Jacques Le Roux (JIRA)" <ji...@apache.org> on 2016/05/03 17:26:12 UTC
[jira] [Updated] (OFBIZ-7033) Bug when getting to
webtools/control/FindUtilCache
[ https://issues.apache.org/jira/browse/OFBIZ-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacques Le Roux updated OFBIZ-7033:
-----------------------------------
Description:
With OFBIZ-7029 I replaced some widget list forms by grids. I don't know why yet but there are some cases, like at webtools/control/FindUtilCache, where it crashes.
I mean I know why, but I don't know why yet it's not in all places. For instance accounting/control/ListFixedAssets has not this problem.
I'll fix the current issue and later check what is the difference between both cases (maybe another Jira issue)
was:
With OFBIZ-7029 I replaced some widget list forms by grids. I don't know wy yet but there are some cases, like at webtools/control/FindUtilCache, where it crashes.
I mean I know why, but I don't know why yet it's not in all places. For instance accounting/control/ListFixedAssets has not this problem.
I'll fix the current issue and later check what is the difference between both cases (maybe another Jira issue)
> Bug when getting to webtools/control/FindUtilCache
> --------------------------------------------------
>
> Key: OFBIZ-7033
> URL: https://issues.apache.org/jira/browse/OFBIZ-7033
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
> Affects Versions: Trunk
> Reporter: Jacques Le Roux
> Assignee: Jacques Le Roux
> Fix For: Upcoming Branch
>
>
> With OFBIZ-7029 I replaced some widget list forms by grids. I don't know why yet but there are some cases, like at webtools/control/FindUtilCache, where it crashes.
> I mean I know why, but I don't know why yet it's not in all places. For instance accounting/control/ListFixedAssets has not this problem.
> I'll fix the current issue and later check what is the difference between both cases (maybe another Jira issue)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)