Plugin Support
Laszlo
(@laszloszalvak)
Hi @mishaml
First of all I am glad you like Nextend Social Login! 🙂
As for the problem:
That check is a part of a security measurement, so we won’t try to link social media accounts automatically to existing WordPress accounts if the email address of the social media account is not verified. So please make sure you keep that code part there.
However in your case, that error is quite strange, as the getProviderEmailVerificationStatus() is overriden in each extending provider specific class, so ultimately the getProviderEmailVerificationStatus() should return a boolean value and we should allow or prevent the autolinking based on that. You should never receive the “Email verification status is not checked in this provider!” error, as that exception is rather for us ( the developers of the plugin ) to make sure the getProviderEmailVerificationStatus() is implemented in each class.
So I find it possible that somehow the update failed, so some of our files on your server are not up to date, thus don’t have that getProviderEmailVerificationStatus() override in the provider specific classes.
To avoid such problems, first of all I would suggest you to try the following:
- go to WordPress > Plugins > Installed plugins
- delete your current Nextend Social Login installation
- connect to your FTP ( or use a file manager plugin ) and make sure there is no “nextend-facebook-connect” folder in your /wp-content/plugins folder
- then install Nextend Social Login from the official WordPress plugin repository just like you did the first time.
- if you have OP cache, then don’t forget to purge it, e.g. with a plugin like this: https://ww.wp.xz.cn/plugins/flush-opcache/
- then check the login with a social media account that:
-is not linked to any WordPress account yet
-but there is an existing WordPress account with its email address already
so we will run our autolinking specific codes.
If you still see a problem even after this, then please get in touch with us directly over the ticket system:
and we will debug this problem there.
Best regards,
Laszlo.
Thanks, the problem was fixed after re-downloading plugin.