You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Al Byers (JIRA)" <ji...@apache.org> on 2007/05/30 06:53:15 UTC
[jira] Created: (OFBIZ-1043)
ContentPermissionServices.viewContentPermission needs to set checkId
ContentPermissionServices.viewContentPermission needs to set checkId
--------------------------------------------------------------------
Key: OFBIZ-1043
URL: https://issues.apache.org/jira/browse/OFBIZ-1043
Project: OFBiz (The Open for Business Project)
Issue Type: Bug
Components: content
Affects Versions: SVN trunk
Reporter: Al Byers
Assignee: Al Byers
Is there any reason why ContentPermission.viewContentPermission does not need the same code as updateContentPermission that sets "checkId"? Below is some code where I have added that code.
If this is a bug, I guess it should also be applied to the release branch?
-Al
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1043)
ContentPermissionServices.viewContentPermission needs to set checkId
Posted by "Al Byers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Al Byers updated OFBIZ-1043:
----------------------------
Attachment: ContentPermissionServices.diff
Here is the proposed patch
> ContentPermissionServices.viewContentPermission needs to set checkId
> --------------------------------------------------------------------
>
> Key: OFBIZ-1043
> URL: https://issues.apache.org/jira/browse/OFBIZ-1043
> Project: OFBiz (The Open for Business Project)
> Issue Type: Bug
> Components: content
> Affects Versions: SVN trunk
> Reporter: Al Byers
> Assignee: Al Byers
> Attachments: ContentPermissionServices.diff
>
>
> Is there any reason why ContentPermission.viewContentPermission does not need the same code as updateContentPermission that sets "checkId"? Below is some code where I have added that code.
> If this is a bug, I guess it should also be applied to the release branch?
> -Al
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.