1) Getting your Facebook App API codes:
Your first step to get Facebook Fan Page working on your Joomla site is to acquire the needed Facebook API codes (Application ID & App Secret ID). Please follow this step-by-step tutorial. Once you obtain these two Facebook codes, copy & paste your Application ID code into the proper module setting field under the 'Required Settings' module tab. Now click onto the 'Select Facebook ID Option' dropdown and select, Use App Secret ID. Copy & paste your Facebook App Secret ID into the provided field and save your module settings. The only other required setting you need to populate is the 'Facebook Fanpage URL name' field. Please note... all you need is the Fan Page name not the entire Facebook browser URL (example: The entire Facebook browser URL for Joomla's Facebook Fan Page is, https://www.facebook.com/joomla. For this module field all you need to enter is, joomla).
2) Securing your Facebook App API codes:
The conventional wisdom when creating your Facebook Fan Page Application ID & App Secret ID is, you are doing so for a 'Public Fanpage' and thus hackers really can't do much of anything with this data. However, Facebook does allow you to generate an Access Token ID via their 'Client OAuth Login'. By obtaining this Access Token ID you are making your connection to a Facebook Fanpage as secure as Facebook currently support. To get your Access Token ID please follow this step-by-step tutorial. Once you have acquired your Access Token ID, copy the 'Permanent Access Token' and within the module Required Settings click onto the 'Select Facebook ID Option' dropdown and select, Use Access Token ID. Paste your Permanent Access Token code into the provided field and save your module settings. Using this feature/option you are not exposing the App Secret ID code within your Joomla website source code. Please read through the instructions carefully because you have two options in obtaining your Access Token ID from Facebook.
Option #1 is to download the provided ZIP package and host this application on your own server (recommended). You will need to have this package residing on the domain server (Site URL) you registered your Facebook App API code.
Option #2 is to temporarliy set your 'Site URL' within your registered Facebook App to "http://graphicaholic.com/" and use the script hosted here. Once you receive your Access Token ID you will want to reset your registered Facebook App 'Site URL' back to it's original registered URL.
*JUMPING THROUGH HOOPS*
Sorry if the above required options seems like you have to jump through hoops just to show a public Facebook Fanpage. Once Facebook established their new API rules, things got a little wonky!
3) All I get is this after setting up the module;
When you get this screen, the first, second or third 'Required Settings' are incorrect. Please check that your fanpage URL name is correct, that your Facebook Application ID is correct or that your Facebook Secret ID or Access Token is correct. If any one is worng, Facebook can not process your request and you will receive the above page output. As a reminder, the 'Facebook Fanpage URL Name' is not the entire Facebook fanpage URL, just the actual fanpage URL name. Example: The entire fanpage URL for Nike is; https://www.facebook.com/nike for this extension's setting option just use, nike
3) Facebook Fan Page was working but now... NOTHING! What gives?
When you registered your app with Facebook you received an app ID code, and a Secret ID code. With this (as explained in the documentations) you were able to generate two unique 'Access Token' codes, a Temporary & Permanent Access Token. The Temporary Access Token only lasts for about 60 minutes and then stops working. The Permanent Access Token last for about 60 days (2 months) and it too will stop working when it reaches it's time limit. In order to get Facebook Fan Page back working you MUST reset all of these codes or create a new app within your Facebook account and enter the new codes into the module settings. Sorry, these limitations are not mine nor the module code. As I mentioned above, with the new Facebook API rules, things got a little wonky!