Cache seems never updates and always show values of the first search stored in the cache. I saw publication date of a tweet (ago_time) never updates with consecutive access in the web (consecutive F5). I decided to never use cache and get items in every access.

Comments

antoniobusrod’s picture

Version: 6.x-1.2 » 6.x-1.1
tachyonimpact’s picture

Version: 6.x-1.1 » 7.x-1.0-rc1
Priority: Normal » Major

I can confirm this bug on 7.x-1.0rc1.
The only way to get Twitter_Pull to update is to disable and re-enable the module.

adshill’s picture

Priority: Major » Critical

This is an issue on 6.x too... you have to manually flush the cache of the site for the items to update, even with cache set to '0' effectively turning it off. Can't see any info on how to manage this, and other issues report similar things going back to October... As Twitter is real time, I see this as critical!

arithmetric’s picture

Please test the development release of this module. I think this has been fixed in: #1068230: cache pulls outdated items

greggles’s picture

Status: Active » Closed (duplicate)

Marking this as a duplicate per comment #4 and the lack of followups since then.