I finally was able to get the module to work after the beta release. However, now I am getting a couple of errors in watchdog.
When I try to upload, I get the following error:

*Video uploads currently unavailable. If this problem persists, contact the system administrator.

I checked watchdog and found the following errors:

*YouTube Connection failed with Expected response code 200, got 403
*Authentication to YouTube succeeded, but failed to generate a token

I have check my settings and they seem to be fine.
What could be causing the errors?

Comments

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
commented

Hey vatoloco,

#257618: I need some help with the settings. has many tips for people getting this error. Unfortunately, I've never been able to replicate the issue, so I can't say exactly which steps will fix it.

kkrgopalan’s picture

kkrgopalan commented
Version: 5.x-1.0-beta1 » 5.x-1.0-beta2

Hi

I was getting a similar error only that my response was

*YouTube Connection failed with Expected response code 200, got 400
*Authentication to YouTube succeeded, but failed to generate a token

I debugged it further by dumping the exception object and referring to the youtube guide
http://code.google.com/apis/youtube/2.0/reference.html#youtube_data_api_...

The culprit turned out to be the youtube tag format. Mine had a space in it. Its supposed to be only comma separated.

This is set while creating a new field for the content type.

The specific text field is
Default YouTube keywords:

It does has instruction on there saying no spaces are allowed :).

Hope this helps others who see the same error.

Thanks
Krishna

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
commented

Thanks Krishna!

So many people have been getting this error, your debugging work is much appreciated. I'll add a validity check on those keywords for the next release.

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
commented
Version: 5.x-1.0-beta2 » 6.x-1.x-dev
Status: Active » Fixed

The latest (6.x) dev release enforces that default keywords not have spaces, so people no longer have to read the fine print when creating a field.

neubreed’s picture

neubreed commented

The culprit turned out to be the youtube tag format. Mine had a space in it. Its supposed to be only comma separated.

I love you! .. it pays to read ALL the instructions on the CCK field config page .. proverbial doh!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.