Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

Smash Balloon Facebook Feed Not Working: Causes and How to Fix It

Smash Balloon Facebook Feed Not Working: Causes and How to Fix It

Short answer

Most Smash Balloon Facebook feeds break when the access token expires after a password change or lost admin role. Reconnect the Page under the plugin's Sources settings with a Page admin account, then clear the feed cache and your page cache. Check Page restrictions and WP-Cron if it still fails.

Key takeaways

  • Read the admin-only error message first.
  • Password changes and lost admin roles break the access token.
  • You must manage the Page you want to display.
  • Clear the feed cache and page cache to refresh posts.
  • Age or country limits on a Page can block the feed.
  • Group feeds were affected by Facebook API changes.

Why is your Smash Balloon Facebook feed not working?

A Smash Balloon Facebook feed usually stops because the connection to Facebook expired, the connected account lost Page admin rights, the feed is cached, or Facebook's API rejected the request.

Smash Balloon's Custom Facebook Feed plugin pulls posts from Facebook through Meta's API. It needs a valid connection, called an access token, to fetch anything.

When that token breaks, the feed shows an error, stays blank or stops updating. Nothing on your site changed, but Facebook stopped answering.

Other causes include Page restrictions, a feed pointing at a source you do not manage, a stale cache and server issues that block outgoing requests.

For background on the plugin family, see our explainer on what Smash Balloon is.

What are the common causes at a glance?

Most broken Facebook feeds come down to a short list of causes.

SymptomLikely causeFirst fix
Error message shown to adminsExpired or invalid access tokenReconnect the Facebook source
Feed stopped updatingCache or failed background updatesClear the feed cache
PPCA error noticeShowing a Page you do not adminConnect a Page you manage
Blank feed, no errorPage restrictions or empty sourceCheck Page age and country limits
Feed worked, then failed after password changeToken invalidatedReconnect the account
Group feed stoppedFacebook group API changesUse a Page feed instead

Smash Balloon keeps a list of Facebook API errors and fixes that matches error codes to causes.

What does the error message on your feed say?

Smash Balloon shows error details to logged-in admins on the page and in the plugin settings, so read that message first because it usually names the exact cause.

Visitors usually see an empty space or a generic notice. Admins see more detail, often with an error code from Facebook.

Check two places:

  1. The front end. Visit the page with the feed while logged in as an admin.
  2. The plugin dashboard. Open Facebook Feed in the WordPress menu and look for notices at the top of the screens.

Write down the error code. Codes about tokens point to a connection problem, while permission codes point to Page access.

Has the access token expired?

Yes, very often, because changing your Facebook password, removing your admin role or revoking app access invalidates the token, so reconnect the source in the plugin settings.

The token is tied to the Facebook account that connected the feed. If that person changes their password or leaves the Page, the token stops working.

To reconnect:

  1. Go to Facebook Feed, then Settings in WordPress.
  2. Open the Sources section.
  3. Remove the broken source or choose to reconnect it.
  4. Click Add Source and log in with a Facebook account that is an admin of the Page.
  5. Approve the permissions Smash Balloon asks for.
  6. Reassign the source to your feed if needed and save.

Smash Balloon's own article on feeds that are unable to connect to the Facebook API covers this flow. Menu names can change between versions, so follow the current screens.

Are you an admin of the Facebook Page?

You need admin-level access to the Page you want to show, because Facebook only lets apps read a Page's posts on behalf of people who manage it.

If you connect your personal account but you are not a Page admin, the plugin may not be able to fetch posts, or it may show a PPCA notice.

PPCA stands for Page Public Content Access. It is a Facebook permission for reading Pages you do not manage, and most small sites cannot get it. Meta describes how apps read Page data in its Graph API documentation.

Smash Balloon explains this in its PPCA error notice article. The practical fix is to ask the Page owner to give you full control of the Page, then reconnect.

If a client owns the Page, they can connect the source themselves, or add you with the right role in their Page settings.

Is the feed showing cached posts?

Smash Balloon caches feed data to stay within Facebook's limits, so a feed that looks stuck may just be cached, and clearing the cache forces a fresh request.

Caching keeps your site fast and avoids hitting Facebook too often. The trade-off is that new posts appear after a delay.

To refresh the feed:

  1. Open Facebook Feed, then Settings.
  2. Find the option to clear the feed cache and click it.
  3. Purge your page caching plugin and any CDN.
  4. Reload the page in a private window.

If you use a caching plugin, the page itself may be cached with old feed content. Our guide on clearing cache in WordPress shows where to purge it.

You can also shorten how often the plugin checks for new posts, but very short intervals add load and may trigger rate limits.

