Hi, thanks for noticing it. The new 2.5.1 plugin release is out now, fixing that issue. Cheers!
Thanks. I upgraded, now the widget just says “No public tweets”.
Oops…after a bit more investigating, looks like users that are logged in, so seeing un-cached content, see “no public tweets”. Users that are not logged in, so seeing cached content, see a blank space.
What do you see when the plugin “Erase cached data” option is enabled?
That makes it function properly. I assume it has a performance cost though?
And huge thanks for the quick help!
Leaving the “Erase cached data” enabled for long time can cause empty data from Twitter, because the Twitter API is rate limited: you have a fixed maximum amount of requests every 15 minutes. Hopefully your “W3 Total Cache” should limit the widget renderings and the Twitter API calls, so it could work for your website.
Anyway, if you enable “Erase cached data” for some minutes and then you disable it, the WordPress cache gets refreshed; it’s a quick way to empty the cache and solve temporary issues like the “no public tweets” string.
It didn’t work for long, I am back to “no public tweets”. So the only way I can get this to work is to enable & disable “erased cached data” on some regular basis?
The plugin works fine on thousands sites, but in some website with different plugins active together it suffers data loss. I’m studying an easier solution for these api+transient+cache issues … I’ll let you know when I find something useful!
Ok. Thanks again for the response, really appreciate it.
