If you are bugged as well as me by constant 'no authorization' screen whenever you come back to your DfB enabled site while still loggedin as FB user, the reason for that behaviour is "Store tokens in session" option.

Just uncheck it and your visitors will no longer be unrecognised.

IMHO, this option should be checkout by default upon DfB installation.

Comments

Dave Cohen’s picture

Dave Cohen commented

Can you explain how to see this "no authorization" screen? I don't know what you're talking about.

skolesnyk’s picture

skolesnyk commented

My understanding of the option "Store tokens in session" is that it stores FB token in Drupal session. Once session is over, token is lost. Meaning that whenever users comes back he'll have to click on Connect with FB once over. With this option deselected he remains logged in as long as he's logged into FB.

Dave Cohen’s picture

Dave Cohen commented

I'm still not sure I understand you. But I did recently find a bug where the data stored in the session gets stale... that is the cookie gets updated but not the session data. So I'm making a change to give the cookie priority, when both are found.

The storing in the session is intended to help when third-party cookies are disabled in user's browser. I'm not sure it works 100%, as different browsers handle this differently.

skolesnyk’s picture

skolesnyk commented

Checking "Store tokens in session" has an effect of forcing a returning visitor, who already logged in into the site once, to go through login dialogue again.