[buddypress-trac] [BuddyPress Trac] #4571: Changes in Gravatar APIs result in failed fallback on default avatars

buddypress-trac noreply at wordpress.org
Sun Feb 2 19:09:48 UTC 2014

#4571: Changes in Gravatar APIs result in failed fallback on default avatars
 Reporter:  boonebgorges   |       Owner:  boonebgorges
     Type:  defect (bug)   |      Status:  closed
 Priority:  normal         |   Milestone:  2.0
Component:  Core           |     Version:
 Severity:  major          |  Resolution:  fixed
 Keywords:  needs-refresh  |
Changes (by boonebgorges):

 * owner:   => boonebgorges
 * status:  reopened => closed
 * resolution:   => fixed


 In [changeset:"7769"]:
 #!CommitTicketReference repository="" revision="7769"
 Improve default avatar handling in bp_core_fetch_avatar()

 Changes to Gravatar over the last few years have placed restrictions on
 the way
 that a default gravatar (to be used as a fallback for when no actual
 is found) can be served to gravatar.com. In particular, Gravatar cannot
 and serve default images that are not publicly available (as in dev
 environments) or are only available over SSL.

 Because BuddyPress's default behavior was to provide a local copy of the
 mystery-man avatar, switching to Gravatar's hosted mystery-man solves
 problems for sites that are using the default mystery-man as a fallback

 This changeset also reconfigures the way that the `BP_AVATAR_DEFAULT`
 is respected, to ensure that it's possible to override the avatar fallback
 no_grav is set to true.

 Fixes #4571

 Props r-a-y

Ticket URL: <https://buddypress.trac.wordpress.org/ticket/4571#comment:21>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac

More information about the buddypress-trac mailing list