WordPress.org

Forums

Alpine PhotoTile for Instagram
Instagram feed not found error (42 posts)

  1. 2GirlsTrippin
    Member
    Posted 1 year ago #

    The widget was working great from the start - until today. Now I get the error:

    "Sorry: - Instagram feed not found."

    A sample of this can be found at http://www.2GirlsTrippin.com. Thanks in advanced for any suggestions.

    https://wordpress.org/plugins/alpine-photo-tile-for-instagram/

  2. theAlpinePress
    Member
    Plugin Author

    Posted 1 year ago #

    That is strange. I'll try to look into it.
    Best, Eric

  3. 2GirlsTrippin
    Member
    Posted 1 year ago #

    Hi Eric,

    Thanks so much for looking into it! In the meantime, I'm going to remove the widget since it's severely slowing down my load time. Please let me know if you need me to put it back for your troubleshooting purposes.

    Thanks again for a beautiful plugin! I'm so excited for it to work again! :)

    Best regards,
    Lena

  4. theAlpinePress
    Member
    Plugin Author

    Posted 1 year ago #

    Can you please try the new update? I have also added a "Plugin Tools" page that should make it easier to identify problems.
    Best, Eric

  5. 2GirlsTrippin
    Member
    Posted 1 year ago #

    Eric!

    That update works like a charm! Everything's back to awesome!

    Thanks again for your quick help & a great plugin!!
    Lena

  6. dakluck
    Member
    Posted 1 year ago #

    Fixed my issues, I was having the same experience at http://www.landroverlove.com.

    Edit: Same problem, still not loading properly the first time, but if i reload it will find and load...

    Around the world and Driver links.

  7. theAlpinePress
    Member
    Plugin Author

    Posted 1 year ago #

    Hello,
    I checked your website and saw the problem you described on the Driver page. I noticed that you are using the User Tag option, which I know to be a little problematic. Instagram does not actually let you filter by user AND tag. Therefore, the plugin fetches many photos for the user and then searches the results for the desired tag. Because of this, the plugin may need to contact Instagram 2 to 4 times before it has found enough photos. In your case, I think this is causing the plugin to timeout (maybe your server is a little slow to make the request or Instagram takes a little too long to respond). However, as you have seen, if you try again, things may start to work.
    Recommendations:
    First, I have increased the max fetch time from 10 seconds to 20 seconds (you can delete and re-install the plugin to see if this helps). This might solve your problem but it might also increase the load time. Second, you could try the "Loading Test" on the plugin's "Tools" page to see if it gives a useful message. Third, displaying fewer images should help.
    Sorry I don't have the perfect answer, but "sometimes" problems are actually much harder to solve than "every time" problems.
    -Eric

  8. skiwhitefish
    Member
    Posted 1 year ago #

    I am also experiencing this issue. Using the latest plugin I used the test tool and here's my output. I have not changed anything in Instagram lately.

    [alpine-phototile-for-instagram user="skiwhitefish" src="global_tag" tag="skiwhitefish" imgl="fancybox" style="cascade" col="2" size="M" num="24" highlight="1" align="center" max="100" nocredit="1"]

    Load from the Instagram feed
    
    P0, UTC:18:18:18.6474, Start plugin.
    P1, UTC:18:18:18.6481, Enqueue styles and scripts
    P2, UTC:18:18:18.6483, Retrieve Photos
    P3, UTC:18:18:18.6484, Check cache
    P4, UTC:18:18:18.6491, Using get_transient()...
    P5, UTC:18:18:18.6497, No cache found
    P6, UTC:18:18:18.6497, Check for access_token
    P7, UTC:18:18:18.6498, Try accessing Instagram feed
    P8, UTC:18:18:18.6498, Use wp_remote_get() (cURL) to make request
    P9, UTC:18:18:19.2215, Request complete
    P10, UTC:18:18:19.2215, An error occured.
    P11, UTC:18:18:19.2215, Code: 400
    P12, UTC:18:18:19.2215, Message: Bad Request
    P13, UTC:18:18:19.2215, Failed using wp_remote_get()
    P14, UTC:18:18:19.2215, Check your Instagram feed. If the feed is empty, then the problem is with Instagram. If you see a full page of text, then the problem is with the Alpine plugin or your web server.
    P15, UTC:18:18:19.2216, Check Results
    P16, UTC:18:18:19.2216, Print Message
    P17, UTC:18:18:19.2216, Loading complete
    Output
    
    Sorry:
    
    - Instagram feed not found.
  9. skiwhitefish
    Member
    Posted 1 year ago #

    Ugh. Nevermind. I reset the "secrets" in Instagram under Manage Clients and it's working again. Sorry to waste your time.

    BUT... my photocentric coworker is miffed because this plugin does not provide "credit" to the user's photo. Anyway to display the Intagram usertag on the photo overlay from the feed? Thanks!! :-)

    Link to photo page I'm talking about...

  10. theAlpinePress
    Member
    Plugin Author

    Posted 1 year ago #

    Sorry, there is not currently a way to show the user, but I do think it's a good idea. I'm still trying to decide how to add captions, but I am working on it.
    Best, Eric

  11. wildcatjrotcbooster
    Member
    Posted 11 months ago #

    I am having the same problem. I just installed this week and it worked fine for a short time. When it stopped working, I tried method 2 and still have an error. http://peaktkd.net/instagram/

    'Load from the Instagram feed

    P0, UTC:3:6:4.3575, Start plugin.
    P1, UTC:3:6:4.3591, Enqueue styles and scripts
    P2, UTC:3:6:4.3594, Retrieve Photos
    P3, UTC:3:6:4.3597, Check cache
    P4, UTC:3:6:4.3607, Using get_transient()...
    P5, UTC:3:6:4.3646, No cache found
    P6, UTC:3:6:4.3646, Check for access_token
    P7, UTC:3:6:4.3648, Try accessing Instagram feed
    P8, UTC:3:6:4.3648, Use wp_remote_get() (cURL) to make request
    P9, UTC:3:6:13.4979, Request complete
    P10, UTC:3:6:13.4980, An error occured.
    P11, UTC:3:6:13.4980, Code: 500
    P12, UTC:3:6:13.4980, Message: Internal Server Error
    P13, UTC:3:6:13.4981, Failed using wp_remote_get()
    P14, UTC:3:6:13.4981, Check your Instagram feed. If the feed is empty, then the problem is with Instagram. If you see a full page of text, then the problem is with the Alpine plugin or your web server.
    P15, UTC:3:6:13.4982, Check Results
    P16, UTC:3:6:13.4984, Loading complete
    Output

    Load from cache

    P0, UTC:3:6:13.4995, Start plugin.
    P1, UTC:3:6:13.5011, Enqueue styles and scripts
    P2, UTC:3:6:13.5014, Retrieve Photos
    P3, UTC:3:6:13.5017, Check cache
    P4, UTC:3:6:13.5019, Using get_transient()...
    P5, UTC:3:6:13.5024, No cache found
    P6, UTC:3:6:13.5024, Check for access_token
    P7, UTC:3:6:13.5026, Try accessing Instagram feed
    P8, UTC:3:6:13.5026, Use wp_remote_get() (cURL) to make request
    P9, UTC:3:6:22.6506, Request complete
    P10, UTC:3:6:22.6507, An error occured.
    P11, UTC:3:6:22.6507, Code: 500
    P12, UTC:3:6:22.6507, Message: Internal Server Error
    P13, UTC:3:6:22.6507, Failed using wp_remote_get()
    P14, UTC:3:6:22.6507, Check your Instagram feed. If the feed is empty, then the problem is with Instagram. If you see a full page of text, then the problem is with the Alpine plugin or your web server.
    P15, UTC:3:6:22.6509, Check Results
    P16, UTC:3:6:22.6509, Loading complete
    Output'

  12. cappybara
    Member
    Posted 11 months ago #

    Same exact problem here. I also just installed this week, and it was working fine for a day or so. The debugger tells me I'm getting a 500 error. The site is hosted on Dreamhost.

    System Check

    Check the settings and extensions on your web server.
    Current PHP version of your server: 5.3.27
    Check: curl_init function found.
    Check: Plugin failed to connect to Instagram.com.
    Code: 500, Message: Internal Server Error.

    Check: json_decode function found.
    Check: Sample JSON successfully decoded and parsed.

  13. wildcatjrotcbooster
    Member
    Posted 11 months ago #

    The peaktkd.net site is hosted on Siteground, but has the same 500 code.

    It looked awesome when it was working. Have been trying to fix for several hours. Have reset secret. Deleted user, etc, still not working. Very sad as it looked awesome for a while.

  14. theAlpinePress
    Member
    Plugin Author

    Posted 11 months ago #

    Sorry for the delayed response. Are you still getting this message?

    A 500 error code means that an error occurred on the Instagram side of things. "Worked for a short time" is an important detail. Perhaps Instagram went down for a period of time or perhaps there are other settings that prevent you from receiving data. I would contact your hosting provider and see if they can connect to instagram.com using the cURL php extension.

    Have you tried any other Instagram plugins? If other plugins worked and mine did not, I would appreciate hearing so that I can check what they do differently.

    Best, Eric

  15. wildcatjrotcbooster
    Member
    Posted 11 months ago #

    I have tried Yakadada and Justified Image Grid. All 3 are having the same problem. I have the site host checking on the problem and will let you know what they find.

  16. wildcatjrotcbooster
    Member
    Posted 11 months ago #

    They claim there is nothing wrong on their end. I am not buying it. I am having the same problem with every instagram plugin I try.

    The only error in the log is this:

    [07-Apr-2014 01:12:17 UTC] WordPress database error Table 'peaktkd0_wp767.wp_wfPerfLog' doesn't exist for query select count(*) as cnt from wp_wfPerfLog made by do_action_ref_array, call_user_func_array, wordfence::dailyCron, wfDB->querySingle

  17. theAlpinePress
    Member
    Plugin Author

    Posted 11 months ago #

    Thanks for letting me know. I assume you are using a shared server and perhaps another user got the entire server block (just an unfounded idea, but might explain why it stopped working). Regardless, I'm sorry the plugin, and ever other Instagram plugin, is not working for you.
    Best, Eric

  18. wildcatjrotcbooster
    Member
    Posted 11 months ago #

    The host checked everything out and claims that it is a problem with instagram. Says that instagram blocks for having too many requests. It's odd because it worked at first. They suggested that as I tested it multiple times for different displays that instagram then blocks after multiple requests. The host also sent me links to articles on stackoverflow.

    I'm developing a tool for checking the integrity of links in a web page.

    I've noticed that various Instagram URLs will return a HTTP 500 response in cases where if one were to visit the given URL in a browser one would get a HTTP 200 response accompanied by the expected resource.

    This is when requesting regular Instagram URLs as one would do as a browser user and not when using the REST API.

    A typical request/response using cURL:

    curl -v http://instagram.com/p/YKTkxHBA-P/
    * About to connect() to instagram.com port 80 (#0)
    * Trying 54.225.159.246... connected
    > GET /p/YKTkxHBA-P/ HTTP/1.1
    > User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
    > Host: instagram.com
    > Accept: */*
    >
    < HTTP/1.1 500 Server Error
    < Cache-Control: no-cache
    < Content-Type: text/html
    < Date: Tue, 15 Oct 2013 08:31:09 GMT
    < Server: nginx
    < Content-Length: 87
    < Connection: keep-alive
    <
    <html><body><h1>500 Server Error</h1>
    An internal server error occured.
    </body></html>
    * Connection #0 to host instagram.com left intact
    * Closing connection #0
    I did for some time get HTTP 200 responses in such cases but am now consistently getting HTTP 500 responses.

    This is all specific to a given host; such URLs, even when sending requests with cURL, will return HTTP 200 responses from other machines.

    Due to this being specific to the host sending the requests I suspect a form of rate limiting or request filtering by IP is going on, however I can find no documentation to the effect.

    Will Instagram officially return a HTTP 500 response as above due to a given IP being denied access?

    instagram internal-server-error
    share|improve this question
    asked Oct 15 '13 at 8:42

    Jon Cram
    5,64253767

    I'm having the same problem. Is it what you (we) are supposing? Aka when your IP gets "banned" you get 500s? – kitsched Nov 6 '13 at 7:02
    3
    @kitsched Yes, I'm assuming that a banned IP gets HTTP 500 responses. That's the only conclusion I can come to with the information I have available to me. I admit the information I have may well be incomplete. – Jon Cram Nov 7 '13 at 12:28

    Same here, about the suppositions, I mean. I submitted a request / question to them, asking for my IP to be unbanned. I'm curious if anything will happen. Thanks for your answer. – kitsched Nov 7 '13 at 16:11

    @JonCram Same problem here. Did you find the real reason of this error? I can reproduce this error on individual server. All API requests work fine on other servers. It looks like a ban from Instagram, but they didn't notify about the ban. And sometimes I'm able to make successful request to Instagram API, but it works very rarely... – Michael M. Kalygin Mar 19 at 16:47

    I am now suddenly getting this also. It appears it may be an error on Instagram's side now. I find it odd that it works in my web browser but not on my server though. Using the same URL. – Francis Pelland Mar 19 at 19:34
    show 7 more comments
    2 Answers
    activeoldestvotes
    up vote
    -2
    down vote
    I'm almost 100% sure this happens because the domain/IP address is blocked from the Instagram API.

    Reason:

    Works to get the JSON in the browser. Doesn't work to get with cURL from webservice.
    I copied my exact application from my primary domain (were the application doesn't work) to another domain. Same application worked.
    The strange thing is that you get a "500 Internal Error" back and not a message "Your IP is blocked".

    share|improve this answer
    answered Mar 27 at 16:35

    Kim
    268114
    1
    But how to explain that sometimes the request is working from the same ip and sometimes not. Moreover, what is the exact criteria for banning?? :-/ – ivicaa Mar 29 at 16:10
    add comment

    up vote
    -2
    down vote
    This is an IP rate limit. If you want to skip the part where you contact Instagram and wait for the monkey crew they have working over there to fix the problem, simply assign 1000 IPs to your server and loop through them randomly for your requests. You won't see anymore 500's.

    Cheers.

    share|improve this answer
    answered Mar 31 at 22:04

    user3482950
    11

    Lots of people start getting these 500's when you're testing API integration. Because you're most likely requesting the same Instagram page data over and over again during testing, Instagram thinks its a bot and promotes the IP address, this is where you start to see 1/10th of your requests being accepted. I stand behind my given answer, it is the easiest way around this issue, as their API is a pile of sh*t with no real support that is ready and willing to help you. – user3482950 Apr 3 at 19:38
    add comment

  19. wildcatjrotcbooster
    Member
    Posted 11 months ago #

    Thought I posted the link but dont see it

  20. theAlpinePress
    Member
    Plugin Author

    Posted 11 months ago #

    It sounds like the server your website is hosted on has been blocked from Instagram. I test the plugin frequently and so I would be surprised if you got yourself blocked by just changing around the settings. Seems more likely that another user on your server is responsible. But who really knows?
    Thank you for passing along the stackoverflow link. It does not look like anyone else was able to come up with a solution though.

  21. nightowl99
    Member
    Posted 11 months ago #

    I am having the same problem again. Worked fine for a while and now stopped, but only on my sites which are hosted on Namecheap. This also affects other Instagram plugins. Sites on other hosts are still fine with no problems.

    Hopefully we can find out how to resolve the issue. Thank you, Eric, for hanging in there with us!

  22. 2GirlsTrippin
    Member
    Posted 11 months ago #

    Me again. It appears that I'm getting that error again.

    "Sorry: - Instagram feed not found."

    Any suggestions are greatly appreciated. :)

    Thanks!

  23. moonlissa
    Member
    Posted 11 months ago #

    Hey there,

    I'm receiving the same error message. "Sorry - Instagram feed not found."

    The widget was working well up until the past few days.

    Looking forward to any suggestions as well.

    Thank you! :)

  24. John
    Member
    Posted 11 months ago #

    Not working for me either.

  25. shoshanna
    Member
    Posted 11 months ago #

    Ours stopped working a few days ago, too.

    Current PHP version of your server: 5.4.27
    Check: curl_init function found.
    Check: Plugin failed to connect to Instagram.com.
    Code: 500, Message: Internal Server Error.
    Check: json_decode function found.
    Check: Sample JSON successfully decoded and parsed.

  26. shoshanna
    Member
    Posted 11 months ago #

    Just in case this is useful information, I had the client try to connect with another plugin (Simple Instagram) and he's unable to authorize the app he set up for that plugin. I'm seeing lots of StackOverflow discussions on various Instagram problems from the last week or so.

  27. theAlpinePress
    Member
    Plugin Author

    Posted 11 months ago #

    Hello everyone,

    Can someone please delete and reinstall the plugin and then send the output from the Plugin Loading Test on the Plugin Tools page? I have edited the code to simply display more information.

    I don't know if this is relevant to anyone, but Instagram does have an access limit: "You are limited to 5000 requests per hour per access_token or client_id overall." However, this does not sound like what people are experiencing. Plus, with the plugin's cache, this should never be a problem.

    My best guess is that Instagram has begun blocking the IP addresses of certain servers. With shared hosting services, the activities of one user can sometimes get the entire server blocked. Again, I have no way of verifying that this is the case, but if Instagram is running just fine and you are seeing a 500 error, it means that you are being blocked from accessing Instagram's servers.

    I will continue to search StackOverflow and try to contact Instagram (who never seem to respond). I will let you know if I identify a problem/solution.

    Best, Eric

  28. nightowl99
    Member
    Posted 11 months ago #

    This is what I get:

    Load from the Instagram feed
    
    P0, UTC:23:29:41.3768, Start plugin.
    P1, UTC:23:29:41.3783, Enqueue styles and scripts
    P2, UTC:23:29:41.3786, Retrieve Photos
    P3, UTC:23:29:41.3789, Check cache
    P4, UTC:23:29:41.3829, Using get_transient()...
    P5, UTC:23:29:41.3845, No cache found
    P6, UTC:23:29:41.3845, Check for access_token
    P7, UTC:23:29:41.3847, Try accessing Instagram feed
    P8, UTC:23:29:41.3848, Use wp_remote_get() (cURL) to make request
    P9, UTC:23:29:50.4697, Request complete
    P10, UTC:23:29:50.4698, An error occured.
    P11, UTC:23:29:50.4698, Code: 500
    P12, UTC:23:29:50.4699, Message: Internal Server Error
    P13, UTC:23:29:50.4699, Try request again using Alpine's cURL function
    P14, UTC:23:29:59.6023, Request complete
    P15, UTC:23:29:59.6024, An error occured.
    P16, UTC:23:29:59.6024, Code: 500
    P17, UTC:23:29:59.6026, Content Received: <html><body><h1>500 Server Error</h1> An internal server error occured. </body></html>
    P18, UTC:23:29:59.6026, Failed using wp_remote_get()
    P19, UTC:23:29:59.6026, Check your Instagram feed. If the feed is empty, then the problem is with Instagram. If you see a full page of text, then the problem is with the Alpine plugin or your web server.
    P20, UTC:23:29:59.6028, Check Results
    P21, UTC:23:29:59.6029, Print Message
    P22, UTC:23:29:59.6029, Loading complete
    Output
    
    Sorry:
    
    - Instagram feed not found.
    Load from cache
    
    P0, UTC:23:29:59.6036, Start plugin.
    P1, UTC:23:29:59.6052, Enqueue styles and scripts
    P2, UTC:23:29:59.6055, Retrieve Photos
    P3, UTC:23:29:59.6059, Check cache
    P4, UTC:23:29:59.6060, Using get_transient()...
    P5, UTC:23:29:59.6077, No cache found
    P6, UTC:23:29:59.6077, Check for access_token
    P7, UTC:23:29:59.6079, Try accessing Instagram feed
    P8, UTC:23:29:59.6080, Use wp_remote_get() (cURL) to make request
    P9, UTC:23:30:8.7053, Request complete
    P10, UTC:23:30:8.7054, An error occured.
    P11, UTC:23:30:8.7054, Code: 500
    P12, UTC:23:30:8.7054, Message: Internal Server Error
    P13, UTC:23:30:8.7054, Try request again using Alpine's cURL function
    P14, UTC:23:30:17.7950, Request complete
    P15, UTC:23:30:17.7950, An error occured.
    P16, UTC:23:30:17.7950, Code: 500
    P17, UTC:23:30:17.7952, Content Received: <html><body><h1>500 Server Error</h1> An internal server error occured. </body></html>
    P18, UTC:23:30:17.7952, Failed using wp_remote_get()
    P19, UTC:23:30:17.7952, Check your Instagram feed. If the feed is empty, then the problem is with Instagram. If you see a full page of text, then the problem is with the Alpine plugin or your web server.
    P20, UTC:23:30:17.7954, Check Results
    P21, UTC:23:30:17.7954, Print Message
    P22, UTC:23:30:17.7955, Loading complete
    Output
    
    Sorry:
    
    - Instagram feed not found.

    I should probably also mention that this particular page gets hardly more that 10 - 20 hits per day.

  29. cissi.wong@gmail.com
    Member
    Posted 11 months ago #

    Hi there!

    I also have this problem... I just updated to WP 3.9 and with that Instagram stopped working. I'm getting this error:

    "P0, UTC:6:57:36.7212, Start plugin.
    P1, UTC:6:57:36.7227, Enqueue styles and scripts
    P2, UTC:6:57:36.7228, Retrieve Photos
    P3, UTC:6:57:36.7231, Check cache
    P4, UTC:6:57:36.7246, Check for access_token
    P5, UTC:6:57:36.7248, Try accessing Instagram feed
    P6, UTC:6:57:36.7248, Use wp_remote_get() (cURL) to make request
    P7, UTC:6:57:37.1853, Request complete
    P8, UTC:6:57:37.1853, An error occured.
    P9, UTC:6:57:37.1853, Code: 400
    P10, UTC:6:57:37.1854, Message: Bad Request
    P11, UTC:6:57:37.1854, Try request again using Alpine's cURL function
    P12, UTC:6:57:37.6381, Request complete
    P13, UTC:6:57:37.6381, An error occured.
    P14, UTC:6:57:37.6381, Code: 400
    P15, UTC:6:57:37.6382, Content Received: {"meta":{"error_type":"APINotAllowedError","code":400,"error_message":"you cannot view this resource"}}
    P16, UTC:6:57:37.6382, Failed using wp_remote_get()
    P17, UTC:6:57:37.6382, Check your Instagram feed. If the feed is empty, then the problem is with Instagram. If you see a full page of text, then the problem is with the Alpine plugin or your web server.
    P18, UTC:6:57:37.6383, Check Results
    P19, UTC:6:57:37.6383, Print Message
    P20, UTC:6:57:37.6383, Loading complete
    Output

    Sorry:

    - Instagram feed not found."

    The site in question is http://www.beyoga.se/, however I have the same plugin up and running on http://www.sanghayoga.se/about/ without problem (although I have not yet updated WP on that site).
    Any ideas out there?

  30. charlesspot
    Member
    Posted 11 months ago #

    I similarly updated to WP 3.9 and am now getting the same error message above.

    Load from the Instagram feed

    P0, UTC:17:3:29.9028, Start plugin.
    P1, UTC:17:3:29.9040, Enqueue styles and scripts
    P2, UTC:17:3:29.9042, Retrieve Photos
    P3, UTC:17:3:29.9044, Check cache
    P4, UTC:17:3:29.9053, Using get_transient()...
    P5, UTC:17:3:29.9063, No cache found
    P6, UTC:17:3:29.9063, Check for access_token
    P7, UTC:17:3:29.9064, Try accessing Instagram feed
    P8, UTC:17:3:29.9064, Use wp_remote_get() (cURL) to make request
    P9, UTC:17:3:30.0347, Request complete
    P10, UTC:17:3:30.0347, An error occured.
    P11, UTC:17:3:30.0348, Code: 400
    P12, UTC:17:3:30.0348, Message: Bad Request
    P13, UTC:17:3:30.0348, Try request again using Alpine's cURL function
    P14, UTC:17:3:30.1422, Request complete
    P15, UTC:17:3:30.1423, An error occured.
    P16, UTC:17:3:30.1423, Code: 400
    P17, UTC:17:3:30.1424, Content Received: {"meta":{"error_type":"APINotAllowedError","code":400,"error_message":"you cannot view this resource"}}
    P18, UTC:17:3:30.1424, Failed using wp_remote_get()
    P19, UTC:17:3:30.1424, Check your Instagram feed. If the feed is empty, then the problem is with Instagram. If you see a full page of text, then the problem is with the Alpine plugin or your web server.
    P20, UTC:17:3:30.1425, Check Results
    P21, UTC:17:3:30.1425, Print Message
    P22, UTC:17:3:30.1425, Loading complete
    Output

    Sorry:

    - Instagram feed not found.
    Load from cache

    P0, UTC:17:3:30.1430, Start plugin.
    P1, UTC:17:3:30.1440, Enqueue styles and scripts
    P2, UTC:17:3:30.1442, Retrieve Photos
    P3, UTC:17:3:30.1444, Check cache
    P4, UTC:17:3:30.1445, Using get_transient()...
    P5, UTC:17:3:30.1448, No cache found
    P6, UTC:17:3:30.1449, Check for access_token
    P7, UTC:17:3:30.1450, Try accessing Instagram feed
    P8, UTC:17:3:30.1450, Use wp_remote_get() (cURL) to make request
    P9, UTC:17:3:30.2561, Request complete
    P10, UTC:17:3:30.2561, An error occured.
    P11, UTC:17:3:30.2561, Code: 400
    P12, UTC:17:3:30.2561, Message: Bad Request
    P13, UTC:17:3:30.2561, Try request again using Alpine's cURL function
    P14, UTC:17:3:30.3622, Request complete
    P15, UTC:17:3:30.3623, An error occured.
    P16, UTC:17:3:30.3623, Code: 400
    P17, UTC:17:3:30.3624, Content Received: {"meta":{"error_type":"APINotAllowedError","code":400,"error_message":"you cannot view this resource"}}
    P18, UTC:17:3:30.3624, Failed using wp_remote_get()
    P19, UTC:17:3:30.3624, Check your Instagram feed. If the feed is empty, then the problem is with Instagram. If you see a full page of text, then the problem is with the Alpine plugin or your web server.
    P20, UTC:17:3:30.3626, Check Results
    P21, UTC:17:3:30.3626, Print Message
    P22, UTC:17:3:30.3626, Loading complete
    Output

    Sorry:

    - Instagram feed not found.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.