I saw that the other day. I though it was a local development environment problem I had, but I believe it’s to do with the Gravatar service; I’ll raise it with Automattic.
Thank you for your quick reply. This is strange because my page never had anything to do with gravatar.com. I also deactivated the plugin “Jetpack for WordPress” which seemd to be a possible trigger for this i0.wp.com, but nothing changed.
What do you mean with “I’ll raise it with Automat(t)ic”? I’m not a native English speaker.
Rgds
Sorry. Gravatar is a service that lets you upload a picture, and it’s used as your avatar across many websites. BuddyPress lets users upload their own picture, of course, but we use Gravatar as a fallback (if you don’t have a gravatar, then we use the uploaded picture).
Automattic (automattic.com) is the company who owns and runs Gravatar.
This problem was caused by a change made by Gravatar. We have a bug ticket tracking the issue at https://buddypress.trac.wordpress.org/ticket/4571
Thanks again for your explanation. I hope the next version will fix this problem.
Rgds
@djpaul,
Thanks for the heads up. I also thought I had a config issue in my local Dev.
@hnla – the problem we looked at yesterday – I noticed the domain name. If you check the trac ticket it’s because the image isn’t publicy accessible (as we’d suspected).
thngs are set that unless you upload your own pic/avatar the gravatar service is brought into the equation whether you like it or not, it’s a behaviour I’m looking into.
any news on this subject i notice the same issue locally and i am using buddypress 1.7-beta1 plugin
No need to bump this topic when you’ve just started your own about a similar thing. There’s been no change.
https://buddypress.org/support/topic/why-the-use-of-httpi0-wp-com-with-gravatars/