JUX Photo Gallery - Joomla Extension

A Practical Guide to Setting Up and Using JUX Photo Gallery on a Joomla Website

JUX Photo Gallery is a Joomla extension delivered as a module for displaying photo galleries, so working with it is different from configuring a full-scale image catalog component. This guide focuses on the practical workflow rather than the generic product listing: how to prepare your site, install the module, choose a position, configure images, enable filtering and the lightbox, verify the result on the front end, and quickly identify the issue if the gallery does not appear.

This article is intended for site owners, Joomla administrators, content managers, and webmasters who need a clean gallery for a portfolio, service page, photo report, work showcase, or visual section on a landing page. Special attention is paid to the fact that JUX Photo Gallery is rendered through Joomla's module system: it is not enough to upload images, you also need to assign the module correctly to a template position, menu items, and display conditions.

The sections below walk through the practical steps without making claims that cannot be supported by sources. The official JoomlaUX and Joomla Extensions Directory pages confirm the module's purpose, responsive behavior, gallery layouts, lightbox, sorting and filtering features, as well as its changelog. General guidance on installation, module positions, and menu assignment is based on Joomla documentation.

What a Gallery Module Solves and Where It Is Not the Right Fit

JUX Photo Gallery is best viewed as a tool for building a visual block that looks polished without having to develop a custom grid. It works well when the images are already prepared, the site runs on Joomla, and the administrator needs to assemble a gallery quickly with a predictable front-end result. Unlike an article with a few embedded images, a module lets you place the gallery into a template position and control its visibility through Joomla's module rules.

The main benefit of this approach is keeping content separate from placement. The images and gallery settings live inside the module configuration, while the page only decides where that module should appear. This works well for a portfolio on a service page, a photo block on the homepage, a visual section at the bottom of an article, an event landing page, or a dedicated gallery on a project page.

When JUX Photo Gallery Is a Strong Fit

The module makes sense when you need to show images to visitors, let them open a larger version, group media by topic, and avoid making the editor build a grid manually every time. According to the official product description, it supports responsive output, multiple layout types, a lightbox for images and video, sorting, and filtering. Those features cover the typical gallery scenario: users see a set of thumbnails, can filter to the group they need, and can open media in an enlarged view.

• A portfolio for a photographer, studio, designer, contractor, or service professional.
• A project gallery on a case study page where you need to show stages, details, and the final result.
• A photo report for an event, exhibition, training program, or community meetup.
• A visual block on a landing page where the images need to serve as proof of results.
• A small media showcase for a product or service when a full catalog is unnecessary.

When You Should Choose a Different Type of Solution

If you need a large media manager with user uploads, editor roles, a complex album structure, dedicated category pages, and advanced access controls, a single module may not be enough. In those cases, it is better to look at component-based gallery solutions: they usually provide a dedicated admin area, a deeper data model, and more tools for managing thousands of images.

You should not use the module as a substitute for a full media repository. If images need moderation, individual permissions, sales, downloads, or customer selection workflows, first verify whether your version of JUX Photo Gallery actually supports those tasks. The official sources confirm gallery display, lightbox behavior, filtering, and responsiveness, but they do not provide a solid basis for confidently promising advanced workflows such as customer photo selection or front-end uploads by users.

Practical rule of thumb: if the task is "show a polished gallery in a specific place on the page," a module-based format fits well. If the task is "manage a large photo archive as a separate section of the site," it is better to compare component-based alternatives upfront.

Product Map: The Features That Actually Affect Configuration

Before installation, it helps to break JUX Photo Gallery down into its working parts. It is not just "a gallery with images," but a combination of media sources, layout options, interactive viewing, filtering, and module display rules. If you understand that structure in advance, setup goes faster and troubleshooting does not turn into random option switching.

Images and Media as the Foundation of the Result

