fbconnect unable to register users where there are modules that affect registration features

do you use "fast registration mode" ?

I have the same issue, I have tried both fast and reg registration and it is saying it is failing due to terms of use.

I get errors when trying to use fast register saying terms of use must be accepted Does anyone know how this can be fixed?

The problem with Gigya is that it costs $15,000 for sites with volume.

The problem with Gigya is that it costs $15,000 for sites with volume.

The terms of use module gives the error is there a way to bypass or add it to this for the fast connect

The terms of use module gives the error is there a way to bypass or add it to this for the fast connect

what do you mean ? explain pls

Well, basically, you cannot use fast registration with the terms of use module enabled.
Why? Because the terms must be selected as "read" or the form returns an error as it is a required item.
If this is turned off then the FB connect works as expected BUT when you do not have the Terms of Use you have no way of requiring members to accept terms for legal reasons.

I think it's not a bug. I can't mark/enter automatically all required items as well

the only way that I see is to output registration form with only required fields (except login/password/email)

what do you think ?

I am confused by your reply can you please clarify? When the terms of use module is enabled it REQUIREs the user to accept the terms, So, when you try to use facebook fast registration what happens is the terms module says hey wait you must accept me and yet it cannot be accepted as it requires the drupal standard registration to be done. So, I wonder if?
A. The terms of use could pop up with FB fast registration to allow it to be checked
B Bypassed?

Thanks for your efforts and input.

A: Probably I can hack the form to hide some elements
B: Also I can create new user account without user_register form (to use user_save directly)

Wonder if there is a way to work in the terms of use module as so many people use it?

Came up with a work-around for this. Create a "page" and set the path_auto url to fbconnect/register/prompt. On that page, explain that the user will have to create an account and link their fb account after they have registered and provide a registrater link.

The path_auto page url will override the drupal hook at that same url and your page should show when the user clicks the "log in with facebook" but then is presented with the option to create a new account with that facebook page (Or at least it does for me. Anyone else have problems with this?).

It's not perfect, but it will work until a solution to this is found with the module.

sry, dubble post

One solution is to let other modules alter the $form_state array with drupal_alter()

See my patch for how is is implemented in fbconnect.

Other modules would then be able to to something like this

function mymodule_fb_fast_reg_mode_values_alter($form_state) {
  $form_state['values']['terms_of_use']  = 1;
}

Using the patch, while installing the module there's this error:
Parse error: syntax error, unexpected $end in fbconnect.pages.inc

Would be great to incorporate terms of use to facebook connect so that it could be checked on the form using either login method-Drupal or FB Connect.

A suggestion for this module would be to implement how the FBconnect works with the Polldaddy registration form.

http://polldaddy.com/signup-free/

When you click on the fconnect button, it shows a message to accept the TOS and that's it. Quite smooth sign up process actually.

FYI, twitter module (which can be used for login/registration the same as this one) does this without an issue. I only mention it because it may want to be mined for code.

For now, my solution was to install captcha alongside mollom and use captcha for user registration and mollom for everything else. When this fix is working, it'll be easy to switch back to mollom.

The problem is well documented, but still vague. Essentially, you can't complete the facebook connect module registration workflow on a Drupal site when you are using Mollom as your account registration (in the case of FB connect /fbconnect/user/registration) form protection.

My workaround is to keep Mollom on the site as the primary captcha solution and simply disable it for the registration form. In it's place, you can quickly setup the re-captcha module and use it only on the registration page. I tested the workflow and everything is fine.

This solution is a bit bulky, but will work until new releases or this bug is fixed.

Subscribing,

CarbonPig.com

Some good news. The legal module works with Facebook connect fast registration. The only issue we noticed (after spending a whole day hunting it down) is that when setting fast reg make sure Manual is set under login/out the auto login caused a redirect loop from firefox but perhaps we could get the fixed going forward.
The legal module bypasses Mollom too so it goes through the whole process great. hope this helps someone.

This one bugged me for a while. For sometimes I had both Mollom and reCaptcha installed as suggested in #28, but I was not satisfied by this workaround: too much memory used by reCaptcha and non homogenous captcha on the website.

So I found another workaround, I figured I don't really need the (Mollom) captcha when someone register via fbconnect, as most bots will fail to fill the facebook login popup box (at least I hope so...) so I simply removed the mollom captcha on the fbconnect register page.

With fbconnect installed and mollom installed and activated on user register page (+ user lost password page, but not relevant here)

/**
 * Implementation of hook_form_alter().
 */
function YOURMODULE_form_alter(&$form, $form_state, $form_id) {
  if($form_id == 'fbconnect_register_page') {
    unset($form['mollom']);  // remove mollom captcha display
    $form['#validate'] = array('user_register_validate'); // keep only necessary validate handler
    $form['#submit'] = array('user_register_submit', 'fbconnect_register_form_submit'); // keep only necessary submit handlers
  }  
}

Any news on CAPTCHA Issue resolution?
Please give us a feedback.

Closing the issue. It was inactive for a long time & it's related to a Drupal Version which is not supported anymore