JUX JoomShopping Products Carousel - Joomla Extension

A Practical Guide to Configuring JUX JoomShopping Products Carousel

JUX JoomShopping Products Carousel is useful when a storefront needs a focused, curated display, not just something to scroll through. The module pulls products from JoomShopping, arranges them in a horizontal carousel, and gives visitors a quick way to browse current offerings: new arrivals, featured products, popular items, or products from a specific category or manufacturer. This guide focuses on how to use the extension, not on a promotional overview. It walks through a safe installation, choosing a product source, placing the module in a template position, configuring carousel behavior, and checking the result on a live page.

The main challenge with blocks like this usually isn't installing the archive. Mistakes tend to happen earlier: a promotional display gets confused with a full category listing, the product selection is empty, the module is assigned to a template position that doesn't exist, or too many cards and effects are enabled at once. This guide starts with the store's goal, moves on to the JoomShopping data, then covers the module and its appearance. That order makes it easier to understand why a particular set of products appears on the site and how to change it without making ad hoc template edits.

Tab and field names may vary slightly between Joomla builds, language packs, and extension versions. Where the interface hasn't been confirmed in a public screenshot, this guide describes what the setting does and what to expect rather than inventing a button name. That is safer than searching for a control that may not exist.

What the Module Does and When a Carousel Makes Sense

This is a module for a JoomShopping store, not a standalone catalog or a replacement for product pages. Its job is to show a focused selection wherever visitors are still deciding what to browse. Good locations include the store homepage, a category landing page, the end of an article about a collection, a block alongside a brand description, or the area above a standard product listing. In each case, the carousel should answer one simple visitor question: what should I look at next?

The module supports several confirmed product sources: featured, latest, random, most popular, and manually selected products. You can also narrow the selection by category or manufacturer. The source and filter together define what the block means. For example, a row of new accessories on a brand page is better built from the latest products by that manufacturer than from all new arrivals in the store. For a short seasonal collection, manual selection is more convenient because the products stay the same even as other items are added to the catalog.

A carousel is especially useful when a page should offer a few ways to continue browsing without taking up the whole above-the-fold area. A wide storefront can show several cards at once, while a narrow viewport can display a readable row that visitors can swipe through. The developer lists responsive columns and rows, touch support, arrows, navigation dots, autoplay, and a Coverflow effect powered by Swiper.js. That doesn't mean you should enable everything at once. These options let you choose a clear browsing experience for the product selection and the amount of content.

Who Is It a Good Fit For?

The module works well for a store that already maintains JoomShopping product pages with images, names, prices, and clear publication status. It's useful for editors who regularly update product selections without changing the template, and for catalog owners who want to feature a specific group on the homepage: a new shipment, products from one brand, items with a previous price and a discount, or featured products from a chosen category. Designers can also use consistent card heights and image proportions to create a tidy row when the source photos have different dimensions.

Another good fit is a site with long product listings. A carousel doesn't have to repeat the full category; it can provide a short introduction to it. Show four to six items in the carousel, then keep the regular catalog with filters below. Visitors get a quick overview without losing the ability to compare the full selection.

When to Choose a Different Format

Don't use a carousel as the only way to browse every product in a category. Horizontal scrolling hides part of the selection beyond the initial viewport and is less suitable for comparing dozens of models. Keep a category page or JoomShopping grid for a long catalog. The module also won't fix incomplete product data: if an item has an incorrect price, no image, or the wrong publication status, an animation will only make the problem more noticeable.

Use autoplay with care on pages where people read specifications or choose product options. A moving carousel can be distracting, especially when there's another slider nearby. Don't expect the module to manage inventory, add SEO markup to product pages, process payments, or edit the catalog itself; those responsibilities remain with JoomShopping and Joomla. The carousel selects and presents data that already exists.

Prepare the Catalog: Get the Data Ready Before Adding Effects

Before installation, define one goal for the first carousel. Write it as a plain sentence, such as "show the latest products from the summer backpacks category on the homepage" or "show manually selected models on the manufacturer's page." That sentence points you to the right source, filter, and placement. Without it, configuring the module becomes a process of toggling options, and the result can turn into a random feed from across the store.

