It looks like a bug to me, but maybe somebody can point out what I'm missing.
I seem to update from the desktop Picasa to the web gallery without any problem, but BG seems to fail to pass the update along. It doesn't matter if I delete, hide, or add, it seems to be frozen in the cache.
For instance: I have a gallery that currently has 14 images shown. It origanlly had 23, but I added one and hide ten, which leaves 14 active that the web gallery correctly displays. The RSS url displays the correct 14 in four different browsers as well. All cache options are turned off in Drupal and it has been cleared. Using IE8, I edit the RSS url to show the 14 images and save it. Then I go to Safari and reset the browser and re-test the url for the 14 images. Another reset and then load the page with the edit and bamm, there is 23 images. I've repeated and repeated this. The strangest thing is that there is a slideshow setup with the same gallery in a block on the left column, and it shows the correct 14 images!?
So then I create a new page with the url for 14 images. Just for kicks, I added another gallery, and you know it. There is 23 images that should be 14, and the other gallery, which, by the way, has the same problems. All of this occurs after the cache has been cleared and reset, then repeated numerous times.
The problem does not seem to be Picasa, and I think that the multiple browsers that I have used rules out their cache as a source of the problem. Then I presume, perhaps erroneously, that I've taken the correct steps for Drupal core. Which leaves the mod as the source of the problem. With all of the different components involved, I almost feel lucky to have derived a process that isolates the problem in BG, but what I really want is some hotshot to come along and tell me that I forgot to set something, somewhere. Any help?
Comments
Comment #1
vacilando commentedYes, cache clearing had issues, esp. in case you used the file caching setting at /admin/settings/brilliant_gallery
The new dev version, submitted today, has a setting for cache expiration (in days). If you use Drupal database cache, then the cached images (thumbnails and other resized images from your galleries) will expire from the cache. If you are using the file cache, then the expired cached images will be deleted during cron run.
Also, after the cache expiration time, if there are new images, they will be detected and added to the gallery.
Further testing is much appreciated (it is tricky, with all the Drupal core and module caches, and browser caches). If there are issues, please re-open this issue and provide precise observations/fixes/patches. Thanks!