Facebook connect links to # since upgrade to 4.1.8
 

Facebook connect links to # since upgrade to 4.1.8 - disabled all plugins and still does the same.

Any ideas?

www.ukcigarforums.com

It's OK that it links to '#' because the button action is done in javascript.

But the facebook connect button doesn't work anymore oon click it does nothing.

I noticed that, I was just saying that I don't think the '#' link has anything to do with it. We don't use that on our site, and I tried to set up a test site but I couldn't find where on the facebook site to get an application ID. But I did verify (on my site) that FB.getLoginStatus() was being called when the button was pressed.

Do you have any other Facebook Elements, for example the Fan Widget in your sidebar?

For example if you copy the Fan Widget code into the sidebar it will include Javascript which will cause the error. If you remove all the javascript so you are just left with the <div>....<//div> section at the end it will resolve your issue

Nope, and that wouldn't explain why it was working before the upgrade to 4.1.8....thanks

Create a new style with no parent:

• Styles & Templates > Style Manager > Add New Style
• Parent Style: No Parent Style
• Title: Default vBulletin
• Allow User Selection: Yes
• Save

Then browse the site using that totally default vbulletin style - do you still have the same problem?

Doesn't make any difference. You can see on www.ukcigarforums.com and selecting vb4 Default Style.

Thanks.

--------------- Added [DATE]1323945548[/DATE] at [TIME]1323945548[/TIME] ---------------

There are no JS errors, and the facebook stuff is in the footer source.

I also cannot seem to get the built in Facebook Connect to function, it also does not use the pre-identified pic when posting threads to Facebook.

It seems that you're getting an error from facebook when it tries to connect that says "Invalid Application ID: The provided Application ID is invalid.". You say it was working before so I'm not sure what would cause it to become invalid. Maybe there's some other problem going on (I don't really know a lot about how the facebook api works).