Feature proposal #4969
closed
- Target version changed from 667 to 5.0.0
This will likely just need to be a new fieldtype specifically for blocking users from viewing your profile, but that functionality won't really extend to anything else.
- % Done changed from 0 to 20
- Target version changed from 5.0.0 to 6.0.0
Moving to 5.1.0 as storage requirements need to be designed. A new database table would be best with 1 row per block as id | user_id | block. Additionally needs to act on CB Activity query trigger so if a user is blocked by someone they won't see their activity.
- % Done changed from 20 to 0
Implement block by username and email address in addition to user id. This further solidifies needing a custom database table.
- % Done changed from 0 to 50
Block is always done by user_id. Username/Email Address will translate to user_id. Blocking will override any privacy controls. So if something is set to Public it won't matter as it will be treated as private when a blocked user attempts to view it. Profile Access, Email Form, and PM Form all have enforced privacy when a blocked user tries to access either (they will be denied access).
- Status changed from Assigned to Resolved
- % Done changed from 50 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by