From: Zach Copley <zach@status.net>
Date: Tue, 20 Oct 2009 22:04:47 +0000 (-0700)
Subject: Twitter now puts out an error msg when the status param is empty.
X-Git-Url: https://git.mxchange.org/?a=commitdiff_plain;h=8a31970ff8fe8a4e440501771756747370e2fa20;p=quix0rs-gnu-social.git

Twitter now puts out an error msg when the status param is empty.
Updated our API to match.
---

diff --git a/actions/twitapistatuses.php b/actions/twitapistatuses.php
index 360dff27cb..b0d3e584ba 100644
--- a/actions/twitapistatuses.php
+++ b/actions/twitapistatuses.php
@@ -236,11 +236,8 @@ class TwitapistatusesAction extends TwitterapiAction
         }
 
         if (empty($status)) {
-
-            // XXX: Note: In this case, Twitter simply returns '200 OK'
-            // No error is given, but the status is not posted to the
-            // user's timeline.     Seems bad.     Shouldn't we throw an
-            // errror? -- Zach
+            $this->clientError(_('Client must provide a \'status\' parameter with a value.'),
+                $code = 403, $apidata['content-type']);
             return;
 
         } else {