The gallery will not fix poorly prepared images. Overly heavy files will slow the page down, mixed aspect ratios can break the visual rhythm, and vague filenames or empty descriptions weaken the overall presentation. The official product page mentions displaying images and videos in a gallery, but the quality of the final page still depends on how the administrator prepares the media.

For a typical site, it makes sense to choose a consistent cropping strategy ahead of time: for example, landscape images for a project gallery, square thumbnails for a work showcase, or a mixed grid for a more dynamic photo report. If your gallery includes images in different sizes, check how the chosen layout behaves both on wide screens and on mobile widths.

Layouts: Grid, Masonry, and Carousel as Different Use Cases

The JoomlaUX and JED sources mention several layout types, including a classic grid, a dynamic masonry layout, and a carousel. These modes are not interchangeable decorations. A grid works well for even presentation, masonry helps with varied aspect ratios, and a carousel is useful when page space is limited and you need to show a series of images in a compact format.

Lightbox and Viewing Controls

The lightbox matters because it lets visitors view an image without leaving the page. That is essential in a photo gallery: the thumbnail acts as navigation, while the larger view reveals the details. The JUX Photo Gallery changelog specifically mentions a setting that lets you disable the download icon in the popup window. That is an important option for sites where images are presented as portfolio work but should not encourage direct downloads.

Do not treat disabling the download icon as copy protection. A web image shown in the browser can never be made completely inaccessible for saving. This setting is more about user interface behavior: the visitor no longer sees an explicit prompt to download the file. To protect commercial work, also use reasonable image dimensions, watermarks embedded in the images themselves, license notices, and legally sound terms of use.

Filters, Tags, and Sorting

Filtering becomes useful when the visitor has a specific question: "show only interiors," "leave only portraits," or "show the stages before finishing." The official changelog also mentions an option to show or hide the filter for items without tags. That means configuration is not just about turning filters on, but also deciding what should happen to images that do not have a topical label.

If tags are used inconsistently, filtering makes the experience worse. The visitor clicks a category and gets an empty or confusing set. That is why, before publishing, you should check not only the appearance of the filter buttons but also whether each thumbnail actually belongs in its group. A filter should help people find the visual material they need, not expose the internal chaos of the media library.

What to Check Before Installing It on a Live Site

Preparation matters for more than formality. Gallery modules quickly expose a site's weak spots: upload limits, script conflicts, poor template positions, aggressive caching, heavy images, and hidden display rules. The larger your initial image set, the greater the chance that a visitor will notice the problem before the administrator does.

Joomla and Environment Compatibility

JED lists JUX Photo Gallery as compatible with current Joomla branches in the 4, 5, and 6 families, and the changelog records support for a new Joomla branch being added. The article does not need to be tied to a specific date, but during installation it is important to verify that your site is within the supported range and that the PHP version in use fits your Joomla version.

Before installing on a live site, make a backup and test the extension on a staging copy or development environment. This is especially important if the site already uses JavaScript optimization, file aggregation, lazy image loading, or a custom template. The JUX Photo Gallery changelog includes fixes related to jQuery in Joomla 5 and progressive caching, so script and cache conflicts should be treated as real risks, not abstract ones.

Template Positions and Gallery Placement

Joomla renders modules through template positions. If the module is published but assigned to a position that does not exist in the current template, or that is hidden on the target page, visitors will not see it. Joomla documentation explains that positions are defined by the template, while modules can be enabled or disabled by menu item. This matters even more for a gallery: the visual block should sit next to text that explains the context, not in some random sidebar.

Before installation, choose one or two suitable positions: the main area below the content, a bottom section of the page, a section under the header, or a template position for a promo block. If the position is unknown, enable Joomla's built-in template position preview, check the page with the ?tp=1 parameter, and disable that mode again afterward on the live site.

The State of the Media Library

For the first publication, it is better to start with a small set: 8 to 16 images, clear names, a consistent caption style, and no unnecessary duplicates. If you add hundreds of files right away, you will not know whether the problem comes from the module itself, the heavy media set, a specific file, or a caching issue.

• Make sure the images are not too heavy for the page and are not being loaded at full original size without a reason.
• Prepare alt text and short descriptions where they are needed to make the story understandable.
• Organize images into tags or categories in advance if you want to enable filtering.
• Remove accidental system files, duplicates, and images with watermarks that were not meant for publication.

Quick preflight check: if you cannot explain in two sentences why each image group belongs on the page, your filters and sorting will feel random.

Installing the Module and Running the First Check

JUX Photo Gallery is installed as a Joomla extension, and JED identifies it as a module in the package contents. That means after uploading the package, you need to do more than just complete the installation: you also need to find the installed module in the site's module list, publish it, assign it to a position, and verify the menu rules. Without those steps, the extension may install correctly but still remain invisible to visitors.

Basic Installation Through the Joomla Admin Panel

The general extension installation process is described in Joomla documentation. For most extensions, you upload an archive through the installation area. Menu names may differ depending on the admin version, but the logic stays the same: open the installer, select the archive, and wait for the success message.

1. Create a site backup or confirm that you already have a recent backup available.
2. Download the installation ZIP archive for the extension from a legitimate source listed by the developer or on the product page.
3. Open the Joomla admin panel and go to the extension installation area, for example System -> Install Extensions.
4. On the Upload Package File tab, select the JUX Photo Gallery archive and start the installation.
5. After it finishes, check Joomla's message. It should confirm a successful installation with no package or manifest errors.

If Joomla reports that the file is not recognized, first check whether you need to unpack a master archive and install the inner package instead. This is a common situation for extensions that are distributed together with documentation or extra materials. Do not upload an archive that contains instructions, a license, and nested ZIP files if it also includes a separate installable package inside.

Publishing the Module and Choosing a Position

After installation, open the site's module list. In newer Joomla versions, this is usually under Content -> Site Modules or a similarly named admin item. Find the JUX Photo Gallery module, open it, and check the core fields: title, publication status, position, access, ordering, and menu assignment.

In Joomla's module system, it is important not to confuse three different cases: the module may be installed but unpublished; published but assigned to the wrong position; or assigned to a position but hidden by menu rules. For your first check, choose an obvious position, temporarily assign the module to a single test page, and save the changes. Then open that page on the front end as a regular visitor.

Test with a Minimal Set First

Do not start with the full final gallery. Add a few images, enable a simple display mode, and confirm that the module appears at all. Only after that should you move on to filters, carousel behavior, the lightbox, and visual fine-tuning. This order helps separate installation issues from issues tied to a specific display mode.

Detailed Post-Install Setup: From Placement to Gallery Behavior

This configuration section should answer the main question: what exactly needs to be changed after the module is installed. With JUX Photo Gallery, practical setup is built around five layers: where the module appears, which images it displays, how they are laid out, what happens when the visitor clicks, and how the visitor filters the set. If you work through those layers in order, you are less likely to end up with a gallery that looks attractive but is awkward to use.

Layer 1. Publication, Access, and Menu Assignment

Start with the visibility rules. In Joomla, a module can be visible to everyone, only to registered users, or to another specific group. For a public photo gallery, Public access is usually the right choice. If the gallery is intended for a restricted section, choose the access level deliberately and test the page under the correct user role, not just as an administrator.

It is usually safer to start menu assignment in "Only on the pages selected" mode. That prevents the gallery from appearing accidentally on the homepage, in the blog, in article views, or in utility pages. Joomla documentation emphasizes that module behavior is controlled by the combination of menu assignment and access level. For a visual block, this is especially noticeable: the same gallery may feel perfectly natural on a project page and completely out of place on a contact form.

How to Roll Back Visibility Safely

If the module disappears after you change the rules, do not start changing everything at once. Open only the menu assignment section, temporarily enable display on all pages, save, and check the result. If the module reappears, the cause is in the menu rules. If it does not, go back to the position, publication status, and access settings.

Layer 2. Image Selection and Grouping Logic

