Needs review
Project:
User Field Privacy
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
3 May 2012 at 14:51 UTC
Updated:
22 Sep 2015 at 06:53 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
boobaaThank you for pointing this out, I'm already considering the upgrade path possibilities.
Comment #2
xbrianx commentedHas this been resolved? I am using Field Permissions, but I created a node type called user profiles but I am not seeing any check boxes or anything when I try to edit the fields. I am using the latest Dev version. Any other idea how to allow users to control what content is being seen. For instance i have a field called birthdate, but users may not want that information displayed for everyone.
Comment #3
jemisond commentedAlso very interested in having this resolved.
Comment #4
pmchristensen commentedHere is a patch which correct the permission so it doesn't conflict with field_permissions anymore.
Comment #5
dpalmer commentedTested the patch in #4, it works fine for me.
Comment #6
Anonymous (not verified) commentedThe previous patch fixed the permission itself, but not where the permission was then used. This patch addresses that too.
Comment #7
boobaaCould you please suggest an upgrade path, too? One would be preferred that does not conflict with the Field permissions module (ie. does not "convert" the granted permissions of the Field permissions module, but only of this module).
Comment #8
boobaaComment #9
Anonymous (not verified) commentedThat's not possible, since both modules had the same permission name. There's no way to know if the 'access private fields' permission was for this module or Field Permissions, hence no way to reliably update it.
Will just have to fix this and add a note to the next release telling users to double-check their permissions when they upgrade.