JUX Social Stream - Joomla Extension

Guide to Setting Up and Using JUX Social Stream

JUX Social Stream is best treated not as page decoration, but as a Joomla module for cleanly displaying updates from social channels on your site. This guide walks through the practical path: what to verify before installation, how to publish the module in the right position, which settings to enable after the first launch, how to build a working feed from Facebook, Instagram, YouTube, RSS, and other sources, and then how to verify the result without guesswork.

This material does not repeat the product's short description. What matters here is understanding the mechanics: what data the module pulls from external services, which settings affect the visual output, why the feed may not appear immediately after installation, where to look for conflicts with the template or cache, and when a different tool may be the better choice.

This guide is written for Joomla site owners, webmasters, and content managers who already have the extension's installation package and want to safely display a social feed on a page. Purchasing, licensing, and obtaining the paid version are outside the scope here. The focus is on configuration, use, verification, and troubleshooting of a module you already have.

What Problem a Social Feed Solves on a Joomla Site

JUX Social Stream combines social updates into one block and displays them on the public side of the site as either a list or a grid. This is useful when a site should not look disconnected from the brand's real activity: news, videos, photos, community posts, RSS updates, and individual social channels can all be shown alongside your main content.

It is important not to overestimate a module like this. It does not replace a full blog, comment system, CRM, or social network inside Joomla. Its job is narrower: to display an external social stream inside the site, give visitors a quick signal that the project is active, and avoid making them open multiple tabs just to check whether the project is alive.

For Joomla, this is especially convenient because the module can be tied to a template position and specific menu items. For example, you can show the feed only on the home page, a community page, an events section, or a page for a school, club, gallery, portfolio, or news project. This approach is better than manually inserting random widgets into articles, because the administrator keeps control through Joomla's standard module system.

Official materials confirm two core display modes: List and Wall. List works well for a compact rotating feed, while Wall displays posts in a grid similar to a media wall. In both cases, the idea is the same: data comes in from external services, the module applies its settings, and the site template displays the finished block.

Who This Module Fits, and Where It Is Unnecessary

JUX Social Stream works best on sites where social activity genuinely supports trust in the project. That can include travel companies, schools, clubs, nonprofits, small media outlets, events, creative studios, communities, local brands, and projects where photos, videos, or short updates appear more often than full articles.

If the site itself is updated infrequently but the social channels are more active, the module helps close the gap between the main site and those external platforms. Visitors see fresh posts directly inside Joomla and understand that the project is not abandoned. It is also convenient for editors, since some short updates do not need to be manually copied into site content.

But there are also cases where the module may be unnecessary or even harmful. If the social channels are irregular, visually weak, full of questionable comments, or unrelated to the purpose of the page, it is better not to place them above the fold. A social feed should strengthen the page, not distract the user from a lead form, purchase, event registration, or important reading.

There is also a technical side. Social networks frequently change APIs, tokens, access rules, and restrictions. The JED changelog for JUX Social Stream shows that the developers have already fixed issues related to Facebook, YouTube, Instagram, Twitter, and Joomla compatibility. Because of that, this kind of module needs periodic review after updates to Joomla, the extension, the template, and the social platforms themselves.

Practical takeaway: use JUX Social Stream where social posts serve as proof of activity, not just as decorative filler. If the feed does not help users make a decision or better understand the project, move it lower on the page or keep it only in a dedicated section.

What to Check Before Installation

Before installing, do not start with the upload button. First, make sure the site has the conditions the module needs to pull data from external services and display it correctly in the template. Many social feed issues are caused not by the extension itself, but by the server, cache, outdated template, or incorrect module publishing.

Joomla and Environment Compatibility

In JED, JUX Social Stream is listed as compatible with Joomla 3, 4, 5, and 6, while the official Joomlaux site may show a less up-to-date product page. It is best to treat that mismatch as a reason to verify information in both places: the developer's site and the Joomla Extensions Directory. There is no need to tie this guide to a specific Joomla build, but before installation you should confirm that the ZIP package you selected matches your CMS branch.

