Code Snippets plugin review and common issues

Smash Balloon caches feed data to prevent excessive API calls. To force an immediate refresh: go to Instagram Feed → All Feeds → [feed] → Settings → Advanced and click “Clear Feed Cache.” After clearing, the next page visit fetches fresh Instagram data. If the feed regularly fails to update automatically: (1) verify the Instagram API connection is still valid in Instagram Feed → Settings → Configure → Instagram Sources — the API token may have expired; (2) the feed’s cache interval may be set too long — reduce it in feed settings; (3) if Instagram posts are still not appearing after refresh, the connected Instagram account’s API permissions may have changed.

Instagram API connection failures since 2023 are often related to Meta’s stricter API access requirements: (1) Instagram Basic Display API (used for personal accounts) is deprecated — you must use a Business or Creator account connected to a Facebook Page; (2) in Smash Balloon → Settings → Configure, follow the setup wizard using “Connect with Instagram Business” — not the old Basic Display API flow; (3) ensure your Instagram account is connected to a Facebook Business Page; (4) verify the Meta app in Facebook Developer is approved and the Instagram API access is enabled; (5) use HTTPS on your site — Meta APIs require SSL.

Smash Balloon feeds have per-breakpoint column settings. Edit the feed and go to Layout settings. Configure columns separately for desktop, tablet, and mobile. For mobile: set columns to 2 or 1 depending on your preference. The feed width also inherits from the container it is placed in — if the containing div has a fixed width larger than the mobile viewport, the feed overflows. Ensure the shortcode or widget is placed in a fluid-width container. Clear the feed cache after adjusting layout settings.

Hashtag filtering requires Smash Balloon Pro. In the feed settings, find the Filters section and add your hashtag (without the # symbol). When filtering by hashtag: only posts that include the specified hashtag in their caption appear in the feed. Combine hashtag filtering with post moderation to curate a specific subset of your Instagram content — useful for campaigns where you want to display only campaign-specific posts on a landing page.

Smash Balloon adds an Instagram Feed Gutenberg block. In the block editor, search for “Instagram Feed” and add the block to your page. Select the feed to display from the dropdown (feeds must be created first in Instagram Feed → All Feeds). Configure the display directly in the block editor sidebar: width, layout override, number of posts. Alternatively, use the shortcode [instagram-feed feed=ID] in a Shortcode block. The Gutenberg block provides a live preview of the feed in the editor.

Since Meta deprecated the Instagram Basic Display API (2024-2025), personal Instagram account support has been significantly limited. Smash Balloon now primarily requires an Instagram Business or Creator account connected to a Facebook Page. If you have a personal account that you want to display, consider converting it to a Creator account (free, no obligations) which retains the personal aesthetic while gaining API access. Check Smash Balloon’s current documentation for the exact API access requirements as Meta’s policies continue to evolve.

Several free alternatives exist: Elfsight Instagram Feed (limited free tier), Embedsocial (free tier with branding), and MasonryLayout Instagram (open-source). The trade-off is typically limited features, branding watermarks on the free tier, or maintenance risk compared to Smash Balloon’s established plugin. For basic Instagram grid display without lightbox, filtering, or multiple layout options, some free alternatives provide adequate functionality at zero cost.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.