Note that there are some explanatory texts on larger screens.

plurals
  1. POFacebook Development - Simple question on best approach
    text
    copied!<p>I am a PHP developer, but completely new to this Facebook stuff and am getting all confused. The whole Apps vs Pages vs Fan Pages terminology is driving me nuts. Please help!</p> <p>My client's requirements:</p> <pre><code>1) Display Like button on a single web page 2) When Like button is clicked, content on the page is unlocked and displayed (PHP) 3) Future visits to the page detects that visitor already likes the page, and content remains unlocked (PHP) 4) All updates to web page profile on FB will show on Likers' news feed </code></pre> <p>My understanding is that the cleanest way of doing (3) above is to use the PHP SDK. But to do this, I need to create an app (to get the App ID). So I created an App. I 'liked' the App from my FB profile. Updates to my app are posted to my news feed. So far, so good.</p> <p>However when I try and implement the PHP SDK, it only works if I authorize the App to my account first. Is there a way of avoiding this authorization step just for a simple "Like" (I ask because I didn't have to authorize anything when liking the app within FB)? If this authorization is unavoidable, are there any alternatives to Apps that would allow me to achieve the above requirements?</p> <p>Ideally, I'd like to use just "Pages" to do this, and not Apps, but I believe I cannot achieve (2) and (3) with pages, correct (remembering everything needs to be server side, so no JavaScript showing and hiding layers etc)?</p> <p>I would be grateful for any guidance.</p> <p>Thanks.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload