JUX Social Gallery - Joomla Extension

A Practical Guide to Setting Up JUX Social Gallery on a Joomla Site

JUX Social Gallery is best understood not as a typical image gallery, but as a bridge module between a Joomla site and public photo sources. In this guide, we will walk through how to prepare the site, install the module, connect social sources, limit the set of albums, place the gallery in the right template position, and confirm that visitors see exactly the result you intended.

This guide does not repeat the product's short description. The focus here is practical: which fields and modes to check first, why Instagram behaves differently from album-based sources, how to tell a token issue from a module position issue, where noConflict can help, when it is better not to load extra scripts, and how to safely refine the appearance through the module class.

This guide is written for Joomla administrators, content managers, small site owners, and developers helping clients bring photo reports, portfolios, events, club albums, or a visual diary from social platforms onto their own site. Any potentially uncertain details are phrased carefully: social APIs change, so before going live, it is important to verify the current requirements of the service you are using and avoid storing secret tokens in public notes.

What Problem a Social Gallery Solves on Joomla

A standard local gallery requires you to upload images into the media manager, organize them into folders, rebuild thumbnails, and make sure the site does not drift out of sync with your social channels. JUX Social Gallery solves a different problem: it pulls public images from supported sources and displays them as a gallery inside Joomla. According to JED and the developer page, the module is built around Facebook, Instagram, Flickr, and YouTube, while giving the administrator control over albums, image count, block width, captions, and jQuery loading.

The practical value of this approach is straightforward. If the team is already publishing photos to social platforms, the website can become a storefront for that stream without manually copying every image over. For a club, school, event venue, photo studio, travel project, or local community, this saves editorial time: new images appear in the original account, and the site updates the block the visitor sees inside a familiar Joomla layout.

That said, the module should not be treated as a universal media repository. It depends on the availability of the external service, the correctness of the public profile, token or identifier, and the limits of the specific platform. The JED changelog shows that the developer has had to fix issues related to Facebook, Instagram, Flickr, and YouTube. That is a normal risk for extensions that rely on external APIs: everything may work today, but after the service changes its rules, you need to review the settings and updates.

How JUX Social Gallery Differs from a Local Photo Gallery

The main difference is the data source. A local gallery displays files that already live on the site. JUX Social Gallery displays a selected external feed or albums and arranges them into a clean grid. That means setup is not only about appearance, but also about source access: account visibility, the correct identifier, token permissions, image limits, and the refresh workflow.

The second difference is Joomla's module logic. JUX Social Gallery is published as a module, which means the result depends on the template position, publication status, menu assignment, access level, and language. Sometimes the module itself is configured correctly but still does not appear on the site because it is assigned to the wrong pages or the chosen position does not exist in the active template. That is a classic Joomla issue you cannot diagnose by looking only at the extension settings.

Which Sources Make Sense as Real Working Scenarios

Support for Facebook, Instagram, Flickr, and YouTube is confirmed, but each one needs to be handled differently. Facebook and Flickr are usually tied to album-based logic, where the administrator chooses what to include or exclude. On the product page, Instagram is specifically described as a source without album creation inside the module, so in that case the image limit and the account connection matter more. YouTube works as a visual source, but if you need a more advanced video gallery with playlists, sorting, and multiple playback modes, it is worth comparing this module to dedicated YouTube extensions.

Practical takeaway: do not start with the visual styling. Start by deciding which source will be your primary one. The checklist is different for Instagram, Flickr, Facebook, and YouTube, so troubleshooting will be different as well.

Who This Module Fits Best, and When Another Tool Makes More Sense

JUX Social Gallery is a strong fit for sites where photos already live in external social sources and need to appear on a Joomla page as a clean visual stream. This is not limited to large portals. In many cases, the module is especially useful for small projects where the editor needs a fast way to show current photos: events, club meetings, travel, school activities, workshops, community initiatives, a studio portfolio, or a Flickr-based photo archive.

The module is especially useful when the site should feel active, but the team does not want to maintain two separate media catalogs. For example, a photographer publishes curated sets on Flickr, an event organizer posts fresh photos to Facebook, and the site administrator shows only the latest few albums on the homepage. In that model, Joomla remains the main information hub, while social platforms provide the visual layer.

