Hello gregorymark-
We are currently using every method of the feed at our site, for this reason, I don’t believe it has anything to do with the API. This plugin was built for API V1.1 so ensure that your Twitter application is up to date – perhaps create a new one? I know it may sound crazy, but also ensure that all of your keys are correct (they are ALL different values found on the OAuth tool tab at twitter).
You’re right. I’ve tested it on another site with the same keys and settings and it works so it must be conflicting with another plugin on my site.
I occasionally get a tweet come through but when I refresh the page it’s gone again, but like I said I used the same settings on another site and that was working fine so I don’t think I’m going over my limit. That doesn’t flag anything up for you does it?
I’ll let you know if I figure it out!
After reviewing your message I looked at the cache implementation code, and found that it could use an improvement when directly calling the widget from a template. I’ve updated it to do a better check for a cached version of the tweet if you are calling it directly (PHP). Not saying it will fix your issue, but it might help.
Ah, that’s great, I did notice that so I was using do_shortcode actually. I’ve installed it on another live site and it’s working nicely so I suspect it might be some throttling on my IP or something.
Thanks for the help!
I tested it on a local build too and it worked so I set it up on the live site and it’s working a treat.
If there’s space for feature requests, integrated hashtag & twitter name linking would be great.
Cheers guys!
