JFBC and EasySocial

I'd recommend trying to use JFBConnect along with the standard EasySocial registration flow instead of the JFBConnect mini registration view. To do that, simply change the "Registration Component" option in JFBConnect to EasySocial. Then, users that register will go through the EasySocial registration flow with their information pre-filled (or hidden). That will allow the user to see the permalink field and be forced to fill it out.

Please make sure that you have the username field mapped to the correct field in the JFBConnect > Profiles > EasySocial tab. If you try the registration component to EasySocial above, it should be populated and you'll be able to edit it as you've configured in EasySocial.

Let me know if this helps.

-Melissa

I am having a hard time reproducing the problem on my test site. Could you give me details on the following:

* Version of EasySocial that you're using
* In your Profile type, for Custom Fields > Profile Permalink > what are the values for Required, Appear During Registration
* Could you provide a URL where I can see the behavior in action? I attempted to create a user on the site for which you last ran Autotune, but the account was automatically created and I did not go through the EasySocial registration flow.

-Melissa

Yes, it seems that Automatic Registration is enabled. If you want the user to be able to enter the permalink, to go through the EasySocial registration flow to set it, 1) the registration component must be set to EasySocial and 2) Automatic Registration must be set to no. Sorry that I didn't point out the second condition in my original response.

JFBConnect can't automatically correct issues in EasySocial that are already there. You'll need to update those user's permalink's manually or choose some other way to force the update. We always recommend rigorously testing JFBConnect to make sure it does what you need it to do. After it creates a user though, we don't have any control how EasySocial or any other extension uses or updates that user.

I hope that helps explain. I'm not sure what more we could do to help update the values in EasySocial, but if there's something else you need, please let us know.

Thanks,
Alex

If you're using the manual registration process now, is it properly storing the alias as you want it to? Previously, with automatic registration, it's probably true that JFBConnect didn't store the alias in the social_users table because it wasn't set. However, since the user is able to set it now in the EasySocial registration flow, is that working for you?

Let us know so we understand what issues remain going forward and we'll gladly help however we can.

Thanks,
Alex