Service Disruption – 24/02/2014

Thank you kellywilson83, that is not great but does make more sense.

On the plugin settings page, does the error log at the bottom show anything? (only visible if errors occurred connecting to the API).

I will continue working on this until everyone can use the plugin again.

No, nothing displays. See this screenshot: https://cl.ly/UGSh

hi kellywilson83,

Thank you, that is certainly strange. This means that the plugin thinks it got a completely valid response from the Twitter API but something else is going wrong.

This has given me a few more ideas of where the process might be going wrong. If I have had no luck by tonight, I will make a debug version of the plugin which will send me useful information and see if any of you wonderful people will install it to help me debug.

OK thanks – please just keep me posted. I would be willing to install the debug version if need be.

Hi Peter – any update on the twitter feed? Thanks, Kelly

Don’t know why people experiencing issues…
Its working perfectly for me …

Those who experiencing issues trying removing/activating/deactivating or installing fresh plugin again i was receiving ‘no tweet found issue’ i have done these. now its rocking again… ??

thanks a lot @peterbooker for good work!

good luck others

I have just updated the plugin to version 1.4.6, this includes two relevant features:

1) In the top right of the plugin’s settings page, there is an API Status box. After the page loads this will turn green or red, depending on whether your website can connect to the API server or not. Can anyone suffering problems let me know what happens please?

2) At the far bottom of the plugin’s settings page, there is a link ‘Debug Tweet Data’. If you click on this, it should (after a short load) fill a text box with your cached Tweet Data. Can anyone experiencing problems email the contents of this to me (there is a ‘Select All’ link, to make this easier) along with your username here. This will help me to debug what is happening on your particular system.

Adding these features took me much longer than I had hoped, but hopefully we can work out what is wrong on your sites and get the problems resolves now.

Hi, Peter, thanks a lot for your work.
Plugin works fine since today. Should i send you Debug data or not?

Hi Vsevolod,

If the plugin is working fine now the Tweet data will be in the correct format, so the debug data will not be useful. If you have any problems in the future it will help to solve them though.

Did the plugin start working at random? Or when you updated it?

If anyone is still seeing the “Sorry, no Tweets found.” message I would love to see the debug data, as it will help me to understand what is going wrong on that particular site.

Hi Peter – I’m still having the same problem, seeing the “Sorry, no Tweets found”. I tried disconnecting service/accounts and reconnecting and no change.

This is all I get when I click the debug cached tweet data:

{“expiry”:1394284395}

Sorry – the API status also reads API 23.239.13.127 Success.

Hi kellywilson83,

Thank you for the information. From that we can tell that your website can connect to the API perfectly (it looks for a specific response from the API, not just a connection), but that it has not stored any Tweet data at all.

Usually I would expect corrupted or malformed data if there was a problem. No data (other than the soft expiry time) is not expected at all.

I will have a look through to see what situation would be required for this to happen and see if I can come up with another test to work out where it is going wrong.

Peter, the plugin begun to work after update.

Hi Vsevolod,

Fantastic news. I was about to write and suggest that anyone experiencing problems since the API change should update and it could well resolve the problem.

The issue was that during the API server downtime, the Tweet Data cache got stuck with just an array containing the expiry time. Instead of the expected Tweet Data object, with the expiry time added on. This means that the Tweet Data was the wrong data type (array instead of object) and failed to do anything properly from that point onwards.

The update fixes this by deleting the transient storing the Tweet Data and re-creating it. It has also made it so that saving the options page does this too.

This has highlighted a weakness in the code which I will be addressing shortly to prevent anything like this from happening again.

This is still not working. I’m still getting the “Sorry no tweets found” message. I’ve updated the plugin, which made no difference. I’ve even deleted and tried reinstalling it again. No luck.