Check the products in JoomShopping. At a minimum, each product should be published, have a clear name and correct main image, and have an available price if you plan to display it. If you intend to show a previous price, rating, short description, label, or add-to-cart button, first confirm that the relevant information is filled in and that the store settings allow it to appear. JoomShopping stores product data, categories, manufacturers, images, and labels as separate entities; the carousel shouldn't be used to hide gaps in that data.

Selection depends on product status, not on how attractive the card looks. A featured product won't appear if it isn't published or doesn't match the filter. A manual list doesn't fix an unavailable product; it only defines which products to include. Before configuring the module, open the public pages for two or three products you plan to feature. This gives you a chance to catch a missing photo, blank price, overly long name, or product that shouldn't be promoted.

Pre-Installation Checklist

• A compatible Joomla and JoomShopping setup. The extension's public listing states that it works with Joomla 4, Joomla 5, Joomla 6, and current JoomShopping versions. A live site still needs a backup and a check against its specific build.
• Administrator access to install extensions and manage modules. Without it, you can install the archive but can't publish the module in a template position.
• A ready-to-use product selection. Prepare several published items in the right category, from the right manufacturer, or in a manual list. Don't test with an empty catalog.
• A known template position. Decide where the block should appear: below the hero section, above the product grid, in a sidebar, or at the end of an article. A position is available only if the active template supports it.
• A page to use for testing. Note the URL where the module should appear. You'll need it to set the menu assignment and to check the page again after clearing the cache.

A safe way to start: don't configure the first storefront display on the live homepage during peak sales hours. Create the module in an unpublished state, fill in its settings, assign it to a test page, and publish it only after checking the result.

Template Position and Menu Assignment Are Separate Settings

The position answers where in the markup the module will appear. Menu assignment answers on which pages Joomla will display it. These are independent reasons why the block may not be visible. Joomla's official module documentation describes the same sequence: publish the module, choose a position, and specify the pages in its menu assignment. If you miss any of these steps, product source settings won't help.

If you don't know the position, don't guess based on its name. Joomla lets you enable template position preview and open a page with the ?tp=1 parameter, if the option is allowed in the global configuration. On a public site, enable this preview only briefly and don't expose it to visitors. It's there to help you match a visible area to a position name, not to serve as a permanent storefront feature.

Install the Archive and Run a Safe First Check

Install the ZIP archive through Joomla's standard extension installer. In the current administrator interface, start under System, open the extension installer, and select the package upload tab. After installation succeeds, don't look for the result in the Components menu. JUX JoomShopping Products Carousel is a module, so you'll manage it in the site modules list, not on a separate catalog management page.

1. Back up the site, or at least its database and files, before adding a new extension to a live project.
2. In the administrator interface, open the extension installer under System and upload the original ZIP archive.
3. Wait for Joomla to confirm that the installation succeeded. If Joomla reports a package error, don't keep uploading the archive. Save the error message first and check that the download is intact.
4. Open the site modules list under Content. Find the created instance, or create a new module instance if the installed module type is available in the list.
5. Give the instance a clear internal name, such as Home - New Backpacks. This name doesn't have to appear on the site, but it makes future maintenance safer.
6. Leave the module unpublished, fill in its source and placement, save it, and then move on to a test publication.

Don't edit Joomla, JoomShopping, or module system files to make the module appear. This isn't needed for ordinary configuration, and your changes would be lost during an update. If the module type doesn't appear in the list after installation, stop and diagnose the installation: check Joomla's message, your administrator permissions, and whether the archive matches the product. Editing code isn't the right first step.

Keep the First Instance Focused

Create the first module instance for one page and a small selection of products. That makes it easier to tell a source problem from a placement problem. For example, if you're testing on a category page, assign the module only to that menu item, choose its position, and show a few products from that category. Once it works, duplicate the instance for other use cases instead of turning one general-purpose block into a set of conflicting rules.

