CodeCanyon Flow-Flow - WordPress Plugin

How to Set Up and Use CodeCanyon Flow-Flow Effectively

CodeCanyon Flow-Flow is not just for displaying a single social media feed. In this guide, we will look at how to turn it into a managed social content block for WordPress: prepare the site, connect sources, build a stream, adjust the visual layout, verify cache refreshes, and understand where to look if posts are not showing up.

This guide is written for cases where the plugin has already been chosen or is being evaluated as a working tool for a brand page, event page, portfolio, review section, media hub, or user-generated content campaign. It does not cover buying the plugin or activating a license. The focus here is on features, safe setup, result validation, and the limitations you should understand before placing the block on a live site.

Flow-Flow relies on external social network APIs, which means some of its behavior depends not only on WordPress but also on account access, source visibility, platform limits, refresh scheduling, and hosting capacity. If you treat the plugin as a "drop in the shortcode and forget it" tool, it is easy to miss important settings. If you build the stream as a small system instead - source, cache, design, moderation, validation - it becomes much more predictable.

How Flow-Flow Fits into a WordPress Site

Flow-Flow works as a social content aggregator. The user creates individual sources in the admin panel, combines them into a stream, and displays the result on a page using a shortcode or a builder element, if that integration is available in your setup. For visitors, it appears as a single grid, wall, gallery, or widget made up of cards from different channels.

The plugin's core distinction is the separation between feed and stream. A feed is a specific source: for example, a public Facebook page, an Instagram account, a YouTube channel, an RSS feed, or WordPress posts. A stream is the assembled block where you can connect one or more feed sources. This model is useful when the same source needs to appear in different places across the site, but with different styling or moderation rules.

According to the official CodeCanyon page, the plugin supports many social sources, RSS, and WordPress content, along with design settings, filtering, caching, load-more buttons, lightbox, search, and sorting. But in day-to-day use, what matters is not using every feature at once but following the right sequence: first the source and access, then the stream and cache, then the visual layout and public-facing check.

Practical rule of thumb: if you are showing a single Instagram feed in a sidebar, setup will be short. If you are building a wall from several networks for a campaign, review section, or event page, plan moderation, refresh frequency, and server load in advance.

The plugin does not replace the social networks themselves or bypass their rules. If a platform API does not provide private content, restricts hashtags, or requires a business account, Flow-Flow cannot display more than what is available through the official data-access methods. This is especially important for Instagram, Facebook, and other platforms that require authorization: the issue is often not in the WordPress template but in the token, account type, or source configuration.

When a Social Wall Is Actually Useful

A social stream works best where you need to show live content rather than a static curated set. That might be brand activity, customer reviews, event coverage, a video collection, a team portfolio, an RSS news feed, or a dedicated user-generated content page. CodeCanyon Flow-Flow is useful because it lets you combine different sources within one visual system instead of installing a separate plugin for every network.

Brand or Company Page

On a corporate site, the stream can serve as social proof. For example, you can connect posts from the official page, YouTube videos, and the company's RSS news. Visitors see not just marketing copy but evidence of real activity. In this scenario, the priority is not the maximum number of cards but clean moderation, a tidy grid, and no conflicts with page caching.

Hashtag Campaign or Event

For an event or campaign, it makes sense to collect hashtag posts, partner content, and your own announcements. This is where risk appears: user-generated content can be random, controversial, or out of step with the brand tone. For campaigns, filters, keyword exclusions, manual pre-moderation, and a separate test stream where an editor reviews the result before publishing are all useful.

Reviews, Case Studies, and User-Generated Content

If the goal is to showcase reviews and real examples of product use, a social wall helps combine posts from multiple sources into a single block. But that section should not be left fully automatic. Reviews have context: an outdated post, an unsuitable image, a questionable comment, or a removed source can damage trust. In this case, it is better to show fewer cards, with proper filtering and regular checks of feed-source status.

Media Hub with Video and Visual Content

YouTube, Vimeo, Instagram, Pinterest, and RSS can all serve as sources for a media hub. In that case, decide up front what matters most: videos, images, short posts, or links. You can mix everything, but the grid will become noisy. It is usually better to create several streams, such as "videos," "social reviews," and "news," rather than one oversized block trying to do everything.

Who the Plugin Is For, and Who Should Take a Different Route

