Frontend

Frontend behavior is whatever your template positions, menu assignments, and module parameters combine to produce. Jukebox does not inject a full second site; it renders HTML5 players where you publish modules.

What visitors see per module

Main player

Visitors see the primary library or sticky bar UI for the tracks you configured. Sticky behavior keeps the control available while they navigate menu items you included in assignment. They interact with Play and track selection using HTML5 audio, not Flash.

Playlist

Visitors see an ordered list tied to subform rows. Order on screen matches the order you saved in the module unless your template CSS changes visual stacking. Empty rows you left in the subform should not appear if you saved cleanly; if they do, reopen the module and remove blank rows.

Grid

Visitors see multiple play controls suited to archive browsing. Density depends on template width and your row count. Test small screens before you send traffic from email campaigns.

Single item

Visitors see one compact control, optionally beside a link you added for shop or download. This module is for tight spaces, not for whole-library browsing.

Access levels and guests

Guests only hear audio when module Access includes Public or Guest and Media Manager files are reachable without a login wall. Registered-only modules show nothing useful to guests; that is correct behavior, not a bug.

Autoplay and mobile taps

Design every layout assuming the visitor must click or tap Play once. iOS and many mobile browsers block autoplay with sound. Do not hide the Play control behind low-contrast styling.

HTTPS and mixed content

If the page loads over HTTPS, audio URLs must also be HTTPS. Mixed content fails quietly in some browsers and loudly in the console in others. Fix site configuration and media URLs before you blame skin colors.

Cache and stale renders

Page cache and Joomla cache can show an old empty module after you just saved tracks. Clear cache when frontend output does not match what you see in admin immediately after save.

Template overrides

Default layouts live in each module’s tmpl folder in the extension. Copy overrides into your template’s html folder only when you accept maintenance during upgrades. Prefer parameter skin colors and custom.css first.