JFBConnect Compatibility with Other Third-Party Login modules?

Yeah, that's what I was talking about above when I said:

f you want their exact styles for hovering and such, it's a little more complex as we need to make sure that our login functionality is always called, not theirs. You can try the below, which may work, but also may not fully override their Javascript:

Glad you tested more.

You should definitely disable their FB integration and not add your App ID / Secret key. Taking a very quick look, I'd say edit the tmpl25.php file. Find the line that looks like:Edit that and make it look like:That just removes the check for whether you enabled that setting or not.

Good luck,
Alex

Haven't looked at the tmp15.php file, but I believe it's pretty much the same. Look for that same line and see if it's there, if so, alter it like I mentioned above.

Good luck,
Alex

I have looked, I'm not sure what's happening though. This is getting back into an area of not knowing your login module well enough. It will take some time to look into and understand what's going on with their extension. At this point, again, you may want to contact their developers to see if they understand the issue better and can provide a solution faster.

We'll try to get you an answer later this week, but I can't guarantee anything faster than that. There are other issues that are JFBConnect-specific we're working on right now for some users. Sorry for the trouble.

Alex

Sorry for the delay in getting back to this. We've been swamped with the upcoming v5.0 release of JFBConnect and v2.0 release of JLinked. I finally had some time to investigate further, and think I found the issue.

In the tmpl15.php file, there are actually 2 lines that include the social.php file:andI had you change the first one above, where $socialpos=='top'. My guess is that you have the module parameter set to show the social button at bottom, so my change made the social.php file be included in both spots. Since that's what you're seeing, I'm pretty sure I'm on the right track...

Anyways, the fix should be to undo the change I suggested above and then modify the 2nd inclusion line. When done, you should have the $socialpos=='top' line look like:Frankly, you could even delete that line, since it should never execute (since $socialpos is not equal to 'top'). Then, the bottom line should look like:As always, test, and let us know how it goes. Things are finally settling down a little so we should have a little more time to investigate extra stuff like this that isn't directly related to our extensions.

Best of luck,
Alex