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.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Picasa Web Albums API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Picasa-Data-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to