• Resolved Lisa Cerezo

    (@lisathirdsideco)


    For some reason, my client’s website is not pulling their live Instagram feed when it had previously been working. I’m getting the error message “Cache Error: Looking for cache that doesn’t exist. Now using a backup feed.” I disabled the caching (WPMU Dev Hummingbird) but the error persists. I’ve tried selecting/unselecting both the “Cache error API recheck” and “Force cache to clear on interval” and still can’t get it reconnected. The system info returns an error 400 – No id returned. But the ID is present and was properly connected and recently working. Can you help me resolve this?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Craig at Smash Balloon

    (@craig-at-smash-balloon)

    For sure! I’ll probably be able to give you some things to try from seeing the feed on the page. Can you send a link? If you don’t want to share that here, try this link:

    https://smashballoon.com/instagram-feed/support/

    Thread Starter Lisa Cerezo

    (@lisathirdsideco)

    I did that yesterday, actually, and got a reply back. It sounds like the client’s API actually had expired again, but the same thing happened just a few weeks ago. I never had these issues when the site was in development, and that was six months or longer. Should we expect this kind of thing to keep happening?

    Plugin Contributor Craig at Smash Balloon

    (@craig-at-smash-balloon)

    Hey lisa,

    Unfortunately this is something Instagram does on their end and there doesn’t seem to be any particular reason it happens. Most access tokens never expire but it sounds like your client is unlucky in that it might happen somewhat frequently.

    We are hoping Instagram changes how this works as the make changes to their API but nothing we know of currently.

    Thanks again,

    Craig

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Plugin not pulling API’ is closed to new replies.