Troubleshooting
When Sync misbehaves, the fix is usually SKU mismatch, map syntax, attachment root path, retail ignored versus unmapped confusion, or you forgot to run Sync after copying files. Work through these sections in order before you email support with a vague subject line.
Sync Now shows no clear result — what should I see?
Version 1.2.4 and newer show a blue notice while sync runs, then green, yellow, or red summary with counts. If the button does nothing, confirm you are a Super User, the plugin is enabled, and browser dev tools show a successful JSON response from com_ajax. Expand the JSON log under the button for per-product messages.
Too many files on the J2Commerce Files tab — why?
Sync registers every versioned ZIP at the package folder root up to keep_prior. ZIPs in archive/ are not registered. Fix wrong tier paths (obsolete free/ when the product should use pro/), move retired ZIPs to archive/, leave one current ZIP at root, then run Sync Now and read the success notice.
Sync Now says no ZIP found — what now?
Confirm J2Commerce Attachment folder path is the parent of free and pro, not a single package directory. Confirm Manual map lines are not commented out. Confirm the folder segment matches disk, including free/ versus pro/. Confirm ZIP names are {package}_{version}.zip where package equals the last folder segment. Confirm the ZIP sits in the package folder root, not in archive/.
A sellable folder appears unmapped — what should I fix?
Set the downloadable product’s master variant SKU to the folder basename (for example pkg_rca_feedfactory for pro/pkg_rca_feedfactory/). If the product already has a file path on the Files tab, copy the folder name from that path into the SKU on the General tab instead of guessing. Do not create a separate J2Commerce product for every child updater folder when you only sell the package. Use overrides only when you intentionally deliver a child ZIP through commerce.
A folder appears under Ignored folders — is that an error?
Usually not on RCA retail. Ignored paths are package-suite children, internal-only packages, or other updater-only directories when retail sellable-only is on. If you actually sell that folder as its own product, add a map override or adjust internal-only settings.
RCA J2C DirectDownload or checkout still serves an old file — why?
Confirm Sync ran after the new ZIP landed. Confirm the lowest-id managed row shows the new versioned filename. Clear Joomla cache. Confirm plugin version 1.2.4 or newer so Sync Now status notices and leading-slash normalization behave as documented. Resolve latest on download is a safety net; it does not replace running Sync after releases.
Auto did not pick up my product after I fixed the SKU — why?
Save the J2Commerce product after changing the master SKU so the product-save hook can run sync for that ID. Run Sync Now manually. Confirm the folder tier (free versus pro) matches scan toggles and that the folder contains at least one valid ZIP name. On Linux, confirm the folder basename matches the master SKU text exactly, including capitalization — a lowercase folder with an uppercase SKU in J2Commerce will not resolve even though the names look equivalent.
Cron never seems to run — what should I check?
Confirm Cron key matches the cron_key parameter exactly. Confirm option=com_ajax, plugin=rca_j2c_downfilessync, group=system, format=json. Confirm the cron host can reach your site URL. Compare your crontab to the Sync panel reminder URL character for character.
A map line syncs the wrong product — how did that happen?
Product IDs are numeric catalog IDs, not SKUs. A typo maps revenue to the wrong folder. Fix the line, Save, run Sync Now, and re-check product files for affected products.
Prior versions or CHANGELOG did not appear — why?
keep_prior limits additional ZIP rows. changelog=1 requires CHANGELOG.md in the folder at sync time. Auto maps use plugin defaults when per-line options are omitted.
When should I contact support?
Email