When JUX Social Gallery Is a Convenient Choice

• You need to display photos from public social sources on a Joomla page instead of uploading every image manually.
• Module-based publishing matters: template position, menu assignment, language, access level, and separate instances for different pages.
• You need to limit the number of images or albums so the gallery does not turn into a long uncontrolled feed.
• A clean grid with captions, hover effects, and basic responsiveness is enough, without needing a full media manager inside the site.
• The team is willing to review external APIs after service updates and keep the extension current.

When It Is Better to Look at Another Solution

If the site needs to store images inside Joomla, sort them by categories, add detailed descriptions, protect files with access rules, build a portfolio from local assets, and avoid depending on social APIs, then a social gallery is not the best system core. In that case, it makes more sense to look at local galleries or portfolio components where media is managed directly on the site.

JUX Social Gallery is also not the right choice if you need a full social wall rather than a visual block: posts, text, links, videos, avatars, and different event types. For that use case, JUX Social Stream or similar social display extensions are a better match. JUX Social Gallery is strongest in the narrower scenario of "show images from social sources as a gallery."

You should also evaluate security requirements separately. If a client asks to connect private accounts, personal photos, or restricted albums, do not promise that without checking the platform's official documentation. The guide below assumes the safer scenario: a public source, correct access permissions, minimal secrets stored in the admin area, and result verification on a test page.

What to Check Before Installing the Module

Preparation cuts down on false errors. If you open the module, paste in the first identifier you find, and publish it straight on the homepage, it becomes hard to tell where the problem is coming from: Joomla, the template, the source, the API, the token, the cache, or JavaScript. A short pre-check and a separate test page will save time.

Joomla Compatibility and the Installation Package

JED shows that this is a module-type extension and lists compatibility with current Joomla branches up through the newer generation, while the JoomlaUX documentation mentions separate packages for different Joomla versions. That matters: do not install the archive blindly if the package includes multiple installation files. Choosing the wrong package can look like a failed install, a blank page, or the module type not appearing in the list.

Before installation, check the following:

• The Joomla version running on the site and the matching extension archive.
• Administrator access for installing extensions and managing site modules.
• A site backup or at least a restore point before installing a new extension.
• Whether the template positions where the gallery will be published are actually working.
• The current cache and JavaScript optimization settings, especially if the site already uses galleries, sliders, or page builders.

Source Visibility and Required Data

Make sure the selected account, channel, album, or image set is available exactly in the form the site visitor is supposed to see. In a JoomlaUX support thread about Facebook integration, the developer pointed to an incorrectly entered token and API changes as possible causes of endless loading. That is a good example: the symptom on the site may be obvious, but the root cause can still live in the external service.

For each source, prepare only the data the module actually needs: page ID, user ID, album ID, channel ID, or token, if the source requires one. Do not share secret values in public discussions, do not hardcode them into template source files, and do not store them in editorial notes. If another team member provides access, ask not only for the token string, but also for a note explaining which source it belongs to and when it needs to be refreshed.

Use a Test Page Instead of Publishing Site-Wide

The safest first launch is a separate hidden or low-traffic menu item. Create a page called "Gallery Check," assign the module only to that page, and choose a template position that definitely exists. That gives you room to test sources, limits, widths, and jQuery settings without breaking the homepage or exposing an unfinished block to visitors.

Quick pre-install check: if you do not know which template position the module should appear in, first publish any simple Joomla module there. If a basic module is not visible in that position, JUX Social Gallery will not be visible either, even with the source configured correctly.

Installation and First Launch in the Joomla Admin Panel

Installing JUX Social Gallery works like installing any standard Joomla extension: the administrator uploads the ZIP archive through the built-in installer, then creates or opens a module instance in the site modules section. The exact interface labels may vary across Joomla versions, but the logic is the same: install the extension first, then publish the module and assign its display location.

Basic Action Order

