Youtube Upload Error
GoogleCodeExporter opened this issue · comments
Google Code Exporter commented
What steps will reproduce the problem?
1. Use the PHP Example Script to insert a video
(https://developers.google.com/youtube/v3/docs/videos/insert?hl=de)
2. Set the config use_objects to TRUE
What is the expected output? What do you see instead?
There was an error on the following line:
$uploadStatus = $media->nextChunk($insertResponse, $chunk);
The method nextChunk expect as first argument a object of type
Google_HttpRequest but the insert function of the class
Google_VideosServiceResource return a Google_Video object.
A screenshot is attached.
What version of the product are you using? On what operating system?
Use the current trunk of the svn on a Mac OSX 10.8 with PHP Version 5.3.27
Original issue reported on code.google.com by sas...@saschanowak.me
on 7 Oct 2013 at 7:31
Attachments:
Google Code Exporter commented
This issue tracker is now closing. Development on the Google PHP client library
moved to GitHub with the release of the 1.0.0-alpha, and now the 1.0 branch has
reached beta status there will be no further releases of the 0.6 branch of the
library.
Please take a look at the latest version on
https://github.com/google/google-api-php-client
For information on migrating, please take a look at this guide:
https://developers.google.com/api-client-library/php/guide/migration
For general library support please ask a question on StackOverflow:
http://stackoverflow.com/questions/tagged/google-api-php-client
If you are looking for support with a specific API, please contact the team
working with that API via StackOverflow or their preferred support mechanism.
If your issue still exists with the new version of the library, please raise a
bug in the GitHub issue tracker with a minimal code sample.
Thanks!
Original comment by ianbar...@google.com
on 22 Jan 2014 at 4:56
Google Code Exporter commented
Original comment by ianbar...@google.com
on 22 Jan 2014 at 4:56
- Changed state: Done
Google Code Exporter commented
Hi the error is still here
Original comment by chris.be...@umail.uom.ac.mu
on 18 Apr 2014 at 11:14