Updates, backups and removal
Update safely while retaining your event data and designs.
Before updating
Back up the database and plugin files. Use staging first, note the installed version, and record the expected event counts and published layouts. A backup is only useful if you can restore it.
Install an update
With a valid license, use WordPress's normal plugin update workflow when a new release is offered. You can also upload an official ZIP through WordPress's plugin replacement flow.
Do not delete database records or manually change tables to install an update. Afterward, verify the version, license, event counts, layouts and public output.
If the update is not offered immediately
Release discovery can be cached. The beta's licensed updater uses a version cache of up to three hours. Recheck later; if the offer still does not appear, verify license status and outbound connectivity before reporting it.
Customer-portal download and a real beta-to-beta WordPress update were verified. That evidence does not replace testing future releases against your own site.
Recover after a failed update
Use the site's backup/recovery process. Import checkpoints support job recovery but are not a general site rollback. Preserve WordPress salts when restoring an installation that relies on encrypted stored credentials and snapshots.
Deactivation and deletion
Deactivation removes MetaSprout-owned scheduled events and retains imported records/settings. Plugin deletion is not a data-erasure feature. Plan a separate reviewed cleanup if permanently retiring the event data or Media Library files.
Related: Troubleshooting and Beta scope.