Overview
RCA J2C Downloadable Files Sync is the Pro system plugin that stops your J2Commerce downloadable products from lying about which ZIP file they serve. You ship versioned builds into free and pro folder trees under your attachment root; the plugin maps J2Commerce product IDs to those folders, points the primary product file at the newest ZIP, and can register older GPL builds plus an optional CHANGELOG. Manual Add Files paths go stale after every release unless something syncs them. This plugin is that sync.
What problem am I actually solving?
J2Commerce stores downloadable products as rows in the database with a path to a file on disk. When you use Add Files and pick a filename, that path is static until someone edits it again. If your release process drops a new package_version.zip into a folder every time you ship, the catalog still points at yesterday’s filename until you fix it by hand. Sync reads the folder, finds the highest version, updates the lowest-id managed product file row so index zero stays current, and optionally attaches prior ZIPs so shoppers can still reach older GPL builds without you clicking through product files for an hour.
What you get in the package
The install package is plg_system_rca_j2c_downfilessync (element rca_j2c_downfilessync), current retail version 1.0.2. You get plugin options on the Settings tab including the Product folder map, a Sync panel tab with Sync Now for Super Users, optional scheduled sync through com_ajax when you set a Cron key, and a frontend shortcode to list version filenames for transparency on articles or product descriptions. Updates arrive through the Pro private feed at https://recreatinganew.com after purchase.
What this is not
This is not J2Commerce itself, not your CDN, and not RCA J2C Direct Download. Direct Download is the separate free content-plugin path for article-level free grabs with the rcadownload shortcode. Downloadable Files Sync keeps J2Commerce product file rows aligned with files you already placed on disk under the J2Commerce attachment folder path. It does not build ZIPs, pull from RCA update feeds, or upload releases for you.
Who should use this?
Use it if you sell or distribute extensions through J2Commerce, store package_version.zip files under free or pro package folders, and you are tired of editing product files every time you bump a version. Use it if you want prior versions listed for transparency without hand-maintaining a dozen product file rows after each build. If you sell one static PDF that never changes name, you can skip this plugin and go enjoy something that is not folder hygiene.
Who should skip it?
Skip it if you do not use J2Commerce downloadable products at all. Skip it if you are not willing to maintain a Product folder map when product IDs or folder names change, because wrong map lines sync garbage or nothing useful and the plugin will not guess your catalog for you.
How does it fit with other RCA J2Commerce tools?
RCA J2C Direct Download reads J2Commerce product files after sync keeps those files current, so article-level free download buttons stay honest when index zero points at the latest ZIP. RCA extension releases that land in L2 download folders pair naturally with this map when your J2Commerce product IDs match the SKUs you sell.
Where should I read next?
Use Quick start when you want the shortest path to one successful sync on a single product. Use Configuration when you are ready to understand every map field without guessing. Use Integrations when you run Direct Download or a full RCA storefront stack. Use Troubleshooting when Sync Now talks back and you need a structured first response instead of panic.