Is WP-Cron updating the feed?

Smash Balloon relies on scheduled tasks to refresh feeds in the background, so if WP-Cron does not run, the feed can freeze on old posts.

WordPress runs scheduled tasks when someone visits the site. On quiet sites, or where WP-Cron is disabled, those tasks can stall.

Signs of a cron problem include feeds that only update after you clear the cache, and other scheduled tasks running late.

Check wp-config for a DISABLE_WP_CRON line. If it is set to true, your host should run a real server cron job instead. The WordPress cron documentation explains how that works.

Does the Page have age or country restrictions?

Facebook Pages with age or country restrictions often cannot be read by apps, so remove those limits if you want the posts to appear in your feed.

Pages that sell alcohol, for example, often limit access by age. Apps like Smash Balloon cannot pass those checks, so the API returns nothing.

Open the Page's settings on Facebook and review audience restrictions. If you must keep them, an embedded Page plugin from Meta may be a better fit than an API feed.

Also check that the Page is published, has public posts, and is not hidden or unpublished.

Did your feed show a Facebook group?

Facebook changed group access for third-party apps, so group feeds may no longer work, and switching the feed to a Page is the usual fix.

Meta retired the API that let apps read group posts. Tools that relied on it, including social feed plugins, lost the ability to show group content.

If your feed used a group, create a Page feed instead, or link to the group with a simple button. Check Smash Balloon's current documentation for any updates on group support.

Is your server blocking requests to Facebook?

Some hosts, firewalls or security plugins block outgoing connections, so if the plugin cannot reach Facebook at all, check your server's outgoing access and SSL setup.

The plugin needs to make https requests from your server to Facebook. If those fail, you may see connection or timeout errors.

Things to check:

  • Security plugins that limit outgoing requests.
  • Outdated SSL libraries on old servers, which can break secure connections.
  • Host firewalls on locked-down plans.

Tools, then Site Health in WordPress runs connection tests and flags failed loopback or https requests. The Site Health screen documentation explains each check.

Could a plugin or theme conflict break the feed?

Yes, JavaScript optimisation or another social plugin can break the feed layout or loading, so test with optimisation features off and other plugins disabled.

If the feed shows posts but looks broken, or the load more button does nothing, JavaScript is the likely issue.

Exclude Smash Balloon's scripts from delay, defer and combine features in your optimisation plugin. Then clear caches and test again.

For deeper testing, the Health Check plugin's troubleshooting mode disables plugins only for your session. Turn plugins back on one at a time until the feed breaks.

How do you keep the feed working in future?

Connect the feed with a long-term Page admin account, keep the plugin updated, turn on error alerts and avoid sharing the connection with people who may leave.

A few habits prevent most repeat failures:

  • Use a stable account. Connect with an owner's account rather than a temporary contractor's.
  • Update the plugin. Updates follow Facebook API changes. The free version is on WordPress.org as Smash Balloon Social Post Feed.
  • Enable notifications. Smash Balloon can email you when a feed has an error.
  • Reconnect after password changes. Do it right away.

If you also show Instagram, our guide on using Smash Balloon Instagram Feed covers similar connection steps.

For other ways to show Facebook content, see how to add Facebook to WordPress.

Frequently asked questions

Why did my Smash Balloon Facebook feed suddenly stop?

The most common reason is an expired access token. Changing the Facebook password, removing the connected person as Page admin or revoking app permissions all break it. Reconnect the Page source in the plugin settings using an account that manages the Page.

What is the PPCA error in Smash Balloon?

It means the plugin tried to read a Facebook Page that the connected account does not manage. Reading other Pages needs a special Facebook permission most sites cannot get. Connect a Page you are an admin of, or ask the owner to connect it.

Why are new Facebook posts not showing in my feed?

The feed and the page are probably cached. Clear Smash Balloon's feed cache, purge your caching plugin and CDN, then reload in a private window. If posts still lag, check that WP-Cron runs so background updates happen.

Can Smash Balloon show a Facebook group feed?

Facebook retired the API that let third-party apps read group posts, so group feeds may no longer work. Switching to a Facebook Page feed is the usual fix. Check Smash Balloon's documentation for the current status.

Why does the feed work for me but not for visitors?

Admins may see a fresh version while visitors get a cached page that captured an error or empty feed. Purge all caches. Also check that Page age or country restrictions are not blocking content for the app.

Sources

  1. Smash Balloon Social Post Feed WordPress.org
  2. Facebook API errors Smash Balloon
  3. Facebook PPCA error notice Smash Balloon
  4. No posts displayed: unable to connect to Facebook API Smash Balloon
  5. Cron WordPress Developer Resources

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.