Invalid License
If you get an invalid license You can go to your account page and click on View licenses to check your license number.
If you already activated the plugin on a staging site and now you want to migrate to the live site, then you can click on manage sites to deactivate the staging site and enable the live site.
Also it could be due a curl problem in your server that can’t communicate with ours. To be sure that’s the problem install the following plugin to test it.
And if it fails the possible solution is this one.
You receive a Gmail ‘suspicious login attempt
Go to https://accounts.google.com/DisplayUnlockCaptcha with your Gmail Account and then try again.
Google uri redirect mismatch
Check in your google console that the callback url is configured properly. Be sure to choose http instead of https. Please go again throw google settings.
Linkedin ‘Authentification failed. The user has canceled the authentication or the provider refused the connection
Check that your server time is properly configured. Go to the debug tab and check for SERVER_TIME. If the minutes have a 5 min difference between real time linkedin won\’t work. Contact your hosting to fix the server time
Invitations are not going out. You see invitations in QUEUE but queue is not locked
Most probably your WordPress virtual cron is not working properly. Try configuring a server cron.
Invitations are not going out. You see invitations in QUEUE and queue is locked
Something went wrong! It\’s time for debugging. In the meantime you can unlock the queue using the link provided on the debug tab.
Icons are not displaying and you see squares instead
That usually happens because you are using a cache server or serving fonts from CDN. To solve this you need to do the following:
If you are using nginx / varnish try adding this to you server config file:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
location ~* \.(eot|otf|ttf|woff)$ { | |
add_header Access-Control-Allow-Origin *; | |
} |
If you are using apache you can add this to .htaccess file or httpd.conf file:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Apache config | |
<FilesMatch ".(eot|ttf|otf|woff)"> | |
Header set Access-Control-Allow-Origin "*" | |
</FilesMatch> |