When you save, check two things. First, make sure the module is visible to editors in the administrator interface and has a clear name. Second, make sure it hasn't appeared in random positions across the public site. A careful first instance pays off later: a month from now, it should be easy to tell which block shows new arrivals and which one features a specific brand.

How Product Selection Works: From JoomShopping Source to a Curated Row

The heart of JUX JoomShopping Products Carousel isn't the scrolling effect; it's the rule JoomShopping uses to supply products. Before configuring columns, choose one source type. According to the extension's public description, it can display featured, latest, random, most popular, and manually selected products, and narrow the selection by category or manufacturer. Each combination serves a different editorial purpose.

Latest, Popular, Random, and Featured Products

Latest products work well on a store homepage, in a new arrivals section, or in a focused category that gets updated regularly. The check is simple: add a published test product to the right category and confirm that it appears in the expected order. If it doesn't, compare the product data with the selection criteria before changing the appearance.

Featured products work well for a deliberate editorial focus when JoomShopping has a meaningful status or flag for highlighting an item. This is more convenient than trying to create a "featured product" using styles alone. However, this source calls for consistent maintenance: editors need to know which flag changes the carousel's contents, or yesterday's promotional selection may remain after the campaign ends.

Most popular and best-selling products make sense only when the store has enough data and the owner understands what determines that ranking in their setup. Don't present an algorithmic list as an editorial recommendation. After enabling it, check the actual product page: products should be published, available to the intended audience, and relevant to the block's purpose.

Random products are useful for a secondary display in a broad catalog, but not for a promotion with a fixed selection. The carousel has no stable order, which makes it harder to check a specific card or run a campaign. If the page promises a particular collection, use a category or manual selection.

Filter by Category or Manufacturer

Filtering by category gives visitors context. On a "Hiking Backpacks" page, a block of products from the same category supports browsing, while a feed from across the store is a distraction. Filtering by manufacturer is useful on a brand page or in an article about a product line, but it doesn't replace a category filter if the brand makes a wide range of products. Don't enable both filters without a reason: their intersection may be so narrow that the carousel is empty.

A small, controlled selection is the best way to check the setup. Choose three published products that you know belong to one category, plus one similar product outside it. Filter the carousel by that category. The expected result is that only the first three products appear. Then switch the filter to manufacturer and repeat the check. This test verifies the filter and confirms that the products have the necessary JoomShopping associations.

Manual Selection for Campaigns

Manual selection works well for a small set where the order and contents matter more than automatic updates: a travel kit, a gift collection, products featured in a how-to article, or a clearance of selected inventory. Its advantage is consistency. Once you save the page, you know exactly what visitors will see. The tradeoff is that the list needs maintenance: unpublished products and missing images won't fix themselves.

Before launching a manual carousel, keep a short editorial record: the product, why it was selected, when it was last checked, and who is responsible for removing it after the campaign. In the module, show only what visitors actually need to see. This habit matters more than elaborate animation because it prevents outdated seasonal products from lingering on the homepage.

Configure Cards and Motion Around What Visitors Need to See

After choosing the products, decide how to present them. The developer lists several display styles, configurable columns and rows, image proportions, equal card heights, sorting, and options to show an image, hover effect, price, previous price, rating, labels, short description, and add-to-cart button. This isn't a list of settings to enable all at once. A good card helps visitors make a choice faster instead of giving every element equal attention.

Choose One Priority for the Card

For a visually distinctive product, the image and name are usually the priority. For a price-driven purchase, show the image, name, and price. For a sale, show the image, current price, and previous price, if the previous price is filled in correctly. For a complex product with a long name, first check how the name wraps before adding a short description. If the image, five lines of description, rating, label, two prices, and button all have equal visual weight, the card will be hard to scan in a row.

Start with a basic version: photo, title, price, and one clear way to open the product. Then add only the elements that help visitors choose. A rating makes sense when the site has trustworthy reviews. A label helps when it has a consistent meaning across the catalog. A short description is useful for a product line where the photo doesn't explain the differences. An add-to-cart button is appropriate when visitors can decide without opening the product page. For products with variations or those that require a consultation, make the card a path to the detailed product page instead.