Joomlaux documentation also lists older server requirements: Apache, PHP, MySQL, XML, Zlib, OpenSSL, and cURL. For a modern site, this is not a list of exact minimum versions so much as a baseline requirement: the server must be able to make outbound HTTPS requests, or the module will not be able to retrieve data from social platforms. If the hosting environment blocks outbound requests, even a correctly published module may show an empty block or stall during loading.

Access to Social Channels

For a basic RSS source, a feed URL is enough, but for YouTube, Facebook, Instagram, and some other sources, you will typically need IDs, keys, or tokens. JUX Social Stream documentation lists separate fields for different networks: Facebook ID, FB Access Token, Youtube ID, Api key, Instagram ID, and tokens for personal or business sources.

Do not leave this data until the last minute. If the administrator does not have access to the social account, business page, or developer console, configuration can stall on the very first source. First decide which channels you actually need, then prepare the current authentication method for each one according to the official rules of the platforms themselves.

Template Position and Page Placement

JUX Social Stream is a module, so the result depends on standard Joomla mechanics: module position, publish status, access level, and menu assignment. Even perfect social source settings will not help if the module is published in a position that does not exist in the current template, or assigned to the wrong page.

Before installation, review the list of positions in your template and decide where the feed will read naturally. For a wall with multiple posts, a wide position in the content area works best. For a compact list, a sidebar can work, but only if the width does not break the cards or the text.

Installing the Module and Performing the First Check

JUX Social Stream is installed through Joomla's standard installer. In the Joomlaux documentation, the module package is listed as mod_jux_social_stream.zip. In modern Joomla versions, the exact interface path may differ slightly, but the logic stays the same: open the extension installer, upload the ZIP package, and wait for a successful installation message.

Safe Installation Sequence

1. Create a backup of your files and database, especially if the site is already live and receiving traffic.
2. Make sure you have the archive specifically for JUX Social Stream, not a similar extension from the same category.
3. Open the Joomla admin panel and go to extension installation through the Extensions management area.
4. Upload the ZIP package through the package upload tab and wait for the successful installation message.
5. Open the Modules list and find the installed JUX Social Stream module.
6. Do not add every social network at once yet. Start with one simple source and verify the output first.

This sequence reduces the risk of false diagnosis. If right after installation you connect five networks, enable Wall, filters, rotation, template caching, and custom styles, it becomes much harder to tell where the actual problem is.

First Launch Without Extra Settings

After installation, create or open the module and temporarily choose a simple configuration. RSS or YouTube are convenient for initial testing because it is easier to separate an authorization problem from a display problem. If you use a token-based source, make sure the token is current, copied without extra spaces, and tied to the correct account.

Publish the module in a visible template position, set the access level to Public, and assign it to a single test page. If the site has a separate hidden menu item for testing, use that. This lets you avoid showing an unverified block to visitors while giving you room to safely debug the appearance.

Quick post-install check: the module should appear in the Modules list, have publish status enabled, be assigned to a test page, and contain at least one configured source. If there is not even a module container on the public side of the site, start by checking the Joomla position and menu assignment, not the social tokens.

Positions, Menus, and Access: The Joomla Side of the Setup

JUX Social Stream has its own settings for social sources, but the page output is still controlled by Joomla. That means part of the configuration people often skip belongs not to the module itself, but to its environment: template position, menu assignment, access level, module order within the same position, and the test page. If this layer is configured carelessly, an administrator can spend hours changing tokens and limits while the real issue sits in Joomla's standard module system.

This is especially important for social feeds because the block is usually placed with intent, not at random. Wall mode needs width, List mode needs predictable height, and both modes should appear only where social content supports the purpose of the page. Joomla lets you control all of that without editing code.

How to Choose a Template Position