Flow-Flow is a good fit for WordPress site owners, marketers, content managers, and agencies that need a configurable social wall without paying for a separate monthly service layered on top of the site. It is especially useful when you need to combine multiple source types, keep control over design, and display the block directly inside WordPress pages.

The plugin can be excessive if all you need is one simple Instagram or YouTube widget with no mixed sources. In that case, a dedicated plugin may be easier: fewer settings, fewer dependencies, fewer failure points. Flow-Flow becomes most valuable when the combination of "multiple sources - unified design - moderation - cache - refresh checks" actually matters.

There is also a technical side to consider. If the site is on weak hosting and is already burdened by a heavy theme, several builders, and aggressive caching, a large social stream can add more load. The official documentation directly ties the number of streams and sources to server resources. That does not mean the plugin cannot be used, but it does mean you should start with a small set of sources and validate results in a measurable way.

It is also worth considering the state of the free version in the WordPress.org directory and the commercial version on CodeCanyon. The public page for the free build includes a closure warning related to a security issue, while the commercial listing on CodeCanyon shows its own update history. For a production site, that is a reason not to rely on a single source: check the current changelog for the commercial version, the developer's support activity, and the results of testing on a copy of the site.

What to Check Before Installation

Pre-installation prep saves more time than it seems. Most social-stream issues do not show up when you upload the ZIP file. They show up later: the source does not authorize, posts do not refresh, cron does not fire, page cache serves an old grid, and the editor cannot tell where plugin setup ends and social network setup begins.

Technical Requirements for the Site

Flow-Flow documentation for WordPress lists server requirements such as a modern PHP version, the mysqli extension, enabled cURL, GD, mbstring, allow_url_fopen, a sufficient file upload limit, and jQuery, which WordPress usually includes already. SSL is also important because some social networks require a secure connection for data transfer.

In practice, that means a simple check: open the server information in your hosting panel or ask support whether the required extensions are available. If the site runs on an outdated plan where cURL is disabled or WP Cron works unreliably, the social stream may load once and then stop refreshing.

Access to Social Accounts and Source Visibility

Before setup, make a list of the sources that should appear in the stream. For each source, answer three questions:

• Is this a public source, or does it require access from the account owner?
• Do you have permission to complete authorization through the required network?
• Has the account type, page name, linked business profile, or post visibility changed recently?

Instagram is especially sensitive because of official API restrictions. Flow-Flow documentation notes that business use cases require Business or Creator accounts, a connection to a Facebook page, and correct authorization. Meta also documents a limit on how many unique hashtags can be queried on behalf of a business account during a rolling time window. If your campaign depends on dozens of hashtags, you need to account for that before launch.

Compatibility with the Theme, Cache, and Builders

Flow-Flow can be displayed through a shortcode and through builder integrations listed on the product page. But any dynamic block depends on its environment. Aggressive minification, deferred script loading, JavaScript bundling, and HTML caching can interfere with card rendering, especially if the stream loads through AJAX or refreshes its cache in the background.

Quick test before going live: create a private test page, place one small stream on it, disable nonessential optimizations only for that page, check the browser console, and then gradually re-enable caching. It is much easier to find a conflict this way than to debug a published page with a dozen sources.

Source Count Planning

Do not start with the maximum possible setup. Even if the product page advertises support for many sources, the real server, API limits, and editorial workflow all have boundaries. A sensible starting point is one stream, two or three sources, a clear refresh schedule, and one responsible editor. After validation, you can add new sources and watch how refresh time, feed status, and public-page behavior change.

Installation and First Launch Without Unnecessary Risk

Installing a WordPress plugin is technically standard, but Flow-Flow has one important nuance: if the site previously used the free version or an older build, do not mix versions. The official documentation recommends deactivating the Lite version before installing Pro. Before updating or replacing a version, it is also wise to back up the settings through the database tab, if that tab exists in your installed build.

General Installation Sequence

1. Create a backup of the site, or at least of the database and the plugins folder.
2. Open the Plugins section in WordPress and choose Add New.
3. Use the Upload tab, select the flowflow.zip archive, and click Install Now.
4. After installation, click Activate and check whether the Flow-Flow settings item appears in the admin panel.
5. If WordPress reports that no suitable plugin was found, make sure you are not uploading the full CodeCanyon package instead of the inner installable ZIP.

