I used this piece of code to get thumbnail image and link to the phto
page, but it doesn't work anymore ; is it a new API version (the
<feed><entry><content src=""> doesn't exist anymore) ?
Then, not being one to trust that the docs haven't been updated in the
not so distant future, I dug into the revision history. This element
has not been changed since launch last year. As far as I know, it has
always been the url attribute that people have had to use to retrieve
the <media:content> link. It appears to be a similar story for
<media:thumbnail> as well.
Cheers,
-Jeff
On Mar 21, 7:25 am, "tk.luczak" <tk.luc...@gmail.com> wrote:
I started using the data api last september and I've always gotten the content and thumbnail from the url attribute of <media:content> and <media:thumbnail>. I don't ever remember seeing just a <content> element inside <entry>.
Cameron
On Fri, Mar 21, 2008 at 10:16 AM, Jeff Fisher (Google) <
> Then, not being one to trust that the docs haven't been updated in the > not so distant future, I dug into the revision history. This element > has not been changed since launch last year. As far as I know, it has > always been the url attribute that people have had to use to retrieve > the <media:content> link. It appears to be a similar story for > <media:thumbnail> as well.
> Cheers, > -Jeff
> On Mar 21, 7:25 am, "tk.luczak" <tk.luc...@gmail.com> wrote: > > I had the same problem. Code under C# used to be:
"As systems developers, we have selected ourselves into the world of cool, calming, rational thought. Either our code compiles, or it doesn't. The compiler is never happy for us, nor mad at us. Perhaps this is why we tend to apply logic as our main device for resolving disputes." -Peopleware, 2nd Edition
"Babies...before we're done here...y'all be wearing gold-plated diapers." -Rock Legend Bruce Dickinson
I was mistaken, the issue is that <atom:content> has changed (it's
missing) rather than anything to do with <media:content>. I'm looking
into this now.
Cheers,
-Jeff
On Mar 21, 10:29 am, "Cameron Hinkle" <goldplateddiap...@gmail.com>
wrote:
> I started using the data api last september and I've always gotten the
> content and thumbnail from the url attribute of <media:content> and
> <media:thumbnail>. I don't ever remember seeing just a <content> element
> inside <entry>.
> Cameron
> On Fri, Mar 21, 2008 at 10:16 AM, Jeff Fisher (Google) <
> > Then, not being one to trust that the docs haven't been updated in the
> > not so distant future, I dug into the revision history. This element
> > has not been changed since launch last year. As far as I know, it has
> > always been the url attribute that people have had to use to retrieve
> > the <media:content> link. It appears to be a similar story for
> > <media:thumbnail> as well.
> > Cheers,
> > -Jeff
> > On Mar 21, 7:25 am, "tk.luczak" <tk.luc...@gmail.com> wrote:
> > > I had the same problem. Code under C# used to be:
> "As systems developers, we have selected ourselves into the world of cool,
> calming, rational thought. Either our code compiles, or it doesn't. The
> compiler is never happy for us, nor mad at us. Perhaps this is why we tend
> to apply logic as our main device for resolving disputes." -Peopleware, 2nd
> Edition
> "Babies...before we're done here...y'all be wearing gold-plated diapers."
> -Rock Legend Bruce Dickinson
> I was mistaken, the issue is that <atom:content> has changed (it's
> missing) rather than anything to do with <media:content>. I'm looking
> into this now.
This has broken my team's app (Windows Live Writer) as well. Please do
keep us posted.
> > I was mistaken, the issue is that <atom:content> has changed (it's
> > missing) rather than anything to do with <media:content>. I'm looking
> > into this now.
> This has broken my team's app (Windows Live Writer) as well. Please do
> keep us posted.
> We have identified the problem and found a solution. We are currently
> testing for further regressions. I will update the thread when the fix
> is live.
> Cheers,
> -Jeff
> On Mar 21, 1:17 pm, Joe Cheng <joe.ch...@gmail.com> wrote:
> > > I was mistaken, the issue is that <atom:content> has changed (it's
> > > missing) rather than anything to do with <media:content>. I'm looking
> > > into this now.
> > This has broken my team's app (Windows Live Writer) as well. Please do
> > keep us posted.
> This issue should now be resolved. Our apologies, and thanks much for
> your patience!
> Cheers,
> -Ryan (on behalf of Jeff)
> On Mar 21, 4:00 pm, "Jeff Fisher (Google)" <api.jfis...@google.com>
> wrote:
> > Hi Joe,
> > We have identified the problem and found a solution. We are currently
> > testing for further regressions. I will update the thread when the fix
> > is live.
> > Cheers,
> > -Jeff
> > On Mar 21, 1:17 pm, Joe Cheng <joe.ch...@gmail.com> wrote:
> > > > I was mistaken, the issue is that <atom:content> has changed (it's
> > > > missing) rather than anything to do with <media:content>. I'm looking
> > > > into this now.
> > > This has broken my team's app (Windows Live Writer) as well. Please do
> > > keep us posted.