Closed (outdated)
Project:
Private
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
16 Nov 2013 at 23:29 UTC
Updated:
18 Feb 2017 at 13:32 UTC
Jump to comment: Most recent
Comments
Comment #1
kerasai commented@mike_san, this is really more of an issue with the behavior of the entity reference field, not the Private module. The Private module only allows you to set access control on the content, but the field is responsible for rendering the field values and by default it's respecting the access that's been defined.
I think your best bet would be to find or make a field formatter that handles the entity reference as you desire. Be careful handling access to your content, as you only want to reveal a bit of info about it and not give away the data of the entire node. In your case you'll likely still want to do some access checks, i.e. an unpublished node should not be listed vs. a private node which should be listed but not in the manner as a non-private node.
Comment #2
mike_san commentedThanks for your advice, kerasai. The problem is that the field formatter has to point to a content type that could be private or public (and may even change at some point). Thanks anyway!
Comment #3
adamps commentedSeems to be complete