An alternative method through FTP or the hosting file manager is also possible: unpack the flow-flow folder into wp-content/plugins. But for a typical administrator, uploading through WordPress is safer because there is less risk of placing the wrong folder or overwriting something unrelated.

Initial Check After Activation

After activation, do not start with design. First, confirm that the admin panel opens, the settings tabs are available, there are no PHP errors on the page, and the browser console shows no obvious JavaScript failures. Then create one test feed from the simplest available source. For some networks, that may be RSS or WordPress posts because they depend less on external authorization.

If a simple source works, move on to networks that require authorization. This order helps separate plugin issues from external API issues. If even a local WordPress source does not work, look at theme conflicts, JavaScript, PHP errors, and access permissions. If the local source works but Instagram or Facebook does not, start with authorization, account type, and source visibility.

Where Not to Rush

Do not place the stream on the home page immediately after installation. It is better to create a draft page, insert the shortcode, check the appearance while logged in as an administrator, and then open the same page in a separate window while logged out. An administrator may see error messages above the stream container, while a regular visitor may see an empty block or stale cache. You need both checks.

Setup Map: Authorization, Feed Sources, and Stream Blocks

The most useful part of configuring Flow-Flow is understanding what each tab does. The documentation describes first-time setup as the sequence Auth, Feeds, Streams, and shortcode output. That is not a random order. Authorization gives access to the network, a feed defines a specific source, and a stream combines sources into one display block.

The Auth Tab: Network Access

Start with Auth if you plan to use Facebook, Instagram, YouTube, or other sources that require a token. For Facebook and Instagram, the documentation describes a unified connection process through a developer app: the administrator clicks Connect, selects the page and the linked Instagram account, and then returns to the settings with a saved token.

The important thing here is not to confuse "I have the account login" with "the plugin has the correct permissions." If the wrong page was selected during authorization, the Instagram account is not linked to the Facebook page, an ad blocker is active, or the token has expired, the feed may be created but still fail to fetch posts. That is why you should create a small test feed immediately after authorization and check its status.

What to Check After Authorization

• The exact Facebook page linked to the required Instagram Business or Creator account is connected.
• The administrator of the social page has sufficient permissions to grant access.
• No outdated token remains in the settings after a password change or account logout.
• Ad blockers, a corporate proxy, or browser restrictions are not interfering with the return to the settings page.

The Feeds Tab: Sources and Retrieval Rules

A feed defines what exactly should be retrieved: an account, page, channel, playlist, RSS feed, or another source. When creating a feed, read the hints next to the Content to show field carefully. The documentation explicitly notes that ignoring those hints is a common mistake. An extra @ symbol, a space, an incorrect account name, or a source that has become private can all trigger a failure that visually looks like "the plugin is broken."

For each feed, define not only the source address but also the refresh logic. Flow-Flow includes settings for refresh frequency and for how many posts are loaded during each update cycle. The important point is this: the plugin looks for new posts and adds them to what has already been stored, rather than turning every run into a full reimport of the entire history. For some sources, the number of retrievable posts is limited by the API or by the network's own logic.

The Streams Tab: Building the Public Block

A stream is what you later place on a page. Inside the stream, you give it a name, connect one or more feeds through +Connect feed to stream, choose the design, behavior, and extra elements, and save the result. Once saved, a shortcode appears in the stream list.

Do not name a stream "test" and leave it that way for long. A month later, it will be hard for an editor to understand which stream controls the home page, which one belongs to the reviews page, and which one was created for troubleshooting. Use working names like "brand-social-wall," "event-hashtag-feed," "reviews-from-social," or "media-youtube-rss." That will not affect SEO, but it makes support and maintenance much easier.

Shortcode, Widget, and Builder

The documentation points to shortcode output, while the product page and the WPExplorer review mention integration with WPBakery and Elementor. If you use the standard WordPress editor, place the shortcode in a separate block or text block. If you use a builder, choose the plugin's native element only if it exists in your version and correctly displays the selected stream.

A shortcode is convenient because it is easier to move between pages and easier to test. A builder element is convenient for an editor who does not want to work with code snippets. But during troubleshooting, it is always useful to create a clean test page with a single shortcode and no complex builder layout. If the stream works there, the problem may be in the builder section settings, lazy loading, or a script conflict.

Mixing Sources Without Creating Chaos in the Feed