1. Create a site backup or confirm that your hosting account has a recent restore point.
2. In the Joomla admin panel, open the extension installer and upload the JUX Social Gallery archive that matches your Joomla branch.
3. After a successful installation, go to site module management and locate the JUX Social Gallery module type.
4. Create a new module instance, give it a clear title such as Social gallery - test, and for now disable the title display on the site if it is not needed.
5. Select a template position, set the status to Published, and assign the module only to the test menu item.
6. Save the module and open the test page on the public side of the site.

At this stage, you do not need to chase the perfect visual result. Your first goal is simply to confirm that Joomla recognizes the module, the position works, the page does not throw an error, and the extension block appears in the page markup. If the block is empty, that is still useful information: the Joomla layer may be working, while the source is not returning data yet.

Which Joomla Fields to Check First

The module may be configured inside the JUX Social Gallery tabs, but Joomla still controls publication. So after creating the instance, review the standard Joomla module fields. In the module list, the important items are status, position, pages, access, and language. In the edit form, pay attention to the menu assignment tab, the basic publishing parameters, and the advanced settings, where Joomla usually stores the module class, caching, and an alternative layout if the template provides one.

After saving, clear the Joomla cache and the optimizer cache if one is present. If the module still does not appear, check the standard Joomla fields first instead of changing tokens or API keys. That lets you quickly separate a display problem from a data retrieval problem.

Configuring Sources, Albums, and Limits in JUX Social Gallery

Detailed setup starts with choosing the source. The JoomlaUX documentation shows separate configuration blocks for supported social services, and JED describes options for including and excluding albums, limiting the number of images, and controlling captions. Do not try to configure every source in one pass. It is better to build one working source, verify it, and only then add a second module instance or expand the current one if the scenario truly calls for it.

Data Source: Facebook, Instagram, Flickr, or YouTube

For Facebook and Flickr, the key question is which albums should appear on the site and which ones should be excluded. For Instagram, correct account linking and the image count limit matter more, because the source does not provide the same album logic inside the module. For YouTube, it helps to decide up front whether you are showing a visual selection from a channel or whether you actually need a full video gallery. If the project requires deep playlist handling, dedicated video players, and many display modes, a specialized YouTube extension may be easier to work with.

At the beginning, choose the most stable and understandable source. For testing, Flickr is often convenient if you already have a public set of photos with a clear album structure. Instagram works well for a fresh feed, but it tends to depend more heavily on the platform's current access requirements. Facebook is useful for community albums, but availability is more tightly tied to correct permissions and tokens.

How to Avoid Mistakes with an ID or Token

If the module requires an ID or token, paste the value without extra spaces, explanations, prefixes, or leftover fragments from older strings. In a JoomlaUX support thread, the developer pointed out that a user had inserted an extra segment before the token, which prevented the module from connecting correctly. That is a classic mistake: visually, the string looks fine, but one extra piece breaks the request.

A safe workflow looks like this:

1. Copy the value from the service's official interface or the developer's instructions.
2. Paste it into the module field without comments or extra characters.
3. Save the module and open the test page in a private browser window.
4. If the gallery does not load, temporarily lower the image limit and check the browser console.
5. If the source requires a new token, update it in the admin panel, not in template files.

Including and Excluding Albums

Album control is not only about tidiness. It affects performance, page structure, and editorial control. If you connect every available album, the gallery can become too long, and users may see old or irrelevant collections. An event site should show recent events, a portfolio should show only curated sets, and a club site should display albums tied to public activities rather than everything in the account.

Start by enabling only one or two albums and checking the result. Then expand the set. If the service supports excluding albums, use that feature for old collections, internal photos, or materials that should not appear on the site. If the source does not support albums, as in Instagram according to the JED description, compensate with the image limit and a more careful publishing location.

Image and Album Limits

The limit is one of the most practical settings. It helps prevent the page from becoming overloaded, keeps the first screen from stretching too far, and avoids making dozens of external requests when the visitor only needs 8 to 12 recent images. For the homepage, a smaller block is usually better. A dedicated "Photos" page can show more images, but it should still have a sensible cap and be tested on a slower connection.

Do not choose the maximum value just because the module allows it. Think about what the user is supposed to do on that page. If this is a promo block above an event description, a handful of strong images is enough. If it is a club archive, you can show more, but it is still better to split pages by topic or create multiple module instances with different sources and assignments.

