JUX Timetable - Joomla Extension

Guide to Setting Up and Using JUX Timetable

JUX Timetable is not just for dropping a nice-looking schedule grid onto a page. In this guide, we will look at how to turn the extension into a clear, usable timetable for classes, lectures, medical shifts, club events, or a hybrid program where visitors need to quickly find the day, time, room, instructor, and event details.

This guide starts with the product logic: which entities you should prepare, where it makes more sense to display the schedule through a menu item and where a module works better, and how to avoid getting lost in categories, trainers, rooms, and filters. Then it covers installation, post-install setup, a practical example, result checks, troubleshooting common issues, and a comparison with similar Joomla calendar extensions.

This guide does not replace the developer's official documentation, and it does not assume that one set of settings will fit every site. Its goal is more practical: to show a safe order of operations, explain what to check after each change, and help you decide whether JUX Timetable fits your specific use case.

What Problem a Schedule Solves on a Joomla Site

JUX Timetable belongs to the category of schedule and event extensions. Based on the developer's description and the listing in Joomla Extensions Directory, the product is built for class and event grids that can be displayed in daily, weekly, or monthly views and filtered by criteria such as category, instructor, location, day, or time. That makes it closer to a visual timetable than to a full booking system or ticketing platform.

The real value of a tool like this shows up when one event needs to be understood in the context of other events. For a fitness studio, that means overlapping days, rooms, and trainers. For a training center, it means sessions, groups, instructors, and classrooms. For a medical site, it means specialist and department schedules. For a conference, it means tracks, rooms, topics, and speakers. If the visitor first needs to understand the structure of the week and only then drill into class details, a grid layout is more useful than a standard list of articles.

JUX Timetable should not be confused with a full service booking system. The sources confirm schedules, filters, pop-up details, and pages for classes, events, and trainers, but they do not confirm payment processing, advanced seat booking, or automatic sync with external calendars. If your goal is to accept payments, reserve time slots, and send confirmations to attendees, it is better to start with a specialized booking extension.

A content-driven schedule works differently. You create the structure ahead of time: class categories, organizers, events, trainers, classes, classrooms, or rooms, and then publish the schedule on a public page. The visitor picks a filter, opens details in a modal window, or goes to a dedicated class page. In a good implementation, the user should never wonder what to click next - the schedule, filters, and details should work as one flow.

When JUX Timetable Fits, and When Another Tool Makes More Sense

Before installing anything, it helps to decide what the site actually needs to do. Many schedule-related problems come not from the extension itself, but from the wrong expectation: the site owner wants a calendar, a class catalog, instructor profiles, a registration form, and payment processing, but installs a tool whose real strength is visual scheduling. So the first step is not uploading the ZIP file, but choosing the right use case.

Good Use Cases

JUX Timetable works well on sites where the schedule needs to be displayed and explained, not necessarily booked. Typical examples include:

• A fitness club or yoga studio showing a weekly schedule with trainers, rooms, and workout categories.
• A school, college, or training center publishing schedules for courses, lectures, workshops, and consultations.
• A conference organizer splitting the program into tracks, rooms, and talks so attendees can quickly find their own route.
• A medical or wellness site showing office hours for departments, doctors, or group programs.
• A nonprofit organization publishing a schedule of in-person and online sessions where dedicated speaker pages matter.

In those cases, the product's confirmed features are useful: multiple schedule views, filters, pop-ups with extra text and images, color and background controls, and entity pages for things like classes, events, and trainers. In practice, that gives you more than just a calendar - it gives you a program showcase that is easy to read.

Cases Where the Product May Be Too Much or Not Enough

If a site only has three events per month and they just need to be listed, a full timetable grid may be overkill. If you need to sell tickets, manage capacity, take payments, send attendee emails, and track registrations, JUX Timetable is better seen as the visual layer, not the process center. For booking consultations, rooms, or services, you will usually need a specialized solution with an availability calendar, registration form, and occupancy rules.

There is also an editorial factor. If the schedule is updated often by people with limited Joomla experience, your team will need clear internal instructions: which fields are required, which filters should not be changed, and how to verify the result on mobile. User reviews mention an easy starting experience, but the developer forum shows that questions still come up around mobile display, languages, filters, and class rendering.

What to Check Before Installing the Extension

