Compatibility with Facebook API 2.2

Thanks man.. - I was about to do a similar patch!

Does it really work? Did anyone tried it?

I'm including this in the dev release of February 14, 2015

Awesome guys! This would be great. I've been worried about this pending deadline on one of the sites I have as well.

I considered incorporating this into a new, to be created, 2.x release of this module, but as it turns out, there is no actual functionality change for fboauth to use Facebook API 2.2. The only change is adding '/2.2' on to the end of 'graph.facebook.com' in the url. So, I'm planning to keep it in the 1.x version of the fboauth module.

Great! Will you be releasing a 1.7 soon?

Yes, lets make sure the dev version doesn't have any other problems in it for another week or so and then I'll roll a 1.7

I suggest to change version of the module to 7.x-2.x because new version with Facebook API 2.2 already broke following task #2149661: Users with empty mail field..

Otherwise it will break websites of users who update from 7.x-1.x to 7.x-1.7. It looks like minor update, that is not really so.

I don't think it break anything. Email is optional permission, so user can opt out it, even in v1.0. My first Facebook user without email registered on Jan 2nd 2013, long before the Facebook API 2.0 was introduced.

BTW we need to fix 6.x branch, too.

Is this going to be fixed for 6.x?????

I'm not sure. I have no time for this.
Maybe someone will fix it. I can commit patch with fixes.

If some one fixes it and you commit it, Ill use it :)

The patch in #14 works partially, I had to modify the file fboauth.fboauth.inc a little bit more to make it work because response from facebook come in json format, so the function fboauth_access_token has to be modified like this:

  else {
    /*
    // The result from Facebook comes back in a query-string-like format,
    // key1=value1&key2=value2. Parse into an array.
    $authentication_strings = explode('&', $authentication_result->data);
    $authentication_values = array();
    foreach ($authentication_strings as $authentication_string) {
      list($authentication_key, $authentication_value) = explode('=', $authentication_string);
      $authentication_values[$authentication_key] = $authentication_value;
    }
    */
    $authentication_values = json_decode($authentication_result->data, TRUE);
  }

Sorry but I can't provide a patch.
I hope it helps someone.