Ah ha…yes it did! Thanks. Are you going to issue a new release then?
Yes. It appears that there’s a problem that – in some cases – the cache is set with an infinite expiry life…. I’ve changed the settings so that this can never happen!
Great. I appreciate that you are an active and supporting author to your plugin. Thanks @martintod !
New release issued!
Hopefully this will permanently fix the problem, but please let me know if it the problem re-emerges!
Ok, when/how does my WP install recognize the new release for updating? I am new to that happening…
Not sure. It’s all to do with when your installation of WordPress talks to the WordPress servers to spot the upgrade.
We’re good to go…WP recognized the new release…I updated…the page/plugin works now.
Thanks @martintod
The problem is back @martintod. Not exactly sure when the problem resurfaced as my client just brought it to my attention today.
[rotatingtweets screen_name='********' tweet_count='2' show_meta_screen_name='0' show_meta_via='0' no_rotate='1']
tweet_count='2' works fine it pulls two tweets. The problem is the 2 tweets are not the latest. The plugin brings back the 3rd and 4th most recent tweet but tags them as 5-days old, which is true — but the 5-days old is the date/time stamp of the 1st and 2nd most recent tweet. SO the plugin is “mixing & matching”…
Site: http://bit.ly/1waPylP
OK. That’s odd (but very helpful)…
Sounds like the ‘merge’ functions are broken…
I’ll get on it.
Martin
Great, I appreciate it…let me know when the fix is in. Thanks.
Thanks for your plugin @martintod.
I ended up going with a more stable plugin for your twitter feeds at this time (https://wordpress.org/plugins/wd-twitter-feed/).
I hate to be the one to “unresolve” this topic but I’m getting the same issue. No caching plugins, freshly generated twitter credentials and it’s pulling in older tweets but not any new ones created after sometime during 17th to 24th October. Using version 1.7.18.
Simple call of [rotatingtweets screen_name=’xxxxxx’]
Did you fix this Martin?
Cheers
Edit: I just used the call in a previous post and it’s working now:
[rotatingtweets screen_name=’xxxxxx’ tweet_count=’5′ show_meta_screen_name=’0′ show_meta_via=’0′ no_rotate=’0′]
Sorry for the mix-up
I can understand how this might happen on a search but can’t imagine how it might happen on a regular account.
What’s the user name? Are you using a cacheing plug-in? And are you seeing any error messages in your source code?
Have you tried it with WP_DEBUG set to true and seen any useful source-code error messages?
Martin
Hi Martin
As I mentioned in the last post edit. It works with the long shortcode call, but not the default short call.
No caching, no errors with debug on.
HTH
Hmm.. Sounds like the name is using the search algorithm instead of the regular algorithm.
Can you confirm that there are no spaces, semi-colons or commas in the screen_name?