Preparation is not just a formality. A schedule touches the public site, menus, modules, language strings, cache, and sometimes the template. If you install the extension directly on a live page without a backup and rollback plan, even a small mistake can turn into a broken block, an empty mobile view, or incorrect navigation.

Compatibility and the ZIP Source

Check the product page on JoomlaUX and the listing in Joomla Extensions Directory. That is where you can see the extension type, package contents, license, Joomla branch compatibility, and change log. For this guide, what matters most is not the version number by itself, but what the changelog actually means: the developer fixed mobile rendering, cache behavior, multilingual support, daily view, room filter, the register link in the modal window, and frontend styles for newer Joomla branches.

Do not install a ZIP from a random mirror. For a commercial extension, it is safer to get the file from the official account, because that is where you get updates, support, and the correct package. If the site already uses an older copy, create a backup first and check whether any template overrides or language overrides were customized.

Backup and Test Page

Before installation, create a backup of both files and the database. This matters even more if the site already runs many third-party extensions, caching, JavaScript optimization, or a custom template. Then create a test menu item that is not part of the main navigation but is available to the administrator via a direct link. That gives you a safe place to test the schedule before publishing it.

Template, Module Positions, and Menus

Joomla displays modules in template positions, while component output is usually tied to a menu item. So decide in advance where the schedule will live:

• A dedicated schedule page - best for a full program with filters, details, and links.
• A module in a template position - useful for a compact "upcoming classes" block or for embedding part of the schedule on a landing page.
• A hidden menu item - useful if you need correct routing and separate detail pages, but do not want the item to appear in the main menu.

If a module does not appear, the first thing to check is usually not the extension itself, but the template position, module publishing status, access level, and menu assignment tab. Those core Joomla rules often solve the problem faster than hunting for a bug in the component.

Installation and the First Post-Install Check

The standard Joomla installation path goes through the admin panel and a ZIP package upload. The interface wording may vary slightly between Joomla branches, but the process is the same: open the extension installer, select the archive, and wait for the success message. If the package includes multiple parts, Joomla will install them as a bundled set: the component, the module, and any extra elements included in the package.

A Safe Installation Order

1. Open the Joomla admin panel using an account with permission to install extensions.
2. Go to the extension installer and use the package upload tab, usually labeled Upload Package File.
3. Select the extension ZIP file obtained from the official source.
4. Wait for the success message and do not refresh the page during the process.
5. Check whether JUX Timetable items appear in the lists of components and modules.
6. If the package includes a module, make sure it is published only on the test page or left unpublished for now.

After installation, do not rush to fill in every field and publish the schedule on the homepage. First create a minimal test set: one category, one trainer, one class or event, and one time slot. This acts as a control sample. If it displays correctly, it becomes much easier to tell whether later problems come from the data, filters, or template rather than the installation itself.

How to Confirm the Extension Actually Works

Create a hidden or test menu item for the schedule, save it, and open the public side of the site in a separate window. Check for five signs:

• The page loads without an error and does not redirect to the homepage.
• The test event is visible in the selected schedule view.
• The filters do not hide the only record for no reason.
• The pop-up or detail page opens if you enabled detailed descriptions.
• The mobile view is not empty and does not break the order of classes.

Quick takeaway: installation is only complete after the test event has been verified on the public page, in Joomla menu routing, and in the mobile view - not when the success message appears.

Product Map: Categories, Trainers, Classes, Events, and Rooms

For JUX Timetable to be useful, its data needs more than just filled-in fields - it needs logical relationships. The official materials and forum discussions mention entities such as Organizers, Events, Classes, Trainers, Class Categories, Levels, Schedule, Classroom, and the rooms filter. That points to the right model: first build the entity dictionary, then connect events and classes to time, location, and filters, and only after that publish everything in the schedule.

How to Avoid Getting Lost in Entities

Think of the schedule as a storefront, not a database for the sake of a database. The visitor sees time, class names, filters, and details. The administrator manages several layers:

• Categories divide classes by direction or format: cardio, yoga, lectures, consultations, conference sessions.
• Trainers or speakers matter when visitors choose a session by person, not just by topic.
• Classes or events describe a specific unit in the program: title, description, image, and extra details.
• Rooms or classrooms matter when several sessions run at the same time in different places.
• The schedule ties everything to days, time, display views, and filters.