First decide where the block should sit from the reader's point of view. If this is the home page for a club, travel company, or creative studio, the social wall may fit well after the introductory description or a benefits section. If it is a contact page, the feed usually works better below the main contact details so it does not pull attention away before the user has found the address, phone number, or form.

The position must exist in the exact template used on the selected page. In Joomla, a site can apply different template styles to different menu items, so a position visible on the home page is not necessarily available on an internal page. If the module seems to "disappear" after moving it, check not only the module itself but also the template style assigned to that menu item.

Wide Position for Wall

Wall mode works best in an area where cards can flow into multiple columns. A narrow sidebar often makes the wall look like a long feed with cropped images. If the template does not provide a suitable position, do not try to compensate with excessive CSS. It is usually simpler to switch to List mode or create a dedicated page with a wide content area.

Compact Position for List

List mode can go in a narrower area, but it is important to control height and rotation. If the list appears next to navigation, a form, or contact details, do not make the items rotate too quickly. Users should have enough time to read a card without losing focus on the page's main task.

Assignment by Menu Item

Joomla does not display a module based on the URL alone. It uses menu items and the related Itemid. That means the Menu Assignment setting should be part of the plan, not a last random click. For testing, it is best to choose the option to show the module only on one menu item. Once everything works, you can expand the assignment to a larger group of pages.

If a page is opened only through a link inside an article and does not have its own menu item, the module may behave unpredictably because Joomla does not receive a clear menu context. In these cases, a hidden menu helps. Create a menu item that is not shown in the main navigation, link it to the needed page, and assign JUX Social Stream specifically to that item.

Test Menu Item

A test menu item is useful not only for initial setup. It is also worth keeping after launch as a safe place to test new tokens, CSS tweaks, switching from List to Wall, or adding a new source. That lets you see the result before changes go live on a public traffic page.

Access and Audience

For most social feeds, the access level should be Public. If you set it to Registered or another restricted level, regular visitors will not see the module, and that can easily be mistaken for an API problem. Restricted access makes sense only on private community pages where the feed is intended for logged-in members.

Module Order Within the Same Position

If several modules already exist in the same position, the order also affects how the page feels. A social feed rarely belongs above the page's main message. The exception is media-heavy or event sections where the feed itself is the primary content. In most other cases, give users context first and show updates afterward.

After changing the order, check the page at different widths. On mobile devices, modules from a sidebar can drop below the main content, and the social feed may end up much farther down than you expected. That is not a JUX Social Stream issue, but normal behavior in a responsive template.

Joomla-layer checklist logic: first position and width, then menu assignment, then access, then order within the position, and only after that the fine-tuning of social sources. This sequence reveals the real cause faster if the module is not visible.

Settings Map After Installation

It is best to go through JUX Social Stream settings from top to bottom: first choose the display type, then limit the number of items, then enable extra interface elements, and only after that move on to individual social networks. This order helps you avoid getting lost in a long list of settings.

Choosing Social Style: List or Wall

The key setting is Social Style. If you choose List, the module works as a compact rotating feed. In that mode, height, direction, delay, and autoplay matter most. If you choose Wall, the feed becomes a grid of posts, where container width, clean card layout, and proper responsiveness across screen sizes matter more.

For a home page or a "Find Us on Social Media" section, Wall is usually the better fit because visitors can immediately see several posts and choose what interests them. For a sidebar, a tightly structured landing page, or a small updates block, List is often better because it takes up less space and does not dominate the page.

Limits and Rotation

The Limit Feed Type and Limit Feed Count fields are not just about neat design. The more external posts the module tries to display, the heavier the page can become, especially if the cards include images or video. For the first launch, use a small limit and increase it only after checking speed and stability.

For List mode, the documentation includes settings such as Rotate, Direction, Rotate Delay, Auto play, and Controls. You do not need to enable them all at once. Automatic rotation can make sense in a compact informational block, but it can also be irritating if the user is trying to read a longer text. If the block sits next to a lead form or an important description, manual control or a longer delay is usually better.

