Open
Bug 1020269
Opened 10 years ago
Updated 3 years ago
UserProfile.objects.public() should include users with public external acounts
Categories
(Participation Infrastructure :: Phonebook, defect)
Participation Infrastructure
Phonebook
Tracking
(Not tracked)
NEW
People
(Reporter: giorgos, Unassigned)
Details
(Whiteboard: [iam-RFE])
UserProfile.objects.public() manager method does not take into account the privacy settings of external accounts. If a user has only external accounts set to be public then we don't include them in the public profiles list. This is an edge case and does not expose any private data but it should be fixed anyway.
Reporter | ||
Comment 1•10 years ago
|
||
Must also update the UserProfile.is_public method
Comment hidden (typo) |
Comment hidden (typo) |
Comment 4•9 years ago
|
||
Couple of questions: -Does this bug wants the user to be logged in and vouched, logged in and not vouched, not not logged in, or all of the above? -Is this searching on full_name, email, or ircname? Or does it matter?
Reporter | ||
Comment 5•9 years ago
|
||
This is about how a UserProfile method should behave and not directly related to a logged in or logged out user. UserProfile.objects.all() returns all user profiles UserProfile.objects.public() should return users profiles with at least one field set to public. Currently it ignores the status of external accounts, meaning that if a user only has "linkedin" set to public and none of all the other fields of their profile, they are not included in the list generated by UserProfile.objects.public()
Updated•3 years ago
|
Status: REOPENED → NEW
Whiteboard: [iam-RFE]
You need to log in
before you can comment on or make changes to this bug.
Description
•