Active
Project:
ProfilePlus
Version:
master
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
22 Aug 2008 at 13:39 UTC
Updated:
22 Feb 2011 at 14:45 UTC
Even if a user decides to make a profile field private the information in that field is still displayed when searched.
maybe this should be filed against the search module?
it's a great module nonetheless. Thanks!
Comments
Comment #1
omnyx commentedThe problem is that the profileplus module (or any module that searches through user profiles) looks at the privacy values in the 'profile_fields' table and not the 'profile_privacy_values' table.
the search code is the following (for users that do not have 'user admin' privileges)
I'm really bad with sql - do you have any ideas how I could join the tables or whatever to filter out fields for the users that declared them private? :D
thanks!
UPDATE:
This is the code that I used - seems to work:
Comment #2
coltrane@omnyx Since you're changing the query in profileplus module this issue should really be filed against it, but I can see how there needs to be some easy way to bridge that module (and any other module that displays profile data) with profile privacy. This is a sticky and larger problem, I'm postponing for now.
Comment #3
cor3huis commentedSince sadly postponed for a long time, and really an issue in another module, moving issue. Otherwise this improvement probably will never see the light of day.