Troubleshooting

When Sync misbehaves, the fix is usually naming, map syntax, attachment root path, 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 says no ZIP found — what now?

Confirm J2Commerce Attachment folder path is the parent of free and pro, not a single package directory. Confirm the map line is not commented out with hash or semicolon. 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 you copied the ZIP into the package folder itself, not into an archive subfolder the scanner ignores.

Direct Download or checkout still serves an old file — why?

Confirm Sync ran after the new ZIP landed. In J2Commerce product files, confirm the lowest-id managed row shows the new versioned filename. Clear Joomla cache and any storefront cache. If you upgraded from an older plugin version, confirm you are on 1.0.2 or newer so legacy leading-slash paths are managed and normalized. Resolve latest on download is a safety net; it does not replace running Sync after releases.

Cron never seems to run — what should I check?

Confirm Cron key in plugin options exactly matches the cron_key parameter in the URL you call. Confirm the URL uses option=com_ajax, plugin=rca_j2c_downfilessync, group=system, and format=json. Confirm the server running cron can reach the site URL you use, including HTTPS certificates and redirects. Read the Sync panel reminder URL when a key is set and compare character for character to your crontab entry.

A map line syncs the wrong product — how did that happen?

Product IDs are numeric catalog IDs, not SKUs, not aliases, unless your own notes say otherwise. A typo maps revenue to the wrong folder while looking almost right. Fix the line, Save, run Sync Now, and re-check product files for both the wrong and right products if you already shipped a bad sync.

Prior versions or CHANGELOG did not appear — why?

keep_prior only registers additional ZIP rows up to your limit; older files beyond the limit drop off by design. changelog=1 requires CHANGELOG.md to exist in the package folder at sync time. Missing optional fields default to plugin defaults described in Configuration.

When should I contact support?

Email This email address is being protected from spambots. You need JavaScript enabled to view it. when you captured Joomla version, J2Commerce version, plugin version 1.0.2 or newer, one example map line, and the exact Sync panel or log message. That package saves everyone a round trip of guessing.