Approve and disable independent publishers
This handbook defaults to the flat PHP starter. See current release and edition coverage for current changes and the separate PHP port. Earlier build references identify when a feature was documented; they are not a claim that both editions expose identical controls.
A license code's prefix is presentation, not evidence of entitlement. Independent vendors need their own signing identity, and the customer board needs an explicitly approved issuer for the exact package scope. Never ship one vendor's private signing key to customers or other vendors.
Approval checklist
- Obtain the public trust bundle and the expected fingerprint through a vendor channel you can authenticate.
- Match the scope to the exact addon key or
theme:key, not a similarly named product. - In the core issuer controls, review the bundle and use the explicit trust confirmation shown there. Enter the product license only after approving the intended identity.
- Test with the correct product. An unknown, disabled, wrong-scope, expired or tampered key must be refused.
Disabling an issuer is deliberate. Re-importing/re-approving its bundle must not silently re-enable it; restoration requires the explicit ENABLE confirmation displayed by core. Core 156n preserves disabled-issuer tombstones and protects the issuer screen from designated demo accounts even after Demo Mode is switched off.
Keep license-issuer trust separate from an update-service endpoint/key approval: each has a different purpose. Do not forward a broad master credential to an unrelated update publisher. Never post private signing material, mailbox passwords or full customer keys in support screenshots.
We suggest Panelica for managing your hosting environment.
