Is the update for the flickr blocks dependent on cron jobs? I am seeing the block but the images stay the same forevere. It's been 3 hours so far and no updates are shown even though I have uploaded several dozen new images to flickr.

Comments

rgracia’s picture

rgracia commented

Is this module also developer-orphaned...?

Anonymous’s picture

Anonymous (not verified) commented
Assigned: Unassigned »

Are you still having problems?

handsofaten’s picture

handsofaten commented

I'm having this problem. There are new images in the group pool that were added almost 24 hrs ago, and although the cache time is set to 1 hr, old images still show up in the block.

EDIT: I have also cleared the cache and it makes no difference.

ANOTHER EDIT: It appears to be a problem with Flickr itself not including certain photos in the API response for the pool, although they are publicly viewable... investigating further, but it doesn't appear to be a problem with this module.

FINALLY: I had the "Hide from public areas" flag set.

rgracia’s picture

rgracia commented

Yes I am.

#2
paulbooker - February 17, 2010 - 14:40

Are you still having problems?

Anonymous’s picture

Anonymous (not verified) commented
Assigned: » Unassigned
rrphoto’s picture

rrphoto commented

I've just installed this module and the block "Flickr group photos" only shows 1 image and it doesn't change. (I've set the block to display 4, but only one static image is shown - group pool has 6 images to draw from)

Any ideas? Thanks in advance.

Anonymous’s picture

Anonymous (not verified) commented
Assigned: Unassigned »

Do you see this problem on the development branch ?

Best,
Paul Booker
Appcoast

rgracia’s picture

rgracia commented

Gotta check. Will report this weekend.

Anonymous’s picture

Anonymous (not verified) commented

@rgracia Thanks.

rgracia’s picture

rgracia commented

UPDATE: my client hasn't added more images to their flickr account so I have to wait another week or so. Sorry for the delay in the testing.

lyricnz’s picture

lyricnz commented
Status: Active » Closed (cannot reproduce)

Issue is 18 months old, with no further feedback from submitter. 6.x-1.2 has been release since then.