Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter Sam

    (@ssharples)

    And yes, my access codes and secret keys are correct

    Plugin Contributor whiletrue

    (@whiletrue)

    Enable the “Show debug info” for some minutes to get more info about the issue.
    Enable the “Erase cached data” for some minutes to refresh the plugin cache.

    Thread Starter Sam

    (@ssharples)

    I have debug enabled but no info is shown
    I also have erase cache enabled but no joy 🙁

    Plugin Contributor whiletrue

    (@whiletrue)

    Hi, the new 2.5.8 plugin release is out, featuring improved Debug info. Please update, enable the “Debug info” advanced widget option and load again your site. You should see some “RSTW” lines printed inside the widget area: copy&paste them here to get help.

    I have the same problem above and I have followed the same steps mentioned above but still nothing shows. It was working until two updates ago.

    Here is the new debug information:

    “RSTW Debug info enabled
    RSTW Fetching erase cached data from Twitter”

    Here is the rest of the debug info that appeared when I turned erase cache off

    “Notice: Undefined index: resources in /home/sidestix/public_html/construction/wp-content/plugins/really-simple-twitter-feed-widget/really_simple_twitter_widget.php on line 395
    RSTW Fetching data from Twitter
    RSTW Fetching 8 items, 0 of 0 calls left, reset in -1415474677s”

    Plugin Contributor whiletrue

    (@whiletrue)

    Hi all, the new 2.5.9 plugin release is out, improving Debug Info a bit more. I realized that sometimes the issue is about expired/invalid API access tokens, so now Debug Info tells you to “try to regenerate your API access token”. If it doesn’t tell, try to regenerate them as well: I’ve seen a lot of people in trouble (on different plugins and platforms) due to broken Twitter API tokens. Also, the new release should be more robust, trying to use valid cached data whenever the API communication is down.

    I updated an tried regenerating both consumer keys and api keys. Still no tweets show up, but this shows in the debug:
    “RSTW Debug info enabled
    RSTW Retrieving API rate limit
    RSTW Using cached Twitter data”

    Plugin Contributor whiletrue

    (@whiletrue)

    Hi kellypl, please update the plugin to the 2.5.10 release. If the update doesn’t fix your issue, paste here the updated Debug Info.

    Ok I updated erased the cache. On first refresh the debug says:
    “RSTW Debug info enabled
    RSTW Retrieving API rate limit
    RSTW Fetching 8 items from Twitter”

    Then for every refresh after it says:
    “RSTW Debug info enabled
    RSTW Retrieving API rate limit
    RSTW Using cached Twitter data”

    But still nothing shows when I turn show debug info off. I also tried again regenerating consumer keys and access tokens.

    Thank you! Whatever you changed in the latest update fixed the issue! I really appreciate how quick you were with support, keep it up!

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘No tweets, no erros in debug’ is closed to new replies.