Topic-icon JFB comment conflict with existing facebook commenting system

Active Subscriptions:

None
I was using a facebook commenting plugin on my website and it was working fine until I installed JFB. After installing JFB, my old facebook commenting filed stopped displaying. Since I suspected that JFB could be causing this,
File Attachment:


File Attachment:

I disabled the System-JFBCSystem Plugin and it started working again. But, the issue is that without JFBCSystem plugin, JFB connect does not work properly.

My question is the following: How can I get JFB to work without interfering without my other facebook comment plugin. (note: the other plugin has been installed as part of the main component that I am using on my website. If I disable it, then, I will not have the possibility to have facebook commenting anymore unless I do a lot of coding to customize the component. And that is the issue, I am the perfect newbie at coding.)
Thank in advance for your assistance.
The topic has been locked.
Support Specialist
The key here is 'my old facebook commenting field'. Around March of this year, Facebook deprecated their older Javascript API and implemented a new one. Unfortunately, the new Javascript library *cannot* be used on the same page as the old one or bad things will happen.

If you're unsure, you can open the HTML source code of the page with the comment box and search for "all.js". If there's a file with that name being loaded from Facebook, that's a problem. The new file is called "sdk.js".

To fix, you'll need to determine how to prevent your template from including that file. Fortunately though, there is no change in the comment box code itself.. so, if you are able to disable the inclusion of the old Facebook Javascript code, the new code included by JFBConnect should make your existing boxes work just as they did before.

I hope that helps explain. Obviously, there may be some work to remove that older all.js file, but hopefully your template provider can help you with how to do that.

Thanks,
Alex
The topic has been locked.