Accounts Named NNN@facebook Without authmap

Jakob,

I'll work with you to figure this out. I'd like to see the database, to learn more details.

My hope is these accounts were created early on, but are not still be created with the latest code. It could be that multiple account were created for the same facebook user. In that case you would see "1234@facebook" and also "1234@facebook_2" and "1234@facebook_3" as names in the users table.

I'm moving the issue to mayor as it runs the module almost useless.
Also moving to Facebook Connect, as it is (I think) the one in charge of creating the user link.

There is no need to enable the canvas module to get this result. I was having this behaviour and canvas nodule was disabled.

It happens with both users name options (User friendly, or Machine friendly).

If have some time will do some more testing.

Cheers

I am also having this issue. I just upgraded to the latest build. For account created with the earliest code I am also getting this on some pages:

Failed call to users.getInfo: Invalid API key 101. (logged into facebook as )
Exception: 101: Invalid API key

Thanks for all your work on this great module.

Ntrepid

Subscribing,
I tried to go back to the previous version, after some work, i still have
Accounts Named NNN@facebook Without authmap in the status report
In y log report i have

Failed to get app properties for Artic Landing Page.: Session key specified cannot be used to call this method 451
exception 'FacebookRestClientException' with message 'Session key specified cannot be used to call this method' in /home/xfaceboo/public_html/sites/all/modules/fb/facebook-platform/php/facebookapi_php5_restlib.php:3374
Stack trace:
#0 /home/xfaceboo/public_html/sites/all/modules/fb/facebook-platform/php/facebookapi_php5_restlib.php(2891): FacebookRestClient->call_method('facebook.admin....', Array)
#1 /home/xfaceboo/public_html/sites/all/modules/fb/fb_devel.module(127): FacebookRestClient->admin_getAppProperties(Array)
#2 /home/xfaceboo/public_html/sites/all/modules/fb/fb.module(758): fb_devel_fb('init', Array, NULL)
#3 /home/xfaceboo/public_html/sites/all/modules/fb/fb.module(105): fb_invoke('init', Array)
#4 /home/xfaceboo/public_html/includes/module.inc(483): fb_init()
#5 /home/xfaceboo/public_html/includes/common.inc(2676): module_invoke_all()
#6 /home/xfaceboo/public_html/includes/bootstrap.inc(1203): _drupal_bootstrap_full()
#7 /home/xfaceboo/public_html/includes/bootstrap.inc(1110): _drupal_bootstrap('fb_init', Array)
#8 /home/xfaceboo/public_html/index.php(16): drupal_bootstrap('init')
#9 {main}

the url is http://xfacebook.artic-group.net/node/46/?fb_page_id=126770517367139

Thanks for your help, my site was in production and i saw the old fb not supported so i tried again to update, but now, i am unnable to go back and working.
Regards
Enrique

Please help I cannot make it working anymore

You'll have to submit a new thread to this issue queue. This thread is another topic.

Make sure you read the README.txt and the upgrade guide first.

@egarias:
Moral of the story, ALWAYS, ALWAYS test first.

Yes @jm.federico allways the same errors come again.
The "not supported" placed me in the bad way.
Nevertheless Drupal is well done, i have installed many different modules and you allways are safe if you know the basics, to go back and forward if some error appears, rarely you have to restore the database. I don't think all of us make backup when upgrading typical modules.
Fb is an excellent nodule, EXCELLENT but this "not supported" .... anyway is my error.
My only hope is this issue "Accounts Named NNN@facebook Without authmap" shold be fixed soon.

Thanks to all, and i will be happy if i can contribute anyway

You should always backup your database before running update.php.

And you should use more caution when upgrading a module major version. That is, going from 2.x to 3.x is a major upgrade. Going from say 2.1 to 2.2 is usually easy.

And in this case, modules/fb 2.x uses older libraries that facebook no longer supports. They have removed all documentation and tell users to use the new libraries. That's the big difference between modules/fb 2.x and 3.x - the libraries that come from facebook.

@Dave Cohen
I know facebook is pushing everyone to update to their new API, but IMHO version 2 should be left as supported. Version 3 has at least 1 bug (this one) which is quite critical and will put a lot of people onto this position where they upgrade per your recommendation and, bum, things won't work.

I'm not saying development should continue in 2, but until this version has no major issues, ppl shouldn't be recommended the upgrade.

@egarias
backup and migrate (http://drupal.org/project/backup_migrate) is what you need. Set it to do automatic backups every hour or so and to keep them for a day.
You know? best practice dictates that you should keep a backup of your things, updating a module or not. You never know what might go wrong. My suggestion, make daily backups and keep them for 15 days or so, and make hourly backups and keep them for a day.

Cheers

People keep installing the 2.x branch and reporting bugs in it, so its not like that branch is bug free. (It might have this bug, too.) I removed it from the project page so that people would stop downloading and installing it. If drupal.org gave me a way to leave just the 6.x-2.x-dev release, I would. But there's no way to do that.

For what it's worth, I get this authmap error in my status report with a site built on the dev version of code from today and a brand new database. Not sure it's related, by my facebook login/session keeps dropping and returning as I navigate my app - will post more when I have more diagnostic info.

A recent update changed things to use the fb_user table, instead of authmap. However the test for the status report was not updated. in short the status report is probably broken, not the authmap table.

Please change the {authmap} in fb_devel.install line 34 to {fb_user} and see if the problem goes away. Below is the full patch I'm testing.

Index: fb_devel.install                                                                                          
===================================================================
--- fb_devel.install    (revision 2917)                                                                          
+++ fb_devel.install    (working copy)                                                                           
@@ -31,12 +31,12 @@
                                                                                                                 
                                                                                                                 
     // Confirm no accounts without authmap.  The problem caused by old bug, should only occur on sites that have been upgraded.                                                                                                 
-    $result = db_query('SELECT count(u.uid) FROm {users} u LEFT JOIN {authmap} a ON u.uid=a.uid WHERE u.name LIKE "%@facebook%" AND a.uid IS NULL');                                                                            
+    $result = db_query('SELECT count(u.uid) FROM {users} u LEFT JOIN {fb_user} a ON u.uid=a.uid WHERE u.name LIKE "%@facebook%" AND a.uid IS NULL');                                                                            
     $count = db_result($result);                                                                                
     if ($count) {                                                                                               
       $status = array(                                                                                          
-        'title' => $t('Accounts Named NNN@facebook Without authmap'),                                           
-        'description' => $t('Drupal for Facebook may have failed to create authmap entry for these accounts.  Please report to the Drupal for Facebook issue queue, we are working on a fix.'),                                 
+        'title' => $t('Accounts Named NNN@facebook Without fb_user map'),                                       
+        'description' => $t('Drupal for Facebook may have failed to create a map entry for these accounts.  Please report to the Drupal for Facebook issue queue, we are working on a fix.'),                                   
         'value' => $count,                                                                                      
         'severity' => REQUIREMENT_WARNING,                                                                      
       );                                                                                                        

Dave,

That cleaned up the status report for me. Thank you.

Marking this as fixed. But if still a problem for anyone, please re-open. just checked in the patch above.