Integrations

Downloadable Files Sync is one layer in a J2Commerce stack. It does not replace commerce, content download plugins, or release pipelines; it keeps product file rows aligned with the folders those other pieces assume are truthful.

How does this work with J2Commerce core?

J2Commerce owns products, orders, and downloadable entitlements. Sync reads the attachment folder path from J2Commerce configuration and updates product file rows for mapped product IDs only. Unmapped products are untouched, which is good until you forget to map a new SKU and wonder why only that product is stale.

How does this work with RCA J2C Direct Download?

Direct Download is the free system for article-level free downloads using the rcadownload shortcode. It reads J2Commerce product files after those rows exist. When Sync keeps index zero on the primary managed row pointed at the latest ZIP, Direct Download buttons that reference the same product stay aligned with your L2 folder releases. Direct Download does not scan folders; Sync does.

How does this fit an RCA release workflow?

RCA ships versioned ZIPs into free or pro download trees on the server. When your J2Commerce product IDs match the catalog you sell, the Product folder map connects each SKU to its package folder. After GinA or your build pipeline copies a new ZIP to L2, Sync Now or cron updates the catalog without hand-editing Add Files. The plugin does not pull from update feeds or build packages; it only reads what is already on disk.

What about optional cron and external automation?

When you set Cron key, any scheduler that can HTTP GET your site can trigger the same sync logic as Sync Now, which helps when releases land from CI and nobody is logged into admin at 2 a.m. Protect the key like an API token. com_ajax must be reachable from the host running cron; firewall rules that block loopback or outbound HTTP to your own domain break scheduled sync in exciting ways.

What integrations are explicitly out of scope?

Sync does not configure Stripe, OS Services Booking, Storefront display modules, or Conditional Products rules. It does not upload to remote storage or rewrite CDN URLs. If your attachment root is on shared storage, you still copy ZIPs there yourself before sync runs.