Update the pair and resume a schema upgrade
Update Free and Pro in order, confirm the result, and resume a paused database upgrade without losing its recorded progress.
For Free 1.2.7 and Pro 1.2.7. Check the download page for available versions and requirements. Verify representative workflows on staging before use.
On this page
WordPress → Plugins; Logged.ai → Settings → Schema upgrade when offered
Update Free first, then the compatible Pro ZIP. If a schema upgrade is pending, follow its saved phase; uninstalling is not a recovery method.
- Keep a current backup of the database, plugin files and separately configured private keys/storage. Keep the previous compatible ZIPs available.
- Test on staging. This guide covers Free 1.2.7 and Pro 1.2.7, requiring WordPress 6.7+ and PHP 8.0+ with the supported MySQL/MariaDB connection. Pro requires Free 1.2.7 or later with edition API 2. Check the download page for versions currently available.
- Update Free first, then the matching Pro ZIP if you use Pro. Keep Free active. Do not uninstall to update.
- Open Logged.ai and read any compatibility or schema message. If Schema upgrade is offered, inspect its status and choose Run next upgrade phase.
- Continue from the recorded phase until complete. Each submission advances one resumable phase; scheduled work may also resume it when WordPress cron runs.
- Check Settings → System status, saved configuration and one harmless representative workflow on staging. Confirm an expected new record, rather than relying on successful activation alone.
The database structure the installed code expects. A plugin-file update and a database-structure update are related, but they are not the same operation.
Updating to 1.2.7: first confirm that the release is available from the download page and your account. Back up and test the compatible pair on staging. In WordPress, choose Plugins → Add New Plugin → Upload Plugin → Replace current with uploaded. Replace Free first, then Pro in a separate upload; keep Free active and do not uninstall either plugin. Free-only sites replace only Free. An update offer is separate from a successful installation and must pass the usual compatibility, entitlement and archive checks.
| What you see | Meaning | Next step |
|---|---|---|
| Another schema upgrade is running | A lock protects an upgrade already in progress. | Wait and retry later; do not bypass or delete the lock. |
| A phase did not finish | The saved checkpoint identifies where work stopped. | Preserve the exact code and retry from Schema upgrade after resolving the reported cause. |
| Retry could not be scheduled | Automatic continuation was not scheduled. | Return to Schema upgrade and run the next phase manually with the required authority. |
| State unavailable or invalid | Progress cannot be safely read or verified. | Preserve the message and contact support. Do not reset checkpoints or delete tables. |
While an incompatible phase is pending, capture and background work needing that schema may pause; compatible request policies can continue. Missed activity cannot be reconstructed later.
Replacing plugin files does not undo database changes. Recovery needs code compatible with the current data; coordinate any restore with the site owner and current customer activity.
Free is available from Downloads (Release notes); Pro account downloads provide the compatible private package. Replacing compatible ZIPs preserves an existing local activation. A first-time Pro installation still needs licence activation to unlock new work.
When upgrading a Pro installation initialized before 0.1.8, local access is retained on its current canonical site and environment. It does not grant paid updates or reserve a licence slot. Moving the site, removing its saved connection, successfully completing the plugin’s Release licence slot action or uninstalling Pro can require activation again. Keep the previous pair and a current backup; replace files without uninstalling. Previously accepted purchase terms are not rewritten.
For the in-plugin route, follow Activate Pro and manage updates. It uses WordPress HTTPS and checks private temporary storage, PHP ZIP and WordPress file access before an update. An unavailable connection does not turn uninstalling into a safe update method.
These instructions describe Free 1.2.7 with Pro 1.2.7. Scoped checks do not certify every host or extension. Read the package notes and test representative workflows on staging before updating production.
After the one-time manual bridge
An offered Pro update must identify a compatible installed Free version. The private updater must also accept the compatibility profile, supported schema, commercial entitlement and offered archive. Check the available release and its package notes rather than assuming that documentation implies a live offer. Background automatic installation remains disabled; verify the result of an explicit update before retrying.
Update authority is checked before WordPress’s ordinary deactivation. A later installation failure can still leave Pro inactive even when WordPress restores its previous files. Read the error, confirm a compatible pair, then reactivate Pro from Plugins if instructed. No custom automatic reactivation is performed.
This guide covers Logged.ai Free 1.2.7 and Pro 1.2.7. Check available versions and package requirements, and verify representative workflows on staging before updating your main site.
Get help with your next step.