Image Proportions and Consistent Card Heights

Differences in the original photos can disrupt a carousel more than the wrong transition effect. The image proportion sets the visible frame for the main product photo. If most catalog photos are portrait shots of clothing, don't use a wide frame just because it looks modern. If the products are wide, an overly tall container will create large empty areas. First open a few real product cards on the public site, then choose a proportion that suits most of them rather than the one perfect image.

Consistent card heights are especially useful when product names and descriptions vary in length. This keeps the price and button aligned, making the row easier to scan. But it can't fix poor data: if one title takes five lines and another is a single word, edit the title or hide the short description rather than relying on the height setting. After enabling it, compare the cards with the longest and shortest names at wide and narrow viewport widths.

Columns, Rows, and Actual Card Size

Column and row settings control how many products are visible at once. Choose a layout based on the smallest useful card size. A wide page area can show several cards as long as the title and price remain readable. In a sidebar, too many columns turn products into thumbnails that are difficult to compare. A single row is usually easier to scan in a promotional block. Multiple rows make sense only when the position is wide enough and visitors won't have to guess where one group of products ends.

Don't check only how the carousel looks on a large display. Resize the browser to a typical tablet and mobile width, swipe through the row or simulate touch, and open the last card. The stated responsive behavior means the module is designed for different devices, but the quality of a particular setup depends on the template, position, and amount of text. The key check is that each card remains recognizable and the arrows, dots, and buttons don't cover the price or title.

Arrows, Dots, Touch, and Autoplay

Arrows work well for a wide row when visitors can see there are more products beyond the current view. Navigation dots help show the size of a collection, but become clutter in a long selection. Touch support matters on narrow screens, but doesn't remove the need for a clear way to move to the next group on desktop. Save Coverflow for a short visual collection where the center product should stand out; ordinary sliding is often easier to follow in a dense commercial catalog.

Autoplay shouldn't get in the way of reading. First enable it only on a test page and see whether visitors have enough time to read the name and price. If there's a banner, video, or another interactive block nearby, turn off automatic movement or keep it to one area of the page. Check that manual navigation doesn't conflict with autoplay and that visitors don't lose track of a selected card when they hover over it.

Sorting Shapes the Editorial Message

Sorting determines which card leads the row. For new arrivals, the newest product should be first. For a manual campaign, keep the order fixed. For popular products, make sure the selected criterion doesn't put an item at the top if it temporarily can't be ordered. Don't use random sorting if the first product is tied to a banner, promotional text, or analytics goal.

After changing the sort order, make a quick note of the selected criterion, the card that should appear first, and the page where you checked it. This may seem minor, but it helps keep the storefront display understandable when another editor opens the settings a few weeks later.

A Map of the Module Settings: Configure Them Without Conflicts

It's easier to configure JUX JoomShopping Products Carousel if you group settings by what they affect rather than by where they appear on the screen. Start with the data, then set the order, card contents, row layout, and finally motion. This avoids a common trap: changing the effect or number of columns when the real problem is an empty category or an overly long product name.

Create a separate test instance if a live carousel already serves a page. You can change one setting at a time and take notes. Start simple: a verified source, several published products, one row, ordinary sliding, and only the essential card fields. After each save, change one group of settings, open the same test page, and note what you see. If the result gets worse, you'll know exactly which change to undo.

Group 1: Product Source and Filter

This group answers the question, "Which products can appear in the row?" Choose a source type: latest, featured, random, most popular, or manually selected products. Add a category or manufacturer filter if the row needs one to make sense. First save the source by itself, then add the filter. This two-step check is especially helpful when the selection is empty: you'll see whether the filter narrowed it down to zero.

For a typical store, this is a reasonable approach. On the homepage, use the latest products from a featured category or a manual selection for a campaign. On a brand page, filter by manufacturer. In an article about a specific theme, use a manual selection if the article discusses particular models. Use random products only for a block that doesn't promise an editorial selection. Don't use popularity or sales as a generic substitute for a recommendation; they follow different rules and set different expectations for visitors.