Filter and External Links

The Filter setting adds navigation by social network. It is useful when the feed combines multiple sources such as Facebook, Instagram, YouTube, RSS, and others. If there is only one source, the filter only adds unnecessary interface clutter.

The External setting relates to outgoing links and sharing. Enable it deliberately: the social feed should help the user, not pull them away from a key page too early. On a landing page with a lead form, viewing the cards may be enough. On a community page, outbound clicks and sharing tend to feel more natural.

jQuery and noConflict

JUX Social Stream documentation specifically calls out Enable jQuery and Enable noConflict. This is an important block for Joomla sites that use templates, page builders, galleries, and other modules that may also load JavaScript libraries.

The safe logic is this: if the template already loads jQuery correctly, do not add a second copy unless you have a reason. If enabling the module breaks menus, sliders, or galleries, check the noConflict mode. It helps reduce conflicts between jQuery and other libraries, but it will not magically fix everything if the page is loading several incompatible scripts at the same time.

Configuring Sources: From One Network to a Mixed Feed

The most common mistake with social feeds is trying to connect every network at once. JUX Social Stream has separate configuration blocks for different sources, and each type of data has its own constraints. Start with one channel, lock in the result, and only then add the second.

Facebook: Page, Token, and Card Composition

The documentation lists these Facebook fields: Facebook ID, Comments, Image Width, Feed, and output composition settings such as Intro, Thumb, Title, Text, User, and Share. In practical terms, this means making decisions on two levels.

The first level is the data source itself. You need to confirm that the ID belongs to the correct page or profile and that the token was obtained through a current method under Facebook's current rules. Older instructions for getting IDs and tokens can still be useful as historical hints, but the exact process is best verified against the platform's current documentation because social APIs change more often than Joomla modules do.

The second level is card composition. For a news page, you may want to keep the title, text, and thumbnail. For a compact sidebar, it usually makes more sense to hide long text and keep only a short excerpt. If the cards become too tall, first reduce the number of displayed items and simplify the content composition before editing CSS.

Instagram: Source Type and Tokens

In JUX Social Stream documentation, Instagram includes a choice of source type, personal or business, along with fields for ID and access token. That distinction matters: personal and business sources are not interchangeable. A token created for one use case may not work for the other.

For safer setup, do not store tokens in notes accessible to the entire editorial team. Give module access only to administrators who actually need to change social sources. After changing a token, clear the site cache and verify the output in a private browser window so you do not mistake a cached page for a working result.

YouTube: Channel ID and API Key

For YouTube, the documentation includes Youtube ID, Search Text, Thumb, Api key, and an output composition block. If your goal is to show the latest channel videos, start with the channel ID and a small number of items. If your goal is a topic-based selection, use search carefully, because broad queries can pull in the wrong content.

The API key should belong to a project you control. Do not paste in a key from someone else's example, and do not publish it in an article or public repository. If videos do not appear, first check API limits and status in Google, then verify the ID, and only after that move on to the module's visual styling.

RSS as a Stable Source

RSS is often underestimated, even though for a Joomla site it is one of the most predictable sources. JUX Social Stream documentation describes the RSS ID field as the feed URL and lets you control output composition: intro, thumb, title, text, user, and share. If you need to show updates from a blog, a partner news feed, a podcast, or an external site, RSS may be more stable than social APIs.

Before connecting it, open the RSS feed in a browser or validator and confirm that it returns data over HTTPS. If the feed works but the module stays empty, check cURL/OpenSSL on the server, the item limit, and the cache. If the feed itself returns old posts, the issue is usually with the RSS source, not JUX Social Stream.

Vimeo, Flickr, Tumblr, Last.fm, Dribbble, and DeviantArt

The documentation includes separate blocks for several niche sources. Only connect them when those platforms genuinely matter to the audience of the site. For example, Vimeo makes sense for a video studio, Flickr for a photo archive, Dribbble for a designer's portfolio, and Last.fm for a music project.

