Closed (fixed)
Project:
Private nodes
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Sep 2007 at 21:25 UTC
Updated:
3 Dec 2007 at 09:11 UTC
I've installed what seems to be the latest version of the module (aug 22).
When I got to admin/user/access there are options to allow users to control privacy on standard content types, but not custom content types created as nodeprofiles (using usernode/nodeprofile modules).
I took a quick look in the code, and it looks like it specifically filters out any node types that are set as nodeprofiles. Why is this? Is this module incompatible with nodeprofile for some reason?
Comments
Comment #1
ben_scott commentedHi Coyote
No its not incomptaible with nodeprofile - this functionality is actually on purpose: You can choose to hide your profile (and so all nodes defined as nodeprofile will also be hidden), or you can hide nodes.
We then used my other module nodeprofile privacy to allow users to show / hide individual fields in their profile.
Together, these allowed us to achieve the user controlled privacy we wanted...
Hope this helps,
Ben
Comment #2
ben_scott commentedComment #3
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.