Closed (cannot reproduce)
Project:
Field Permissions
Version:
7.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Feature request
Assigned:
Reporter:
Created:
1 Jun 2011 at 13:56 UTC
Updated:
23 Jul 2016 at 20:50 UTC
Jump to comment: Most recent
Comments
Comment #1
puravida commentedA lot of what I've seen with D7 security framework is that "view" is implied with "edit", so it is a requirement. Perhaps the maintainer would be willing to code around that for your use case, but I don't think it is the "standard" way.
Comment #2
Vasu commented@danielmtv2
If you could describe a 'use case' or 'scenario' where this might be required it will be easier for others to suggest a solution (which I think will be outside the purview of this module).
BTW, a possible workaround is to create a panel-page variant for the content-type and put the field into a pane/region and the set the visibility of that pane to be visible for specific roles. The field will still be available for editing (You can still use this module to control which roles can edit the field)
Comment #3
robloachHmmm? "View", "View own", "Edit" and "Edit own" are in there.
Comment #4
mariacha1 commentedI suspect this is a duplicate, but without any new info in 5 years I'm closing this.