[buddypress-trac] [BuddyPress] #5292: Error with default 'mysteryman' avatar

[buddypress-trac]

#5292: Error with default 'mysteryman' avatar
--------------------------+----------------------
 Reporter:  bradt1999     |       Owner:
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Members       |     Version:  1.8.1
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |
--------------------------+----------------------
Changes (by boonebgorges):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 > Obviously, the mysteryman image is being wrongly concatenated onto the
 gravatar url.

 I'm not sure what you mean by "being wrongly concatenated". Do you mean
 that *it shouldn't be concatenated at all*, or that *the concatenation is
 incorrect*?

 The concatenation is intentional. Your BuddyPress installation has no way
 of knowing whether a user has a Gravatar or not. We simply pass a hashed
 version of the user's email address along to gravatar.com, and let
 Gravatar decide what to do. If that email address is associated with a
 Gravatar, that Gravatar is served up. If not, then Gravatar will fall back
 on the value of 'd' (the mysteryman).

 The reason why the images are not found on your installation is because
 you are testing on localhost. Last year, Gravatar made some security-
 related changes that made it impossible to use a non-public image file as
 the value of 'd'. gravatar.com does not have access to your localhost,
 thus it can't act as a proxy for your image. See #4571 for an extended
 discussion of the problem, and some suggestions for working around it in
 BuddyPress.

 As long as your production site is public, this problem will go away when
 you deploy. If you would like to avoid using Gravatar altogether, do this:

 {{{
 add_filter( 'bp_core_fetch_avatar_no_grav', '__return_true' );
 }}}

 Closing this ticket as invalid, because I believe that the feature is
 working as expected, and future discussion can take place on #4571. If I'm
 misunderstanding, please feel free to reopen with details.

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/5292#comment:1>
BuddyPress <http://buddypress.org/>
BuddyPress