One of the reasons to choose Flow-Flow is the ability to mix sources. But just because you can mix everything does not mean you should. A good stream answers one editorial question: "What should the visitor understand or do after viewing this block?" If there is no clear answer, the social wall turns into a noisy showcase.

One Stream, One Job

For a brand page, you can combine official posts, videos, and news. For an event page, a hashtag, the organizer's account, and partner mentions make sense together. For a reviews page, only use sources where customer reactions, photos, or comments are actually expected. This separation makes the stream easier to understand and much easier to moderate.

If the same feed is needed in two places, do not duplicate the source without a reason. Create one feed and connect it to different streams. For example, a YouTube channel can appear in the main brand stream and separately in a media section. The differences will be in the stream design, the number of cards, the filters, and the placement on the page.

Balancing Different Networks

Social networks publish content at different rhythms. Instagram may generate lots of visual cards, YouTube fewer but more substantial ones, RSS text-heavy news items, and WordPress your own posts. If you do not configure post counts and sorting, one highly active source can crowd out the others.

Start with modest values: limit how many posts each feed loads, check how the stream looks on the page, and then increase the volume gradually. For hashtag campaigns, create a separate stream and do not immediately mix it with the corporate feed. That way, you stay in control if the hashtag starts bringing in irrelevant content.

Filtering and Exclusions

Flow-Flow supports excluding posts by word, username, and URL. This feature is useful for more than spam control. You can use it to remove repetitive technical mentions, irrelevant references, partner posts outside the campaign, or content that does not fit a product page. But filters should not be your only line of defense: people phrase things differently, and an image can still be inappropriate even if the text looks harmless.

When to Enable Manual Pre-Moderation

Manual pre-moderation makes sense for public campaigns, reviews, fundraising pages, events, and any niche where reputational caution matters. The documentation describes turning on the moderation switch while editing a feed and then approving or rejecting posts on the stream page. For a standard corporate feed, that may be unnecessary work, but for user-generated content it is often an essential control layer.

Card Design, Grid Layout, and Visitor Behavior

The visual design of a social wall affects more than appearance. Cards can function as part of the page layout, proof of brand activity, a video showcase, a reviews block, or a live event recap. That is why design should not be handled as "I will just pick the brightest preset." The right setup should answer a better question: which content type matters most, and what should the visitor notice first?

Grid, Cards, and Density

If the stream contains a lot of visual content, a card grid usually works better than a long list. If it contains a lot of text or RSS headlines, an overly dense masonry grid can make the content hard to read. For reviews, calmer cards with a clear source, date, and link work better. For events, more visual rhythm and a Show More button help avoid overloading the first screen.

Check the stream at three widths: desktop, tablet, and smartphone. The official product page mentions a responsive layout, but your theme, container spacing, and third-party styles can change the outcome. Pay special attention to card images and the lightbox. If portrait images are cropped too aggressively, adjust the card settings or reduce the grid density.

Colors and Theme Fit

Flow-Flow offers settings for colors, spacing, animations, and card content. For most sites, the best result comes from aligning the stream with the page design rather than copying the colors of each social network. Source icons can remain recognizable, but the background, spacing, card radius, and text should still look like part of the site.

If the site follows a strict design system, do not edit plugin files directly. Use the built-in style settings, extra fields for custom CSS if they are available in your version, or CSS in a child theme scoped to your own page container. Do not edit public.css inside the plugin folder just for a minor tweak, because those changes are easy to lose during an update.

Animations, Lightbox, and Interaction Buttons

Animations and lightbox features can make the stream feel more dynamic, but on a heavy page they can also add load. If the block exists mainly as social proof, a static grid and a clean button that opens the original post may be enough. If the block is meant to serve as a media gallery, lightbox and video matter more. If it is a news stream, the headline, source, and clickability come first.

Social buttons and sorting should also be enabled for a reason. On an event page, sorting by source may help visitors find videos or photos faster. On a short landing page, extra controls can distract from the main form or call-to-action button. Configure stream behavior in the context of the page, not in isolation from it.

Moderation and Publication Quality Control

A social stream should feel alive, but not uncontrolled. This is especially true for user-generated content, hashtags, reviews, and external public accounts. Flow-Flow gives you several levels of control: source selection, filtering, exclusions, manual pre-moderation, and regular feed-status checks.

Editorial Rules Before Technical Settings

