Jump to:
| Project: | Video Upload |
| Version: | 6.x-1.6 |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | ritu27 |
| Status: | closed (won't fix) |
Issue Summary
Hi,
I'm getting the following status message: YouTube uploads currently unavailable, and cannot seem to get my posts to work on Youtube.
I've followed the documentation, created a youtube account, and a google youtube developer account and got an API key. I've downloaded the required Zend libraries, and otherwise seem to have the module setup properly with CCK, can create a new node, upload a .mov file, and submit the post.
I've opened up the zend_gdata.inc file to see where that error gets generated from, and it looks like authentication is failing, but I've double, triple, checked my credentials which all seem accurate.
I'm wondering if this is user error or an actual bug, but I think I'm stuck. Thanks!
Comments
#1
I have the same problem, did you ever figure out this issue?
#2
I have had the same issue; adding "@gmail.com" to the name in the "Youtube Username" field fixed the issue.
#3
I am also getting the same problem please help.......:(
#4
Same issue here, and by the way ... the @gmail.com tail didn;t help
#5
I have confronted the same issue, fortunately I removed the "@gmail.com" in the username in the setting page, it works.
So it's quite weird and just opposite #2. But this module is amazing and easy to use. Thanks a lot:)
#6
on one site I had a look into watchdog and OpenSSL in apache required.
#7
Seems to be an intermittent problem with the Zend->YouTube API link. Using your username or email will sometimes stop working, generally after your first upload on the site.
The fix appears to be:
OR
(ie. Email -> Username OR Username -> Email)
arpis at #4 stated that this fix didn’t work but my testing and others in this thread report it fixing the issue.
I’m not sure exactly whether the bug lies, however it appears to be somewhere in the link between the Zend framework required and YouTube’s developer API – outside of this modules specific code. Therefore I’m going to set this one as won’t fix since it most likely can’t be fixed within this module alone.
Also it appears to still be an issue through to 1.6 updating to reflect this.