Changes in Gravatar APIs result in failed fallback on default avatars
|Reported by:||boonebgorges||Owned by:||boonebgorges|
|Component:||Component - Core||Keywords:||needs-refresh|
BP allows admins to specify a default avatar, which is to be used when a user both has no Gravatar and has not uploaded a local avatar. We implement this by passing the URL of the default avatar along to Gravatar using the ?d= parameter. I'm not 100% sure how Gravatar handles these params, but it appears that they cache a copy of the local avatar and serve it from their servers.
A change made at gravatar.com last week means that this method no longer works in all cases. For security reasons, your default image must now be "publicly accessible". That means that they can't be behind HTTP authentication or otherwise hidden with Apache rules. See https://twitter.com/beaulebens/statuses/251407787341524992
I first noticed this in a password-protected staging environment, but users are already reporting the issue in their production installations.
Possible solution: Near the end of bp_core_fetch_avatar(), we detect when a Gravatar query has failed, and if so, we serve up the local default directly.
Change History (22)
comment:8 in reply to: ↑ 7 ; follow-up: ↓ 13 @johnjamesjacoby — 3 years ago
comment:10 @r-a-y — 3 years ago
- Keywords has-patch added
comment:13 in reply to: ↑ 8 @rogercoathup — 3 years ago
comment:17 @DJPaul — 2 years ago
- Keywords needs-refresh added; has-patch removed
- Resolution set to fixed
- Status changed from new to closed