Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • @all

    Unfortunately there still seems to be a ‘caching time’ issue, regardless of dynamic or fixed IP address assignment. Increasing the timespan (> 24 hours) might work on dynamic addresses, but then the feed is often outdated. Seems plugins like these stop working without token authentication.

    @blazer380

    Has the ‘old’ plugin been deactivated and the (blocked) public IP address replaced with a new one – if allowed by the provider?

    Here still it works, but possibly only because the internal testsystem has a dynamic IP address (DSL router and port forwarding to the private LAN) that changes after 24 hours. The caching problem (duration) might still occur on servers with fixed addresses.

    Network ban and plugin caching is described and resolved here. That plugin does the job for me. Many thanks to all involved authors.

    “Instagram-feed-without-access-token”

    Just substitute the included (outdated) file ‘jquery.instagramFeed.min.js’ with the newer one from that github repo:

    “Github-Instagram-Feed”

    Finally, I also added option ‘display_captions’: true,’ while editing the config file (igfeed.js).

    • This reply was modified 5 years, 4 months ago by wp35353.

    This browser console error message has already been listed here several times.

    Wordpress 5.6 / WP Instant Feeds 1.3.4:

    (x) Uncaught TypeError: Cannot read property '0' of undefined
            at Object.<anonymous> (script.js:60)
            at fire (jquery.js:3496)
            at Object.fireWith [as resolveWith] (jquery.js:3626)
            at done (jquery.js:9786)
            at XMLHttpRequest.<anonymous> (jquery.js:10047)

    Looks like the token authentication method can no longer be avoided. Or does someone know of a plugin for which the Instagram name is sufficient to display the feed?

    Instant feeds are always displayed once and disappear when the browser cache is refreshed (F5). A new assignment of the public Internet address causes the whole thing to be repeated. Presumably Instagram has deliberately tightened the API restrictions again. Thank you FACEBOOK!

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