Topic-icon EasySocial - jFBC

Active Subscriptions:

None
10 years 3 months ago #57328 by imnlimited
EasySocial - jFBC was created by imnlimited
Two issues:

1) When user uses JFBC to register with Social Profile on our community they are not automatically assigned to a Group as we have configured for all new users. When you use non-social registration (ES standard) then the new user is automatically added to the group (OpgroeiGids) as per (profile) configuration. However this does not happen when they register with their social profile.

2) Google+ Default Avatar instead of User's Avatar or Default ES Avatar. After investigated long time ago, I noticed those user registered in your site is actually register via Jfbconnect Google social connection.

For now I am not really sure if Jfbconnect is suppose to get the avatar from Google plus user account yet, because I noticed the reason why it didn't show Easysocial default avatar is because this Google plus default avatar 4.bp.blogspot.com/-ZzOpik5sFZg/UleI27zMJ...1600/profileicon.jpg already stored as Easysocial user avatar after done the registration part.

Can you assist us with this please?

Thanks,


Andrew
The topic has been locked.
Support Specialist
10 years 3 months ago #57332 by alzander
Replied by alzander on topic EasySocial - jFBC
1) Can you tell us what setting you are using in EasySocial for this? We don't currently look at every setting possible within ES during the registration process, so it's likely just something we don't support yet. To be sure, are you adding the user to a user group (like registered, admin, etc) or to a Group page within EasySocial? Also, are you expecting *all* users to go into that group, or just ones that register with a social account?

That will help us understand more.

2) Google+ doesn't have any way to automatically detect if the avatar they are sending us for a user is a real avatar or if it's that blue shadow default one. We have a method that *tries* to guess if it's the default based on the size of the image that's returned. However, Google changes their default a lot (even a one pixel difference or just re-saving it on their end with different compression changes it), which means our method isn't always up to date.

Unfortunately, that behavior with Google+ is just something that happens and there's no way around it if you want to try and import the user's actual avatar. Google, of course, isn't updating Google+ anymore, so I don't expect any improvements to their API soon.

I hope that helps explain what you're seeing, at least, even if it doesn't really help with either issue for now.

Thanks,
Alex
The topic has been locked.