to add option "visible for my buddies only"

While this is a great feature, I think it needs further thinking. People have requested ability to make checkboxes for Organic Groups for instance, plus allowing access per group for buddy list. If you can suggest an adequate UI for such a permissions control, i'll consider implementing. Thanks!

hi quicksketch,

I'd be extremely grateful for the option to have this feature (i.e. to enable profile to be viewed by buddies). How hard would that be to implement?
also, it wouldn't hurt to have it present for the time being (if it's not hard to implement) or maybe as a patch and who ever wants it can use it...

don't want to sound ungrateful - profile privacy is great...i just wish there was this little thing to make it even better (for some users at least :)

What a pity that discussion stopped... Is there still interest in a solution for this?

Concerning the user interface:

The admin interface needs not to be changed, just that one in the user profile page.
If the buddylist module exists, we have radios instead of a checkbox (we could have radios anyway).

Access per buddygroups would be nice, of course, but should not be in the scope of this module. There should be a genral api solution in buddygroups for that. I'm not up to date with development, but we have work on 3 buddy solutions going on (buddylist, buddy api + buddylist2, user relations). So I think this will do.

If additional support for organic groups is needed, I would prefer a checkbox solution again:

I am waiting for this really great feature, I hope for this new addon will be someday.
Igor

+1

I would love to see this feature! Support for organic groups would be great. I really like the idea of the checkbox solution.

I'd really like to see this feature added also!

I'd really love this feature as well. I think a good implementation would be to do it by content types.

In the Privacy module settings you could simply check the content types* that you want to see this option displayed on, like so:

In the above example the privacy option would be listed on the Blog content type. Now when a user goes to create a new blog entry, they would have a new menu set with options similar to these:

So now, the privacy settings apply to the blog content type and this particular blog entry would be set as viewable by only people on your buddylist.

Doing it this way allows for expandability and flexibility for the developer, as they can assign it to any CCK content they wish.This would cover all aspects of node privacy within drupal on a single node basis.

@STyL3, what you're describing is very beyond the scope of profile_privacy. This module deals with the privacy setting of profile fields, it doesn't go into dealing with nodes or content types in any way.

+1 for the buddy api module aka buddylist2.

Privacy for users of sites with many users is absolute key! Our site have members with sensitive information that should only be visible to selected friends.

Is this concept still in development for the drupal 5 branch?

Regards,
Marius

I'm still completely open to adding this funtionality, however I maintain several other modules that receive a lot more use that this one. I'd love to review any patches providing a solid implementation.

Thanks quicksketch, I wish I could. After further brainstorming however I realized I really need a one click privacy setting for friends. I resorted to using usernode as a profile container, since nodes have bigger support for privacy solutions including for buddy api which I use. So no pressure on this one from me.

Regards,
Marius

PS. Your "Views Bookmarks" module is simply amazing!

hi folks,

had the same problem - so a created a patch to work with the buddylist2.

summary:
- introducing a new table 'profile_privacy_user_setting'
- introducing a new checkbox for user 'show all profile information to my buddies'
- show the profile info if the 2 user are direct buddies

i kept the style from the original code.

please review!

i'm quite new to the comunity - so please tell me if the patch is fine and useable!

neurovation.kiwi, thanks this looks like a good start!

A few things need to be fixed before I can really accept though:

- Please follow the coding standards: http://drupal.org/coding-standards, this module follows them already, so just stay consistent with the current code style.
- We'll need an update function in profile_privacy.install.php to upgrade existing installations to the new database schema.
- The option "PROFILE_PRIVACY_SETTING_SHOW_BUDDIES" should be a setting somewhere in the interface, not a constant defined at the beginning of the file. Otherwise users will need to remember to change this constant every time they upgrade the module.

will this feature added??

visible for buddylist / relationship only?

- well, as i stated in my original posting, i kept the style to what i was seeing already in the code...
- did'nt know i had to, sorry...
- why the heck does a user have to remember a coded constant if upgrading the module?

please elaborate, or give me some hints where i can finde docs for that. i want to know it ;)

Thanks for submitting this patch! I would recommend using the coder module http://drupal.org/project/coder to review your patched version of the module and fix any warning it gives you. Module maintainers try to keep up the rather strict coding standards, and for good reason, but i know that it can sometimes be a pain to those trying to help. If you have any questions using the module, feel free to contact me through drupal.org.

cheers!

Does this patch works for drupal 6.x and/or the User Relationships module?

Thanks!