Marketplace — current settings and requirements
Inspected build
Marketplace 1.6.11, package key forovanta-marketplace. Declared core requirement: >=1.0.0-beta.156j. Required core features: resource-price-contract-v1. This is source documentation, not a fresh live-install certification. Preserve the package/data and read its update plan.
Premium: use an authorized package/license and normal core entitlement controls. A zero/absent selling price does not turn the package free.
Settings
The following labels/defaults come from the inspected manifest. The runtime may group or replace these controls with a dedicated screen; save through that screen.
| Control | Initial value | Meaning |
|---|---|---|
| Show add-on / theme / product types | true | Adds the listing-kind filters and badges to the Downloads area. With this off, every listing is treated as a plain download. |
| Publish official listings | true | Publishes the free add-ons this build ships as official Resource Manager listings, and keeps them in sync. |
| Ask for compatibility | true | Shows the free-text compatibility line on listings, e.g. “Forovanta 1.0.0 · manifest v1”. |
| Marketplace categories | "separate" | Keep the Marketplace's own category list, or share the Downloads categories with it. Separate is the default, so a marketplace product never rearranges the board's download taxonomy. Switching modes preserves both sets of assignments. Choices: Separate Marketplace categories, Share the Downloads categories. |
| Allow paid listings | true | Lets creators put a price on a listing. A buyer can only pay through a provider that is both enabled in Admin → Payments and supported for Marketplace purchases there (Admin → Payments → Marketplace purchases); otherwise paid listings stay visible but show as not purchasable. |
| Confirm offline payments manually | true | On for provider-less payments (PayPal.me and similar): the order stays pending and the owner records the payment before the buyer can download. Integrated providers confirm themselves through their webhook. |
Install or update
Use the addon ZIP itself in Admin → Add-ons → Upload → Review → Install/Upgrade; addon.json belongs at its root. Do not upload the complete source/recovery bundle to core Package Manager. Back up database and private files, preserve existing settings/license/enabled state, and do not uninstall as an update step. After upgrading, test the actual member and staff operations, not just the new version label.
Current operating workflow · Shared addon installation
We suggest Panelica for managing your hosting environment.
