Licensing & Activation (Freemius, Free vs Pro Gating)

1. How Licensing Works in Davix (From Your Code & Docs) #

Your documentation and code snippets clearly show that Pro-versus-Free is handled via Freemius:

• You use the my_fs() helper.
• Pro-only features check my_fs()->can_use_premium_code() before:
  • Registering settings fields.
  • Saving certain options.
  • Exposing REST endpoints (e.g. Telegram human endpoints).
  • Rendering Pro-only UI controls.

If can_use_premium_code() is false:

• The Pro parts of the code return early or skip execution.
• Pro-only fields are sanitized out or reset to defaults by your sanitize_options() logic.

2. Where Licensing Info Appears in the UI #

Your plugin uses a typical Davix/Freemius pattern:

• A dedicated About / Licensing or Account section where users see:
  • Current license state (Free vs Pro).
  • Site activation status.
  • Links to manage the license via Freemius (upgrade, cancel, etc.).

The exact title of that page is what you use in the plugin, but the docs clearly state that:

• Pro gating uses Freemius.
• The plugin respects license state at runtime.

image IMAGE PLACEHOLDER: Screenshot of a “Davix AI Engine → About / Licensing” admin page showing license status (Free / Pro), activation email, and a button like “Manage license / Upgrade”. IMAGE image

3. What Happens When There Is No Pro License #

From the Pro gating rules documented:

• If Freemius indicates the site is Free:
  • AI Writer module (aiWriter.php) returns early (no sidebar, no submenu).
  • Telegram human handoff REST endpoints reject requests with HTTP 403.
  • Comment & review auto-reply logic is disabled.
  • Forms Pro fields (Forms AI Pro, auto-email template fields, etc.) are ignored at save time and not used in front-end logic.
  • Human color fields and other Pro-only theming fields are cleared/ignored in sanitize_options().

In other words:

• The plugin readme’s feature table matches exactly what the code enforces via my_fs()->can_use_premium_code().

4. What Your Docs Should Tell Users About Licensing #

On your About/Licensing documentation page, describe:

• Where to see license status in the admin (the About or Account page).
• That Free sites:
  • Can use Chatbot, LLM Index, basic Forms, Debug Logs.
• That Pro sites:
  • Unlock Telegram live chat, Forms AI Pro, Comment/Review auto-replies, AI Writer, advanced theming fields, and Pro-only debug channels/endpoints.
• That changing license state may require:
  • Refreshing the admin.
  • Clearing caches so Pro JS (e.g., AI Writer) assets load properly after activation (your docs already warn about clearing editor/browser cache for AI Writer).