Before turning on filters, define the rules: which posts may be shown, which should be hidden, who is responsible for reviewing them, and how often the stream is checked. Without rules, technical moderation turns into a series of random exclusions. For a brand, that matters a lot: one unsuitable post in a reviews block can look like an endorsement from the site itself.

• For reviews, show only posts where the context and source are clear.
• For events, exclude sensitive words and irrelevant accounts in advance if they are already known.
• For corporate news, do not mix employees' personal accounts with official channels unless there is editorial approval.
• For a product page, use fewer sources, but make sure every card helps the visitor make a decision.

Pre-Moderation as an Actual Workflow

In the documentation, manual pre-moderation is described as enabling a toggle while editing a feed and then approving or rejecting posts on the stream page while the administrator remains inside WordPress. This is not "magic protection." It is a separate workflow. It has to be assigned to a specific person, otherwise the stream stops updating or ends up waiting for approval with no clear reason.

For large campaigns, create two streams: a working stream with pre-moderation and a public stream containing only approved content. If your version does not support that approach directly, use different sources and streams and test the workflow on a private page first. The key point is simple: do not publish user-generated content without review in situations where reputational risk outweighs the benefit of automation.

When Filters Are Not Enough

A keyword filter cannot interpret image context, sarcasm, a screenshot containing text, or a post that technically avoids banned words but is still wrong for the page. That is why, for review showcases, fundraising campaigns, political topics, medical services, and content aimed at children, manual review is often the safer choice, or else a manually curated gallery may be better than an automatic wall altogether.

Practical Example: A Social Block for an Event Page

Let us look at a concrete scenario: an event organizer's site wants to show a live stream on the event page with official announcements, videos, and attendee posts collected by hashtag. The goal is not just to display a nice grid but to give visitors a sense of activity without losing control over the content.

Goal

You need a block on the event page where the first cards show official announcements, followed by hashtag posts and videos from the organizer's channel. The block should be responsive, should not hurt page speed, and should give the editor a way to remove unsuitable posts.

Preparation

Before setup, collect three sources: the official social page, a YouTube channel or playlist, and the campaign hashtag. Check that the accounts are public, the hashtag is already in use, and the administrator has access to authorize the required networks. On the site, create a draft page containing only the title, a short description, and the future stream.

Setup Steps

1. Open Flow-Flow settings and complete authorization in the Auth tab for any networks that require a token.
2. In the Feeds tab, create a separate feed for the official page, a separate feed for video, and a separate feed for the hashtag.
3. For the hashtag feed, enable filters or pre-moderation if user-generated content is expected.
4. In the Streams tab, create a stream with a clear name, such as event-social-wall.
5. Connect all three feed sources through +Connect feed to stream.
6. Configure the appearance: grid, number of cards on the first screen, the Show More button, and lightbox for media.
7. Save the stream and place its shortcode on the test page.
8. Open the page as an administrator and as a regular visitor, then compare errors, speed, and visual output.

Validation

The result can be treated as working if the page shows cards from the correct sources, the images do not break the grid, the load-more button works, and the feed sources in the admin panel show no errors. After that, check refresh behavior: add a test post to one source or wait for a real new post, then see whether it appears after the next cache refresh cycle.

The Nuance That Often Gets in the Way

If the hashtag produces no posts, do not rush to change the stream design. First, check Instagram API restrictions, the account type, the Facebook-page connection, the exact hashtag spelling, and the authorization status. If the official source works but the hashtag does not, the issue is almost always closer to API rules or feed configuration than to the WordPress template.

How to Verify the Result After Setup

Result verification should be a separate stage, not a quick glance at the page. A social wall depends on external services and background jobs, so "the cards are showing right now" does not automatically mean the setup is stable. Check the public side, the admin area, refresh behavior, cache, and how it behaves for different user roles.

Public Side of the Site

• Open the page in a private window while logged out of WordPress.
• Check that the stream container is not empty and is not showing internal service messages.
• Make sure the cards do not overflow the container width on a mobile screen.
• Click Show More if the button is enabled, and verify that additional items load correctly.
• Open an image or video in lightbox if that feature is in use.

Admin Panel and Feed Status

Open the list of streams and feeds. The documentation says the administrator can see errors above the stream container and status indicators in the list. Do not ignore warning icons. If one feed is broken, it may prevent the whole stream from refreshing properly or create the impression that the plugin is unstable.

Cache Refresh

