LAUNCH DEAL — LIMITED Das Nest Lifetime 499 € 149 € Get the deal →
KakapoWP KakapoWP
Log in Get Lifetime
Help Center/Getting started/Installing an update

Installing an update

Applies to: All plugins· 5 min read

New versions come via kakapowp.com and appear in WordPress like any other plugin update. An update can only be installed with one click if there is a valid license; you can always upload a new version by hand.

How an update arrives

  • All eight plugins carry “Update URI: https://www.kakapowp.com/” in their header. WordPress therefore does not ask wordpress.org but asks kakapowp.com through the plugin — with the license key, the address of the website and the installed version.
  • The plugin remembers the answer for six hours; if no usable answer came back, it asks again after an hour. “Check again” under Dashboard → Updates asks again right away.
  • If there is a newer version, it appears in the plugin list and under Dashboard → Updates, with a description and the changes in its details.
  • The server only hands out the package with a valid license. Without one, WordPress does show the new version, but offers no automatic update.
  • A deactivated plugin of the suite is reported too, as long as another one is active. The package only comes with it, however, if the key of the suite’s first-loaded active plugin also covers the deactivated one, for example with a bundle.

Securing the way back first

Kakapo Backup can automatically create a backup immediately before every plugin, theme or core update. The switch for it is off out of the box. If Kakapo Backup is dormant for lack of a valid license, it creates no backup — the update still runs, just without a way back.

  1. Open Kakapo Backup and choose “Update rollback” on the left in the “Action” (in German: „Aktion“) group.
  2. Flip the “Auto snapshot before updates” switch.
  3. Update the plugin in the plugin list or under Dashboard → Updates. Without a valid license, upload the ZIP archive instead via Plugins → Add New → Upload Plugin and confirm that the existing version is replaced.
  4. Open the plugin page once afterwards — on the first visit in the admin area the plugins bring their data up to date.
  5. Check under “System” → “Guide” whether the expected version number is shown there.

What happens automatically when the files are swapped

  • The addresses of admin.css and admin.js carry the timestamp of the respective file. After an update the browser loads the new files instead of the old ones from its cache.
  • Analytics checks its stored schema version on every visit in the admin area and, if it differs, adds the missing tables and columns.
  • Consent remembers the installed version and, on the first page view after an update, adds an internal cut-off date once.
  • Backup makes sure that its hourly profile cycle is scheduled again even without another activation.
  • On the next visit in the admin area, Roles adds a missing or outdated table for the change log.
  • Media compares its stored version on every request and, after an update, fills in missing settings with their default values. Findings on the images stay in place; if they come from an older set of rules, the next batch run checks them again.
A pure file update does not call the activation routine. That is precisely why the plugins handle such follow-up work themselves: Analytics, Backup and Roles on the next visit in the admin area, Consent and Media as early as the next page view of any kind.

If the snapshot is still running

If “Auto snapshot before updates” is active and the backup is not finished in time, WordPress cancels the update and states the reason. The update was then not carried out; try again in a few minutes or switch the automatic snapshot off. After a completed snapshot a five-minute lock applies, so that not every further update in the same pass creates another backup.

Was this article helpful?
← Back
System requirements