Frontend

Most of Downloadable Files Sync is admin-side folder hygiene. The frontend surface is intentionally small: shoppers still download through J2Commerce, and you optionally show version transparency with a shortcode.

What do customers actually experience?

After Sync runs, checkout and My Downloads use the product file rows J2Commerce already exposes. Shoppers do not install the plugin or see the map. They receive whatever filename and path Sync wrote to the primary product file row, plus any additional files you registered for prior versions or CHANGELOG.md.

How do I show version filenames without exposing raw server paths?

Use the prior-versions shortcode in an article or product description. Wrap the numeric J2Commerce product ID with rcafilesversions opening and closing tags the same way you use other content shortcodes. The output lists versioned filenames for transparency; it is not a separate download engine. Purchases and entitlement still go through J2Commerce.

Does this replace article-level free download buttons?

No. RCA J2C Direct Download serves free products from articles with the rcadownload shortcode. Downloadable Files Sync keeps catalog product file rows honest. You can run both when free article grabs and paid or logged-in catalog downloads must point at the same refreshed ZIP tree.

What should I verify on the storefront after sync?

Log in as a test customer or use a safe order flow, download the mapped product once, and confirm the file matches the version you just shipped. Clear Joomla cache and any full-page cache if the filename in admin updated but the storefront still feels sticky. If Resolve latest on download is enabled, it is still worth confirming behavior with a normal sync-first workflow.

What frontend caching mistakes show up often?

Admins see the new ZIP in J2Commerce product files while anonymous visitors still hit an old cached product page description. Fix cache, then re-test. The shortcode output also respects whatever caching wraps your articles, so bust cache after large map changes if your site aggressively caches content.