I'll put out my goal with a Drupal 6 version of CCK Field Privacy - the ability to use it with the Content Profile module. My goal is to allow the user to selectively make certain profile fields private if the choose, such as birthdate or sex. This is similar to what you would find on Facebook on the "Basic" tab of your profile.

To date I have a working and updated jQuery Impromptu which is helpful but I am not using buddylist so hacking that stuff out of the code is one of the things I'll be looking to do. I also saw the issue about integrating it with friendlist which is nice, but I'd really like to integrate with the User Relationships module since that seems to be the ultimate direction that social networking type features are headed in version 6 of Drupal. This isn't a huge priority for me, but the ability to allow users to globally hide profile fields is.

I'm happy to contribute to the Drupal 6 efforts for this module - either with coding or testing. Thanks.

Comments

a_c_m’s picture

a_c_m commented

+1 to this statement, we are also looking at this exact combination.

obsidiandesign’s picture

obsidiandesign commented
Assigned: Unassigned » obsidiandesign
Status: Active » Postponed (maintainer needs more info)

In terms of the User Relationships integration, promote/encourage #315714: Integrate with cck_field_privacy, as the 6.x version of CCK Field Privacy uses the new hook format, to prevent having code from 2+ other modules inside this one.

I haven't used Content Profile yet, but I would imagine it creates a content type? Does the content type show up in the settings page? Also, do the fields show up correctly? I'm trying to figure out the scope of what has to be changed to make Content Profile work with this.

obsidiandesign’s picture

obsidiandesign commented

In #326712: default value, it's referenced that Content Profile is being used with CCK Field Privacy. Can anyone else confirm this? That would allow me to close this specific issue, at least in terms of the Content Profile usage.

obsidiandesign’s picture

obsidiandesign commented
Status: Postponed (maintainer needs more info) » Fixed

I've tested with Content Profile, and CCK Field Privacy works as expected. Marking fixed since the second issue, in terms of User Relationships integration, is not something that I can directly fix.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.