From 36543c0e27da087399f53b4e4e7c870fc46b7a8a Mon Sep 17 00:00:00 2001
From: Rey Ramos <reymundo.ramos@gmail.com>
Date: Fri, 20 Jun 2014 09:42:03 -0400
Subject: [PATCH] Update vimeo.php

I added the extra expl, to VimeoAPIException, the standard message is to vauge to know what is the real issue unless digging into the code.
Ex:
With just the VimeAPIExpection -> results are
Fatal error: Uncaught exception 'VimeoAPIException' with message 'Invalid / expired token
VimeoAPIException: Invalid / expired token in

--the two messages are the same with no real explanation

If you add the new Exception(expl), the results are:
Fatal error: Uncaught exception 'Exception' with message 'The oauth_timestamp passed is either too far in the past or in the future.
VimeoAPIException: Invalid / expired token

--this new message at least narrows the issue with the server internal clock being incorrect.
---
 vimeo.php | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/vimeo.php b/vimeo.php
index b845db2..b03344a 100644
--- a/vimeo.php
+++ b/vimeo.php
@@ -236,7 +236,7 @@ private function _request($method, $call_params = array(), $request_method = 'GE
                 return $response;
             }
             else if ($response->err) {
-                throw new VimeoAPIException($response->err->msg, $response->err->code);
+				throw new VimeoAPIException($response->err->msg, $response->err->code, new Exception($response->err->expl));
             }
 
             return false;