User not logged in after registration

A possibly relevant update: I just noticed that, after doing the basic registration attempt with the Facebook button, there is no entry in fb_user for this newly-added user. However, once I give the user a password and then have the user log in (cf. "What I CAN do..." above), an fb_user entry for that user is created. Hope that helps...

One more thing: I have the app's settings in DfB configured as "Do not create accounts automatically" and "Map account when both local uid and Facebook id are known". Maybe I need to do this latter bit of work myself?

Thanks for the note. Some of this is my own fault, as I've got a certain amount of custom funk around the reg process (getting values for and setting profile variables). But, as a test, I set up DfF on another D6 site that just does a standard reg process. This one was configured as "create local account if user has authorized the app", and, when I use the Facebook Connect button to register, everything works the way it "should" -- a new account is created, and the user is logged in to it.

Anyway, I'm starting to get a handle on the architecture here, and will explore the submit handler matter. Login toboggan is a good pointer; thanks much!

Just to restate what I'm seeing here, for clarity:

* On a site that I have configured as "create local account if user has authorized the app", DFF creates a new Drupal user, links that user to his Facebook account, and logs him in.

* On a site that I have configured as "Do not create accounts automatically" and "Map account when both local uid and Facebook id are known", DFF creates a new Drupal user, but does not link him to his Facebook account (even though he's currently logged into Facebook) until hs logs into Drupal with a Drupal-assigned username and password.

There may be other things going on wrt my profile variables, but that's to be defined.

Progress, of a sort: The following _user hook successfully logs in a user after authenticating with Facebook (per my issue above):

function zzz_mymodule_user($op, &$edit, &$account, $category = NULL) {
	global $_fb_app;
	if ($_fb_app && $op == 'insert') {
		// We have a facebook app, and are inserting the new user into the database:
		// Log in as the newly-created user, using code stolen from user_authenticate_finalize in user_module
		$user = user_load($account->uid);
		$user->login = time();
  		db_query("UPDATE {users} SET login = %d WHERE uid = %d", $user->login, $user->uid);
  		// Regenerate the session ID to prevent against session fixation attacks.
  		sess_regenerate();
	}
}

Fortunately, my module has a lower weight (due to its filename) than fb_user, so fb_user_user has run and done the preparatory work. If your module is aaa_mymodule, you would probably not be so lucky, and might have to explicitly fiddle with the module weights to get things ordered properly.

CAVEATS: I don't really understand what I've done here other than solve my short-term problem. I may be introducing all sorts of awful things into the register/login process. You'd have to be crazy to use the above code. Stop, now. Really.

Having said that, it does at least succeed in getting the user logged in after the FB registration. I'd love it if there were a more principled solution to this problem (i.e. one written by somebody who actually knows what he or she is doing).

Just checking in,
Jim