Okay, so I cannot detect any requests being made at all (successful or with errors).
On top of this I checked the users Twitter account and it is protected. From a little basic research it appears that it is not possible to get Tweets from protected accounts. We only request access to the public feed when connecting to the account. Which means that even if a request did go through, at the moment it would be returning nothing (likely the cause of the fatal error and now the “Sorry, no Tweets found” message.
Is the Twitter account being protected on purpose? Is it going to stay that way?
Well I checked the account & the Tweets ARE NOT protected. So what does this mean?
This is what I get when visiting the page: http://postimg.org/image/nn3bil54d/
OH! It’s actually @CantosDAlabanza. Sorry.
Okay, no problem. In that case I can see successful requests going through. Which means the Twitter API requests are happening correctly.
Did anything change with the site/server around the time the plugin stopped working? Other plugins perhaps?
No. Not that I know of. It was working fine yesterday.
Okay, thanks JPSKILLZ.
I think at this stage, there is nothing more I can do without access to the site/server to debug more.
The plugin is not logging any errors and the Twitter API requests are going through correctly. Which means the data is arriving at the site, but for some reason not being in the expected format and/or not being saved correctly.
If you are going live with the site today, it might well be better for you to use another plugin to avoid spending more time on this right now, as I cannot guarantee that I can resolve this problem quickly.
I need to get some sleep right now, but I can debug this further tomorrow if you would like. I am sorry you have had problems using our plugin and that I could not get it working tonight.
Well the good news is they’re not taking it live till the 27th so I still have some time. I’d really LOVE to use your plugin, so let’s pick it back up tomorrow & see what happens. Worse case scenario, I’ll have to use another plugin.
That sounds good, let’s continue tomorrow. I am sure we can get it working.
Fingers crossed. I’m working on 2 hours of sleep in 48 hours…so I feel your pain. LoL We don’t get paid enough for this. Get some rest man.
I have spent this morning attempting to work out what could be going wrong, but I will need more access to debug further. To get round this I have prepared a ‘debug’ version of the plugin, which will email me the contents of the $tweets variable, which contains the data returned from the Twitter API.
Assuming you are happy with this you can download it here: http://peterbooker.com/kebo/kebo-twitter-feed.zip
This will allow me to see if/what is wrong with what is being returned/stored and hopefully to think work out how to fix it. The next version of the plugin which you update to will overwrite the ‘debug’ portion and everything will be back to normal.