The order of images in the gallery should tell a clear story. For a portfolio, it is usually better to start with the strongest finished work, then show details and variations. For a photo report, chronology often works best. For a service or product page, a useful structure is "overall view - close details - real usage example." If JUX Photo Gallery is configured with sorting or filtering, order and tags become part of the user's path through the page.

Do not overload the first gallery. If you have 60 images but the visitor only needs a minute to judge the quality of your work, it is better to show 18 strong shots and provide filters. The rest can live on a separate page or in a second gallery. A good gallery does not have to show everything in the media library; it needs to show what helps the visitor make a decision.

Layer 3. Columns, Spacing, and Responsiveness

The official sources mention responsive design, but responsiveness still has to be tested in your own template. On a real site, the gallery is affected by template containers, position width, theme CSS, caching, image optimization, and nearby content blocks. If the module is placed into a narrow position, even a good grid mode can feel cramped.

For a typical site, start with a moderate number of columns on wide screens and check how the grid reflows on tablet and mobile widths. If the images crop important details, adjust the thumbnail proportions or choose a mode that handles mixed image shapes more gracefully. If the spacing looks too large, do not rush to edit CSS. First check the module's built-in options and the template settings.

Layer 4. Lightbox, Captions, and Control Icons

The lightbox should be convenient without being intrusive. Check whether the large image opens on click, whether titles and descriptions are visible, whether there is navigation between images, and whether the popup overlaps important template elements. If your version includes a setting to disable the download icon in the popup, use it anywhere a direct invitation to download is not appropriate.

Captions should not turn into long descriptions. For a gallery, short and specific wording works better: location, type of work, stage, material, event, or task. If the caption becomes the main text in the lightbox, it may be a sign that the content belongs in a dedicated case study or article, with the gallery left as visual support.

Layer 5. Filtering and the "No Tags" Group

Filters are only helpful when the taxonomy is clean. If some images have no tags, decide whether you want to show a filter for those items. The official changelog mentions a dedicated option to show or hide the no-tags filter, so this setting should be tested against the real media set. For visitors, a button labeled "no tags" rarely means anything unless you explicitly explain it.

For a business page, it is usually better to hide a meaningless group and clean up the image labeling instead. For an internal project, photo archive, or test page, leaving the no-tags group visible can sometimes help you quickly see which images still have not been classified.

Post-setup check: save the module, clear the Joomla cache and browser cache, open the page in normal viewing mode, and then test the filter, lightbox, and mobile width. Do not judge the result from just one screen view.

How to Place the Gallery in the Right Spot on the Page

The most common logic error when working with Joomla modules is assuming that installing an extension automatically creates a visible block on the correct page. In reality, the module must be placed into a position, that position must exist in the template, and the menu assignment must include the target page. For JUX Photo Gallery, this is not a minor technical detail. It is the foundation of the user-facing result.

Template Position as the Rendering Area

A position is an area the template has prepared for modules. Joomla documentation explains that the template designer controls the positions, while the administrator chooses which module goes where. That is why a position name such as sidebar-right, bottom, main-top, or content-bottom does not guarantee that the gallery will look good there. You need to judge it on the actual page.

For a photo gallery, a wide position is usually the better choice. A sidebar only works for small previews or a carousel. If you want to show a portfolio or photo report, a narrow column will make the images too small and hurt lightbox navigation. Start by placing the module in a wide area, check the grid, and only then experiment with more compact positions.

Menu Item Assignment

Joomla ties module visibility to menu items. This matters even when the page looks like "just an article." If the article does not have the correct menu item, or if users reach it through a different route, the module may appear somewhere other than where you expected. When configuring a gallery for a specific page, verify which menu item is acting as the main route for that URL.

If the gallery should appear only on a project page, choose the display mode for that page only. If it should appear on all items in a category, first check how your template and menu structure build the routes. On more complex sites, administrators sometimes create a hidden menu for utility pages so they can control the template, modules, and metadata more precisely.

