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

[buddypress-trac at lists.automattic.com]

#4571: Changes in Gravatar APIs result in failed fallback on default avatars
--------------------------+-----------------------------
 Reporter:  boonebgorges  |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Core          |     Version:
 Severity:  major         |  Resolution:
 Keywords:  has-patch     |
--------------------------+-----------------------------

Comment (by r-a-y):

 > How difficult would it be to modify to make Gravatar optional -- keeping
 it as default if necessary to deal with backward compatibility?

 > there was no option to not use gravatar!

 There's a simple filter to disable Gravatar. (There's no admin option for
 this at the moment.)

 Add this to your /wp-content/plugins/bp-custom.php:

 `add_filter( 'bp_core_fetch_avatar_no_grav', '__return_true' );`

 In BP 1.6, to use a custom avatar in this instance, you'll also need to
 hook into `'bp_core_default_avatar_$object'`, which would translate to
 `'bp_core_default_avatar_user'` for users.

 View the hook here:
 https://buddypress.trac.wordpress.org/browser/tags/1.6.1/bp-core/bp-core-
 avatars.php#L373

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