If you start creating events before defining a consistent category scheme, duplicates will show up within a week: "Yoga", "Morning Yoga", "Yoga Class", and so on. Filters become useless, and the editor will assume the extension "is not showing all classes." Early on, it is better to define a short internal dictionary and agree on who is allowed to create new categories.

How Much Detail to Use

For a small studio, categories, trainers, and time may be enough. A conference usually needs more: track, room, level, session type, and attendance format. For a hybrid program, it helps to separate online and in-person parts from the start, because a review on JED describes exactly that as a real-world use case. But do not create a filter for every field. The more filters you add, the greater the chance that a visitor ends up with an empty result by accident.

A good rule is simple: a filter should exist only if the user genuinely makes decisions based on it. "Trainer," "day," "room," and "category" are usually helpful. An "internal group code" or an "admin note" is better left in the description or hidden entirely.

Schedule Views, Filters, and Pop-Up Details

The official sources emphasize three groups of features that matter most to users: schedule views, filters, and the pop-up detail window. Your public page should be built around them, because they answer three different visitor questions: "When?", "What fits me?", and "What is included in this session?"

Daily, Weekly, and Monthly Views

The daily view works well for a conference, marathon, or one-day event where users need to scan the program from top to bottom. The weekly view is usually a better fit for fitness studios, schools, clubs, and recurring classes. The monthly view is useful when the schedule behaves more like an events calendar, but for dense grids with several sessions per hour, it can become too crowded.

Do not choose a view just because it looks better in the demo. Start with the real number of sessions. If one day contains ten parallel tracks, a weekly grid may feel heavy, and a room filter becomes essential. If there are only a few sessions, the weekly grid can look empty, and a list or compact upcoming-events module may work better.

Filters as Program Navigation

Filters by category, instructor, location, day, and time are confirmed in the JED description. This is not a decorative panel - it is the main way to reduce noise. On a site with many sessions, think through the filter order: start with what visitors choose most often, then add secondary criteria. For example, a studio might use "discipline - trainer - day," while a conference might use "track - room - time."

If a filter suddenly hides sessions you expect to see, do not check only the filter settings. Check the data itself: are the categories published, is the class attached to the wrong category, is a different language active, is cache enabled, is a menu item restriction in place? The product changelog includes fixes related to filters, multilingual behavior, and cache, so if something acts strangely, first confirm that the installed package is up to date.

Pop-Up and Detail Page

A schedule cannot show everything at once. If every cell contains a long description, the schedule stops being a schedule. That is why JUX Timetable uses class details: individual text, images, and pop-up styles. This works well when the visitor first needs to see the time and then open more details: who leads the session, what to bring, who the program is for, and whether there is a registration link or an additional page.

A good detail card answers four questions: what it is, who it is for, where it takes place, and what to do next. Try not to turn the pop-up into an ad block. A short description, one useful image, the presenter's name, the location, and a clear link are usually enough. If the details are extensive, create a dedicated class page and use the pop-up as a quick preview.

Component, Module, and Menu Item: How to Build Navigation Without Chaos

For a Joomla schedule extension, it is especially important to separate three things: where the data lives, where the main page is, and where the short block is displayed. In JUX Timetable, the data lives inside the extension, the main page is usually built through a component menu item, and the module works for displaying the schedule or part of it in a template position. If you mix those roles, the administrator quickly ends up in a situation where one schedule appears in a module, but its details open under a strange URL, while another schedule only appears on certain pages.

A good structure starts with the main menu item. Even if you do not want to show it in the top navigation, create it in a hidden menu. That gives Joomla a stable routing point: the component knows which Itemid to use, and the user gets predictable URLs for details. This is especially useful if the schedule includes pages for classes, events, or trainers.

When to Use a Component Page

A component page is the right choice when the visitor needs the full schedule experience. There you can add an intro, filters, view switching, details, and links from other parts of the site. For a training center, it might be a "Class Schedule" page. For a studio, it could be "Training Schedule." For a conference, it might be "Program."

On that page, the table itself is not enough. Add two or three short sentences above the schedule explaining how to use the filters, what the category colors mean, and where to find details. That is not promotional copy - it is navigation guidance. If a user sees a dense grid and several filters with no context, they may not realize the schedule is interactive.

When to Use a Module