Checking a Hidden Menu

If the gallery does not appear on an article even though the menu rules look correct, check whether that article has its own dedicated menu item. Sometimes Joomla uses the nearest parent item, and the module ends up following a different rule set. Temporarily assign the module to all pages. If it appears, go back to the menu rules and tighten the assignment more precisely.

Embedding It Next to Content

If your template does not provide a convenient position next to the article content, do not rush into editing template files. Check whether your site supports rendering modules inside an article through Joomla's built-in mechanisms, such as loading a module position within the content. The usual approach is to create a unique position, assign the module to it, and insert the corresponding call into the content, assuming your editor setup and site policy allow it.

This approach requires care: the position should be unique, the module should not appear on every page, and the editor should not strip out the utility syntax. For most users, it is simpler to start with existing template positions. Inline placement becomes useful when the gallery needs to appear directly after a specific paragraph or inside a case study.

Filters, Tags, and the Lightbox: How to Keep the User Journey Clean

Filters and the lightbox make the gallery interactive, but the interaction has to feel clear. Visitors should not have to guess why one group is empty, why some images disappeared, where a click will lead, or how to close the popup window. That is why these features should not be configured as simple on/off switches, but as part of an actual user flow.

Start with Meaningful Groups, Then Add Filter Buttons

For a portfolio, filters can be named by work type: "interiors," "portraits," "details," or "before and after." For a photo report, they can follow days, venues, or themes. For a service page, they can reflect project stages. The closer the labels are to the visitor's language, the more likely the filter is to be used. Do not expose internal tags like set-01 or client-a in public navigation.

If you have only a small number of images, a filter may be unnecessary. Three groups with two photos each create more visual noise than value. In that case, a simple grid is often clearer, and the grouping can be explained through captions or image order instead. Filtering is useful when it shortens the visitor's path to the right image set, not when it merely proves that the feature exists.

What to Check in the Lightbox

The lightbox should open quickly, display a large image, and provide an obvious way to close it. Check keyboard navigation and click behavior, mobile usability, the visibility of titles and descriptions, and whether the popup overlaps important elements such as a cookie banner or a sticky header.

If the gallery includes video, test that media separately: check how it opens, whether playback stops after closing, and whether embedded videos conflict with script optimization tools. The official product page mentions an image and video lightbox, but the exact behavior always depends on the module version, site settings, and hosting environment.

The Download Icon in the Popup

The JUX Photo Gallery changelog includes an option to disable the download icon in the popup. In practice, that means if the gallery displays client work, original photography, or visual assets that are not intended for direct download, you should verify this setting before publishing. It does not replace content protection, but it reduces the chance that visitors will interpret the gallery as a downloadable file library.

After disabling the icon, check the popup itself. Removing a single control can sometimes change the visual balance of the toolbar. If the lightbox interface becomes less intuitive, add short captions to images or choose a different viewing mode. The key point is not to leave visitors without an obvious way to move to the next image or close the window.

Practical Example: A Portfolio Gallery for a Service Page

Consider a realistic use case. You have a Joomla site for an interior design studio. On the "Projects" page, you need to display a gallery of completed work: overall views, details, layout solutions, and final photos. The gallery should appear only on that page, open images in a lightbox, offer filters by project type, and avoid overloading the page.

Goal

Create a module-based gallery placed in a wide position beneath the page's introductory text, showing 12 to 18 prepared images, allowing visitors to filter by "overall view," "details," and "process," and opening a large image without taking users to a separate page.

Preparation

Before configuration begins, the administrator prepares the images: reduces overly large files, standardizes the caption style, assigns tags to the media, and decides on the display order. On a test page, the template position is checked in advance, for example the area below the main content. If the position is unknown, the administrator reviews the template position map through Joomla's built-in mode.

Configuration Steps

