PlugPress

How to Update Loggle

Updating Loggle is safe. Your tracking history is stored separately from the plugin files, so updating never touches your data.

Automatic updates

With an active licence, Loggle behaves like any other plugin.

  1. Go to Dashboard → Updates, or Plugins → Installed Plugins.
  2. When a new version is available, Loggle appears in the list.
  3. Click Update Now.

To check for a new version immediately rather than waiting:

  1. Open Loggle → Settings.
  2. Find the Licence card.
  3. Click Check for updates.

Or from the command line: wp loggle license check-updates

If Loggle never appears in your updates list, your licence is probably not active on this site. See How to Activate Loggle and Your Licence.

Updating manually

You can always update by hand — useful on a staging copy that has no activation, or if your licence has expired.

  1. Download the latest loggle.zip from your Freemius receipt link.
  2. Go to Plugins → Add New → Upload Plugin.
  3. Choose the zip file and click Install Now.
  4. WordPress notices Loggle is already installed and offers to replace it. Click Replace current with uploaded.

You do not need to deactivate or delete the old version first, and doing so is not recommended.

Updating with WP-CLI

wp plugin update loggle when the licence is active, or install the newer zip over the top:

wp plugin install /path/to/loggle.zip --force

What happens to your data

Nothing is lost. Specifically:

  • Your visitors, page views, and payments stay exactly as they were.
  • Your settings are preserved.
  • Your licence stays activated.
  • Tracking continues without a gap.

Some updates improve the database structure. That happens automatically the first time you open an admin page after updating — you do not need to do anything.

Tip: after any update, load your WordPress admin area once. That is what triggers the database step. Sites that are updated but never visited in wp-admin will not have run it yet.

One-off step for SQLite sites

This applies only if your site stores data in SQLite rather than MySQL, and you used Loggle 1.0.x. Most sites use MySQL and can skip this.

Versions before 1.1.0 had a fault on SQLite: repeat-visit counts and payment counts stopped increasing, and last-click attribution was never recorded. Version 1.1.0 fixes the cause. To correct figures already stored, run once:

wp loggle repair

To preview what it would change without writing anything:

wp loggle repair --dry-run

The command recalculates visit counts, payment counts, and revenue from your own records. It only ever raises a count, never lowers one, so nothing is lost.

Please note: last-click data from before the fix cannot be recovered, because it was never written. The command tells you how many visitors this affects. First-click attribution — the default — was never affected, and neither was your revenue total.

Before a major update

Good practice for any plugin:

  • Take a backup, or confirm your host has a recent one.
  • Update on a staging site first if you have one.
  • Read the changelog for anything marked as changed behaviour.

Common problems

Loggle does not appear in my updates list

Automatic updates need an active licence on that site. Check Settings → Licence shows an active status. If your licence has expired or is used elsewhere, update manually instead.

“Update failed: destination folder already exists”

An earlier update was interrupted. Delete the leftover loggle folder inside wp-content/plugins/ using your host’s file manager or FTP, then install again. Your data lives in the database and is unaffected.

My numbers changed slightly after updating to 1.1.0

Expected, and correct. From 1.1.0 date ranges are counted in whole calendar days rather than rolling hours, so “last 7 days” now means seven complete days. Totals may read a little differently. Nothing was lost.

The site broke after updating

Almost always a PHP version that is too old. Loggle needs PHP 8.1 or later — check Tools → Site Health. If you cannot reach wp-admin, rename the loggle folder via FTP to deactivate it, then fix PHP and rename it back.

Frequently asked questions

Will updating reset my settings?

No. Settings are stored in the database and survive updates, and survive deactivation too.

Can I go back to an older version?

Yes — install the older zip over the top. Be careful downgrading across a version that changed the database structure, and take a backup first.

Can I still update after my licence expires?

Manually, yes, using any zip you already have. Automatic updates and new downloads need a current licence.

Next steps

After updating, run through How to Test Whether Loggle Is Working to confirm everything still records.