[Plugin: Facebook AWD All in one] Facebook AWD Error: (#2500)

I got the same problem. i hope he can fix it as soon as posible. 😀

Hi, got the same error. After you login with FB and then when you click on WP logout the error shows preventing any page to display.

The problem might be in the cookies handling. After deleting cookies related to the website (specifically PHPSESSID and fbsr_xxxx) the error disappears.

Edit:
It’s your plugin’s generated error so it’s hard to say from which line of code it is generated.
When enabling WP Debug the following PHP notice shows:
Notice: ob_end_flush() ref.outcontrol: failed to delete buffer zlib output compression. in /wp-includes/functions.php on line 2504 but I have no clue if it is relevant at all.

It happens on all browsers I tried.
Don’t have a public URL yet am testing on local environment.

I nailed the line where the error comes from.
It’s in AWD_facebook.php line 1899.
My WP version: 3.4.2.

Call stack:
wp-content/plugins/facebook-awd/AWD_facebook.php.AWD_facebook->get_facebook_user_data:1899
wp-content/plugins/facebook-awd/AWD_facebook.php.AWD_facebook->login:2079
wp-content/plugins/facebook-awd/AWD_facebook.php.AWD_facebook->login_listener:2070
wp-content/plugins/facebook-awd/AWD_facebook.php.AWD_facebook->parse_request:2187
wp-includes/plugin.php.call_user_func_array:484
wp-includes/plugin.php.do_action_ref_array:484
wp-includes/query.php.WP_Query->parse_query:1674
wp-includes/query.php.WP_Query->get_posts:1920
wp-includes/query.php.WP_Query->query:2941
wp-includes/class-wp.php.WP->query_posts:460
wp-includes/class-wp.php.WP->main:524
wp-includes/functions.php.wp:775
wp-blog-header.php.require:14
index.php.{main}:19

https://www.facebook.com/logout.php?next=http%3A%2F%2Fmytestdomain.com%2Ffacebook-awd%2Flogout%3Fredirect_to%3Dindex.php%26amp%3B_wpnonce%3Db69d42fb25&access_token=AAAEvnD4aoZAgBAGZCRiuSxKHxrrmuAZBZAN8GUm4PGAm28WZBxpEAdoXL0esv1ZCrkZC2y6my8en6xB6IJlaJXAOzdNySFc2AnxcezoO2or9wZDZD

What I learned so far is that error happens not during wp_logout process but after redirect.

Alright. Here is what I got so far:
I’ve changed the option “Url after logout” in your plugin settings. However it didn’t influence shape of the url of WordPress logout link (not the AWD FB logout link). It is still:
https://www.facebook.com/logout.php?next=http://mytestdomain.com/facebook-awd/logout?redirect_to=index.php&_wpnonce=b69d42fb25&access_token=AAAEv…

However, I noticed that it does change the logout button generated by your plugin.
The button name is now the “after logout url” I entered in plugin settings (before it was just the word “Logout”).
The button code is now:
<a href="https://www.facebook.com/logout.php?next=http://mytestdomain.com/facebook-awd/logout?redirect_to=http://mytestdomain.com/users/?action=login&_wpnonce=b69d42fb25&access_token=AAAEvn...">http://mytestdomain.com/my-board</a>

Please notice that redirect_to has value I entered in “Url after login” in plugin settings. And the anchor tag content is: http://mytestdomain.com/my-board which is url which I entered “Url after logout” plugin settings.

The error still appears no matter which logout link I press.

Me again. So the problem you are facing is exactly same as expressed in this post:
http://stackoverflow.com/questions/8517934/facebook-getuser-returns-a-userid-after-logout
The suggested solution is to use function Facebook->api(‘/me’) to determine whether user is logged in.

So workaround I’ve came up with is changing function is_user_logged_in_facebook() in your plugin to:

public function is_user_logged_in_facebook()
{
    try {
        if ($this->fcbk->api('/me') && isset($this->uid) && $this->uid != 0)
                return true;
    } catch (FacebookApiException $e) {
        if (is_object($this->fcbk))
                $this->fcbk->destroySession();
        return false;
    }
}

For the bug I mentioned before (log out redirect url used as a label and log in url used in log out redirection) I’ll create another thread.

Apply the brutal fix above and clean your browser cookies.
However, this version of plugin has many other flaws and am not sure if it is usable at this stage.