Flow-Flow uses caching so it does not query external networks on every visitor request. That is the right approach for performance, but it requires an understanding of timing. If a post does not appear immediately, that is not always an error. First, check the feed refresh frequency, then the cron job status, and only then start changing source settings.

Compatibility with Site Cache

If the stream refreshes in the admin area but the public page still shows old content, the cause may be page caching, a CDN, or an optimization plugin. Clear the cache for that specific page, exclude the test page from aggressive optimization, and check again. If the issue disappears, configure targeted exclusions instead of disabling site-wide caching altogether.

Performance, Cache, and API Limits

A social-stream plugin always balances freshness against load. The more often it refreshes and the more sources it uses, the greater the load on the server and the higher the chance of hitting external network limits. That is why the best Flow-Flow settings are not the most aggressive ones but the most stable ones for a particular site.

What Flow-Flow Cache Actually Does

According to the product description, Flow-Flow caches feed data and serves already prepared content to visitors so the page does not wait for external APIs every time it loads. The documentation also describes settings for how many posts are fetched during an update and how often updates run. In other words, the plugin acts as an intermediate layer: it collects data on schedule, stores it, and shows visitors a ready-made grid.

If you shorten the cache interval too much, you may create unnecessary load and run into API limits. If you make updates too infrequent, the stream will look stale. For a corporate page, a moderate refresh frequency is often enough. For an event, faster checks may be needed, but those should be tested in advance rather than promising updates every minute without proof.

Settings That Affect Load

• Number of streams. Every public block adds work for preparation and rendering.
• Number of feeds in a stream. The more sources there are, the harder refreshes and troubleshooting become.
• Posts to load during update. This setting affects how many new posts the plugin tries to retrieve on each update.
• Feed update frequency. Refresh timing should match both the use case and the server's capabilities.
• Media and lightbox. Images and videos are heavier than text cards, especially on mobile devices.
• Page cache and optimization tools. They can speed up the site, but they sometimes interfere with dynamic blocks.

How Not to Overload Weak Hosting

Start with one stream and a small number of feeds. Reduce the number of posts loaded per update and increase the refresh interval if you see a cache-building message or noticeable delays. Official documentation for issues caused by a large number of feed sources recommends removing feeds with error status, lowering the number of items fetched per update, making refresh intervals less frequent, checking Cron, and reducing the number of streams or feeds if the server cannot keep up.

For events with heavy traffic, validate the stream before the campaign starts. If it builds slowly on a test page, it will not become faster under load. It is better to show fewer cards reliably than to enable a huge feed that disappears periodically.

Safe Improvements Without Editing Plugin Files

With Flow-Flow, you should not begin by editing files like FlowFlow.php, public.js, or public.css. The documentation describes the file structure, but that is not an invitation to modify the plugin core. It is safer to use design settings, custom CSS fields, a child theme, and page-level limitations.

Wrap the Stream in Your Own Container

If you need to control spacing around the block, place the stream inside a group block or builder section and assign that section its own CSS class, for example event-social-wall-wrap. After that, you can adjust the outer spacing of the container without touching the plugin's internal classes. That approach survives updates much better than editing files inside wp-content/plugins.

.event-social-wall-wrap {
  margin-top: 32px;
  margin-bottom: 32px;
}

.event-social-wall-wrap + .event-cta {
  margin-top: 24px;
}

This snippet does not change Flow-Flow's internal markup. It only controls spacing around the section that you manage in the page editor. Validation is simple: clear the page cache, open the public page, and confirm that the spacing changed while the stream cards kept their own styles. Rollback is just removing the CSS and the container class.

Exclusions in the Optimization Plugin

If the stream appears empty after minification or deferred script loading, do not disable optimization for the entire site. Create an exclusion for the page containing the stream or for Flow-Flow scripts, if your optimizer lets you target individual files. Do this only after testing on a clean page: first confirm the stream works without optimization, then restore the settings one by one.

Refresh Control Through WP Crontrol

Flow-Flow documentation suggests checking for the flow_flow_load_cache job through WP Crontrol when refresh problems occur. This is a diagnostic tool, not a permanent dependency. Use it to see whether the job exists, when it is supposed to run, and whether similar jobs are stuck. Do not delete cron events blindly: some events are recreated by plugins, and deleting them without understanding the cause may only hide the symptom.

If the Stream Does Not Refresh or Does Not Display