1. Install JUX Photo Gallery through Joomla's standard installer and confirm that the installation completes without errors.
2. Open the site's module list, locate the JUX Photo Gallery module, and publish it.
3. Choose a wide template position that sits next to the page's main content.
4. In menu assignment, select display only on the portfolio page or on the group of pages where the gallery is actually needed.
5. Add the prepared images, assign titles, short descriptions, and group tags.
6. Select a layout: a grid for an even portfolio presentation, or masonry if the images use mixed proportions.
7. Enable the lightbox and check whether download controls are needed in the popup.
8. Save the module, clear the cache, and open the page as a regular visitor.

Result Check

The page should show thumbnails, the filter should display only relevant images, clicking a thumbnail should open a larger view, and closing the lightbox should return the visitor to the same gallery state. On mobile widths, the images should not turn into tiny tiles, and the filter should not take up half the screen.

A Common Detail That Gets in the Way

If the module is visible on the homepage but not on the portfolio page, the cause is often not JUX Photo Gallery itself but the menu assignment or template position. Temporarily enable display on all pages and choose an obvious position. If the module appears, restore the restrictions gradually: first the position, then the access settings, then the menu rules.

Practical Usage Scenarios: What Kind of Gallery to Build for Different Pages

The same module can be configured in very different ways, and this is where JUX Photo Gallery stops being just a set of thumbnails. A service page, photo report, work showcase, and homepage promo block all call for different choices: in one case filtering matters, in another compactness matters, elsewhere a large lightbox matters, and sometimes a calm grid with minimal motion is the better fit. If you apply the same settings template to every page, the gallery quickly becomes decorative rather than useful.

Service Page: Prove the Quality of the Work

On a service page, the gallery should answer the question "what result will I get?" That is why the first screen of the gallery should begin with finished results rather than process shots. Filters can be used for work types, materials, room types, or categories of service. The lightbox matters here because visitors need to inspect details without losing the context of the page.

In this scenario, avoid adding too many similar shots. Choose strong images, add short captions, and check that after opening the lightbox the user can return easily to the service description. If the gallery sits after a benefits section, it should visually support those benefits. If it sits before an inquiry form, it should help the visitor decide rather than distract them with endless scrolling.

Photo Report: Preserve the Sequence of Events

For an event report, workshop recap, or exhibition page, sequence matters. In that case, filtering by image type may be less useful than a clear order: setup, opening, main segment, details, and wrap-up. If the photos vary widely in aspect ratio, masonry helps preserve a lively rhythm without harsh cropping.

The main risk in a photo report is excessive volume. Visitors do not need to see every image. It is usually better to show the key shots and keep the full archive in a separate repository or second gallery. On a report page, the gallery should support the story, not replace it with a massive unstructured image feed.

Homepage Promo Block: Do Not Overload the First Screen

If JUX Photo Gallery is used on the homepage, the setup should be especially restrained. The homepage already contains a header, navigation, a call to action, news, or a service showcase. A large grid with dozens of images can slow the page and blur the main user journey. For the homepage, a compact carousel or a short grid with a few strong images is usually the better choice.

Check not only how it looks, but how it balances with the rest of the page. If the gallery competes with the main headline, inquiry form, or another important block, reduce the number of images, move the module lower, or switch to a calmer layout. On the homepage, the visual block should quickly communicate quality and encourage the visitor to move into a more detailed section.

Internal Project or Restricted Section

In a restricted area, the gallery can be less promotional and more functional. For example, a team may use it to review renovation stages, mockups, site photos, or materials for approval. In that case, access control, menu assignment, and clear grouping matter more than polish alone. If the block is available only to registered users, make sure to test visibility not only as an administrator but under the actual user role.

For internal galleries, more technical captions can sometimes be useful, but do not turn the public presentation into a utility archive. If the same image set needs to serve both the client and the internal team, it is usually better to create two separate module instances: one polished public version and one more detailed version for the restricted section.

Verifying the Result: Speed, SEO, and Viewing Usability