A module works well as a supporting entry point. For example, on a "Yoga" topic page, you can show only upcoming sessions in that category, and on the homepage you can place a short block with today's sessions. But a module should not be the only access point if the schedule is large. Otherwise, visitors cannot comfortably switch views, explore details, or share a link to the full program.

Check the module using Joomla logic: is it published, is the template position selected, is it assigned to the correct menu items, and does the access level match the intended audience? If the module is visible to the administrator but not to guests, the reason may not be JUX Timetable at all, but the Access field. If it appears on one page but not another, the menu assignment tab is usually the first place to look.

How to Avoid Duplicate Schedules

Duplicates usually appear when an editor creates a separate module for every section of the site and starts repeating settings manually. A month later, one module has been updated, another was forgotten, a third is assigned to an old position, and a fourth uses the wrong filter. For a small site, it is usually better to keep one main component output and one or two modules with clearly defined roles.

Name modules clearly: not "Timetable 1," but "Homepage - Upcoming Classes," "Course Page - Online Sessions," or "Sidebar - Weekly Schedule." In the module description or your team's internal instructions, note which filter is enabled and which pages it is assigned to. It is a simple habit, but it can save hours of troubleshooting.

Post-Install Configuration: From a Test Grid to a Working Schedule

The configuration phase works best when done in layers. Start with the data structure, then the output, then the visual styling, then mobile behavior, then languages and cache. That order lowers the risk of wasting time adjusting colors and styles when the real problem is an unpublished category or the wrong menu item.

Data Layer: A Minimal Working Set

Create a set that resembles your future real-world use case but does not overload the admin area:

1. One class or event category.
2. Two trainers or speakers, so you can test person-based filtering.
3. Two rooms or classrooms, if your use case includes locations.
4. Three sessions on different days and one additional session on the same day, so you can test sorting.
5. One detailed description with an image to test the pop-up.

After saving, open the public page and make sure all records are visible without filters. Only then should you enable additional filters and modes. If a record disappears even at this basic stage, the cause is almost always publishing status, access, category, language, date, or the menu item.

Output Layer: Menu Item or Module

The changelog mentions a menu item for the schedule, and the JED listing states that the package includes both a component and a module. In practice, that means two different output scenarios. A component menu item is better for the main schedule page: routing, separate detail pages, and SEO-friendly URLs are more reliable there. A module is the right choice when the schedule or part of it needs to appear in a template position, such as the homepage, a sidebar, or a topic page.

Use a menu item for the main page. Use a module for a short "today's schedule" block. If you use both, do not make them identical. The homepage can offer a compact entry point, while the full page provides filters, views, and details.

Visual Layer: Colors, Background, and Readability

The official description highlights settings for colors, the schedule title, time slots, and the background, including an image used as the schedule background. That can be useful, but it is also easy to overdo. A background image should support the design, not hurt contrast. For a schedule, the readability of times and class titles matters more than decoration.

A practical order is this: choose a neutral background first, then set category color accents, then test contrast, and only after that experiment with an image. If the background image makes the text harder to read, use it only in the header or skip it entirely. People read schedules quickly, often on a phone, and weak contrast immediately reduces usability.

Mobile Layer

The JoomlaUX forum and the changelog show that mobile rendering has been a recurring topic: fixes were issued for empty mobile screens, navigation, class order, and responsive view rendering. So mobile testing is mandatory, even when the desktop page looks fine.

Check more than just the browser width. Test real actions: filtering, moving to the next and previous day, opening details, going back, and verifying that classes appear in time order. If the classes are out of order on mobile, make sure the time format is consistent, the records are published, the cache has been cleared, and the installed version includes the mobile schedule fixes.

Language and Localization Layer

The changelog includes fixes for weekday language and language select in the Schedule module, and the forum includes topics about translating weekday names and frontend strings. For a non-English site, do not edit extension files manually. Use Joomla's built-in language override system instead. That way the changes survive updates and are easier to roll back.

In Joomla, the path usually looks like System - Manage - Language Overrides, or something very close depending on your Joomla branch. Find the needed constant by text, create an override for the site or the admin area, and save it. Then clear the cache and check the public page again.

Practical Example: A Hybrid Course Schedule

Let us use a scenario that closely matches a real JED review: an organization runs a hybrid course with online sessions and in-person meetings. Participants need to see the full program, filter sessions by format, open speaker profiles, and understand where each session takes place.