Troubleshooting is best done from simple to complex. First check the source and authorization, then feed status, then cron and cache, then theme conflicts or optimization conflicts. Do not change every setting at once, or you may lose track of the real cause.

Posts Do Not Appear After Creating a Feed

Symptom: the stream is created and the shortcode is inserted, but no cards appear, or an error is shown only to the administrator.

Possible causes: incorrect source name, an extra character in the Content to show field, a private account, missing authorization, an unsupported Instagram account type, or an expired token.

What to check: open the source directly on the social network while logged out, verify the exact spelling, check the feed status in the admin area, and repeat authorization through Auth if the network requires a token.

How to fix it: correct the feed, save it, rebuild the cache, and test again on the test page. If the issue involves Instagram or Facebook, check that the Business or Creator account is linked to the Facebook page and that the administrator has the required permissions.

The Feed Worked Before but Stopped Refreshing

Symptom: old cards remain visible, but new posts do not appear.

Possible causes: WP Cron is not running, the Flow-Flow cron task is missing or overdue, the social-network token has expired, the source became private, or the server cannot handle the number of feeds.

What to check: install the WP Crontrol diagnostic tool, look for flow_flow_load_cache, check the next scheduled run time, inspect feed status, and try a manual refresh.

How to fix it: remove the feed with an error, repeat authorization, reduce the number of posts per update, increase the refresh interval, or configure a server-side cron according to the developer documentation and your hosting rules.

The Message "Feeds cache is being built" Does Not Go Away

Symptom: the visitor or administrator sees that the cache is being built, but the result takes a long time to appear.

Possible causes: too many sources, heavy media, an error in one feed, a weak server, or refreshes that run too often.

What to check: temporarily disable some feeds, reduce Posts to load during update, increase Feed update frequency, and inspect cron status and PHP error logs.

How to fix it: split one large stream into several smaller ones, keep only the necessary sources, resolve the specific feed error, and test the page again after clearing cache.

400 Bad Request Error

Symptom: the feed does not retrieve data, and the status or message shows a request error.

Possible causes: missing network authorization, an incorrectly copied token, incorrect feed configuration, an expired Facebook token, or exceeded request limits.

What to check: the Auth tab, the accuracy of the source field, token validity, and the number of posts being loaded.

How to fix it: repeat authorization, recreate the feed with correct data, reduce API load, and verify whether the network restricts the chosen use case.

The Stream Exists in the Admin Area but the Page Is Empty

Symptom: the stream is saved and the shortcode is inserted, but the public page shows an empty block.

Possible causes: a JavaScript conflict, deferred script loading, page cache, a builder error, an unsuitable container, or the block being hidden by theme CSS rules.

What to check: a clean page with only the shortcode, the browser console, a mode without minification, and how the page renders for an administrator versus a guest.

How to fix it: exclude the page or the Flow-Flow scripts from aggressive optimization, test the shortcode outside the builder, and then restore page elements one at a time.

The Design Changed or Cards Disappeared After an Update

Symptom: after updating the plugin, the stream looks different, some cards are missing, or settings no longer apply.

Possible causes: API integrations changed, UI settings changed, old cache conflicts with the new version, or edits were made directly inside plugin files.

What to check: the changelog, the settings backup, custom CSS, Flow-Flow cache, and site cache.

How to fix it: clear caches, resave the stream, check feed statuses, and move edits into the child theme or settings rather than plugin files. If the update affects API connections, repeat authorization according to the documentation.

When CodeCanyon Flow-Flow Is a Strong Choice

Flow-Flow is worth using when you need more than a simple social button and instead want a managed social showcase: multiple sources, a unified design, moderation, caching, and clear output inside WordPress pages. It is especially useful for brands, agencies, event pages, reviews, portfolios, media hubs, and user-generated content campaigns.

Before rollout, check more than just appearance. Validate stability too: authorization, API limits, cron behavior, page cache, mobile rendering, lightbox behavior, and the status of every feed. If the stream fails on a private test page, do not publish it on the homepage. First bring it to a stable pattern of "source - refresh - stream - result."

If, after reading this guide, you understand which sources you will connect, who will moderate the content, and how refreshes will be verified, you can move on to a practical test and download the installation file. Start with one small stream, document the settings, and expand the feed only after the first scenario works reliably for both the administrator and a regular visitor.