get_avatar WordPress function and NextEnd

Hi @omgstu

I just checked it on my local test site and the get_avatar() function, e.g.:
<?php echo get_avatar(get_current_user_id()); ?>
worked fine for me, as it displayed the currently logged in users’s avatar that we stored with social login.

If it didn’t work for you for some reason. Could you check please if the user that you checked the get_avatar() function with, indeed have an avatar stored by Nextend Social Login. E.g. in the users table ( /wp-admin/users.php ) we display the avatars by default. Can you see the social avatar appearing there?
Also does the get_avatar() function displays the social avatar, when you disable all plugins except Nextend Social Login and you change your theme to a WordPress default one like Twenty Twenty?

Hi @omgstu

I am sorry, but currently the social avatars can only be retrieved over the get_avatar() function:

• https://developer.ww.wp.xz.cn/reference/functions/get_avatar/

but not the get_avatar_url() function:

• https://developer.ww.wp.xz.cn/reference/functions/get_avatar_url/

However it is on our To Do list, so we may make it in a future release. I will inform you here.

Best regards,
Laszlo.

Hi @omgstu

Nextend Social Login stores the avatars only in one size, and you can find them in the wp-content/uploads/nsl_avatars folder.
This one size depends on the size of the image that the provider returns.

So when you display the image with the get_avatar() function, it won’t create additional sub-sizes of the image, but it will simply get the image with the size that is available and that image will be displayed in an img element with the specified size.

So this is already the max size, I am sorry.

Hi @omgstu

We use the OAuth2 REST API endpoint to get the basic profile information like name, email, avatar.

But returning to the problem with the scaling of the image:
In the current release we have a function hooked to the get_avatar filter, and in that function we are rendering the avatar, but it can not scale larger then that original size.
But starting from our next release ( version 3.0.27 ) we will rather use the “pre_get_avatar_data” filter:

• https://developer.ww.wp.xz.cn/reference/hooks/pre_get_avatar_data/

which means:

• you will be able to get the social avatars with the get_avatar_url() function
• we will no longer need to modify the avatars over the get_avatar filter, so the get_avatar() function will be able to render the image the same way as WordPress does. ( So the images will be able to be scaled up )

We will try to release a new version soon, hopefully before the end of this week.

Best regards,
Laszlo.

Hi @omgstu

I just wanted to let you know we have just released the version 3.0.27 which contains the modifications I described above.
Feel free to give it a try.

Hi @omgstu

Please note that, we can not provide support for custom coding. But I checked your codes and the problem is that, at the point where you are trying to get the avatar with get_avatar_url() function, we haven’t stored the avatar yet, as the avatars will be synchronized on login.

The second parameter of the “nsl_register_new_user” action is the instance of the provider that the user is trying to connect over. Using that you could run the functions of the provider, e.g. you could synchronizing the profile. That way you could get the avatars stored on registration, too.
Here you can find an example code for triggering the avatar synchronization on the action that you used:

add_action('nsl_register_new_user', 'nsl_register_activated', 10, 2);
function nsl_register_activated($user_id, $provider) {
    $provider->syncProfile($user_id, $provider, $provider->getAccessToken($user_id));
};

So in your function, this syncProfile() method should be called before you use the get_avatar_url() and that will fix the problem!

Best regards,
Laszlo.