Do not turn the module into a collection of every possible icon. The more sources you add, the higher the chance of API errors, empty cards, inconsistent image sizes, and an uneven visual rhythm. A good social showcase is usually built around two or three strong channels, while the rest remain simple links in the footer or a separate contact block.

A Practical Update Rhythm

After connecting your sources, decide how often visitors should see new data. For fast-moving channels, such as event news, overly aggressive caching can make the block feel outdated. For calmer pages where the feed serves mostly as social proof, there is no reason to make the site query external services too often.

A practical approach is to divide sources by role. An RSS feed for your own site news can be refreshed more often because it is usually stable and under your control. Instagram or Facebook are better reviewed after token updates and should not overload the page with too many cards. A YouTube channel often updates less frequently, so a small limit and a clear thumbnail are usually enough.

If the page mixes sources with different update frequencies, do not promise visitors a "live" real-time feed. It is better to think of JUX Social Stream as a showcase of recent posts, where freshness depends on the API, caching, and the limits you chose.

List and Wall: How to Choose the Right Display Format

The two JUX Social Stream formats solve different problems. A bad mode choice often shows up as "the module looks ugly," when the real issue is that the format does not fit the placement on the page.

When to Choose List

List is useful when the social feed needs to take up little space. This mode works well in a sidebar, at the bottom of a page, in a "Latest Updates" block, or as a small informational widget. In this mode, container height, rotation direction, and the delay between items matter most.

If you enable autoplay, check whether the user has enough time to read the text before the card changes. On sites with older audiences, educational content, or longer captions, it is usually better to increase the delay or provide manual control. If the feed consists mostly of short headlines and thumbnails, automatic rotation may work well.

When to Choose Wall

Wall is better for visual posts: photos, videos, news cards, and event announcements. It needs more space, but in return it shows social activity immediately, without making the user wait for the next slide. For a home page, media page, or community section, this is usually the clearer format.

The main risk with Wall is inconsistency between cards. Social sources return content in different sizes: some have wide images, some only text, some video, some long captions. For that reason, it helps to limit the number of items, hide unnecessary fields, and test responsiveness at tablet and phone widths.

Network Filter and Reading Order

If the feed is mixed, the filter helps visitors quickly separate videos from photos, RSS from Facebook, or Instagram from the rest of the channels. But a filter is useful only when each network has enough content. If one channel has three posts and another has twenty, users may read an almost empty filter as an error.

Place the filter above the cards and do not overload it with icons. If you have too many channels, it may be worth rethinking the whole showcase idea. The page may need not one unified feed, but two separate modules serving different goals.

Practical Scenario: A Social Wall for a Club Page

Let's walk through a concrete example that is easy to adapt for a school, sports club, tour group, studio, or local community. The goal is to display a social wall on a dedicated Joomla page using Facebook news, YouTube videos, and RSS updates from the site, without breaking the main template.

Goal and Preparation

You want a page called "Social Feed" where visitors can see the club's latest posts in a wall layout. Before you begin, prepare a test menu item, a template position with enough width, the Facebook page ID, the YouTube channel or playlist ID, the RSS URL for site news, and access to the Joomla admin panel.

If Facebook or YouTube requires a token or API key, prepare those in advance and do not pass them through open task comments. For the first launch, you can start with RSS and YouTube, then add Facebook in a second stage so you do not mix authorization errors with module publishing issues.

Setup Steps

1. Create or open the JUX Social Stream module in Joomla's Module Manager.
2. Set Social Style to Wall so the output appears as a grid of posts.
3. Use a small Limit Feed Count, such as a few posts per source, for the initial test.
4. Enable Filter if you are connecting more than one channel and want to let users switch between them.
5. Fill in the RSS source and verify that it displays posts without authentication.
6. Add the YouTube source and enter the ID and API key if your configuration requires it.
7. Add the Facebook source only after the first two sources are already displaying correctly.
8. Publish the module in a wide template position and assign it only to the test menu item.
9. Open the public page in a private browser window and verify that the cards appear.

