[buddypress-trac] [BuddyPress Trac] #7298: xprofile fied user visibility settings regression
buddypress-trac
noreply at wordpress.org
Fri Oct 21 16:44:04 UTC 2016
#7298: xprofile fied user visibility settings regression
------------------------------+--------------------
Reporter: hnla | Owner:
Type: defect (bug) | Status: new
Priority: high | Milestone: 2.7.1
Component: Extended Profile | Version:
Severity: major | Resolution:
Keywords: needs-patch |
------------------------------+--------------------
Comment (by DJPaul):
My thoughts on different ways to address this:
1) Revert the `bp_current_user_can` change and rely on the "broken"
behaviour with `current_user_can_for_blog`... which will last until
if/when WordPress fixes that function. Just punting the problem down the
calendar.
2) Add special edge-case handling to `bp_user_can` specifically for
`bp_xprofile_change_field_visibility`. Probably calling it directly. This
is a bit of a poor long term solution but would fix the problem for now.
3) Do something like 2, but accommodate anonymous user capabilities
properly. I don't know if bbPress has anything smart for this, I know it
uses capabilities for logged-out users a lot more than WordPress does
(WordPress doesn't, really; there is that odd `read` capability for a few
things).
4) Decide that the profile field visibility on the registration form isn't
something we want to support, and call this a feature.
--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/7298#comment:5>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac
More information about the buddypress-trac
mailing list