WordPress.org

Support

Support » Plugins and Hacks » [Resolved] Feed not updating – Console reports 404

[Resolved] Feed not updating – Console reports 404

  • Hi Aaron,

    First, thanks for making this great plugin. And thanks for being so responsive in the support arena.

    So as with some others, I’ve noticed that my feed (at http://joelglovier.com) stopped working within the past few days (maybe week or two? not sure exactly).

    I started to debug this evening by checking my console in web inspector, and noticed this error: http://cl.ly/KR1P It appears that Twitter is not delivering the JSON object for my tweets, and I’m not sure why it’s returning that way.

    Sure enough, if you visit the URL directly, you get:
    twittercallback2({"errors":[{"message":"Sorry, that page does not exist","code":34}]});

    So my first thought is, did Twitter change something with their API?

    Also, I double checked in my settings for Twitter Widget Pro to see what my API usage is, and it’s actually at 0. http://cl.ly/KRhe

    Do you have any idea what’s going on here, or tips for where to troubleshoot next?

    Thanks,
    Joel

    http://wordpress.org/extend/plugins/twitter-widget-pro/

Viewing 9 replies - 1 through 9 (of 9 total)
  • Well – I found the answer. Turns out Twitter changed the API in March, and finally just shut off the old functionality at the beginning of October. (see this article)

    Looks like the API URL must now use a new format that includes “api” as the subdomain, and “/1” after twitter, like so:
    https://api.twitter.com/1/statuses/user_timeline/jglovier.json?callback=twitterCallback2&count=1

    Apparently the Twitter for WordPress plugin users were discovering the same issue.

    Can you please push a plugin update as soon as possible?

    Thanks!!

    Plugin Author Aaron D. Campbell
    Participant

    @aaroncampbell

    What version of the plugin are you using? Those URLs were updated in 2.2.4 which was released about 15 months ago (we’re currently on version 2.4.0).

    Interesting. Yeah I’m running 2.4.0.

    Screenshot: http://cl.ly/KU4p

    Plugin Author Aaron D. Campbell
    Participant

    @aaroncampbell

    Then the plugin is already using the newer API location.

    Yeah but that’s what I’m saying – it’s not asking for it that way. It’s still asking from the old URI format.

    You can see right here (screenshot): http://cl.ly/KVCz or by going to joelglovier.com

    @jglovier — How is your site exposing a JSON request to Twitter? I’m a developer trying to use this plugin and having a similar issue, but I’m not getting the same 404 as you in your console.

    Further, Aaron seems to be correct in stating that it’s using the new API URL — see wp-twitter-widget.php, line 227. That’s the only place where the API URL is defined. Further, the only file in the plugin that fetches user_timeline is on line 822 (Which is then rewritten a bit a couple lines down with add_query_arg).

    In other words, I have no clue how your site is possibly making a JSON request to Twitter that is visible to the browser (I.e., via JavaScript), unless you’re using something like XDebug (Which you’re not, because that’s the Chrome console). Perchance do you have another Twitter widget installed?

    Don’t get me wrong, I’m still having massive issues with getting this plugin to update properly (It seems highly dependent upon the number of items being requested), but, tl;dr — I really don’t think it’s the API.

    Hope this helps!

    Plugin Author Aaron D. Campbell
    Participant

    @aaroncampbell

    aendrew is right. The screenshot you just showed is definitely caused by something else. Possibly another Twitter plugin or possibly something bundled with your theme.

    Sorted my problem, thanks jglovier

    Hah – yup. You’re right. Looks like I commented this plugin out a while back when I was having issues, and am actually using the twitter html widget currently.

    Thanks.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘[Resolved] Feed not updating – Console reports 404’ is closed to new replies.