Goal

The goal is a "Course Schedule" page with a weekly view, filters by format and speaker, session cards, and separate detail pages for each session. On the site homepage, there should be a compact module with upcoming sessions or a link to the full program.

Preparation

Before configuring anything in Joomla, prepare the class list in a spreadsheet outside Joomla. This speeds up data entry and reduces mistakes. The minimum columns are: title, day, start time, end time, format, room or online room link, speaker, category, short description, image, and detail link. If two people are working on the project, let one enter the data and the other verify the public result.

Configuration Steps

1. Create the categories Online and Offline, or use other public-facing labels if those are what your site uses.
2. Add speakers under the trainers section if your package and use case rely on trainers.
3. Create rooms such as "Room A," "Room B," and "Online Room." If the room field is available in your version, use it as a separate filter instead of hiding the location inside the description.
4. Create classes or events with short titles. A title inside the schedule cell should be shorter than the heading on the detail page.
5. For each class, fill in the time, category, speaker, location, and description. Do not leave important fields empty, or the filters may behave unpredictably for the editor.
6. Create a menu item for the full schedule and choose the weekly view if the program repeats by weekday.
7. Enable category, speaker, and location filters if they genuinely help the participant.
8. Configure the pop-up so it includes the session goal, speaker name, format, and a link to details or registration if your workflow includes one.
9. Create a module for the homepage if you need a compact entry point to the schedule, and assign it only to the appropriate menu items.

Expected Result

On the public page, the participant sees a weekly grid, can filter online or in-person sessions, open a session card, and understand where it takes place. The homepage stays clean and avoids an overloaded table - it is better to show a short block with upcoming sessions or a link to the full schedule.

A Common Detail That Gets in the Way

If the same course needs separate schedules for online and offline parts, do not rely on color alone. Use an explicit filter or separate categories. Color helps visually, but a filter helps people act. If the records are not separated in the data, visitors will not be able to quickly hide the format they do not need.

Editorial Workflow: How to Update the Schedule Without Breaking It

After the first launch, a schedule rarely stays unchanged. A trainer calls in sick, a room becomes unavailable, an online link changes, or a new group gets added midweek. That is why JUX Timetable should be introduced not as a one-time setup, but as an ongoing editorial workflow. The clearer that workflow is, the lower the risk that the site shows outdated times or empty session cards.

The One Source of Truth Rule

If your team also maintains the schedule in a spreadsheet, chat thread, or external calendar, assign one source of truth. Otherwise, the editor will end up copying changes manually from multiple places and will eventually make mistakes. For a small site, a simple approach works well: the working spreadsheet is used for coordination, and Joomla is treated as the published source. After updating JUX Timetable, the editor marks that row as published and checks the public page.

Not every staff member should have full access to the component. If Joomla uses multiple user groups, identify the people responsible for the schedule and do not broaden permissions unless there is a real need. Schedule mistakes are visible to visitors immediately: the wrong time or location can ruin someone's visit.

A Mini Checklist Before Publishing a New Week

Before publishing the next batch of classes, the editor should follow the same short routine every time:

1. Confirm that all new classes are published and linked to the correct categories.
2. Make sure trainers, rooms, and levels have not been created as duplicates.
3. Open the schedule with no filters and verify that the full set of records appears.
4. Check every public-facing filter that visitors can use.
5. Open two or three detail cards and verify the text, location, image, and link.
6. Check the mobile view and make sure class order matches the time order.
7. Clear the cache if the site uses caching, then reopen the page in a private browser window.

This checklist looks simple, but it prevents most of the common issues: unpublished records, wrong categories, stale cache, duplicate trainers, and unexpected empty filters.

How to Handle Seasonal and Recurring Programs

If the schedule changes by season, do not build a chaotic archive of old classes inside the same structure. Think through naming: "Spring Course," "Summer Intensive," "Fall Group," or other clear labels. For recurring classes, use a consistent title format so the editor can quickly distinguish a base entry from a temporary replacement.

If your version includes features for copying or reusing records, use them carefully. After copying, always check the date, time, language, category, trainer, and room. The product changelog includes a fix related to Save & copy and date changes on save, so this check matters even more on older installations.

How to Write Class Descriptions

