These answers match the user guide and product summary for version 1.0.7. If your installed version is older, upgrade first, then re-read Configuration for toggles that did not exist on your build.
No. J2Commerce delivers downloadable files after purchase through orders and customer account views. Even a zero-dollar downloadable product normally goes through cart and checkout. RCA J2C Direct Download adds article-level DOWNLOAD NOW for qualifying free products only.
J2Commerce continues to use J2Store-compatible helper paths, table names, and shortcode tags on many installs. The plugin calls the same APIs J2Commerce documents for extensions. On newer sites you may use j2commerce instead of j2store for cart shortcodes. Direct download always uses {rcadownload} from this plugin.
No. The server rejects any product whose price is not exactly zero. Use J2Commerce cart and checkout for paid downloadables.
Yes, when Allow Guest Downloads is Yes in plugin options. Downloads are tracked in the RCA ledger when tracking is enabled. Guests do not receive automatic J2Commerce orders with invented emails.
The plugin may create a completed free J2Commerce order in the background so the download appears in normal J2Commerce order history. Guests still use ledger-only tracking when guest downloads are allowed.
No. Uninstall removes the plugin and the RCA ledger table. Existing J2Commerce orders stay in the database.
Administrators sometimes see diagnostic hints when eligibility fails. Visitors see nothing or a generic denial. Check product type, zero price, published state, attached file, and per-product direct download override.
You can, but you should not for the same product. Pick direct download or checkout for that landing page, not both.
No. Files live where J2Commerce stores product downloads. The plugin resolves paths the same way J2Commerce order download logic expects and streams the file after checks.
Support covers plugin installation, configuration, and eligibility behavior documented in this manual. It does not cover custom template design, unrelated J2Commerce configuration, or server limits on large file downloads.