After configuring the gallery, do not evaluate the appearance alone. A photo gallery affects load speed, page perception, visitor behavior, and how well images are indexed. The official page describes the product as SEO-friendly, but the real outcome depends on how the administrator prepares the images, captions, page content, and Joomla environment.

Speed and Image Weight

A gallery can be technically correct and still be too heavy. If the page loads slowly, check file sizes, the number of images above the fold, lazy loading, caching, and template optimization. Do not enable every effect at once if the goal is to showcase a portfolio quickly. A nice transition does not make up for a delay that causes visitors to close the page.

For the first release, compare the page before and after enabling the module. You do not need complex tooling: it is enough to open the page on a normal connection, watch how long it takes for the first row of images to appear, and see whether the layout shifts during loading. If the visual block jumps around, set stable thumbnail dimensions or choose a more predictable layout.

Image SEO Without Inflated Promises

A gallery by itself does not guarantee ranking gains. It helps make the page more useful when the images are relevant, the captions are clear, and the surrounding text explains the context. For SEO, filenames, alt text, titles, captions, and the overall value of the page matter. If the gallery shows work without explanation, both search engines and users have a harder time understanding why those images matter.

Use short captions that explain what is shown, where it applies, and what result is being demonstrated. Do not stuff captions with repetitive keywords. For a portfolio, "Kitchen after built-in lighting installation" is far better than "best portfolio interior design photo gallery." That kind of wording helps both people and search engines.

Accessibility and Clarity

Check the contrast of filter buttons, the size of lightbox controls, the ability to close the popup, and keyboard behavior. If visitors cannot tell that thumbnails are clickable, add a visual cue through settings, captions, or light styling. If the filter looks like plain text, people will ignore it.

Final validation: ask someone who did not configure the site to open the page, find the right image group, enlarge one photo, and return to the page. If they can do that without guidance, the gallery is clear enough.

Safe Visual Improvements Without Editing the Extension

Sometimes the built-in settings are enough, but the gallery still feels slightly out of sync with the template: spacing is too tight, captions look too small, or the filter buttons do not match the rest of the interface. In that situation, there is no need to edit JUX Photo Gallery files or the Joomla core. It is safer to use CSS in the template's custom stylesheet or in the built-in custom styles field, if your template provides one.

This approach follows standard Joomla practice: presentation is best handled on the template side, not inside the extension files. The exact module classes may vary, so before applying changes, inspect the page in the browser and replace the selector with the one your site actually uses. If the exact class is not confirmed, do not paste the code blindly.

Example of a Careful CSS Adjustment for the Gallery Container

This example demonstrates the principle rather than promising the exact JUX Photo Gallery classes. Replace .jux-photo-gallery with the actual outer container class used by the module in your page HTML. Add the change to the template's custom CSS, not to the extension files.

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

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

.jux-photo-gallery .filter,
.jux-photo-gallery .gallery-filter {
  margin-bottom: 16px;
}

After saving, clear the cache, reload the page, and check two states: the regular grid and the lightbox. If the change affected the wrong block or made the layout less responsive, remove the CSS and return to the built-in settings. Do not add aggressive rules such as !important unless there is no other choice, because they make future maintenance harder.

Localizing Captions and UI Strings

If English words remain in the module interface on the public page, first check the language files and Joomla's built-in language overrides. In Joomla, this is safer than editing text inside the extension files. A language override can be changed or removed later without the risk of losing the edit during an update.

If you cannot find the specific string key, do not invent one. Locate the string through the language override area in the admin panel or through the developer's documentation. If the extension does not expose the string for translation, document the limitation and decide whether it is actually critical for the page.

Why the Gallery May Not Work and How to Diagnose the Problem

Problems with JUX Photo Gallery are often caused by more than the module itself. The result is shaped by the template position, menu assignment, cache behavior, script conflicts, image quality, and lightbox settings. Below is a practical troubleshooting path that starts with visible symptoms and moves toward targeted checks.