A Control Note for Every Source

To avoid mixing up external service issues with Joomla settings, create a short working note for each source, either in the module instance's Note field or in the site's internal documentation. It only needs a few items: which source is connected, which album or channel is used, who is responsible for refreshing access, what image limit is set, and where the result is checked. Do not store secret tokens there. The point of the note is not to keep credentials, but to leave the next administrator a clear verification path.

For a Facebook-style setup, that note makes it clear why a specific public album was chosen and where to start looking if the album stops loading. For an Instagram setup, it documents that album logic is not being used and that the result is controlled through the image count. For Flickr, it helps to note whether the content comes from a user, a set, or another available source. For YouTube, it is useful to state explicitly that the module is being used as a visual gallery rather than a full video catalog.

This kind of small discipline matters even more on client sites. A few months after the setup, nobody remembers why one source is limited to eight images while another is shown only on an event page. If the decision was documented, refreshing a token, switching an album, or moving the module to a new template position does not turn into detective work.

Why It Is Better Not to Mix Every Source into One Block Right Away

Even if the interface allows you to connect several social sources, the first working scenario should stay narrow. One source, one clear result, one verification cycle. Once that is stable, you can add a second source or create a separate module instance. This approach helps you stay in control of both appearance and performance: if the gallery gets slower after adding a second source, you immediately know which change caused it.

A mixed gallery sounds attractive on paper, but in real editorial work, the sources often follow different rules. One service returns albums, another only a feed, a third requires access refreshes, and a fourth changes its response format. For important pages, do not aim for the broadest possible source mix. Choose the source that solves the page's actual job reliably.

Grid Styling, Captions, and Script Compatibility

Once the source is returning images, you can move on to presentation. The sources confirm that JUX Social Gallery supports responsiveness, an even grid, hover highlighting, captions, gallery width control, and jQuery/noConflict options. Change these settings gradually: make one change, save, check the public page, then make the next change. Otherwise, it becomes difficult to tell which setting affected the result.

Gallery Width and Template Placement

The gallery width should match the template position. If the module sits in a wide position above the component area, a full grid can work well. If it is in a sidebar position, reduce the number of images and check whether the thumbnails become too small. If the gallery sits inside a page builder or custom block, confirm that the container is not imposing conflicting overflow, display, or fixed-height rules.

The practical check is simple: open the page at desktop width, then reduce the browser window to tablet and mobile widths. If the images start overlapping, captions spill outside the cards, or the block suddenly changes height after load, look for a conflict with the template, optimizer, or custom styles. Do not try to fix that by increasing the image limit. The problem is usually in the container, the scripts, or the CSS.

Captions and Editorial Value

Caption support is useful if the original service provides meaningful captions or if the visual material needs context. But captions from social platforms do not always work well on a site: they may include hashtags, casual phrasing, emoji, people's names, or internal notes. Before enabling captions, check how they look on the public page and whether they disrupt the clean grid.

If the captions feel noisy, a clean gallery is often the better choice, with context added in the Joomla page text instead. For example, you can place a paragraph above the module that says, "Photos update automatically from the club's public album." That keeps the design clean and does not depend on the quality of each individual caption.

jQuery and noConflict

The jQuery and noConflict settings matter on sites that already use sliders, galleries, template effects, or optimizers. If a JavaScript error appears on the page, the gallery may stop opening images, stop responding on hover, or get stuck in a loading state. In that situation, do not switch everything on and off at random. Start by checking the browser console for errors related to duplicate jQuery, an undefined $, a lightbox script conflict, or file merging.

A safe strategy is this: if the template already loads a compatible library and the other page elements work reliably, try not to duplicate jQuery through the module. If disabling it makes the library disappear and the gallery stops working, turn the setting back on. If enabling noConflict resolves the conflict, keep it enabled and test the neighboring interactive blocks as well. Record every change in the module note so the next administrator understands why that mode was chosen.

Practical Scenario: An Event Photo Report on a Dedicated Page

Let us walk through a use case that fits JUX Social Gallery well: the site has an event page, and the photos are published in an external album or account. The goal is to display an up-to-date gallery on a Joomla page without uploading images manually and to make sure the visitor sees only the intended photos.