Group 2: Order and Limit

The limit isn't the maximum number of products in the database; it sets the size of this particular display. Choose it based on the position's width and the block's purpose. A short block above a catalog usually works better with fewer cards: visitors see a coherent row and know there's a category page for more. A larger limit makes sense when the navigation and layout make it easy to reach the end. Don't choose a number just because it divides neatly into the columns.

The order determines what the first card means. If you're showing new arrivals, make sure the first item is the expected latest product. For a manual campaign, make sure the first product matches the nearby headline or banner. Random order is useful only when it doesn't break the page's promise. After saving, record the source, filter, limit, order, and expected first card in a screenshot or a short project note. This makes it easier to undo an experiment.

Group 3: Card Contents

The module can show several kinds of product information, including an image, hover effect, price, previous price, rating, labels, short description, and add-to-cart button. Treat each toggle as a commitment to show visitors accurate information. Don't display a rating until you know where the store gets it. Don't show a previous price if some products have it recorded incorrectly. Don't show a short description if the text was written for the full product page and turns into five lines at a narrow width.

For the first version, choose the essentials: image, name, and price. Then try one extra element and check again. Keep a label if it helps visitors identify a sale or new arrival. If the add-to-cart button is appropriate only for simple products without options, don't make it a universal call to action. In a storefront where buyers need to choose a size, color, or configuration first, the product page is a clearer next step. The goal is to make the decision easier, not hide a complex choice behind one button.

Check Card Contents in Edge Cases

Choose four test products: one with a long name, one with a short name, one discounted item and one without a discount, and one with a wide image and one with a portrait image. This isn't an artificial stress test; it's a realistic sample that reveals weak spots in the catalog. Open the carousel at wide and narrow widths. If some cards are too tall, try hiding the short description first. If prices don't line up, try equal card heights and fewer columns. If photos are cropped, revisit the image proportions. Fix the cause, not the symptom.

Group 4: Row Layout

Columns and rows determine how many products visitors can take in at a glance. Start with a layout where people can read the title and price without zooming in. Increase the number of columns only after checking the narrowest target viewport. Multiple rows may look impressive, but in a short carousel they can make the navigation unclear: visitors may not know whether they're moving through a row, a grid, or both. For a straightforward use case, a single row with clear navigation is easier to follow.

The image ratio sets the frame, while consistent card heights keep the row aligned. These settings affect each other: a tall frame combined with a long description can make the block bulky, while a frame that's too wide can make the product itself look small. First choose a shape that works for most catalog photos, then enable equal heights and check the most difficult card. An aligned row doesn't have to be perfectly symmetrical if that would crop important details in a photo.

Group 5: Navigation and Effects

Arrows, dots, touch, autoplay, and Coverflow affect how visitors move through the carousel, not which products it contains. Configure them last. For a standard product display, a reliable baseline is manual scrolling with a clear indication that more products follow. Arrows help desktop users, and touch supports natural browsing on narrow screens. Add dots only if a small number of them makes the size of the collection clearer.

Autoplay can work in a secondary promotional area, but not where people are comparing prices and specifications. Transition effects shouldn't change which card gets the most attention. If Coverflow makes the side products look too small or suggests that only the center product is available, switch back to ordinary sliding. The best carousel settings make the value of the products clear and let visitors control the row easily; they don't make the animation the main attraction.

This sequence also helps with ongoing maintenance. If the store owner asks you to "increase sales," don't respond by choosing a random effect. Ask which product group should be featured, in what context, and what success means: opening a product page, visiting a category, adding an item to the cart, or simply presenting new arrivals neatly. Then change the setting that affects that goal.

Place the Module in Joomla: Position, Pages, and Cache

Even a carefully configured selection remains invisible until the module instance has a matching status, position, and menu assignment. After setting up the cards, return to the tab where Joomla shows the instance's main settings. Choose a position provided by the active template. Set the status to Published only after deciding which pages should display the module. For the first launch, assign it to one menu item rather than choosing "on all pages."