The Module Is Installed but the Gallery Is Not Visible

Symptom: the installation completed successfully, but there is no gallery on the page. The likely reason is that the module is unpublished, assigned to the wrong position, hidden by menu rules, or available only to a different user group.

Check the publication status, position, access level, and the menu assignment tab. Temporarily enable the module on all pages and choose a position that definitely exists in the template. If the gallery appears, restore the restrictions one by one. If it still does not appear, verify that images have been added and that the template CSS is not hiding the block.

The Gallery Appears on the Wrong Page

Symptom: the module is visible on the homepage or in other sections even though it should appear only on a project page. The cause is usually the menu assignment. In Joomla, module visibility depends on selected menu items, not just on the URL or article title.

Open the module settings and choose display only on the required menu items. If the page does not have its own menu item, create the correct one or use the appropriate parent route. Do not leave the gallery in "all pages" mode if it belongs to a specific case or project.

The Filter Shows Empty Groups or Odd Results

Symptom: after clicking a filter, some images disappear in a way you did not expect. Likely causes include inaccurate tags, untagged images, a misunderstanding of the no-tags filter, or stale cached data.

Check the tags assigned to each image and decide whether the no-tags group should be shown at all. After making changes, clear the cache and test the page again. If filtering is not actually useful to visitors, it is better to turn it off than to leave a confusing set of buttons in place.

The Lightbox Does Not Open or Looks Broken

Symptom: clicking a thumbnail does nothing, the popup opens without styles, or the controls overlap each other. The likely cause is a JavaScript conflict, aggressive file aggregation, caching, or a conflict with the template or another extension. The JUX Photo Gallery changelog includes a fix for a jQuery conflict in Joomla 5, so this class of problem is entirely realistic.

For testing, temporarily disable JavaScript optimization, file aggregation, and deferred script loading. Clear the cache and reload the page. If the lightbox starts working, re-enable optimization gradually and exclude the gallery scripts from aggressive processing. If the issue remains, check the browser console and the developer documentation.

Images Are Duplicated When Caching Is Enabled

Symptom: duplicate images or an odd order appear in the gallery after progressive caching is enabled. The JUX Photo Gallery changelog mentions a fix for duplicates in Progressive Caching mode, so if you see this symptom, the first step is to verify the extension version and cache settings.

Disable progressive caching during troubleshooting, clear both the Joomla cache and browser cache, and test the page again. If the issue disappears, update the extension to a supported version before re-enabling caching. Do not leave duplicates on a live page: they make the gallery feel broken and reduce trust in the presentation.

The Grid Breaks Across Columns or on Mobile Widths

Symptom: rows look uneven, images jump around, or columns become too narrow. The changelog includes a fix related to column issues, and the official sources describe the output as responsive. That means your checks should include both the module version and the influence of the template.

Check for an extension update, reduce the number of columns, switch the layout mode, and test the page in a wide position. If the grid still looks poor inside a narrow template position, use a carousel instead or move the gallery into a wider area.

When JUX Photo Gallery Is the Right Choice

JUX Photo Gallery is a good fit if you need a manageable Joomla photo gallery that can be displayed as a module, tied to the right position, and configured for a specific page. Its strength is the practical combination of a visual grid, responsive output, filtering, and a lightbox. The weak point of any module like this is its dependence on template positions, menu rules, cache behavior, and the quality of the prepared images.

Before publishing, walk through a short verification path: the module is installed, published, assigned to the correct position, visible only on the intended pages, images are optimized, filters make sense, the lightbox works, mobile width has been tested, and caching does not create duplicates. If all of those checks pass, you can move on to the download section and download the installation package for safe testing on your own site.

If what you actually need is not a visual module but a full media component with deeper photo archive management, do not try to force a simple module into that role. Compare JUX Photo Gallery with Phoca Gallery, Balbooa Gallery, Simple Image Gallery, and sigplus based on where the gallery is supposed to live: in a module, inside an article, or as a separate section of the site.