CODEWITHSUNDEEP
facebookfacebook-graph-api
CharliePrynn
CharliePrynn

Reputation: 3082

Facebook create an album graph api

I have written a facebook app which checks if an album exists, if it does not it creates one.

This was all working 2 weeks ago and now I go and check it to show the client and it is no longer working. I was thinking it could have something to do with Facebook and maybe they now require an SSL? I can't find any evidence of this on there website however.

The error I am getting is:

Warning: file_get_contents(https://graph.facebook.com/517578134925015/albums?access_token=AAAD5tUCp808BAIZBPk4eV11mlf9C92velLsDeZAm5mXhKZCkwpM3LNy7ax6BBmhuH4BVZBUN6Iycyt55NoXZAFSts9zHeCFNzT6FLJYucgT2SQG8fOYIP) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.0 500 Internal Server Error in /var/www/vhosts/hidden/development/cms/backend/publishAlbum.php on line 59

My current code is:

                //If no album ID is set, create a new album.
            $graph_url = "https://graph.facebook.com/".$pageId."/albums?" . "access_token=". $pageAccessToken;
            $postdata = http_build_query(
                array(
                    'name' => $albumName
                )
            );
            $opts = array('http' =>
                array(
                    'method'=> 'POST',
                    'header'=>
                    'Content-type: application/x-www-form-urlencoded',
                    'content' => $postdata
                )
            );
            $context = stream_context_create($opts);
            $result = json_decode(file_get_contents($graph_url, false, $context));

Any help is appreciated.

Thanks

EDIT:

The code I tried that uses the API.

$params = array(
    'name' => 'testtest',
    'message' => 'test test'
);
try{
    $albumtResult = $facebook->api('/'.$pageId.'/albums', 'post', $params);
}
catch(FacebookApiException $e){
    error_log($e);
    $albumtResult = null;
}
$albumId = $albumtResult->id;

Here is the caught exception: http://pastebin.com/pxeyRTDn

Upvotes: 1

Views: 2463

Answers (2)

CharliePrynn
CharliePrynn

Reputation: 3082

After a lot of searching, someone created a bug report on Facebook that was almost identical to my problem.

Since being created it has had a lot of repo's and other people reporting that they are also having the same issue.

The priority on facebook has been changed to high so hopefully it gets fixed soon.

Facebook bug report: https://developers.facebook.com/bugs/376442565760536?browse=search_50361119879b15494037772

Thanks for everyones time.

Upvotes: 1

C3roe
C3roe

Reputation: 96306

Well, the reason for this error would be much easier to figure out, if you’d used the PHP SDK to make API calls, instead of doing them “by hand“ using file_get_contents … because using the SDK, you get an exception that should point to the error cause, whereas file_get_contents (by default) just throws a warning when it gets anything else than a 2xx HTTP status code for an answer, and does not let you access the response body (which will most likely contain a human-readable error message as well).

My advice: Use the SDK!

Otherwise, add to the context parameter that you want to see the returned data even if the status code signals an error. (details -> see manual)

Upvotes: 1

Related Questions