Hi,

I have installed and tested the use of your module. Quite neat! One frustration is that I can't seem to refresh the album node's content. Say in picasa I have created 'Album1' with 2 photos. Then I create the picasa GUser. I can then see the new node with the album link and photo count just fine. BUT if I then add a new photo to 'Album1', OR if I create 'Album2' with 2 photos, neither the new photo nor the new album shows up in my node. I have tried clearing cache (i.e. http:///?q=devel/cache/clear&destination=node%2F133), and have also logged out, start a new browser and logged back in, but the changes are still not reflected. The only way in which the changes will show is if I EDIT the node and resubmit it. Any suggestions?

- Celine

Comments

cyberswat’s picture

Assigned: Unassigned » cyberswat
Status: Active » Closed (works as designed)

When you create the node it synchronizes with Picasa. When it synchronizes it stores the album information in Drupal. Right now the only way to synchronize it again with your albums is to edit the node. At that point you should go through the authentication and everything gets pulled down from Google and updated. This is structured this way so that if Googles Picasa were to ever go down you would get 404's on the images instead of a total Drupal lock-up (the original version of this module had that problem). I have the ability to tie the updates into the cron cycle so that it would be able to keep things updated without having to edit them and plan on bringing that about in Drupal 6.

one51’s picture

This is a major problem for me, as my site requires me to update the galleries as I add new pictures. Has this even been seen by the maintainer?

I could not find any other hints in the drupal.org site on how to solve this...

one51’s picture

Okay I found one workaround which isn't very nice: if you have the Picasa files cached in the site's tmp directory, just delete the folder containing the photos of the picasa album you need to update.

(some brainstorming) This should be easy to remedy in the module: compare the #images and filenames in the Picasa album, and if changed, download the new-filename images. It would miss modified (same-name) images, but is at least better than using this workaround I've found. And there could be a button or cron task to re-check all files linked to picasa, on demand or on schedule.

I suspect the most common problem to remedy is people adding new images to existing albums, or deleting old images. I rarely modify already-uploaded images, unless you count the picasa captions (which BG doesn't use anyway).