Integration with User Relationships
DaniOrama - October 15, 2008 - 14:36
| Project: | Profile Privacy |
| Version: | 6.x-1.2 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Hello, I think an integration with user relationships would be also wonderful. Right now there is an issue regarding integration with User Friendlist http://drupal.org/node/314195 and I think we could follow the same approach with this one. I'm right now really busy, but I will try to help alex (the mantainer of User relationships) next week with this issue.

#1
+1 for this... quicksketch, is there an API in place to do this for the various relationship modules or does that still need to be written?
#2
This issue may provide a solution to the problem: #597546: Code attached that forks profile_privacy to add support for onepageprofile, user relationships
Thanks,
Chris
#3
@cpliakas If you would, I'd appreciate some more information on how profile_privacy and user relationships were integrated in your fork. I could start digging through the code but from the description on #597546: Code attached that forks profile_privacy to add support for onepageprofile, user relationships profile_privacy was forked in many different ways.
#4
Hi coltrane.
The code isn't forked too badly so you can use WinMerge or Meld to see the differences, but the major difference is as follows. Currently, the user override privacy settings are boolean, i.e. they are either public or private. I modified the schema to accept strings so that more than two privacy settings may exist, and I added a couple of hooks that allows other modules to define privacy settings and react accordingly. The forked module has a profile_privacy.api.inc file that defines the hooks, and it also has a user relationships add-on in contrib/ that implements the hooks and adds UR support. The base module was a great help for us, and I appreciate your work on it. The fork works for our specific implementation, but I think there are pieces like the hooks mentioned above that could be added back into the community version of the module. Again, it isn't forked too badly (yet too much for a patch to make sense in an issue queue) so you should be able to see the differences.
Again, thanks for your work on this module. It helped us out a ton.
~Chris