Applies to core 0.1.2 and Pro 0.1.0.
Back Up a Consistent Site
Before cleanup, migration, or an update, back up the database and files together. Include WordPress attachment records and metadata, all Media Sentry tables, uploads, and the actual lf-media-quarantine directory. That directory is a sibling of uploads, so an uploads-only backup misses it. Keep a copy of the installed core and Pro packages and record their versions.
Use your normal backup system and verify a restore on staging. Media Sentry exports are reports, not restorable backups. A quarantine log without its file cannot recover an image; a file without the matching site records may require manual recovery.
Allow running scans and cleanup batches to finish before taking a consistent migration snapshot or replacing plugin files. Preserve error evidence when a batch cannot finish. Check live commerce activity before any database rollback.
Update
- Record the installed versions and read the release-specific compatibility notes.
- Back up, then test the compatible core and Pro pair on staging using the supplied release packages.
- Apply the supplied packages through the site's normal plugin update procedure. Keep the free core active when using Pro.
- Check System, run the doctor command if available, and inspect Setup Baseline for stale or failed steps.
- Verify representative pages and product images and confirm existing quarantine entries remain restorable.
Exact Pro license and update-delivery screens are pending launch verification. These instructions do not promise an automatic updater, download account layout, or activation button label.
The product was renamed from Liberty Forge Admin Toolkit. Existing installations retain the legacy plugin directory, lf media WP-CLI namespace, settings, and quarantine name. Do not rename or delete them as an upgrade step, and avoid activating two copies of the core plugin.
Maintenance Expiry
Installed Pro functionality continues after the included year of updates and support expires. Optional manual annual renewal at the same tier price extends maintenance; there is no automatic subscription. Continued functionality does not promise compatibility with all future WordPress, PHP, or third-party changes. See Pricing and Maintenance.
Disable or Remove
Restore needed files first and retain a backup before removing either plugin. Deactivation is not a restore operation. Do not delete quarantine storage, logs, or legacy-named settings as routine housekeeping. Retain the free core when you need its recovery interface. If an update fails, use a compatible backup recovery plan rather than assuming older code can safely read every newer schema.