Jump to content
nbcommunication

InstagramBasicDisplayApi

Recommended Posts

Hi @Tyssen,

The message that the API is returning when I try to add my own account is "Error validating access token: Session has expired on Saturday, 24-Oct-20 00:35:05 PDT. The current time is Monday, 15-Mar-21 09:08:47 PDT".

I tried regenerating the access token and got exactly the same message.

This looks to me to be an issue on Facebook's end. I'll submit a bug report and see if they get back to me.

Cheers,

Chris

Share this post


Link to post
Share on other sites

Hi @Tyssen,

I never got a bug report submitted yesterday (there's a lot of hoops to jump through).

I've just been to check the process again and it has worked for me this time. Can you please try again? You may need to regenerate the access token from inside the Facebook developer admin, but worth trying the one you already have first.

Cheers,

Chris

Share this post


Link to post
Share on other sites

@nbcommunication Yes, it's OK for me now.

Another question though: you say that the module doesn't require OAuth for authentication but if I try and set up the module on my local version of the site, which isn't accessible outside my local network, I still get the same error. So at the moment, I only have an authorised account on the production version of the site (the same domain as I entered into the OAuth settings).

How do I get my local version of the site authorised so I can work on template changes in my local environment?

Share this post


Link to post
Share on other sites

Hi @Tyssen,

No idea why it says that in the README! It does use OAuth.

Quick solution if you have access to phpMyAdmin, find the record in the instagram-basic-display-api table and copy it to your local copy.

Cheers,

Chris

  • Thanks 1

Share this post


Link to post
Share on other sites

@nbcommunication Great thanks. I wasn't sure whether there was going to be something straightforward like that or not. 👍

Share this post


Link to post
Share on other sites

Hi, first of all great module, very helpful.

Found an odd issue with this, not sure if its just some issue with my own setup? I added a second user and used the wrong token (I had generated two for two different accounts and grabbed the wrong one)

The new user doesn't appear in the list (though they're in the db table) 

I also couldn't remove the original user (though they disappeared from the db)

It's using the value stored in the caches table but it restores itself even if I forcibly delete that cached row.

Forcibly deleting the user row from the module table and then putting it back in right, fixed the user being fetched, although still shows the wrong one in the module settings.

 

Share this post


Link to post
Share on other sites

Hi @cjx2240,

I've not come across this before. Hoping to have some time toward the end of next week, so will look at it then and see if I can replicate.

Cheers,

Chris

Share this post


Link to post
Share on other sites

Hi @cjx2240,

I've tried to replicate this without success. I tried adding another account with a valid token from a different account, and I just got the 'User could not be added' response.

Adding the second user with an incorrect token should not have resulted in a record being added to the database - I'm sure that this is what has caused the subsequent issues. It sounds like the original user details were partially overwritten with the new (incorrect) ones. No idea how this could've happened. Are there similarities in the usernames/ids? Are the two accounts linked in some way on the IG side? 

Cheers,

Chris

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...