David,
I'm glad to hear things seem to be working for you now. I'm not sure why the links were causing a fatal error before and aren't now. In the next SCLogin release, we have an update to our code which should prevent the fatal errors in all cases (if you want/need that change now, just let me know).
As for the registration using the EasySocial component, that *should* work as well, of course. We do a lot of testing with that registration flow to make sure that social logins can work while using the registration path of other extensions. If you register normally through EasySocial, I'm assuming you're not running into those problems... it's only when you do the social registration with JFBConnect?
Either way, if you're satisfied with using the JFBConnect registration flow, that's great. If you need more help, just let me know and we'll do what we can.
mh1,
Sorry for not getting back to your question earlier. The changes you mention shouldn't have been causing the problem. We use EasySocial's API to fetch the user's avatar, and those calls were updated with their latest release to respect their own configuration values.
If you are still having the fatal error and want the fix that we're implementing in the next release of SCLogin that should fix it, please let me know. We'll gladly post it. It's very simple.
Thanks,
Alex