Expected Result

The page should display a grid with several cards. Each card should have a clear source, a thumbnail or text, a link to the original post, and, if enabled, sharing controls. If the filter is active, switching networks should hide and show the relevant posts without reloading the page.

After the initial check, increase the limit gradually. Do not add dozens of items right away. The social wall should feel active enough to be useful, but it should not turn into a heavy gallery that slows the page down and competes with the main content.

A Common Detail That Gets in the Way

If the module works on the test page but does not appear on the real one, the cause is often menu assignment or template position. In Joomla, a module can be published but still not display if the selected position does not exist in the template used on that page, or if the correct menu item was not selected in the assignment settings. That is why moving from a test page to a live page should not be done by eye. Recheck the position, access level, and Menu Assignment.

How to Verify That Everything Works Correctly

Result verification should be its own step. It is not enough to see one card and consider the setup complete. A social feed depends on external services, JavaScript, caching, the template, network requests, and access permissions. You need to check not only whether the block appears, but how it behaves.

The Public Side of the Site

• Open the page as a regular visitor, not only from the admin panel.
• Check that the module is visible on the correct menu item and does not appear on pages where it is not needed.
• Compare the display on a wide screen, tablet width, and phone.
• Make sure images are not stretched, text is not cut off in the middle of a word, and the filter does not overlap the cards.
• Click the original post link and verify that it goes where you expect.

Admin Panel and Sources

After the visual check, go back into the module and disable sources one by one. That will help you identify which channel is causing empty cards, duplicates, or slow loading. If the feed is mixed, it is often helpful to leave only one source temporarily and test it on its own.

For YouTube and other API-dependent sources, check whether the quotas are exhausted and whether the key was copied correctly. For RSS, open the feed URL itself. For Facebook and Instagram, verify token validity and access rights to the correct page or account.

Speed and Cache

Social widgets can add external requests and images. After enabling JUX Social Stream, test the page with a speed analysis tool or at least compare perceived load time before and after. If the page becomes noticeably heavier, reduce the number of items, disable unnecessary card fields, and review caching.

Joomla can cache the page, component, and module output. That helps with speed, but it complicates diagnostics. If you changed a source setting and the public page does not update, clear the Joomla cache, template cache, or third-party optimization cache. Only then should you check whether the change actually worked.

Safely Adapting the Appearance Without Editing the Module

Sometimes the module works, but visually it does not match the template: the card background is too gray, spacing feels wrong, or links look out of place. JED reviews include cases where users wanted to change the gray background. The safe solution is not to edit extension files, but to add your own CSS through the template or a custom CSS file.

Start by giving the module its own CSS class using Joomla's standard module class field, if that field is available in your version and template. For example, use the class social-stream-brand. After that, you can style only this instance of the module without affecting other blocks on the site.

.social-stream-brand {
  --stream-card-bg: #ffffff;
  --stream-card-border: rgba(32, 39, 55, 0.14);
  --stream-link-color: #2f6fed;
}

.social-stream-brand .dcsns,
.social-stream-brand .stream,
.social-stream-brand .social-stream {
  background: transparent;
}

.social-stream-brand .dcsns-content,
.social-stream-brand .stream-item,
.social-stream-brand li {
  background: var(--stream-card-bg);
  border: 1px solid var(--stream-card-border);
  border-radius: 6px;
}

.social-stream-brand a {
  color: var(--stream-link-color);
}

This snippet is intentionally conservative: it is scoped to a specific module class and does not require editing mod_jux_social_stream files. Before publishing, open your browser's developer tools and inspect the actual classes used in your version of the module. If the HTML structure differs, keep the outer social-stream-brand class, but adjust the inner selectors to match the real markup.

How to roll it back: remove the added CSS or remove the social-stream-brand class from the module. Do not edit extension files inside the module folder, because an update may overwrite those changes.

