-
Notifications
You must be signed in to change notification settings - Fork 858
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It started #571
Comments
There have been some "effective immediately" deprecations made today. See #345 Which endpoint were you requesting from? |
@chasevorn It depends on what endpoints you need to use. This should be a pretty easy library overhaul for the most part. I was able to update my agency's usage of the library at the user endpoint with small changes. line 259 of instafeed.js This should fix any queries to the user endpoint to get the most recent posts. This was only tested for our use case, and not for all library options. |
/v1/users/USERID/media/recent I have this js set up |
@chasevorn How are you loading up the library? |
@georanma THANK YOU!! |
@georanma your code gets my own instagram feed not the one from the customer that i'm building the feed for :(
|
@tatof you will need to update to using an access token generated from your client's instagram account. It is no longer possible to pull another user's instagram feed via their userId. |
This got solved for me only by creating an app and generating a new access token from my client account and not from mine. |
I see thanks! :) |
@tatof np. @chasevorn yes, see my previous response. |
@chasevorn Thanks for your fix. Since @stevenschobert doesn't seem to be keeping this active at the moment I created a fork here (at least while InstaFeed is inactive). It includes your fix which solved the issue I was having of |
@rfearing Hey there! Thanks for the contribution! For what it's worth -- I am still here, I've just been extremely busy with other projects, so that's why many of the PRs haven't been merged or deployed yet. I'm happy to see other people sharing knowledge in the issues though, which is why I've left many issues open. Given Instagram's decision to sunset their API, I'm not sure yet what the future of this library will be, but I'll participate as much as I can! |
@stevenschobert That totally makes sense! I hope my comment didn't come off as rude at ll, as I definitely appreciate the plugin and your work! Thanks again! |
This issue has been automatically marked as stale because it hasn't had new comments in the last 3 months. It will be closed if no further activity occurs. If you still need assistance with this issue, or believe it shouldn't be closed, please respond with a new comment to let us know. |
This wasn't supposed to happen until Dec 11, 2018 according to their website: https://developers.facebook.com/blog/post/2018/01/30/instagram-graph-api-updates/
Are there any other solutions for this?
The text was updated successfully, but these errors were encountered: