Hello,
This should be working on the stage.gdata.youtube.com server next
week, and in production the following week. Sorry about the
inconvenience in the meantime.
Cheers,
-Jeff Posnick, YouTube API Team
groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
@YouTubeDev
On Apr 4, 1:51 pm, Jeffrey Posnick <je...@google.com> wrote:
> Hello,
>
> Thanks. I've brought this up with the core engineering team, and I'll
> report back with their response.
>
> Cheers,
> -Jeff Posnick, YouTube API Team
> groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
> @YouTubeDev
>
> On Mar 31, 6:11 pm, Gate777 <arevans...@yahoo.com> wrote:
>
>
>
>
>
>
>
> > The following search:
>
> >http://gdata.youtube.com/feeds/api/videos?v=2&q=query&author=channelname
>
> > always works fine for regular YouTube channel names. However searches using
> > the new Google+ type channels using either the 22 character id string (uri)
> > or the name string (name) fails to return any results. Is there another
> > way to achieve this? Or is this an aspect of the recent changes that
> > developers have overlooked? Put another way, if one omits the query part of
> > the call it should return a list of all videos in a channel that have been
> > added into the search index. This works perfectly well for regular (up to
> > 20 character) account names, but returns nothing at all for the new 22
> > character id format.
>
> > The upload feed
>
> >http://gdata.youtube.com/feeds/api/users/channelname/uploads?v=2
>
> > does work with the new channel id format, but the results are not always
> > what one wishes to achieve.
>
> > Any light you can shine on this would be appreciated.
--
You received this message because you are subscribed to the Google Groups "YouTube APIs Developer Forum" group.
To post to this group, send email to youtube-api-gdata@googlegroups.com.
To unsubscribe from this group, send email to youtube-api-gdata+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/youtube-api-gdata?hl=en.
No comments:
Post a Comment