Goal and Preparation

The goal is to create an "Event Photos" page for a club or event where the gallery pulls images from a single public source, shows a limited set of frames, does not interfere with the page text, and looks clean at different screen widths. Before you begin, you should already have the module installed, a test menu item ready, a working template position selected, and a prepared source: album, profile, channel, or another verified identifier.

Setup Steps

1. Create a separate Joomla article or menu item where the photo report will appear.
2. Create a new JUX Social Gallery instance and name it so its purpose is obvious, for example Social gallery - event report.
3. Select the source, enter the ID or token if required, and save the module.
4. Limit the number of images so the first page load stays fast and predictable.
5. If the source supports albums, enable only the needed album or exclude the extra collections.
6. Assign the module to the photo report page through Menu Assignment.
7. Choose a template position that works visually for a wide gallery block.
8. Open the public page and check the grid, captions, hover behavior, image opening, and how the block behaves when the browser width is reduced.

Expected Result and One Important Nuance

The expected result is a clear photo block on the page that does not push out the main text and does not show unrelated albums. If the images do not appear, do not start by changing the styling. First check whether the module container itself is visible. If the container is missing, the issue is probably in status, position, menu assignment, access, or language. If the container exists but contains endless loading or empty space, the more likely problem is the source, token, limit, external API, or JavaScript.

Post-scenario check: add one new test image to the external source, wait the normal refresh interval, and confirm that it appears on the test page. If it does not, clear the cache and review the source limitations before changing the template.

How to Verify the Result on the Site After Saving the Settings

Result verification should be its own step, not just a quick glance at the page in the same browser where the admin panel is open. An administrator may see a cached version, may be logged in with a different access level, or may miss JavaScript errors that affect guests. For a module tied to external sources, you need to check several layers: Joomla publication, data retrieval, appearance, performance, and behavior after the source updates.

Public Check as a Guest

Open the page in a private window or a different browser. Confirm that a guest can see the gallery, that the images load without logging in to Joomla, and that the block appears only on the intended pages instead of across the entire site. If the module uses an access level other than Public, make sure that was done intentionally. For restricted sections, it is better to explain clearly to editors who is supposed to see the gallery and why.

Performance and Stability Check

A social gallery adds an external dependency. The page may load quickly one day and more slowly the next if the external service responds more slowly. Do not make the gallery the only critical content in the first screen of an important landing page. If the visual block must appear immediately, limit the number of images, avoid enabling unnecessary albums, and check how the page looks before the external data finishes loading.

On sites with caching, it is useful to test two situations: immediately after saving the settings and after clearing the cache. If everything works without cache but the gallery freezes or shows stale data with cache enabled, you may need to configure an exclusion or change the module caching mode. Do not disable the site's global cache without a reason. First identify which layer is causing the issue: Joomla cache, a template optimizer, JavaScript merging, a CDN, or browser cache.

Check After the Source Updates

A social gallery feels simple until the source changes. The real test starts when a new image appears in the source account, an old album is removed, or a publication changes visibility. After each such change, check the page both as a guest and as an administrator. If the guest sees the old version but the administrator sees the new one, cache or access level is the likely cause. If both see the old set, review the limit, sort order, source availability, and any delay on the external service side.

Do not promise editors instant synchronization unless the sources and the cache behavior have been tested on your specific site. A safer internal rule is this: photos update after they are published in the source and after cache is cleared, while the exact timing depends on the service and the site configuration. That does not reduce the value of the module, but it does remove false expectations and gives support staff an honest answer to pass along.

How to Tell Whether the Page Is Still Strong for the User

After adding the gallery, do not check only for the presence of images. Check the page's purpose as well. A good page with JUX Social Gallery should answer three questions: what this collection is, why it is here, and what the visitor should do next. If the module has no explanation around it, the gallery turns into a visually appealing but disconnected block. Add a short paragraph before the module and, if appropriate, a link to the page's main action after it.

The visual block should not overpower the content. If the page is about an event, the text should still explain the event, the schedule, the participation terms, or the outcome of the meeting. The gallery strengthens the material, but it does not replace it. If the page is a portfolio page, it is useful to explain what kind of work is shown, how the images were selected, and where the user can view the full collection.