Depending on the template, the same position may appear below the header, before the main content, above the footer, or in a sidebar. Don't rely on a name like top or sidebar alone; the template developer may use it differently. Preview the template positions or check the template documentation, then compare them with the actual page content. If the block should appear only in the store context, assign it to the menu item for the JoomShopping storefront or the chosen landing page, not the entire site.

Why Menu Assignment Matters

Menu assignment prevents the same carousel from appearing in places where it isn't relevant. For example, new arrivals may belong on the store homepage but get in the way during checkout or on a privacy policy or account page. Assigning the module to one specific page also helps with troubleshooting: if it's visible there but shouldn't appear elsewhere, the issue is with the assignment, not JoomShopping.

On a multilingual site, check the module's language and page assignment for each language. Without assuming a particular site configuration, the general rule is that visitors shouldn't see an empty carousel just because the product selection or menu item exists in another language context. Test the public URL for each version, not just the module in the administrator list.

Cache: Confirm the Change Before Trying to Improve Performance

The module's public description states that it supports Joomla caching. This is useful for a recurring storefront display, but caching affects how you check changes: an editor saves new settings, sees the old row in the browser, and assumes the filter isn't working. For the first launch, save your changes, open the page in a new window, clear the Joomla cache according to the project's usual process, and check again. If the site uses a separate cache or CDN, coordinate with whoever manages the infrastructure.

Don't disable caching across the site for one test. First confirm that the module, page, and browser copy are up to date. Then decide whether to keep the system's caching mode for the module. A carousel that changes infrequently is usually a good fit for caching. For a block that needs to reflect frequent editorial changes right away, a consistent cache-clearing process matters more than turning off performance features without a clear reason.

A practical check: change one easy-to-recognize product in the test selection, save the module, clear only the standard cache levels used by the project, and open the page as a logged-out visitor. If the old state remains, identify which cache layer is still involved instead of changing carousel settings at random.

Step-by-Step Example: A New Collection from One Category

This repeatable example shows how the module works without depending on a specific template. The goal is to display a short carousel of new products from one category on a store page. This use case checks the source, category filter, order, placement, and responsive behavior at the same time. It's a better test than a feed of random products because each item has a clear reason to appear in the block.

Set the Goal and Prepare the Page

Suppose there's a "City Backpacks" category with at least four published products that have main photos, titles, and current prices. Add one product from another category to use as a control. If the store has multiple manufacturers, choose test products from at least two of them. That will help confirm later that the category filter, not a coincidental manufacturer match, determines the selection.

Create or choose a menu item that opens the store or this category's landing page. Note its URL for testing. Find a template position above the main product listing. For this first test, don't create a new position by editing template files. Use an existing area so you can assess the module separately from template development.

Set the Source and Selection

1. Create a new JUX JoomShopping Products Carousel instance and give it the internal name Category - New City Backpacks.
2. Choose the latest products source. In this example, the carousel should show recently added items, not best sellers or a manual selection.
3. Filter the selection by the "City Backpacks" category. Don't add a manufacturer filter unless the display is meant to feature one brand.
4. Set a small number of products to display. At this stage, checking the selection matters more than filling the entire viewport.
5. Choose an order that fits the new-arrivals goal and save the settings.

Before publishing, open the settings for each test product. Confirm that all of them are published and belong to the selected category. Don't test the source while also changing the status, price, image, and category of several products. If the result is wrong, you won't know why. A controlled product outside the category is especially useful because its absence from the carousel proves that the filter is working.

Configure Cards for the First Version

For backpacks, a simple card makes sense: main image, name, price, and one clear way to open the product page. Enable equal heights if the names vary in length. Choose an image proportion that doesn't crop the top of the backpack or distort its shape. If you use a previous price and sale label, add them only for products where that price is correctly filled in and follows the store's rules.

