litemotiv

@emiliopro i’ve just tested with 3.2.2 and it works okay here for docs, so i’m guessing that it may have another cause on your installation.

@ciorici i see it yes, that’s interesting thanks. I hadn’t touched it anymore since the last reactions here, so it spontaneously started working again by itself. I’m curious whether it will keep working now or if it will give an error again in a while, let’s wait a bit and see. ??

P.s. i think i notice a small bug with the feed output, the first image of the feed currently is:

https://cstor.eu/bteh-nl/2020/01/312624976_569562731311989_8813756711299758002_n-180×320.jpg

Which has a width of 180 and a height of 320. In the feed output on the page however this code is used:

<img src="https://cstor.eu/bteh-nl/2020/01/312624976_569562731311989_8813756711299758002_n-180x320.jpg" width="320" height="180">

The width is set as 320 and the height as 180, which is the other way around.

@ciorici thank you for the extra testing and feedback, it’s unfortunate that there doesn’t seem to be a clear reason or solution to fix it.

@ciorici

Most probably, it’s just a local problem with your server or a plugin conflict. Or maybe Instagram blocked your server’s IP temporarily.

That’s not it, i have another website on the same webserver which has the same plugins enabled, and there the WPZOOM widget works okay. That one uses a Business account though.

And lastly, maybe you want to manually connect to one of our Instagram accounts using this Access Token key

Your wpztravel account works okay here. The only difference i notice is the account type, which says Personal for your account, Business for the other website that works okay, but Media_creator for the account that doesn’t work:

View post on imgur.com

Perhaps you can try the access token to see if it works for you?

IGQVJXbkltdnp3Nmw1S1BHbG5SWHI5NkpiZAjFERUNldW1RejNQUjNfRk5JYlNYd3JjSkRxUFU5SF9mc2tsbkRJMnBGQ254dE1ZAazA3ZA2JkUTM2Nko3TEFKTWQwNjlBQ2ZAUcm1nLUh3

@ciorici since WPZOOM recently added the option for business accounts, is it possible that this causes the problem? Business accounts are connected through Facebook, and personal accounts are not. Since my client’s account is a Non-Profit account, which is neither personal nor business, could it be that the plugin is trying to retrieve the feed using the wrong format? See the screenshot below for context:

View post on imgur.com

@ciorici i have revoked the access token via the Instagram settings yesterday after @inamoro advised that, but the same error occurred after reconnecting it.

This particular feed used to work okay using the legacy widget. The error started occurring when i noticed a few days ago that about half of the Instagram thumbnails were missing because their URLs were expired, so i lowered the renewal timeout from 1 day to 4 hours. After that this error started to show.

Hi @ciorici

This is using the shortcode and the same error is visible in the preview panel in the admin: https://i.imgur.com/3lyO6yb.png

@inamoro it’s https://bring-the-elephant-home.org/ and the Instagram profile is https://www.instagram.com/bring_the_elephant_home/. It’s classified as a non-profit organization, which i believe is neither a business nor a personal account.

Hi Ina,

This is my client’s installation so i don’t have access to their FB account, but it all feels strange to me. What does Facebook have to do with this exactly? I really cannot send my non-technical client on a random search through Facebook settings to find some unknown setting on integrations, especially since it’s not clear if this problem can actually be solved there.

I have removed the WPZOOM widget as an app from Instagram and reconnected it, but it keeps giving the same error:

Instagram Widget misconfigured or your Access Token expired. Please check Instagram Settings Page and re-connect your account.

Geting items from the Instagram API Feed failed. Invalid response.

The access token itself is okay:

View post on imgur.com

Please note that the error i pasted earlier was only visible because i added some debug code to the WPZOOM widget.

Update, i added some debug lines to the WPZOOM widget and got the actual error:

[body] => {"error":{"message":"Error validating access token: The session has been invalidated because the user changed their password or Facebook has changed the session for security reasons.","type":"OAuthException","code":190,"fbtrace_id":"A_1bRHjf2aNUODtvgVSbpV1"}}

Perhaps it would be good if the widget gave back those actual errors instead of the more generic “Invalid response”.

Hi @planvova

I can confirm the fix works on our installations, thanks!

Update: i can confirm the issue also occurs on standalone (non-multisite) installations.

@jeffpaul PHP8 might be something to look into in terms of compatibility. WordPress 5.9 is supporting up to PHP8.1 but Safe SVG appears to be lacking PHP8 support at this point.

I am having similar issues as the topic starter, i get this error page on the wpzoom website:

View post on imgur.com

Is there a way to find out whether this is a problem on the wpzoom site, or somewhere else in the authentication process?

Thanks in advance,
-lite

@AnAdminer CDN and ephemeral should give the same results, the increased latency occurs when there is no local storage available for operations such as with the stateless mode.