Hi guys,
We’ve fixed this issue in Bricks 1.9.8 beta, now available as a manual download in your account (see changelog).
Please let us know if you are still experiencing issues.
As with any beta release, please do not use it on a production or live website. It is only meant for testing in a local or staging environment.
Feed is gone again. Theme version 1.9.8 Can You check the solution ? I´m going refresh token manually for the 3rd time. Thanx
Hello guys,
I have the same issue on all my sites, the token is inserted in Bricks settings but the feed totally disappeared.
Thank you!
Hi Emeric,
Please send temporary login credentials and a link to this thread to help@bricksbuilder.io using the email address you used during the purchase.
Hi! Is this already fixed or not? I need to update a client’s website only because of this
Hi pcomedy,
Most problems occur because the token has expired.
I quote @charaf’s email response to Emeric:
Your access token expired, so you need to regenerate the token manually by following our guide here: How to get your Instagram Access Token – Bricks Academy.
The token expires every 60 days. Once it’s expired you can’t regenerate it, so you should create a new one. We have created a CRON job that should refresh the token every 20 days. But you need to make sure that your WordPress site has a real server CRON rather than relying on WordPress CRON which can be unreliable, especially so if the site doesn’t receive many visitors.
For example:
- Cloudways created this guide: https://www.cloudways.com/blog/wordpress-cron-job/.
- This is from Siteground: How to Replace the WordPress Cron with a Real Cron Job Tutorial - SiteGround Tutorials
- And this one from WooCommerce/AutomateWoo: Replace WP Cron with a real Cron job Documentation - WooCommerce
4 months ago I asked If I could make my own cron job in order to fix this and @charaf told me you were working in a solution. Now you are telling me to make my own cronjob. Funny.
My response did not suggest that you need to create your own CRON job from scratch. As I mentioned in the reply that Stefan shared:
“We have created a CRON job that should refresh the token every 20 days. But you need to make sure that your WordPress site has a real server CRON rather than relying on WordPress CRON which can be unreliable, especially so if the site doesn’t receive many visitors.”
It’s recommended that your WordPress site uses a real server CRON because the default WordPress CRON is not a real CRON job and depends on site traffic to run, which can be unreliable. This is a general recommendation for any WordPress site, not just for our CRON job.
Mate, I’m just trying to show ig images on some dude’s website. This shouldn’t be so complicated.
So, should I update the site to the last bricks version? And then how do I know if the cronjob is “real” or “not real”?
Yes, you should update to the latest Bricks version. We’ve created a CRON job to refresh the Instagram access token every 20 days.
The suggestion about CRON jobs isn’t specific to Bricks—it’s just general advice for WordPress sites. WordPress CRON jobs only run when someone visits the site, so they might not be reliable on low-traffic sites. Setting up a real server CRON ensures consistency, but it’s entirely optional.
If you want to learn more, there are many resources online, but here’s an example article: https://raidboxes.io/en/blog/wordpress/wordpress-cron-jobs/
And again, the feed is gone. Is token refresh really works ? Doesn’t seem so…
My client’s feed has also stopped working again.
Not sure how long it’s been inactive.
Meta deprecated the Basic Display API which was used to retrieve the access token previously: https://developers.facebook.com/blog/post/2024/09/04/update-on-instagram-basic-display-api/
This means that you would have to retrieve a new token using the new “Instagram API with Instagram Login” by Meta. We have updated the instructions in our academy article to reflect the new steps required: How to get your Instagram Access Token – Bricks Academy.
Unfortunately, this is outside of our control. But our implementation works with the new API out of the box (including token refresh after you retrieve it the first time).