› Forums › NextScripts API Forums – Google+, Pinterest, LinkedIn, etc.. › Pinterest not working – New API
- This topic has 3 replies, 1 voice, and was last updated 10 years, 7 months ago by NextScripts.com.
- AuthorPosts
- May 31, 2014 at 7:27 pm #213447RyanParticipant
Hi.
I still cannot post to Pinterest after updating to the new API.
Debug is as follows:
[PN] NO Saved Data; [PN] Checking....; [PN] Checking....; Board ID = Pinterest ERROR MESSAGE : | | | | | | Oops! | Our server is experiencing a mild case of the hiccups. | We've reported it to the team. | Try again? | | |Posting error Array ( [0] => 2 )
Any ideas?
June 1, 2014 at 12:36 pm #213654RyanParticipantShould have pointed out that I am using the latest version of the standalone API library.
June 1, 2014 at 2:29 pm #213679Yagmur AkgünParticipantSo, no one is bothering answering my support tickets, I’ll just post here. In the example for Pinterest Standalone API there is a call for nxs-api.php:
require_once “nxs-api/nxs-api.php”;
which is not included in the API library zip.
There is a file called nxs-http.php though, so I changed my script to reference this file.
My script for testing looks like this:
<?
require “postToPinterest.php”;
global $nxs_gCookiesArr;
$nxs_gCookiesArr = doCheckPinterest(); // Use your function to retrieve saved data to array$email = $argv[1];
$pass = $argv[2];
$msg = $argv[3];
$imgURL =$argv[4];
$link = $argv[5];
$boardID = $argv[6]
$loginError = true;
if (is_array($nxs_gCookiesArr)) $loginError = doCheckPinterest();
if ($loginError!==false) {
$loginError = doConnectToPinterest($email, $pass);}
if (!$loginError)
{
doPostToPinterest($msg, $imgURL, $link, $boardID);
} else echo $loginError;
?>So, since changing to the newest API library (because login was broken in the old one), I am getting this error:
PHP Notice: Undefined index: SERVER_NAME in C:\php\nxs-http.php on line 188
nxs_Error Object
(
[errors] => Array
(
[http_request_failed] => Array
(
[0] => SSL certificate problem: unable to get local issuer certificate
))
)
– ERRORI am running this script on localhost, which worked well until this new update.
June 1, 2014 at 4:17 pm #213721The answer is in the FAQ – #4.4:
- AuthorPosts
- You must be logged in to reply to this topic.