Thanks for this added info. Anyhow, I tried to do a shortcut and
regressed back to adding "?imgmax=800" in each of my old direct embeds
and links (or leeches) and they worked - for only one day. So, I
decided to do the longer route and fixed everything up by adding that
text snippet in the feed getter itself. I can see those "/s800/" and
"/s72/" snippets now in my image URLs so I know I got the feeds
right. I still add a paranoid "?imgmax=800" and "?imgmax=72" to each
URL though even when in the presence of "/s800/" and "/s72/".
Anyway, thanks for showing me the FAQ on the embedding limitation.
"Everyone has a photographic memory. Some just don't have film."
Loloy D
On Oct 28, 1:26 am, "Jeff Fisher (Google)" <api.jfis...@google.com>
wrote:
> Hi,
> Nothing has changed. It's the fact that pictures > 800 pixels can't be
> hotlinked:
> http://code.google.com/apis/picasaweb/faq.html#embed_image
> Cheers,
> -Jeff
> On Oct 27, 8:18 am, Loloy D <lol...@loloyd.com> wrote:
> > I have been using Google Picasa Web Albums API on my website for a
> > very long time now but it appears that something has significantly
> > changed the way I used to "leech" from my Picasa web albums.
> > I am able to successfully grab and manually parse the GData feed and
> > cache it in my website's database. The new problem I'm having is when
> > I am trying to directly display my pictures from an IMG/SRC tag/
> > attribute.
> > I have this sandbox page where I am attempting to incorporate Lightbox
> > and GData in my Drupal website:http://www.loloyd.com/sandbox/d6/node/22
> > As you can test and see, my Lightbox fails to work there. But you can
> > try to right-click on any image, and open that in a new tab - this new
> > tab will indeed display a 404 not found on the URL saying something
> > like
> > "Google Error
> > Not Found
> > The requested URL /xxxxxxxxxxxxxxxxxxxxxxxx.jpg was not found on this
> > server"
> > But if you try to click on that 404'd tab's address bar and click on
> > GO (I guess this blankens the Referer field), you would be able to get
> > the correct image. This leads to me suspect that I should either be
> > authenticating myself properly as I didn't have to in the past or that
> > I should find a way to fix that Referer field, which would be
> > impossible.
> > The weirdness doesn't end there, however, as I have a properly working
> > non-Lightbox webpage on the same set of images that totally works:http://www.loloyd.com/photosets/2008_introducing_cutie
> > Before you go dismissing that there's a problem with the Lightbox
> > script, please note that I have been able to use this same "feed
> > mechanism" from another image hosting provider that I control and that
> > it works OK.
> > Thanks for any insight.
