[buddypress-trac] [BuddyPress Trac] #7298: xprofile fied user visibility settings regression

[buddypress-trac]

#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:  has-patch 2nd-opinion  |
-----------------------------------+--------------------

Comment (by boonebgorges):

 >  I don't really agree that a quick function, not doing any significant
 work, even being called hundreds of time, is not by itself any significant
 overheard.

 @DJPaul Calling a function vs not calling it does add overhead, though
 whether it's "significant" is, I guess, subject to debate.
 https://gist.github.com/boonebgorges/a4f40af56d3e9263575daee5cd6d4c3c

 >  I also don't feel I can offer much further technical wisdom regarding
 best ways to fix this; my best effort in this area was #7176 -- which I
 was hoping would start moving that ball rolling more than it has -- so
 more than happy to go with whatever you think a good fix is.

 Like you, I spent many hours looking at #7176, so please don't think I'm
 ignoring the efforts there. As far as I can see, that ticket wouldn't
 directly address this one anyway - the assumption there is that we'll use
 'map_meta_cap' to implement BP caps, while the inconsistent application of
 the 'map_meta_cap' filter for non-logged-in users is the source of the
 difficulty here.

 If others have strong feelings about a general strategy for anonymous user
 caps, please offer them up. Otherwise I guess I'll go with something like
 [attachment:7298.diff] for 2.7.1.

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/7298#comment:11>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac