Instagram Photos

[DonnonGT]

Hello. There was a change that affected what could be shared through the Instafeed API, but now I'm not sure if it is preventing the plugin from working. I ran across several pages that referenced the changes. I'm sorry if I was wrong about those changes breaking the plugin though. I thought the changes were preventing me from getting the access token. I was incorrect.

I went to http://instagram.com/developer and fought it for a couple of hours. The registration  form would not submit. It said the form was not completely filled out and the captcha info was wrong. I must have filled it out twenty times. Turns out the form isn't working properly on MacOS. I started Windows 7 via Parallels and the form submitted just fine, the first time. So, I have the Instagram user id installed in the widget and the access token installed in the plugin settings, but the widget doesn't work. The widget doesn't preview any content while I still have the Block Manager open and when I close it, the widget disappears completely. I have been trying to get this thing working for more than 5 hours and I don't know what else to try.

[Adriano Faria]

Do you have  PHP cURL extension enabled? This is a requirement for the plugin. 

I’ll test tomorrow in the morning anyway. 

[DonnonGT]

I have cURLSSL running. Does it have to be cURL specifically?

[Adriano Faria]

Yes, AFAIK.

You can only have one enabled. Either Curl (without SSL support) or CurlSSL (Curl with support for SSL). I don’t use SSL and it’s s a requirement, so support is provided for cURL only.

Ask your host to rnable it and make a test.

[DonnonGT]

I'll change over to cURL and see if it fixes things.

[DonnonGT]

Changing from cURLSSL to cURL made no difference. The plugin still wouldn't work.

[Adriano Faria]

I will test it in a couple of hours. 

[Adriano Faria]

8 hours ago, DonnonGT said:

Changing from cURLSSL to cURL made no difference. The plugin still wouldn't work.

 

1 hour ago, Adriano Faria said:

I will test it in a couple of hours. 

My host disabled cURL!

But I just checked a couple of other clients and it seems to be working:

• http://www.motards.re/ (bottom of page: Instagram Motards.re)
• http://www.tacklenfish.com.au/ (bottom of page: Instagram Photos)

Requested my host to re enable it so I can make a screen video.

[Adriano Faria]

Ok, host just re enabled it and it's working fine:

You probably are inserting the wrong Access Token in the settings. The way I did:

Then after you get the CLIENT ID (mine is obscured above), go to this URL: https://instagram.com/oauth/authorize/?client_id=YOUR_CLIENT_ID&redirect_uri=http://localhost&response_type=token

Replace the YOUR_CLIENT_ID by the Client ID you just get when you created the app and you'll be redirected to a URL with the token on it.

 

 

[DonnonGT]

I've done that. I have the client id in the widget and I have the token in the plugin config.  I've deleted and repeated the steps above three times now. It just is not working. No content is being displayed.

[DonnonGT]

I reinstalled cURL, instead of cURLSSL, to try once again to see if it would fix the plugin, but the plugin still didn't work. In addition to that, running cURL instead of cURLSSL causes problems with the IPS software. With cURL installed, I get this warning in my ACP:

and this error throughout the site:

The IPS software apparently uses cURLSSL to do its software license checks. Many third-party plugins and apps use cURLSSL as well. If you aren't getting a license warning on your site, I am guessing that your ISP is using cURLSSL.

Anyway, my Instagram account's profile area shows that the plugin is an approved application, I have the client id number added to the widget and the access token added to the plugin config. I don't know what else to do. Any ideas?

[Adriano Faria]

Well, there’s no magic there. Either you’re doing it wrong or the extension isn’t “properly” available.  

I showed 3 sites working.

No, no ideas. If the problem is cURL, then there’s nothing I can do, sorry. The file description is pretty clear when it says it is required. I can change it in a future version but I have absolutely NO ETA to do that.

[DonnonGT]

So, I've just wasted $15 and about ten hours of my time.

[DonnonGT]

When I type in the url you access via cURL in the plugin, with my user id and access token plugged in, I get a page not found error. Should this happen?

 

[DonnonGT]

FWIW, I just put a cURL test script on my site and cURL is functioning.

 

I've also looked up my Instagram user id again and generated my access token one more time. They are installed where they are supposed to be. There are no cURL errors in my server's logs.

Could this be a version issue? I am running the latest version of IPS. Do you know what version the sites you used as examples are running?

 

[Adriano Faria]

7 hours ago, DonnonGT said:

So, I've just wasted $15 and about ten hours of my time.

Yes, since it’s pretty clear the requirements but as I don’t want to waste all day ling again here, I just filled a refund request to IPS. You will get your $15 back as account credit. 

[Adriano Faria]

On 13/10/2017 at 11:01 PM, DonnonGT said:

So, I've just wasted $15 and about ten hours of my time.

 

On 14/10/2017 at 6:17 AM, Adriano Faria said:

Yes, since it’s pretty clear the requirements but as I don’t want to waste all day ling again here, I just filled a refund request to IPS. You will get your $15 back as account credit. 

You were refunded. 

[Adriano Faria]

What's New in Version 1.0.1

Enhancement:

• Removes the cURL PHP Extension requirement. It now uses IPS4 methods

Instagram API changes:

• IMAGES: it now displays only images from the tojen owner 
• COMMENTS are not being displayed and no change in documentation were done yet, so I'll wait to make it compatible when it's time
• The widget option MEDIA LIKED isn't returning data, so it will display only images from the User ID informed

[Adamas]

I do have an access_token and I have tried multiple different instagrams ID. However, for all of them nothing shows up in the feed.

 

[Adriano Faria]

20 minutes ago, Adamas said:

I do have an access_token and I have tried multiple different instagrams ID. However, for all of them nothing shows up in the feed.

 

Paste your token here. Just change some numbers/letters randomly. I want to see the “format” of that string. 

Did you create the app in the Instagram.com/developer? Did you authorized it?

There’s a ton of tutorials in the Google to show you how to do that.

[Adriano Faria]

9 hours ago, Adamas said:

I do have an access_token and I have tried multiple different instagrams ID. However, for all of them nothing shows up in the feed.

 

Yes, I just tested and can confirm it. It is showing only images from the token owner:

Apparently this is one of the several changes they made in the API lately.

Read: https://www.instagram.com/developer/endpoints/users/#get_users

Quote

Get information about a user.
The public_content scope is required if the user is not the owner of the access_token.

According to the text above, it's possible if you require a public_content: https://www.instagram.com/developer/authorization/

Only in this page I used 3:

So yeah, that's how it is now. I will update the file description.

[Adamas]

On the link you just posted it says public_content applications are no longer being accepted. Does this mean that this plugin no longer can get feeds from other people instagram without their permission?

[Adriano Faria]

Yes. 

My plugin uses Instagram API to display their content. I’m not responsible for the changes they made. They changed the API. Now it displays only for the token owner. Simple like that.

[Adamas]

Can I receive a refund then? As this no longer does what I want?

[Adriano Faria]

No. The plugin keeps doing what it is supposed to do: it connects to instagram via API and list photos. The fact Instagram changed their API doesn’t make me culprit of anything. 

Feel free to request to IPS, if you feel you should. I just disagree.