Not able to update 'Incidents' in v0.2 about cachet.php HOT 13 CLOSED

Hi.

Just took a look into this. The truncated Bad Request you are getting is probably:

{
    "errors": [
        {
            "id": "1c2fc534-9e21-427c-8682-b8db7901b60d",
            "status": 400,
            "title": "Bad Request",
            "detail": "The request cannot be fulfilled due to bad syntax.",
            "meta": {
                "details": [
                    "The status format is invalid."
                ]
            }
        }
    ]
}

This is pretty strange, as the Cachet documentation says the status should be an integer when updating an incident. In fact, using the try it out form on the documentation page also fails with the same error. See here: https://docs.cachethq.io/docs/update-an-incident

So it looks like you're doing everything correctly.

@jbrooksuk Have we stumbled upon an Cachet API bug or a bit of outdated documentation?

from cachet.php.

I'm pretty sure this is fixed in the RC releases of 2.3 :)

from cachet.php.

For future reference, you can get the full un-truncated messages by surrounding your code segment with a try catch block similar to what's below.

try {
  $incident->status = 1;
  $incident->save();
} catch (Exception $e) {
  // Output full response body contents
  var_dump($e->getResponse()->getBody()->getContents());
}

from cachet.php.

Thanks for checking this out @jbrooksuk.

from cachet.php.

I'm still on v2.1.2 of Cachet, I haven't tried any RC release of 2.3. But ideally, it should still work as I'm able to achieve the same using cURL.

from cachet.php.

I'm still on v2.1.2 of Cachet, I haven't tried any RC release of 2.3. But ideally, it should still work as I'm able to achieve the same using cURL.

The bug is in Cachet though, so how are you able to do it in cURL?

from cachet.php.

cURL is working fine for me. I'm running something like this -

$data = array('id' => 2, 'status' => 3, 'message' => 'hello world');

$url = "status.xyz.com/api/v1/incidents";
$url .= "/" . $data['id'];
$ch = curl_init($url);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "PUT");
curl_setopt($ch, CURLOPT_HTTPHEADER, array(
    'X-Cachet-Token: ' . $token
    ));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($data));
$response = curl_exec($ch);

from cachet.php.

@DivineOmega https://github.com/DivineOmega/cachet.php/blob/master/src/Models/Incident.php you're missing the component status field from here?

from cachet.php.

@jbrooksuk You're looking at the master branch there. This issue refers to v0.2 (tagged).

from cachet.php.

@Srthk Cachet 2.3 is out now. Is the issue still present with the latest version of Cachet?

from cachet.php.

@Srthk Did you manage to solve this issue in the end?

from cachet.php.

@DivineOmega the issue is fixed in Cachet, so this should no longer be a problem.

from cachet.php.

Hi. I haven't tried it out. But shouldn't be a problem I guess.

from cachet.php.