We just had an entire production site taken down by a password change. Seems a bit over the top.
Reported error:
GuzzleHttp\Exception\ClientException: Client error: `GET https://graph.instagram.com/me/media?fields=id%2Cmedia_type%2Cmedia_url%2Cthumbnail_url%2Ctimestamp%2Cpermalink%2Ccaption&access_token=<scrubbed>&limit=` resulted in a `400 Bad Request` response: {"error":{"message":"Error validating access token: The session has been invalidated because the user changed their pass (truncated...) in GuzzleHttp\Exception\RequestException::create() (line 113 of /var/www/html/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php).
I believe this is coming from FbInstagramAccess::getClientToken ln 117
Install Instagram Lite
Configure module
Place block
Update IG password
Note "unexpected error" WSOD
1. Wrap offending call in a try catch block
1. Ignore following logic if response threw an exception
1. Continue displaying old content until the account is updated
[] Review/test
N/A
Updated FbInstagramAccess::getClientToken to catch and log exceptions
N/A
Needs review
2.0
Code
Wraps the offending call in try/catch, displays generic error message and logs exception to watchdog.
For our customers site the problem was add block level.
This is a fast fix for that.