Limitations Worth Considering in Advance

Any social feed aggregator depends on external platforms. That is the main limitation of JUX Social Stream and similar tools. If Facebook, Instagram, YouTube, or another service changes its API rules, the module may require an update, a new token, or a different connection method. The JED changelog clearly shows that these kinds of fixes have already happened.

The second limitation is content consistency. Social networks return different data types: images, videos, text, links, events, thumbnails, and metadata. Even with a good grid, the cards may not all look the same. That is acceptable when the wall is meant to feel like a live stream, but it is less suitable for pages with very strict design requirements.

The third limitation is the quality of the social channels themselves. The module does not improve photos, edit text, or make weak communication more convincing. If the content across your social networks is chaotic, it is better to clean up those channels first and only then display them on the site.

The fourth limitation is the page's role. On conversion-oriented pages, such as lead forms, registration pages, or critical instruction pages, an external feed can pull attention away from the main action. In those cases, place it lower on the page or use a compact List mode instead of a wide wall.

How to Maintain the Social Feed After Launch

After successfully configuring JUX Social Stream, you should not leave the module unattended for months. A social feed is different from a static Joomla block because its output depends on external services. Even if the administrator has not changed anything in the module, the API, token, response format, access rule, request quota, or the structure of the posts themselves may still change.

A good maintenance process does not need to be complicated. It is enough to define who is responsible for the social sources, how often the public page is checked, where source-type information is recorded, and what to do if one channel stops returning data.

What to Record in an Admin Note

For every enabled source, create a short internal note. Do not store secret tokens there in plain text, but document the purpose of the source: which channel is connected, what type of data it displays, where to verify access validity, and who on the team is responsible for the account. This helps when the site is handed off to another administrator or when you later need to understand why this specific set of networks was configured in the module.

• The source name and its role on the page.
• The data type: page, channel, RSS feed, playlist, profile, or another supported source.
• Where to verify access: the social network dashboard, business account, Google API Console, or another official interface.
• The expected result: how many cards should be visible and which display format is being used.
• The contact for the responsible person who can update access without sharing secrets through public tasks.

Checks After Joomla and Extension Updates

After updating Joomla, the template, an optimizer, a cache plugin, or JUX Social Stream itself, open the page with the feed and run a short check: the module is visible, the filter works, the cards are not broken, links go to the original posts, and there are no obvious JavaScript errors in the browser console. If the update is related to Joomla compatibility, do not stop at the admin panel. Check the public side of the site itself.

If the site uses a staging copy, update the module there first. For social feeds, staging may not always be able to retrieve the same data because the domain, redirect URI, or app settings on the social platform may differ. That is why, even after moving changes to production, you still need a final verification on the real domain.

When It Is Better to Disable a Source Instead of Fixing It Immediately

If one channel stops working right before an important publication or ad campaign, it is not always necessary to urgently fix everything inside the module. Sometimes it is safer to temporarily disable the problematic source, clear the cache, and leave the working channels in place. Empty cards or a stuck loader do more damage to the page than the absence of one social channel.

This approach is especially useful for mixed feeds. If RSS and YouTube are working but Instagram temporarily needs a new token, disabling Instagram preserves the usefulness of the block. After the campaign, you can calmly update access and return the source to the feed.

Why JUX Social Stream May Not Work and How to Find the Cause

It is best to troubleshoot from Joomla mechanics outward to external sources. If you start by changing tokens, styles, and JavaScript right away, it is easy to fix the wrong problem. Below is a practical path that helps separate a module publishing issue from an API, template, or cache issue.

The Module Does Not Appear on the Page

Symptom: there is no JUX Social Stream block on the public page even though the extension is installed. Sometimes the administrator sees the module in the list, but visitors see nothing.

Possible cause: the module is unpublished, the wrong access level is selected, the position does not exist in the template, or the menu item is not assigned. Joomla controls module visibility through a combination of status, position, access, and Menu Assignment.