People scan a schedule quickly, and they only open the details when the title catches their attention. So the title inside the schedule cell should stay short, while the pop-up should be specific. Do not use "Workshop Session" in ten different places. Better examples are "Breathing Basics," "Strength Training," "Project Review," or "Application Consultation."

Use the same structure in each class description: goal, who it is for, what to prepare, where it takes place, who leads it, and what to do next. That format helps both the visitor and the editor. If every card is written in a different style, the schedule starts to feel like a collection of random announcements.

How to Verify the Result on the Site

Result checking should be a separate stage, not a quick glance at the page. A schedule can look correct in the admin area and still be frustrating for visitors: a filter hides classes, mobile navigation scrambles the order, the pop-up contains too much text, a link points to the wrong page, or the cache shows old data.

Checking the Public Page

Open the schedule like a regular visitor, ideally in a private browser window. Then follow this path:

• Go to the page from the main menu or via a direct link.
• Switch between schedule views if more than one is available.
• Try each filter one by one and make sure none of them produces an empty result without a valid reason.
• Open a class detail view and verify the text, image, link, location, and trainer name.
• Go back and make sure the user does not lose context.

If the schedule is meant to function as a reference page, it should be understandable without calling the administrator. Class names should be distinct, time formatting should be consistent, and filters should behave predictably.

Checking the Mobile Screen

On a phone, overall beauty matters less than the ability to find a class quickly. Check whether the days are visible, whether times are cut off, whether the pop-up opens, whether the window can be closed, and whether the navigation buttons stay in place. If the grid is too wide, it is usually better to show a compact view, a list, or fewer filters at once.

Checking Cache and Data Refresh

The product changelog includes a fix related to identical data being shown when cache is enabled. So after changing the schedule, check the result in two states: immediately after saving and again after clearing the Joomla cache. If the site uses server-side cache, a CDN, or an optimizer, check those too. Do not conclude that the extension failed to save data until you have ruled out cache.

Checking SEO and Accessibility

A schedule should not be the only source of key information if a search engine or a user with accessibility needs may struggle to read a complex grid. For important events, add clear detail pages, proper headings, text descriptions, location, and time. If you use a pop-up, do not hide the only important information inside it if users still need to find that information easily.

Safe Improvements Without Editing the Extension Core

Any design or behavior changes should be made in a way that an update to JUX Timetable will not wipe them out. In Joomla, that means not editing the component or module files directly, and instead relying on extension settings, template parameters, language overrides, and custom CSS in the template.

Localization Through Language Overrides

If you need to change a weekday label, filter title, or button text, look up the string through Joomla language overrides. That is safer than opening the extension language file and editing it manually. After an update, a manual file edit will almost certainly be lost, while an override remains manageable.

CSS for Cleaner Mobile Behavior

If the schedule is too wide for the template container, you can add a small CSS block to the template's custom stylesheet. First assign your own CSS class to the module or page, for example training-schedule. Then add the code to the location your template uses for custom CSS. This example does not modify JUX Timetable files and applies only inside your custom class:

.training-schedule {
  overflow-x: auto;
}

.training-schedule table {
  min-width: 720px;
}

.training-schedule img {
  max-width: 100%;
  height: auto;
}

Check the result on the test page: the schedule should scroll horizontally only where it truly does not fit, and images inside the detail views should stay within the container. If the design gets worse, remove this block from the custom CSS or remove the class from the module.

When It Is Better Not to Add Code

Do not add JavaScript just to change class order, work around filters, or interfere with the pop-up if the issue can be solved through settings and clean data. Changes like that often break after updates. If you need to change the output structure, first check whether the extension supports template overrides or built-in parameters. Reviews mention the possibility of overriding different views, but before doing technical customization, confirm that in the documentation for your version and test everything on a site copy.

Common JUX Timetable Problems and Troubleshooting

This section is based on the official changelog, public JoomlaUX forum topics, and standard Joomla rules for modules, menus, languages, and cache. Not every problem points to a bug in the extension. In most cases, you need to check the data, menu item, publishing status, cache, or template.

The Schedule Does Not Appear on the Page

Symptom: the page opens, but there is no schedule, or the module does not appear where it should.

Possible causes: the module is unpublished, the selected position does not exist in the current template, the module is not assigned to this menu item, the access level hides the block, the menu item was created for the wrong schedule view, or the data is unpublished.

