Login redirect losing subdomain

We close old posts after 45 days of inactivity to prevent them being resurrected from the dead..

In your case, Facebook is actually the odd-man-out. For Google, Twitter, and others in the future, the code to do what you're looking for would be in the /components/com_jfbconnect/libraries/providers/google.php file. Around line 55, you'll see:Update that JURI::base() how you did with Facebook.

One thing to note is that Google requires *every* possible callback URL to be defined in your Application. That was covered in the Google+ setup instructions (step 10). Please make sure you add all the subdomains possible for your site there or G+ authentication won't work for them.

I hope that helps,
Alex

That's what I like to hear! Glad that helped. Just so you know, we did investigate this quickly for the v5.2 release, but it will *not* be in that release. So you'll need to make a similar change when you upgrade. There will then be a similar change for Twitter that you'll need to do.

We're still investigating adding the check for a switched subdomain in a future release, or, at the least, we'll add code that you can modify in just one spot to make the change.

Thanks,
Alex

The change for Twitter is similar to that for Google. Edit the /components/com_jfbconnect/libraries/provider/twitter.php file. Around line 30, you'll see:Do your magic on that URL. I'm also going to try to make a new "getCallBackUrl" function in a future release so that you can edit the code in only one place for all providers. It'll make both of our lives easier

Just upgraded to 5.2 - works great - you need to remind users to clear CDN/CloudFlare/etc as older JS probably caused my initial concerns - everything is fine now.

Glad to hear it went (mostly) smoothly. A lot of work goes into trying to ensure that for everyone. As for CDN's, we do add a new query string to our Javascript so that it can be reloaded by the CDN. Some ignore that, depending on how aggressive they are.

Another question - slightly off topic from this thread... I want to migrate to EasySocial from JomSocial. I noticed that the EasySocial plugin wasn't installed (obviously) since I currently don't have it installed. Once I install EasySocial, what's the best way to install your EasySocial plugin?

Either re-install JFBConnect which will re-detect your configuration. We'll likely have v5.2.1 out in a week with some minor bug-fixes, if you want to wait till then. Of course, that means re-making the modifications.
Otherwise, you can unzip the component file you downloaded from here and install the EasySocial plugin manually from the /admin/install/packages/socialprofiles directory.

Just letting you know the above, even though you already got it installed.

However, I still can't see JFBConnect login icons on our frontpage (now easysocial) - I've opened a ticket with StackIdeas, but I'm not sure if it's a JFBConnect issues or EasySocial issue. I think ES since it was working fine under JomSocial before the switch. Comments?

JomSocial has some specific integration to automatically add our buttons when enabled. I chatted with the StackIdeas guys this weekend, and that is (hopefully) in the pipeline.. feel free to nudge them on how awesome that would be Until then, you'd have to edit their template files and add the buttons manually. I can help out with doing so if you'd like instructions.. but I don't know it offhand yet. Just let me know!

Thanks,
Alex

Glad you hacked something in that works for you. My plan was to investigate how/where to do that today. If you don't like your solution, let me know what you did, and we'll gladly check to see if there's some better way to do it.

The SCLogin module should be updated in the v5.2.1 release of JFBConnect (next week) to add the EasySocial options.

Thanks,
Alex