This module uses the same permission as the Field Permissions module: "access private fields". I propose this be changed to "access private user fields" in this module.

Comments

boobaa’s picture

Assigned: Unassigned » boobaa

Thank you for pointing this out, I'm already considering the upgrade path possibilities.

xbrianx’s picture

Has 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.

jemisond’s picture

Also very interested in having this resolved.

pmchristensen’s picture

Issue summary: View changes
Status: Active » Needs review
StatusFileSize
new620 bytes

Here is a patch which correct the permission so it doesn't conflict with field_permissions anymore.

dpalmer’s picture

Tested the patch in #4, it works fine for me.

Anonymous’s picture

StatusFileSize
new1.12 KB

The previous patch fixed the permission itself, but not where the permission was then used. This patch addresses that too.

boobaa’s picture

Could 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).

boobaa’s picture

Status: Needs review » Needs work
Anonymous’s picture

Status: Needs work » Needs review

That'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.