The D7-version still has a dependency on Profile. This is not mentioned on the Modules page, since Profile is a deprecated/hidden module. profile should only be used for migrating purposes.

Comments

johnv’s picture

johnv
Primary language Dutch
commented

You can use core account (which is now fully fieldable) or Profile2 as a basis.

Anonymous’s picture

Anonymous (not verified) commented

Yes profile privacy should be available for all user-related fields.
I also suggest integrating with profile 2 and core account.

TimelessDomain’s picture

TimelessDomain commented

so - we can remove the dependency for profile?

Anonymous’s picture

Anonymous (not verified) commented

The D7 version should integrate a privacy "checkbox" with *any* D7 field: nodes, terms, users, accounts, profile2 and cck. Will removing the depency do all this?

I will have a better look in a week or 2, because I really need all this for an important project.

It shouldn't be too hard right, just add a field option and check user access. But for large sites, we might also need a new caching table or a db summary table, to avoid unnecessary joins. This could extend the D7 "rebuild content access rights" action.

But then again, it wouldn't be "profile privacy", it should be called "privacy2" or "field privacy".

boobaa’s picture

boobaa
he/him
commented

Looking at the code of this module I have learned that this one is deeply tied to profile.module. It looked easier to craft a new module from ground-up than dealing with this one, so I took a breath and wrote it. Here you are the User Field Privacy module, at your service. Please go and have it tested thoroughly, and should you find any issues with that one, file them there. :)

sw3b’s picture

sw3b commented

Nice work !!!