Take screenshots of your facebook application setup and share with us - this way we can first rule out or identify if something has been wrongly configured from your end.

masky007 wrote:

Nicholas helped me trough skype for a long hour or even more.. and after debiging we narrowed downthe problem to the template.. it was because of using the jat3 framewrok (cashe mode) .. i disabled the option from the template backend and everythint worked.

So for others reading .. there is nothing wrong with the cb facebook plugin.

But please understand that we cannot possible debug the hundreds of templates out there.

FBC has been tested on numerous installations and there is no known problems. Any issue experienced is likely due to a conflict of some sort.

FBC uses its own PHP library which I wrote so it is impossible for the PHP library to conflict (unless someone took the library for 3rd party usage).

The JS library will conflict with other Facebook integrations; I can't fix this.. it is a limitation of Facebooks library not supporting multiple instances (they overwrite one another).

If you have a single fatal JS (or PHP) error on your site then FBC will fail. This is how JS and even PHP works. A fatal error prevents any further code from functioning properly (typically from a conflict).

ALL caching usage will cause, again, the plugin to fail. This is because caching is horrible, never use it. It feeds inaccurate (wrong) data to integrations and to users. The only acceptable caching is Server side and/or "Static" functions/vars inside the code it self. Aside from that disable any other caching as it will NOT give you better performance.

Last but not least please read the documentation included. I can't stress this enough. Follow the exact steps. Do not tamper with your Facebook Application thinking it would be cool to enable XYZ for your application, ONLY use the directed configuration and nothing else (if you do so it is as your own risk).

Post edited by: krileon, at: 2011/01/03 18:18