hi,

sorry I meant piero.pavan.20. to fix the issue, open /warp/js/warp.js and search for

if(a.facebook&&!e.facebook)f("body").append('<div id="fb-root"></div>')

and replace it with

if(!window["FB"] && a.facebook&&!e.facebook)f("body").append('<div id="fb-root"></div>')

that's it.

greets,
artur

hi,

I managed to solve it in your backend by patching warp. the fix will be included in the next warp release.

greets,
artur

I am also using JS since the very beginning , I can't find any issue in my tests. Please see WidgetKit Functions Not Working in Shelf Template - YOOtheme and implement that solution and then clear caches and test if you still have this issue.

YOOgards

Hi Mustaq, thanks for your help.

I followed your suggestions, but I didn't solve my issue yet.

I just created a new page where there is ONLY the JomSocial Facebook Button, deleting every other mod and plugin, in order to effect test to discover what component, or plugin, or module, causes my issue.

Please check at http://www.1001notte.com/test-fbc.html

I don't know how to go on and solve it.

P.S. my widgetkits are perfectly working, take it as a cue.

Updating

I did set "NO" the following settings in the backend of your Balance Template and the FB Button started to work perfetly!

Twitter Button
Google+ Button
Facebook Button

Sure, I would like to use them, but if set them on YES my FB Button stops to work.

I am having the same issue with Cloud template. The Jomsocial Facebook Connect button is non-functional. If I disable JUST the FB "like" option in the template it works perfectly. I'm not sure what has to give to make it work, but I already submitted a trouble ticket to Jomsocial. They are the ones that identified the issue. I think there must be a workaround or fix here?

Thanks!

In "my backend"? You were on my site or are you speaking generically?

Artur, I just made that mod on my site and it did not fix the problem. i cleared the browser cache and Joomla cache, but no difference. Does it matter if it's J2.5GA?

UPDATE: Artur, it is working now. I really don't know what changed, but it does appear to be fixed. Sorry for the false alarm.

Ok Artur, I will try to change as suggested by you.

I will let you know about result.

Thanks.