Hi. I looped through an array of 13 elements sending 13 different emails. Below is an example of the last two elements and the foreach() loop. Looks like I got a curl error on the last iteration of the loop.
*Fatal error:* Uncaught exception 'CurlException' with message 'Error making request with curl_error: Operation timed out after 10000 milliseconds with 0 bytes received' in /domain.com/php/createsend-php-master/class/transport.php:165 Stack trace: #0 /domain.com/php/createsend-php-master/class/base_classes.php(289): CS_REST_CurlTransport->make_call(Array) #1 /domain.com/php/createsend-php-master/class/base_classes.php(224): CS_REST_Wrapper_Base->_call(Array, 'POST', 'https://api.cre...', Array) #2 /domain.com/php/createsend-php-master/csrest_transactional_smartemail.php(144): CS_REST_Wrapper_Base->post_request('https://api.cre...', Array) #3 /domain.com/roster/preshow-email.php(55): CS_REST_Transactional_SmartEmail->send(Array) #4 {main} thrown in /domain.com/php/createsend-php-master/class/transport.php on line 165

            Array
            (
                [11] => Array
                    (
                        [email] => [email protected]
                        [name] => Brett Loudermilk
                    )

                [12] => Array
                    (
                        [email] => [email protected]
                        [name] => David Deeble
                    )

            )


            foreach($a as $act){
                # Create a new mailer and define your message
                $recipient =  "{$act['name']} <{$act['email']}>";
                print $recipient;
                $wrap = new CS_REST_Transactional_SmartEmail($smart_email_id, $auth);
                $message = array(
                    "To" => $recipient,
                    "Data" => array(
                        'SHOWDATE' => $db,
                        'SHOWORDER' => 'http://boobietrapshow.com/',
                        'PERFORMERPAGE' => 'http://boobietrapshow.com/',
                    ),
                );
                # Send the message and save the response
                $result = $wrap->send($message);
                echo "<br/><pre>" , print_r($result), "</pre>";
            }

using: v3.1.3

I'm sending 1000 subscribers at a time to import() and I keep getting:

Fatal Error Error: Error making request with curl_error: Operation timed out after 10000 milliseconds with 0 bytes received in [CampaignMonitor\class\transport.php, line 158]

Why not do something like:

