Black Friday
Skip to documentation content

Security & Privacy

Protect license activation and premium updates

Free booking functionality does not require a license. Pro and commercial themes own their separate license/update relationships; a paid theme is not authority to enable Pro, and copying a database does not establish a valid activation on another site.

Free booking functionality does not require a license. Pro and commercial themes own their separate license/update relationships; a paid theme is not authority to enable Pro, and copying a database does not establish a valid activation on another site.

Keep identities separate

The canonical Free plugin folder is kimorapro-hotel-booking; Pro is hotel-booking-pro. Pro’s commercial license product slug remains hotel-booking, which is not an instruction to rename the Free plugin. Theme products keep their own identifiers and activation state.

Use the intended license server and normal activation/check controls. Current Pro source defaults to the canonical https://www.kimorapro.com origin. Older packages with the same version label can contain different defaults; verify actual delivered bytes before assuming source and installed behavior are identical.

Protect credentials and cloned sites

Restrict license/settings access to authorized operators. Keep keys, activation tokens, installation identities and protected download URLs out of public logs, screenshots, repository content and support attachments. Ask for a private handling route when necessary; never send credentials simply to prove a feature exists.

On a clone or hostname/environment change, inspect activation identity and use the supported rebind/recovery procedure. A copied stored license, cached entitlement or old package URL is not permission to bypass validation. Connection problems, expiry and identity mismatch can have different states; retain the reported reason and timestamps.

Verify an update before installation

The Pro update workflow reauthorizes the package before download and validates expected version, permitted origin, size and SHA-256. Do not bypass those checks or supply an arbitrary replacement URL. A license check and package offer do not prove installation succeeded.

Back up files and database, retain the previous compatible Free/Pro pair, install through the supported replacement path, then read back active versions, schema readiness and representative booking behavior. Code rollback is separate from database restore, privacy recovery and license-seat changes.

Diagnose without weakening gates

Collect redacted plugin/runtime versions, origin pattern, environment, exact error code and UTC time. Check clock/TLS/network conditions and whether the package matches its recorded digest. Do not disable TLS verification, edit entitlement storage or publish a protected download link as a repair.

Real activation, seat release, premium-download access and update delivery require their own authorized environment evidence; source inspection alone establishes none of them. See upgrade and rollback.

Was this article helpful?

Your feedback helps us improve the documentation.