Disable registration but keep association?

Here's my situation - life was wonderful with JomSocial and JFBConnect (even with multiprofiles) until last night. I installed XIPT (JoomlaXi's JomSocial ProfileTypes) because I simply have to. It has the ability to do advanced searching and ACL based on profile types that JomSocial won't have for at least 6-8 months (and if their track record is any indication, likely more like a year).

The problem is that JFBConnect and XIPT don't interoperate. Let me be clear, this is nobody's fault. It's just the situation.

Registration with JFBConnect brings up a registration page that is not XIPT's, so profile types are only set in JomSocial, and, at that, only the default is set, no matter what is selected, since XIPT gets into the registration workflow and expects its own profile type. When it doesn't see it, it doesn't look at JomSocial's (that JFBConnect properly set) and it presumes the default.

So this breaks registration.

What I'd like to do, for the time being, is disable JFBConnect's registration flow, but still allow users to log in with Facebook and associate. They simply need to register in the normal manner.

Now, that said, JoomlaXi tells me that their PayPlans extension does integrate, so I'm looking into that. But I'd like to do the above, just for now, until I can get this working properly. This is fine, because we do plan to have paid account types, so setting up PayPlans now and forcing it to use a single, free plan is totally cool with me.

But for now... no JFBConnect registration flow at all. Only log-in with Facebook if you're associated and, if you're not associated, only the option to associate with an existing account. If not, the user should use the standard (in this case, JomSocial) registration flow.

How can I accomplish this?

So now, if you click the "log in with facebook," and you're not associated, it takes you to JFBConnect's registration page.

Best case, a single configurable option:

What do you want to happen if someone tries to log in with facebook but must register?

[ ] Use JFBConnect
[ ] Use Joomla Registration
[ ] Use JomSocial Registration

If you hit the default JomSocial, JSPT will actually be triggered because it hooks JomSocial's registration event.

This would get the job done, I think.

Works. Here's what I replaced your code with:

This makes it very non-confusing for the user Now, of course, there's no Facebook profile being brought down, but that's okay. They can associate later. So in cases where a site admin has XIPT loaded, this removes any bifurcation of the registration flow.

Now... another thing you'll want is an option in SCLogin for XIPT that goes to the route, above. Right now, my XIPT goes to JomSocial, but if you added XIPT as an option, it would go there directly and avoid an extra plugin trap and redirection.

The *real* fun will be in integrating Facebook signup with XIPT. This is because XIPT does all kinds of field manipulation based on profiletype. This might make it tough for you to fill in the fields with Facebook values. I suspect you'll need *them* to consume your data, once set. That's going to be some discussion between you and them, I think.

Again, though, they say they may have done this work in PayPlans. I'll know in a few days when I purchase and integrate that to see what it does.

But for now, this gets me what I needed and should get you simple bypassing for XIPT for anyone who wants it.

Okay, so let's talk about this now - the way XIPT works is that if you point to its registration instead of JomSocial, or you tell it to "take control" (in which case it hooks into JomSocial's registration trigger and imposes itself first) it asks you to pick a profile type. It then persists this profile type on subsequent queries into JomSocial's registration system and, using JomSocial's triggers, does its own thing when user accounts are created or profile fields are assembled.

Where would you see JFBConnect getting involved in order to be a part of the process?

Right now, you have your own registration system that pre-fills fields based on your mappings. Personally, I love this, but it means that one cannot use JomSocial's registration system and templates, which I don't like.

Ideally, I'd love for you to abandon your own registration flow in the case where JomSocial is installed and, instead, hook their notification that registration fields are being prepared and inject Facebook's values there if the registrant came in using your system. That would not only simplify things by removing the need to have yet another registration shunt, but would allow *any* JomSocial integration to work seamlessly. Then, you could hook onSaveUser (or would it be onCreateUser) to do your mapping and all would be done. Okay, probably not all, I'm sure I'm missing lots, but you get the idea

PS: Right now, what I have is sufficient. What I'm proposing would be better, but thinking it out and doing it right is a good idea. And, that said, I'll be evaluating PayPlans later this week, and JoomlaXi *says* it integrates. I'm going in with no preconceived notions, so we'll see what they've done.

I love JoomlaXi's design work, but their code occasionally has some serious eyebrow-raising decisions. And the biggest frustration is that they're not native English speakers, and, as such, their documentation is not only useless, but often confusingly misleading. No judgment on their abilities - I couldn't write documentation in French if I had to, but it is what it is. If they hired a native English technical writer to grok their code and do their documentation, they would be heroes.

And here's their documentation on how they integrate with you: www.jpayplans.com/payplans/documentation/item/jfbconnect.html ... have fun with that ;)

Nobody has complained about the registration flow as it stands now, and I'm working on our new quiz system (because we make decent money on ad revenue every time we have a quiz - people love their stupid content), so I'm fine waiting for the next release (or the one after).

This becomes more critical to me when we start rolling new verticals (niche sites) much later this year. A good registration flow on a brand new site is critical. For our main sites now, we're good.

Getting the quiz system to post results to Facebook is my focus this and next week as I finish it up. We have over 30K fans on our Rocky Horror Facebook page, and when we promote a quiz, they flock to the site to take it, and getting results posted will just make that explode. That's why I want to make sure it offers them the chance to post even if they're not logged in, as the vast majority of quiz takers aren't site members, but use the features as guests (quizzes, showings directory, etc).