That’s odd. It appears that it can’t get through to the server, so it’s using an old cache of the data for some reason.
Looking at the code on your page, there might be an authentication problem:
<!-- Twitter error: 32 - Could not authenticate you. -->
Are the Twitter credentials on the settings page up to date? Might someone have reset them?
-
This reply was modified 8 years, 3 months ago by
Martin Tod.
Thanks for the reply!
I figured out that at first I got the 89 error, so I had my client refresh their access tokens (I control the WP site, but not the twitter account….).
Now I assume they either supplied the wrong/incomplete credentials.
To be continued…. I will let you know!
Cheers!