ZOVANTA SOFTWARE / KNOWLEDGEBASE

Forovanta starter 1.0.0-beta.157n • edition-specific source guide

Licensed add-on and style updates

Current inspected core:157n

Use Admin → Add-ons → Updates / Licensed updates, as named in your edition. Both editions now have check/download/review/install paths. Earlier156x wire-contract defects and157j beta-ordering defects are historical findings, not instructions to change vendor scopes or waive package requirements.

  1. Verify the publisher's identity/fingerprint through an independent authenticated channel. Approve the exact HTTPS endpoint and signing key. A package descriptor is only a suggestion; it cannot approve itself.
  2. Check the desired channel. Stable is the default; beta is explicit opt-in.
  3. Review version, changelog, release ID, signed minimum core, bytes and SHA256.
  4. Download and verify into private staging. This does not install the release.
  5. Explicitly install through the normal package review/backup/compatibility gates, or discard the staged release without changing installed files.

Scope, address and requirement rules

Add-on wire scope is the bare package key; theme scope is theme:key. The LMP endpoint may be a route with a non-secret query, such as addon-page.php?addon=license-manager-pro&view=lmp-updates. Userinfo, fragments, HTTP and credential-bearing query names are refused. Credentials belong in the Authorization header, never the URL. A refused licensed request must not retry keyless. Premium at zero price stays Premium.

157l and later include strict prerelease/build ordering and signed minimum-core enforcement at check, before download and at apply. An explicit requirement such as >=1.0.0-beta.456j is not satisfied by157n. The deliberate legacy unqualified >=1.0.0 policy is a separate compatibility rule, not permission to ignore qualified minima.

The native License Manager Pro beta17 remains a private Premium preview with host/provider acceptance still required. Its earlier157j vendor/customer fixtures demonstrated comparator defects; repeat the complete native journey against your actual corrected core before treating the combination as production-certified. The public SDK does not replace native installation/trust/compatibility decisions.

Publisher trust · LMP release vault

We suggest Panelica for managing your hosting environment.