I have just been made aware of a bug in the way we collect your tweets. If you have made a connection to Twitter through our plugin, but cannot display your Tweets, this may be effecting you.
There is a very small chance that the screen_name Twitter provides is not actually the screen_name in use by Twitter. We then use this to identify who when requesting your Tweets and
I am currently creating an update to change the way we identify you to using your User ID instead, which should prevent this problem occuring. This should be released in the next 30mins and any new connections formed using that version should not suffer the same problem.
I will update this thread as resolved once the update has been released.
Sorry for any inconvience caused.
The latest version 0.27 should have fixed the above issue. If you were having problems getting your tweets to display, disconnect your current Twitter Connection and re-create it. You should now be able to display your tweets correctly.
If you have any problems with this update, or still cannot display your Tweets (with a connection to Twitter) please let me know.
I have just installed this plugin, authorised the app to my client’s twitter account, and added the widget, but still shows ‘sorry, no tweets were found on the site?
Thank you for taking the time to let me know. If you go to ‘Settings’ -> ‘Kebo Twitter’ (the plugin options page), does the error log at the bottom show anything?
If not I may need to enable tracking on the requests to see if something odd is happening.
Thanks for the swift reply.
This is what shows in the error log:
**Good news, there have been no errors received from Twitter recently**
None of common errors apply for what is showing on the site.
Ok, so that is a good sign.
Would you mind letting me know your account_name? if so I will output the requests to a console windows for a little while and see if your site is making requests to fetch the tweets.
Sorry account name for twitter account? or site?
Should have been more specific, for Twitter please.
I have also been working on improving the code to identify if WP failed to actually make an HTTP request, which currently is not checked.
I have been watching the console and there have been around 10 successful requests made using your account name.
This suggests that the plugin has successfully fetched the Tweets from your Twitter account. Is the Widget still displaying ‘Sorry, No Tweets Found’?
It’s late so I am going to continue with this tomorrow. I really appreciate you taking the time to help me troubleshoot bernecreative. I am sorry the plugin has caused you inconvenience so far.
One last question before I head off, are you currently running any security plugins on the website? It might be possible that one is blocking the responses with the Tweet data.
The widget is still displaying ‘sorry, no tweets found’. The website I am building is:
And no security plugins are installed either.
I just wanted to let you know I am working on this.
It seems that requests for the Tweets are properly being made and sent back to the plugin. Next I need to look at what could go wrong after that and ideally add code to the plugin so that it can gracefully catch and deal with those situations.
I am currently attempting to replicate your experience on my development environment. Hopefully I will have something useful for you soon.
I have spent the morning investigating this issue and I have not been able to confidently identify the problem.
The latest plugin update which is going live in the next 30mins records internal WordPress errors when making HTTP requests (on top of the current Twitter API errors). While testing the internal errors my test environment site began showing “Sorry, no Tweets Found.” so it may be linked.
These WP errors will show as Code 1, with the explanation WP provides. If anything like this appears it may help us to track down the cause.
No problem, I will try updating the plugin in half hour and let you know if this makes a difference.
- The topic ‘Not fetching your Tweets?’ is closed to new replies.