if (!defined(''CS_REST_CALL_TIMEOUT')) { define('CS_REST_CALL_TIMEOUT', 10); }

or something?

So it was possible to set a custom timeout

Since some time we get the error

{
  "Code": 50,
  "Message": "Must supply a valid HTTP Basic Authorization header"
}

A similar problem was reported in closed issues campaignmonitor/createsend-php#15 and campaignmonitor/createsend-php#33 I tried to fire a sample request like shown on getting-started with my own api-key, and I get the same response.

  echo file_get_contents('https://api.createsend.com/api/v3.2/clients.json?pretty=true', false, stream_context_create(
    array('http'=>array(
    'method'=>"GET",
    'ignore_errors'=>true,
    'header'=> "Authorization: Basic ".base64_encode($auth['api_key'].':x')."\r\n"
    ))
  ));

I can ensure that:

• no proxy or firewall is stripping the Authorization header
• I have no trailing or leading whitespace in the APIKey string

This errorcode is not listed in API Docs - response-status-codes, but I checked the Authorization that is delivered by you API class and by my exmpla with native php file_get_contents. Both seem to send a valid Basic auth header, that contains my correct api-key.

Is it possible that there could be a problem with the API-Endpoint or any changes in the auth-methods?

Alternatively, I'd consider dropping Services_Json altogether. Since php 5.2 php comes in with bundled json ext so it should be available everywhere.

The motivation for this is that requireing this file always not only registers a class definition but also produces some undesired side-effects - namely, global constants definitions

I was using the add Subscribe function fine, but a few hours ago it stopped working.

The response indicates a successful entry - but when I view the list on campaign monitor the subscribers are blank.

function addSubscriber($list_id, $emailAddress, $name, $title, $showName, $showDate, $showTime){ //create subscriber $subscriber = array( 'EmailAddress' => $emailAddress, 'Name' => $name, 'CustomFields' => array( array( 'Key' => "Title", 'Value' => $title ), array( 'Key' => "ShowName", 'Value' => $showName ), array( 'Key' => "ShowDate", 'Value' => $showDate ), array( 'Key' => "ShowTime", 'Value' => $showTime ) ), 'Resubscribe' => true, 'RestartSubscriptionBasedAutoResponders' => true );

    //print_r($subscriber);

    $subwrap = new CS_REST_Subscribers($list_id, $this->auth);
    $result = $subwrap->add($subscriber); 
    //var_dump($result->response);

    echo "Result of POST /api/v3.1/subscribers/{list id}.{format}\n<br />";
    if($result->was_successful()) {
        echo "Subscribed with code ".$result->http_status_code;
    } else {
        echo 'Failed with code '.$result->http_status_code."\n<br /><pre>";
        var_dump($result->response);
        echo '</pre>';
    }
    return $result->response;
}

CS_REST_SOCKET_TIMEOUT and CS_REST_CALL_TIMEOUT constant definitions are now wrapped in conditional checks to see if the values have been defined earlier to allow larger requests to not timeout.

This was needed to allow subscriber imports to function without timing out.

I am using the supplied example to test the API:

require_once 'csrest_general.php';

$auth = array('api_key' => 'your API key');
$wrap = new CS_REST_General($auth);

$result = $wrap->get_clients();
var_dump($result->response);

However, the response I get is;

array(
   'Code' => 50,
   'Message' => 'Must supply a valid HTTP Basic Authorization header',
)

I have also tried using the supplied example for adding subscribers, with the same result.

How do I set the Basic Auth header? Given the docs say that Basic Auth simply requires the API key as the username and a blank password, I assumed the library would handle that if I just give it an API key, as the samples do.

This is my relevant code

require_once('campaign/csrest_general.php');
$auth = array('api_key' => $_POST['code']);
$wrap = new CS_REST_General($auth);

I am getting this error on the first line itself

Fatal error: Cannot redeclare class cs_rest_wrapper_result in campaign/class/base_classes.php on line 19

Any ideas? The code has not been edited in any way.

Hi,

first thanks for the great package to work with the CM API!

I am having now some problems with the import limit. There is a limit of 1000 subscribers / import. Is there way to handle more data?

I tried to make several imports through a loop but this didn't work:

Error making request with curl_error: Operation timed out after 10000 milliseconds  with 0 out of 144 bytes received

Do you have any advice on how to handle this? Thx and cheers Christoph

PS: I am working with Laravel 4

The examples feature this lovely gem:

$result = $wrap->add(array( 'EmailAddress' => 'Subscriber email', 'Name' => 'Subscriber name', 'CustomFields' => array( array( 'Key' => 'Field Key', 'Value' => 'Field Value' ) ), 'Resubscribe' => true ));

Great! Except what if I a want to add more than one custom field? Surely the following makes good sense, no?

$result = $wrap->add(array( 'EmailAddress' => 'Subscriber email', 'Name' => 'Subscriber name', 'CustomFields' => array( array( 'field1' => 'value 1', 'field2' => 'value 2' ) ), 'Resubscribe' => true ));

But that does not work. So I think you need to demonstrate your data structure here more thoroughly. EXAMPLES ARE GOD.

What I think you mean is this:

$result = $wrap->add(array( 'EmailAddress' => 'Subscriber email', 'Name' => 'Subscriber name', 'CustomFields' => array( array( 'Key' => 'Field Key', 'Value' => 'Field Value' ), array( 'Key' => 'Field 2 Key', 'Value' => 'Field 2 Value' ), // ... etc ... ), 'Resubscribe' => true ));

I think ???

I have a user who's using an addon of mine that uses the Campaign Monitor API PHP wrapper on IIS and when the API is called, he's receiving this PHP fatal error:

Call to a member function make_call() on a non-object in C:\Inetpub\xxxxx\xxxxxxxxx\expressionengine\third_party\subscriber\libraries\class\base_classes.php on line 220

It seems to work just fine on Apache servers. Do you know it would fail on IIS?

Hi! This is maybe not the right place, but I can't find any other way to reach out to you guys. My client is using campaign monitor and when I'm trying to embed one of the forms on their website I get this error:

Oops! Something went wrong.
We could not process your request. Please enable Javascript in your browser. and try again.

Javascript is of course enabled and all I've done is copied the code generated for me. How can i debug this? Or how can I get in touch with support?

Documentation states the result is in this format:

     * @return CS_REST_Wrapper_Result A successful response will be an array of the form
     *     array(
     *         array(
     *             "MessageID" => string
     *             "Status" => string
     *             "SentAt" => string
     *             "Recipient" => string
     *             "From" => string
     *             "Subject" => string
     *             "TotalOpens" => integer
     *             "TotalClicks" => integer
     *             "CanBeResent" => boolean
     *             "Group" => string, optional
     *             "SmartEmailID" => string, optional
     *         )
     *     )
     */

Actual Response is: CS_REST_Wrapper_Result {#64 ▼ +response: {#65 ▼ +"Query": {#66 ...} +"Sent": 14 +"Bounces": 0 +"Delivered": 14 +"Opened": 9 +"Clicked": 2 } +http_status_code: 200

Campaign Monitor recently sent out an email asking all customers to switch over to TLS v1.2 before October 12, 2020. Our website is using this code. How do I know what version of TLS we are using? Does this code support TLS v1.2?

When PHP configuration option allow_url_fopen is truthy (the default), it's easy to use it as a transport. It's probably less error-prone than a raw socket, too.

$response_body = file_get_contents(
	"https://api.createsend.com/api/v3.2/${endpoint}.json"
	, false
	, stream_context_create([
		'http' => [
			'method' => 'POST',
			'header' => [
				'Authentication: Basic ' . base64_encode("${api_key}:"),
				'Content-Type: application/json',
			],
			'content' => json_encode($request_data),
			'ignore_errors' => true, # prevents returning boolean false for error http statuses
		],
	])
);
$response_headers = $http_response_header; # https://www.php.net/manual/en/reserved.variables.httpresponseheader.php

Obviously it'd need a little bit more logic to choose HTTP method, be more generic, etc., but the code's a lot simpler than cURL and raw sockets.

The ConsentToTrack field is mandatory and should be a valid value ('yes' or 'no'). If you don't add it, the API will return an error that it is mandatory.

Deprecated function: Array and string offset access syntax with curly braces is deprecated in require_once() (line 4 of vendor/campaignmonitor/createsend-php/class/serialisation.php).

Version: 5.1.3