Miled

update wsl if your are using an old version.

if it doesn’t solve the issue, then try this: (THIS NOT RECOMMENDED THO, this “could” make fb works but you need to resolve it somehow on your server setup)

--- hybridauth/Hybrid/Providers/Facebook.php
+++ hybridauth/Hybrid/Providers/Facebook.php
@@ -31,6 +31,8 @@
 			require_once Hybrid_Auth::$config["path_libraries"] . "Facebook/facebook.php";
 		}

+		BaseFacebook::$CURL_OPTS[CURLOPT_SSL_VERIFYPEER] = false;
+
 		$this->api = new Facebook( ARRAY( 'appId' => $this->config["keys"]["id"], 'secret' => $this->config["keys"]["secret"] ) ); 

 		if ( $this->token("access_token") ) {

dunno what it could be.. but here is how compatibilities issues are “usually” fixed:

1. reinstall wsl
2. reset networks settings (by reset i mean check u apps credentials and hit save)
3. reset widget settings (try to change “Authentication flow” to “No popup window”)

Please. what I’m talking about is “opinions” not “GPL”. as explained here: http://www.gnu.org/philosophy/selling.en.html, selling WPML is legitimate and it’s their right to do so.

WSL was made a free software, free as in freedom and price alike. the fact that someone have paid for WPML shouldn’t make him any better _no offense_ than the rest of WSL users, meaning: if this feature were to be implemented then it must be available for anyone and everyone. furthermore, if I were going to bother spending my time working on something, then it won’t be on making WSL compatible with a “commercial” plugin.

Have you tried using the shortcode or it doesn’t work either?

many thanks @goodevilgenius!

I guess I’ll take it from there and attempt to find a workaround for this issue.

@ivnus, its already done deal. and also, in the current state and when it come to bp, wsl is barely able to display the widget where it should be and to auth users. so there is no point reporting issue related to that..

and btw, I’m still waiting for the coffe 😛

to be honest I have no clue how this “multisite” even works.. when writing wsl, I took into account some recommendations I read about the subject here and there, but I never tested it due to how lazy/busy I am.

On another note I found that you are a developer, so if you could fix that it would be amazingly awesome!

its really hard to know the exact reason for as there is many.. but it was reported that this could happen when the callback url is misconfigured or missing on dev.twitter.com