[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:                |
--------------------------+-----------------------------
Changes (by boonebgorges):

 * milestone:  1.6.2 => Future Release


Comment:

 > Why even use Gravatar? Most people dislike it.

 We must continue to use Gravatar because we currently use it. If I were
 building BP from scratch I would not include it in core. But we have to
 deal with it for backward compatibility.

 >  When we move to using meta for avatars, we'll also have to be DB query-
 conscious. Will probably have to add the avatar query to BP_User_Query.

 Right. Just so long as we're not creating a new DB query for every avatar
 on a page. As r-a-y notes, this can be easily done by adding the check to
 BP_User_Query and BP_Core_User.

 Let's definitely go with user education (including pointing users to
 Gravatar's updated documentation, when it exists), at least for the 1.6.x
 series. If this turns out to be an enormous problem, we can try for a
 stopgap solution in 1.7. But I doubt this will be the case - as John noted
 in chat, this will affect only a small number of users (as vocal as they
 may be). Let's maybe look at a refactor of avatar stuff for 1.8.

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