SEO and Accessibility Check

JUX Social Gallery helps display visual content, but it does not replace the page's text structure. Search engines and users still need a heading, introductory text, contextual description, a gallery caption, and clear navigation. If a page consists only of an external gallery, it may be weak as a reference page or landing page. Add a short explanation above the gallery describing what the collection is, where the photos come from, and how often it updates.

Practical Use Ideas for Different Types of Sites

JUX Social Gallery makes sense beyond a dedicated "Gallery" page. The module can serve as an editorial bridge between active social publishing and the stable structure of a website. Below are several scenarios built around the product's confirmed capabilities: an external image source, albums or limits, Joomla module assignment, and responsive output.

Event and Club Websites

For an event-driven site, the module works well on pages for individual events. The editor publishes photos to the source album, and the Joomla page receives an updating block. The key is not to mix every event into one stream: use a separate module instance for important pages, or enable only the relevant albums. Make sure older events do not leak into the current block on the homepage.

Studio or Photographer Portfolio

If the photos are already organized in Flickr or another supported source, JUX Social Gallery can display selected series in a module position. For portfolio use, captions and consistent image sizing matter especially. Before publishing, verify that automatic alignment does not crop important visual details. If cropping becomes a problem, it is better to reduce the number of items or choose another display method than to show damaged previews.

News or Education Website

On an educational site, the gallery can complement articles about trips, classes, and projects. The key is not to let the social stream become the main source of facts. The article text should explain the event, while the module provides visual confirmation. If the photos are updated regularly, add a short note near the block explaining that the images come from a public source and may update after new material is published.

Homepage as a Showcase of Fresh Photos

For the homepage, use the strictest limit. The visitor does not need to see the entire archive. They only need a visual signal that the project is active. If you display too many images, the gallery starts competing with navigation and the page's main offer. In this scenario, it is better to use a compact grid, hide long captions, and link to a separate page with the full photo report.

Safe Appearance Tweaks Without Editing the Extension

Sometimes the source works correctly, but the appearance does not fit the template perfectly: the spacing is too large, the border is too strong, the container width feels off, or the captions look heavier than the rest of the page. Do not edit the extension files. An update can overwrite those changes. In Joomla, a safer approach is to use the module class and your template CSS, for example in user.css if the template supports that workflow.

Goal: Give the Gallery Its Own CSS Wrapper

In the advanced settings of the module instance, assign a class such as jux-social-gallery-clean. Then add CSS to the template's custom stylesheet. The extension's internal class names may vary, so the example below acts as a gentle outer wrapper: it does not depend on an invented module API, it does not change PHP, and it is easy to roll back.

.jux-social-gallery-clean {
  margin-block: 24px;
}

.jux-social-gallery-clean img {
  border-radius: 6px;
}

.jux-social-gallery-clean a:focus-visible {
  outline: 3px solid #2b7cff;
  outline-offset: 3px;
}

After saving, clear the template cache and open the page in a private window. Check three things: whether the spacing appears, whether the grid still works, and whether focus is visible during keyboard navigation. If the result is not right, remove the class from the module or comment out the CSS. That rollback is safe because it does not touch any JUX Social Gallery files.

What Not to Customize Manually

Do not modify the module files to "fix" the token, the API logic, or image loading. That is risky and will not survive updates well. If the problem is source-related, look for the solution in the settings, documentation, changelog, or the developer's support responses. If the problem is template-related, use a separate module class, a template override only when the structure is clear, and cautious CSS. If the problem is a JavaScript conflict, start by checking the jQuery/noConflict modes and the optimizer instead of making random edits to the scripts.

Why the Gallery Does Not Display or Gets Stuck

Troubleshooting works best when you move layer by layer. JUX Social Gallery sits at the intersection of Joomla modules, the template, the external source, JavaScript, and cache. If you jump between settings randomly, you can fix one issue and create another. Below are the typical symptoms that are especially common with a social gallery module.

The Module Does Not Appear on the Page at All

Symptom: on the public page there is no grid, no loader, and not even an empty container. The module block is missing from the page source.

