[Plugin: Wickett Twitter Widget] “Error: Twitter Did Not Respond”

I wonder if it’s related to caching? I was thinking “I wonder why the responses are not cached” so I looked through the code and found a couple references to wp_cache_get. That made me thing that caching IS being used, but maybe there’s a conflict with WP Super Cache. I was using WP Super Cache 0.9.5 in full on mode. I turned it off and this error went away. I wonder if the error will return in 5 minutes 15 minutes or something, if there is an expiration on the cached data?

This is working for me, right now, with WP Super Cache turned off.

Also, WP_CACHE is true in wp-config.php

Today, with the WP Super Cache plugin off, it still occurs randomly.

I’ve been having the same problem all day. I’ve tried two or three other plugins as well, all with similar results. The funny thing is, on my other blog (also WordPress) my twitter plugin works fine, yet the same plugin won’t work on my newest blog.

I thought mine was resolved because it was working fine for a little while, but it has been awful the last few days. Ryan, you say none of the other widgets are any better? This is frustrating…

The only Twitter widget I’ve been able to get to work consistently over the past few days is “Twitter Widget”, which says it uses the Javascript Twitter ‘badge’. But then you’re loading JavaScript on every page – and I’m only showing the Twitter feed on a home page. It’d be nice not to have the overhead when not needed.

You can use the Widget Logic plugin to show the Twitter badge on the home page only.

https://www.ads-software.com/extend/plugins/widget-logic/

But wait, is it the plugin that loads the JavaScript on each page? How do you make the badge appear on the home page only? Curious how you’re doing this.

Hello,

I just installed this plugin and got this “twitter did not respond” error for a few hours now, nothing is changing.

Anyone found how to display the last statuses easily ? It’s amazing that there is still no reliable and easy Twitter widget so far. Also I need it to be multi-instance capable…

Thank you very much for your help.

@chrishajer: I am putting Twitter updates in a subsection of the footer area that is only shown on the home page. Since the overall subsection display is already being controlled by CSS, I don’t need to have widget-level display control, e.g. Widget Logic.

But as I mentioned above, the JavaScript would still load on every page – so I put a routine in my functions file to only load the JavaScript lines if the user was on the home page. Maybe Widget Logic would lead to same result, but I’m using a variety of custom page templates and have a lot of manual “widget” areas using hardcoded template tags and custom functions, so it was relatively trivial to handcode it. This is all in a child theme of the Thematic framework.

Since none of the non-Javascript Twitter plugins have been working, I’ve actually just gone ahead and used Twitter’s HTML/Javascript badge code right on the website – HTML in a text widget, JavaScript in the functions file. Not much control over the display elements, but at least it consistently works for my client.

I was getting the same errors at random but the biggest problem is that this widget added an extra 5 – 6 seconds to the load time of each one of my blog. Not sure why, but for now I am reverting back to Twitter Tools.

Alex

This message is annoying as hell. I constantly get it and what’s worse the author of this widget does not respond.

Isn’t this an official WP widget? Has ANYONE gotten this to work? Where do we contact support? It looks like this forum thread is useless in reaching the developers.

For those having problems, do you have WP_Cache enabled?

https://codex.www.ads-software.com/Function_Reference/WP_Cache

If not, can you try enabling it?

Update: Thank you Nick

I enabled WP_Cache and figured out that it was because I was accessing the page too often. It still happens, but only when I’m working on the site and refresh/access the page about 60 times within an hour.

I did have WP Super Cache and WP_CACHE was true in wp-config.php, initially when it happened to me. I’ve stopped using the plugin though so I cannot test it right now.

Yes I have WP_Cache enabled…. no use.