user status blocked
Posted Thu, 06/02/2011 - 16:38 by 574233049@facebook

I am just about to start using Drupal for facebook on a site for the facebook connect part and I am wondering what happens when you set a users status to blocked after their account has automatically been created when they logged in with facebook.
Does it stop them logging into the site altogether. Does it stop them from creating another account if you also allow anonymous users to create accounts?

‹ Connect and create local account without clicking connect Like and Send buttons work normally if all drupal for facebook modules are unchecked but won't allow comments otherwise ›

I'm not sure!

by Dave Cohen - 06/02/2011 - 21:50

Huh. I don't believe I've tested that.

What I'd like it to do is show that your are connected to facebook, but leave you anonymous as far as drupal is concerned. Or perhaps just give you access denied.

But what it actually does I'm not sure. Please let us know if you find out.

I've somewhat tested this,

by 608555728@facebook - 06/03/2011 - 21:50

I've somewhat tested this, but my site does not allow anonymous logins and is a strict facebook app... but if the account is created by drupal for facebook and uses the same account name for both when you block a user it will give him a "You are not authorized to view this page." I then tested what would happen if the user de-authorizes the app and attempts to authorize again, it will give a message "The account was not created. User name has been blocked" or somewhere along those line. I doubt this would work this way if the user creates an account in durpal then links it to their facebook account though.

I have just been

by 574233049@facebook - 06/05/2011 - 11:16

I have just been testing....
This is all with the setting 'create local account' set at 'If user has authorized the app'
When a user has logged into the site with facebook previously, and then I set them to blocked. They see errors like above.
If they then create a new account via the site (without using facebook connect). they can use the site as per usual as this new use....But if they are connected to facebook when logged in as this new user it seems that drupal for facebook logs them in with their old account and and they see the same errors. Did that all make sense?
I might try to hook into this so when DFF tries to log them in with their with facebook connect and sees that the original user is blocked, it will block the current user too.

My app also required the 'email' permission but I don't know if that had anything to do with the above.
Also, I tried to user the 'FB Extended Permissions' to add email address access as a required permission but facebook sent back errors, so had to do it myself in the 'fb_required_perms_alter'.

Now the next thing to test....the 12352345@facebook username problem...any pointers? use 'theme_username'? how does this site do it?

When logged into facebook, it

by Dave Cohen - 06/07/2011 - 22:29

When logged into facebook, it changes the drupal session. That's why you see them as the drupal user connected to the facebook account.

modules/fb is not specifically doing the user blocking. It's using an underlying drupal api, and that's where the error messages are coming from.

This site used modules/fb/fb_connect.module, which overrides the normal theme function for user names and pictures. Your site should get this by default if fb_connect.module is enabled.

so I don't need to create an

by 100000431342020... - 06/07/2011 - 09:50

so I don't need to create an account to comment?