× Joomla Facebook Connect support forum

Topic-icon CB required fields and full Joomla registration

Active Subscriptions:

None
12 years 7 months ago #14006 by guero
Hi!

I'm also facing the same problem that a CB user is not created in the DB if I have required fields. I only see the Joomla User in the database. Is this problem already covered by your latest version 4.0.2 ?- I'm using 3.2.2`. - Community Builder 1.3.1 gets used.

I have seen your proposal "Show Non-Mapped Required Fields:yes" at FB registration - but if I leave some fields empty I do not get a warning anyhow the user is logged in but the profile is still unconfirmed/unapproved?

Is there any workaround available that the CB user gets forced written to the Database with state confirmed/unapproved but the requiered fields are empty?
After the FB registration we redirect the user to the profile edit page. We have installed the CB Progress Field Plugin+/CB Triggers so that the user will see the profile edit page until all required fields are filled out correctly. If the user clicks on other links/menus or what ever an automatic redirect to profile edit page will be done by the CB Progress field plugin.

Hope you have a quick workaround available

Thanks for your great support

Frank
The topic has been locked.
Support Specialist
12 years 7 months ago #14035 by alzander
Frank,
The 4.0 release has a lot of improvements to the CB plugin for this type of problem, including validation of the required fields and tooltips for those fields (if configured in CB).

There isn't any workaround for writing the user to the CB database without those fields filled in. We use CB's functions to hand it a user, and tell it to save that user. If it doesn't pass CB's checks, it simply will reject the user. It's the only system we integrate with that is that finnicky over the required fields, and is an issue, but 4.0 does improve the situation considerably.

Finally, the 4.0 release has other improvements to the registration/login flow that are required by Facebook as of October 1st (2 days from now). We've sent out a few newsletters, tweets, and blog posts about the change, and hopefully you've seen them. Either way, we'd recommend upgrading to 4.0 for that reason alone, as 3.x likely won't work when Facebook pulls the trigger on October 1st.

Hope this helps, and good luck,
Alex
The topic has been locked.
Active Subscriptions:

None
12 years 7 months ago #14074 by guero
Hi Alex,

Thanks for your response. I am a little (a lot actually) surprised by the last sentence "3.x likely won't work when Facebook pulls the trigger on October 1st. " as in another email / post I understood that we should be fine with 3.2.2 (www.sourcecoast.com/forums/jfbconnect/jf.../2175-jfbc-open-auth ).

Should I be worried now? Please advise.

Thank you,
Frank
The topic has been locked.
Support Specialist
12 years 7 months ago #14086 by alzander
Frank,
That thread was concerning a security issue from Facebook, that JFBConnect was never affected by. The 3.x series uses the OAuth 1.x protocol. Though I was a bit confused at the beginning of that thread (we were in a rush to determine what was going on), I tried to make it clear in the post below that we'd be moving to OAuth2.0 when it was available (which, at the time, was required by Facebook on September 1st, but was subsequently moved back to October 1st).
www.sourcecoast.com/forums/jfbconnect/jf...open-auth?p=2#p10262

Facebook finally released the updated PHP & Javascript libraries at the end of August, and we implemented it in our 4.0 release in early September.

The move to 4.0 was specifically to delineate that it uses the new methods, and is compatible with the change requirement.

In our most recent newsletters and 4.0 release blog posts, we made this very clear. Hopefully, you're following one of these, but both are linked below.
JFBConnect v4.0 Now Available (Newsletter, Sept 16)
JFBConnect 4.0 release post

We auto-subscribe all of our subscribers to the newsletter just because we send out important updates like this, so you would have had to opt-out at some point if you didn't receive it.

Hope that explains the situation. We'll definitely be monitoring things closely tomorrow with the 3.x series as we really don't know what Facebook will do with user's trying to login through the old scheme.. hopefully, there will be a good grace period where they send out notices to admins.. but you never know.

Thanks,
Alex
The topic has been locked.