For the first pass, don't enable hover effects, autoplay, Coverflow, multiple rows, the maximum number of columns, and every secondary field at once. The carousel should be clear in a static state first. Then enable arrows if the row is wider than the initial group of visible products. Use dots if they help visitors tell how many views there are. Add autoplay last, and keep it only if you've checked how it behaves alongside the other page elements.

Publish the Module and Assign the Page

Choose a template position you've already checked. Set the status to Published and assign only the category or storefront page you've chosen for the test in Menu Assignment. Save the module, then open the public page in a logged-out browser window. Don't check only from the administrator interface: editors may see a different cache state, and the module may be available to a different user group.

A successful first result looks like this: a row of products from the "City Backpacks" category appears in the right area of the page; the test product from another category is absent; the first card matches the chosen order; photos and titles stay within their bounds; and arrows or dots, if enabled, don't cover interactive elements. If all these checks pass, the connection between JoomShopping data, module rules, Joomla placement, and the public page is working as intended.

Check the Page at Wide and Narrow Widths

At a wide viewport, check the spacing between cards, the alignment of the prices, and the last visible card before the arrow. At a narrow width, make sure a finger or cursor doesn't accidentally hit a nearby button, the cards don't shrink into unreadable thumbnails, and scrolling doesn't push the page sideways. Open the last card, then return to the first. If the behavior is unpredictable, temporarily turn off autoplay and visual effects while keeping ordinary navigation. This will help you tell whether the issue comes from motion or from the product data.

How to Check the Setup Without Relying on Appearance Alone

Checking a carousel should answer specific questions, not come down to "it looks fine." The module has at least four layers to verify: product selection, page placement, card appearance, and scrolling behavior. Check each one separately. Then, if something goes wrong, you'll know whether to adjust the product category, source settings, menu assignment, or appearance.

Four Things to Check

After each change, run one check that matches the setting you changed. For example, after changing a filter, there's no need to review the button color. After moving the module to a different position, there's no need to change its sort order. This rhythm keeps cause and effect clear and reduces the risk of breaking a working setup.

Pay special attention to the experience for visitors without administrator access. They should see the published content the module was configured to display. If everything looks right in the administrator interface but the public page is empty, first check publication, access, menu assignment, and cache. If cards appear but the products are wrong, go back to the source and filter. This simple order can save a lot of time.

Small Improvements Without Editing Core Files

This module is designed to be configured through an administrator-managed instance, so the most useful improvements usually involve cleaning up the data and display rules rather than editing PHP files. Don't edit the Joomla, JoomShopping, or extension core just to change a label, adjust spacing, or hide a secondary element. Those changes complicate updates and are difficult to undo.

If the cards still conflict with a specific template after you've checked the settings, first review the built-in display options: whether the module title appears, its position, number of columns, image proportions, equal card heights, and card fields. If that isn't enough, ask the template developer about its override system or adding local CSS in the place provided by the theme. Do this only after creating a backup, using a precise selector you've checked in the browser, and making sure the change can be removed in one step. The available sources don't confirm any CSS classes specific to this module, so inventing a code snippet here wouldn't be reliable.

The most useful improvement without code is an editorial process. For each instance, record its goal, source, filters, position, assigned pages, and last check date. When the season or store owner changes, the editor can update not just the product display but also the rule that decides which products appear there.

Troubleshooting: Why JoomShopping Products Carousel Isn't Showing the Expected Products

It's easiest to troubleshoot a carousel by starting with the visible symptom and checking one layer at a time. Don't begin by reinstalling the extension or changing five settings at once. First confirm that Joomla recognizes the module instance, then check whether JoomShopping can supply matching products, and finally verify that the module appears in the right position and on the right page. This approach preserves working settings and makes the problem easier to reproduce.

The Module Is Installed but Doesn't Appear on the Page

Symptom: The instance appears in the administrator list, but nothing shows on the public page. Likely cause: The module isn't published, it's assigned to an unsupported position, or the page isn't included in Menu Assignment. What to check: Open the module instance and check Published, the position name, and the assigned menu item against the actual page. Then confirm that the active template contains that position.