Possible cause: the module is unpublished, assigned to the wrong menu item, restricted by the wrong access level, set to a different language than the current page, or placed in a position that does not exist in the template.

What to check: open the Joomla site modules list and review Status, Position, Pages, Access, and Language. Then temporarily assign the module to one known-good position and a test page.

How to fix it: publish the module, choose an existing position, assign it to the correct page, and clear the cache. If the block appears after that, restore the settings one by one. If it still does not appear, check whether the template conditionally hides that position.

The Gallery Shows Loading, but No Images Appear

Symptom: the container or source icon is visible, but the photos do not load. A similar symptom came up in a JoomlaUX support thread for Facebook integration, where API changes and an incorrectly entered token were possible causes.

Possible cause: an incorrect ID, an expired or invalid token, a private source, changed API requirements, an overly large limit, or a blocked external request.

What to check: start with one source and the smallest reasonable limit. Confirm that the album or account is public. Compare the value in the module field with the service's official interface. Open the browser console and the network panel to see whether access errors appear.

How to fix it: refresh the token or ID using the official instructions, remove any extra characters, lower the limit, and save the module again. If the problem started after a service rule change, review the changelog and check whether an extension update is available.

The Images Load, but the Grid Breaks in the Template

Symptom: previews overlap, cards have uneven heights, captions spill outside the layout, hover effects break the frame, or the block does not adapt to the container width.

Possible cause: a template CSS conflict, a position that is too narrow, a fixed-width parent container, a CSS optimizer, or custom styles. JED reviews have mentioned CSS issues, jQuery issues, and template compatibility problems, so this is a realistic scenario.

What to check: temporarily move the module into a wider position and reduce the number of images. Disable custom CSS if it was added recently. If possible, test the page in the default template or a staging copy.

How to fix it: use a separate module class and gentle CSS adjustments. If the problem disappears in another position, choose a position that better fits the gallery width. If the conflict appears only after CSS or JS optimization, configure an exclusion for the extension files or change the optimizer mode.

Hover Effects, Image Opening, or Filters Do Not Work

Symptom: the images are visible, but interactive elements do not respond, the filter does not switch albums, the lightbox does not open, or the console shows a JavaScript error.

Possible cause: duplicate jQuery, a conflict with another slider, the wrong noConflict mode, script merging by the optimizer, or an issue in an older template.

What to check: temporarily disable JavaScript merging and inspect the console. Then change the jQuery loading and noConflict settings in the module one at a time. Do not change multiple parameters at once.

How to fix it: keep the mode in which both the gallery and nearby interactive elements work together. If the problem appears only on one page, check which other module or script loads alongside it. If the conflict is persistent, document it in the module note and refer to the developer's documentation or support.

The Gallery Shows Old Images

Symptom: new photos already exist in the external source, but the site still shows the old set.

Possible cause: Joomla cache, module cache, CDN cache, browser cache, external API delay, or a limit that prevents the new item from appearing.

What to check: clear the Joomla cache, open the page in a private window, and temporarily lower the limit so the newest item should clearly appear in the selection. Then check whether the new image shows up after a full cache clear.

How to fix it: tune caching carefully. On the homepage, you can keep caching enabled if minute-by-minute freshness is not critical. On a page with active photo updates, it is better to find the right balance between freshness and speed. If the source itself returns delayed data, a Joomla setting will not make the external service faster.

When JUX Social Gallery Is the Right Choice

JUX Social Gallery is worth using if you need a Joomla gallery that pulls images from supported social sources, displays them as a module, and lets you control albums, limits, width, captions, and script compatibility. It is especially useful when visual content is already being published regularly to an external account and the site needs to show a fresh, well-presented result without manually uploading every image.

Before going live, verify three things: the source is truly public and returns the expected data, the module is published in the correct position and on the correct pages, and the appearance does not conflict with the template or cache. Once those layers are separated, troubleshooting becomes predictable: you know where to look for the issue and what to roll back.

After testing on a staging page, you can download the installation package, install the appropriate build, and move the configured setup to the live page. Start with one source, a small limit, and a clearly defined position, and expand the gallery only after the basic chain of "source - module - page - result" is stable.