Read up a few posts, and look for robdawg's workaround. That seems to be working for me on two 3.x sites.

It's correct that I put the footer code into process_templates_complete. That code originally was from global_start. In an effort of organizing template related code, I moved it and it stops working in vBulletin 3. My fault. Sorry mates :D

Going to release new version to fix this soon

PS: Also, the workaround really miss the point of mine because I tried to skip loading Facebook Javascript library as much as possible :D

Hey,

I get this error when trying to send a notification
Also, no one has mentioned yet on how i can move the Connect with facebook button under the login box besides being in the navbar

After installing the workaround and getting the bridge operational, it appears that a number of avatars have simply vanished from one of my sites. That's with the avatar sync turned off (the available sizes down match my requirements, and honestly, the sync wouldn't make sense for my userbase). So, not sure what's up with that. Not even sure if it's related, but I figured I'd mention it, since that problem occurred within an hour of the first account sync.

hmm all of the other features are fine on our site. Its just that we cannot send notifications without getting that error. Like today our site had a login probelm and i was going to send out a notification saying that we was working on it but i got that error. We would love to get it fixed if possible. Plus we kinda hate where the connect with facebook button is located and we would like to move it

vbulletin 4.0.3 has built in facebook connect but dont have much feature yet

Yeah i checked into that and i find this system to be way more better than theres. On theres you cant even do wall posts etc.

Any luck with this?

Will members who have created a account using YAFB be able to login/keep this existing account if they used the new default vBulletin Facebook bridge?

I haven't noticed anything else yet, but I'm getting a few errors in the log. Is there a decoder ring for the errors so that I can tell what they refer to?

As far as moving the facebook button, that shouldn't be too tough. On my main site, moving it will have nothing to do with other sites, since we completely reworked the header and navbar. However, on my other site, that stuff is pretty default, so unless someone beats me to it, I'll be able to at least provide a basic hacked way of moving it.

I am to Lazy too remove this one, I would let it go and ignore built-in thing until it comes better than this