The new version (2.6.0) did fix an issue that affected a couple specific versions of PHP (there was a bug in PHP that I had to work around). Other than that, the issue with a feed not updating is usually due to one of the following:
- Your account has hit it’s API call limit. You can see your rate limit status by looking at the settings page (WP Admin->Settings->Twitter Widget Pro). Remember that all apps that you authenticate to your Twitter account are using your API calls, so they’re not necessarily all being used by Twitter Widget Pro. Twitter Widget Pro actually uses only 20 calls per hour per distinct widget (a distinct widget is a widget with the same settings, so same username, number of tweets, etc).
- Your server is limiting loopback calls. This basically means that your server is keeping your site from calling itself. Whenever a user is visiting your site and Twitter Widget Pro determines that you need updates from Twitter, it actually calls another page on your site that does the update. This way the user doesn’t have to wait while all the processing is being done. There have been some hosts that have turned off this functionality or blocked it with their firewalls. If this is the case, Twitter Widget Pro cannot update.
- Some people have also had problems with some locks not clearing. There is a lock put in place to keep Twitter Widget Pro from trying to update the feed when it’s already updating the feed in another process. There is a link on the settings page labelled “Clear Update Locks” that you could use to clear the locks and see if it helps.
It sounds like yours is most likely #2. Try talking to your host.
hello.
I’ve got the same problem.
I used the plugin in two hosting providers and they have the same issue.
Is there any solution?
I am sorry to say, but it doesn’t work on my site either. And this is since latest updates. Same host, different version of the plugin works perfectly at one of my client’s site.
Yep, I have the same problem. Unfortunately it looks like we may have to look elsewhere for another solution as, to be fair to the developer, this plugin is only compatible with up to v 3.6 of WP so it looks like something in the latest version of WP has broken the plugin. Shame as it was a really good little plugin.
