Mandrill ValidationError
Bansi's answer worked for Dan B, but if someone else is having the same issue is good to check if the content have special characters (accents,umlauts,cedillas,apostrophes,etc). If that's the case the solution could be to utf8 encode the text:
$content = utf8_encode('<p>Greetings from Bogotá, Colombia. Att:François</p>');
I don't know about mandrill, but your $content
string has double quotes"
in it and your delimiter in the $postString
is also double quotes. This is going to break in any language. You need to escape the double quotes in the $content
as required by mandril.
"html": "' . $content . '",
will translate to
"html": "<p>this is the emails html <a href="www.google.co.uk">content</a></p>",
^ ^
Try
"html": "' . str_replace('"','\\"',$content) . '",
"text": "' . str_replace('"','\\"',$content_text) . '",
Instead of
"html": "' . $content . '",
"text": "' . $content_text . '",
You may also want to just use arrays, and let PHP handle the JSON encoding for you. This particular error is common if the JSON is invalid for some reason. So, for example, you could set your parameters like this:
$params = array(
"key" => "keyhere",
"message" => array(
"html" => $content,
"text" => $content_text,
"to" => array(
array("name" => $to, "email" => $to)
),
"from_email" => $from,
"from_name" => $from,
"subject" => $subject,
"track_opens" => true,
"track_clicks" => true
),
"async" => false
);
$postString = json_encode($params);
You can also use json_decode
to parse the response if needed.
The PHP Mandrill API error: "Mandrill_ValidationError - You must specify a key value"
This error can also indicate that json_encode() is failing to encode and returning an empty string. When the empty string is submitted to Mandrill via curl, it fails to let you know that it got totally empty POST content, and instead issues the helpful message "You must specify a key value".
Obviously this problem could be mitigated by better detection at several levels:
- Mandrill at API level could return an error like "Empty POST"
- The Mandrill.php API class could return an error like "json_encode fail, possible non-base64 image or content problem"
- The Mandrill.php API class could check for non-base64 content in images and give an error like "unencoded image"
- It would be kind of nice if json_encode() threw some sort of error (not sure re this one)
None of this is being done at this point, hence this was unnecessarily hard to debug.
The simple fix in my case was to effectively change code to run base64_encode() before including image content, that is:
'content' => base64_encode(file_get_content("image.jpg"),
A better fix is, as above, to upgrade the Mandrill.php API file to detect a failure to encode and throw an error.