Fix: Temporarily assign the module to one known page and a position you've confirmed. Save and check the public page. If the module appears, gradually restore the intended assignment. When to undo the change: If the module starts appearing on every page or disrupts the layout, restore its previous position and narrow the assignment instead of disabling it across the store.

The Block Appears but Has No Products

Symptom: The module leaves an empty area or a wrapper with no cards. Likely cause: The source can't find published products that match its rule, the category and manufacturer filters overlap too narrowly, or the manual list contains outdated products. What to check: Choose one known published product and compare its category, manufacturer, status, and selection mode. For a manual list, check each ID or selected item in the module itself.

Fix: Temporarily simplify the rule to a minimal working selection, such as the latest products from one verified category. Once the cards appear, add the other filters one at a time. When to undo the change: If the campaign depends on a combination of filters that actually produces no products, remove the manufacturer filter or prepare the products in JoomShopping instead of leaving visitors with an empty block.

The Wrong Products or Order Appear

Symptom: Products from another category appear, older items are shown, or the first product doesn't match the expected recency. Likely cause: The source and filter don't match, a product has multiple associations, the wrong sort mode is selected, or the editor expected a manual selection from an automatic source. What to check: Write one sentence describing the row's goal and compare it with the actual settings. Then check a test product that should be absent.

Fix: Choose one source and one clear filter, save, and repeat the test with the control product that should be excluded. For a campaign with fixed contents, switch to manual selection. When to undo the change: If the sort change alters the purpose of the display, restore the last documented order and confirm the business rule with the editor.

Cards Are Uneven, and Images or Prices Don't Line Up

Symptom: Some cards are taller, titles jump around, prices sit on different lines, or photos look cropped. Likely cause: The source images have different formats, titles are too long, descriptions are enabled at a narrow width, or too many columns are displayed. What to check: Compare the longest and shortest cards at different widths, and inspect the original image rather than only its appearance in the module.

Fix: Enable equal card heights, choose image proportions that fit the catalog, reduce the number of visible columns, and turn off secondary descriptions. If necessary, correct the product data first. When to undo the change: If equal heights create too much empty space, return to a more compact card instead of compensating with aggressive effects.

The Settings Are Saved but Visitors Still See the Old State

Symptom: The administrator interface shows new products or a new order, but the public page still has the previous carousel. Likely cause: Joomla cache, a browser copy of the page, or another cache layer. What to check: Open the page in a private window, clear the Joomla cache according to the project's process, and check again as a logged-out visitor.

Fix: Follow the agreed process for clearing all cache layers in use, then confirm again that the new selection was saved. When to undo the change: If someone suggests turning off the site's global cache for one block, don't apply that change. First identify the specific layer that is serving the old response.

Scrolling Is Difficult on a Phone or Beside Another Interactive Block

Symptom: Cards are hard to swipe through, autoplay moves a product away, arrows cover a button, or the motion is too fast. Likely cause: The layout is too dense, several navigation options are enabled at once, another slider is causing a conflict, or the effect isn't suitable. What to check: Temporarily leave a static row with ordinary scrolling and test it at a narrow width.

Fix: Reduce the number of columns, keep one primary navigation method, turn off autoplay, and make sure the last card is accessible. When to undo the change: If an effect makes the cards harder to read or the buttons harder to use, switch back to ordinary sliding. A clear product display matters more than decorative motion.

When This Carousel Becomes a Useful Part of the Store

JUX JoomShopping Products Carousel works well when it has a clear job: show new products from one category, a manually selected group, or a manufacturer's products in a specific Joomla position. Configure it in this order: data, selection rule, card, placement, and verification. Don't start with the scrolling effect. That keeps the module understandable to editors and gives visitors a short, useful path to the products they want instead of motion without a purpose.

If your products are published, you've checked the template position, and you can describe the first row's selection rule in one sentence, you can download JUX JoomShopping Products Carousel and start with a test instance on one page. After a successful check, expand gradually: one module for new arrivals, one for a brand, and one for a short manual campaign.