What to check: publish status, template position, Public access level, the menu assignment tab, and whether that position exists on the specific page. If the module is missing on only one page, the menu item and position are almost always the first things to check.

How to fix it: assign the module to one test page, choose a known existing template position, and temporarily allow access for everyone. After the block appears, you can restore the exact restrictions.

The Container Exists, but the Feed Is Empty

Symptom: the module area appears, but there are no posts. Sometimes you see an empty block; sometimes it loads forever.

Possible cause: an incorrect source ID, an expired token, a missing API key, the external service not returning data, hosting that blocks HTTPS requests, or a server missing the required cURL/OpenSSL support.

What to check: start with a single source. For RSS, open the feed URL directly. For YouTube, verify the ID and key. For Instagram and Facebook, verify the account type, permissions, and token validity. If no external source works at all, ask your hosting provider about outbound HTTPS requests.

How to fix it: refresh the token, reduce the source set to one, clear the cache, and test again. If the issue started after a social platform changed its rules, check whether an extension update and changelog entry are available.

The Cards Look Broken or Overlap Each Other

Symptom: Wall mode shows cards with uneven heights, images are stretched, the grid shifts, or text overlaps other elements.

Possible cause: a template CSS conflict, a position that is too narrow, overly long card text, inconsistent media sizes, or older styles overriding the module's CSS. In the Joomlaux support forum, for a similar case, the developer pointed to style conflicts with the user's site.

What to check: temporarily move the module to a wide position, reduce the number of items, disable some card fields, and test on a default template or a clean test page. If everything looks fine on a clean page, the issue is in the template or custom CSS.

How to fix it: use a separate module class and targeted CSS through the template. Do not edit extension files. If the conflict is severe, it is better to keep a minimal set of card fields than to force long social posts into a narrow grid.

The Filter or Rotation Works Unreliably

Symptom: the filter does not switch networks, List does not rotate, control buttons do not respond, or other page elements break.

Possible cause: a JavaScript conflict, duplicate jQuery loading, incorrect noConflict mode, third-party script compression, or file load order.

What to check: disable JavaScript combining and minification on the test page, inspect the browser console, and temporarily change Enable jQuery and Enable noConflict. If everything starts working after optimization is disabled, configure exclusions in the cache/optimizer.

How to fix it: keep only one valid copy of jQuery, enable noConflict when needed, and exclude the module scripts from aggressive minification. If you are not sure, return the settings to the last working state and change one parameter at a time.

Nothing Changes on the Site After Editing Settings

Symptom: settings are changed in the admin panel, but the public site still shows the old feed or old appearance.

Possible cause: Joomla cache, template cache, CDN cache, module cache, or a third-party optimization cache. This is especially noticeable with social feeds because administrators expect immediate updates to external data.

What to check: clear the Joomla cache, disable module caching temporarily during troubleshooting, test the page in a private window and with a refreshed URL parameter. If the site uses a CDN, clear its cache as well.

How to fix it: during setup, temporarily disable aggressive caching on the page with the social feed. After everything is stable, restore caching, but verify how often the feed should refresh and whether the site is showing posts that are too old.

When JUX Social Stream Is Worth Using

JUX Social Stream is a strong choice if you need a Joomla module for displaying a mixed social feed, are willing to configure the sources carefully, and understand the dependency on external APIs. It is especially useful for pages where visitors benefit from seeing real project activity: news, videos, photos, community posts, and RSS updates.

Before the final launch, run through a short checklist: the module is published in the correct position, assigned to the right menu item, visible to regular visitors, sources have been tested one by one, limits do not overload the page, List or Wall fits the placement, cache has been cleared after setup, and JavaScript does not conflict with the template.

If those conditions are met, you can move on to the install package and download the installation file for testing on your Joomla site. Start with a test page and a single source, then gradually shape the feed into the format that actually helps visitors understand the activity behind your project.