What to check: module publishing status, template position, menu assignment tab, Public access, and whether a test class exists with no filters applied. If this is a component page, also check the menu item itself and its parameters.

How to fix it: temporarily assign the module to all pages, choose a position you know exists, disable extra filters, and test with one simple sample class. Then bring the restrictions back one by one.

A Filter Hides Some Classes

Symptom: records are visible with no filter, but after selecting a category, trainer, room, or day, some classes disappear.

Possible causes: the record is linked to a different category, the trainer or room field is empty, a different language is enabled, cache is serving an old data set, or the installed package does not include filter-related fixes.

What to check: the class card, category, language, publishing status of related entities, and cache clearing. The product changelog includes fixes for the rooms filter, image display during filtering, and multilingual elements, so also check for updates.

How to fix it: standardize your category dictionary, fill in the required relationships, clear the cache, and test again. If the problem only happens with one specific filter, temporarily disable that filter on the public page and contact documentation or support with a precise reproduction scenario.

The Mobile View Is Empty or Shows Classes in the Wrong Order

Symptom: everything looks fine on desktop, but on a phone the schedule is empty, the next/prev buttons do not work, classes are out of time order, or the link in responsive view is inactive.

Possible causes: a template conflict, an outdated package, JavaScript optimization, inconsistent time formats, an overloaded grid, or an issue that has already been fixed in a newer release.

What to check: whether the extension is up to date, whether the script optimizer is disabled in testing, whether time values are consistent in the data, how mobile navigation behaves, and one simple test day without layered filters.

How to fix it: update the package from the official source, clear the cache, test without minification, reduce the density of the display, and apply CSS only to the page container. If the mobile issue persists, include the URL, screen width, screenshot, and active filter list in your support request.

Weekday Names or Frontend Strings Were Not Translated

Symptom: English weekday names, system labels, or partial translations remain on a localized page.

Possible causes: the string comes from a different language file, the override was created for the admin area instead of the site, the wrong schedule language is selected, the cache was not cleared, or the installed version contains the old weekday language bug.

What to check: the language override scope, the active site language, Schedule module settings, the presence of multilingual elements, and cache clearing.

How to fix it: create the override in the correct scope, do not edit extension files manually, and test the page in a private browser window. If the string cannot be found through search, record its exact text and check the developer documentation.

The Site Still Shows the Old Schedule After Data Changes

Symptom: the class was updated in the admin area, but the public page still shows the old text, old image, or the wrong set of classes.

Possible causes: Joomla cache, page cache, server-side cache, CDN, a caching plugin, or stale browser data. The JUX Timetable changelog also notes a fix related to identical data with cache enabled.

What to check: Joomla cache clearing, template or optimizer cache, a private browser window, another browser, and whether cache is disabled on the test page.

How to fix it: clear cache after large schedule updates, test the page without optimization, and add one rule to the editorial process: after editing classes, always reopen the public page.

The Detail Page or Link Goes to the Wrong Place

Symptom: the pop-up works, but the details link or register link displays incorrectly, routes to the wrong path, or breaks the SEF URL.

Possible causes: there is no correct component menu item, the link was entered into the wrong field, SEF settings are enabled without route testing, or the installed version had an issue with the register link or router link.

What to check: the hidden menu item, the link fields inside the event, behavior with SEF disabled during testing, and changelog notes related to the register link and router link.

How to fix it: create a stable menu item for the schedule, test external links separately, update the package if the issue is confirmed, and do not edit router files manually.

When JUX Timetable Is the Right Choice

JUX Timetable is a good fit if you need a clear visual schedule grid for Joomla: classes, events, trainers, rooms, filters, details, and multiple viewing modes. The product is especially useful when visitors need to choose not just a single date, but the full context of the program: day, time, category, location, and instructor.

Before publishing, run through a short final check: make sure you have a backup, a test menu item exists, the data is split into clear categories, filters do not hide records, the mobile view is readable, language strings are translated through overrides, cache is cleared after edits, and class details actually help the visitor make a decision. If all of that is in place, you can download JUX Timetable and test the extension on a site copy or test page.

If your project needs payments, attendee registration, external calendar sync, or a complex booking system, do not try to force all of that through schedule settings alone. Choose a tool built for the main task, and use JUX Timetable for the scenario where it is strongest: a clear, filterable, visually tidy schedule on a Joomla site.