Ambikly 0.0.11 and Ambikly Pro 0.0.1 are current. Versions follow major.minor.patch, the schema migrates itself on update, and every line below describes something that shipped.
| Plugin | Version | Requires | Tested up to | License |
|---|---|---|---|---|
| Ambikly | 0.0.11 | WordPress 5.4+, PHP 7.4+ | WordPress 6.8 | GPLv3+ |
| Ambikly Pro | 0.0.1 | Ambikly (free core) | WordPress 6.7 | GPLv3+ |
Ambikly → Tools → System status reports the PHP, WordPress and MySQL versions and the multisite flag alongside these, so one copy of that screen carries the whole picture.
Versions follow major.minor.patch. A patch release fixes bugs and never changes the schema, hooks or REST responses. A minor release may add tables, columns, routes or hooks — always with an automatic migration — and may deprecate a hook while keeping it working. A major release is the only place a hook, template or REST contract is removed, and the release notes list every one.
Updates appear on your Plugins screen like any WordPress plugin. Database changes run automatically through versioned migrations on the next page load.
With an active license key, Pro updates appear on the same Plugins screen. The key is re-checked once a day; an expired key stops updates but never stops the store.
Add-ons ship inside Pro and update with it. Each one carries its own version so it can migrate its own tables when needed.
Ambikly → Tools → System status shows plugin and database versions, and flags any missing table.
Migrations are one-way. Take a database backup, or apply the update on a staging copy first — a staging domain counts as its own activation and can be deactivated afterwards.
Pro checks the core version on load and waits if it is behind. Updating in this order means add-ons never run against a schema they do not expect.
Confirm both versions, that the schema version matches, and that no table is flagged missing. This is the report to paste if anything looks wrong.
Use an offline payment method, then refund it. Checkout, emails, invoice and the webhook queue all run in that one order.
Because we number honestly. The engine is complete and takes real orders, but the public API surface is still being finalized; 1.0 will mark the point where hook and REST contracts are frozen. Pre-1.0 releases already ship with versioned, automatic migrations, so upgrading is never a manual step.
Only through migrations that run once, on the first page load after the update, inside the version check. Each migration is recorded, so a store that skips several releases applies them in order. System Status shows the schema version alongside the plugin version.
Release notes call out any template whose markup changed and any hook whose arguments changed. Overrides in your theme’s ambikly/ folder are never overwritten, because they live in your theme, not in the plugin.
The free core first — Pro declares it as a requirement and checks its version on load. If Pro is updated first it waits, shows a notice and activates its add-ons once the core catches up.
This page is the record. License holders also receive an email for releases that change how license data is used, as the Privacy Policy describes; we do not send marketing mail on every release.
The free core installs in a minute and migrates itself from any earlier version.