Changelog

What changed in each release — the honest version, same as we write it for the plugin.

1.0.6

  • New in Pro: Excluded countries, on the Privacy tab. Leave visitors from chosen countries out of your statistics. It hides them from your reports only — it does not block anyone from your site or stop them buying, and WooCommerce orders from those countries are still recorded.
  • New: the plugin now honours Global Privacy Control as well as Do Not Track. Visitors whose browser sends either signal are not tracked. Both are covered by one setting, “Browser privacy signals” on the Privacy tab, which is on by default. If you had switched Do Not Track off, Global Privacy Control is off too.
  • New: “Record country only” on the Geography tab. Each new visit keeps its country but not its town, region, postcode or map position. A “Clear stored city data” button removes that detail from visits already recorded.
  • Fixed: the desktop / mobile / tablet split in the email report, the Overview and the Devices report could show 0% or come up short for date ranges reaching back further than your data retention period. It now adds up to the views total for any range.
  • Fixed: on sites behind Cloudflare with location detection on Automatic and no location database downloaded, the plugin said visitor countries were not being recorded and hid the Geography report, although countries were being recorded from Cloudflare.
  • The warning about WordPress’s scheduler being switched off (DISABLE_WP_CRON) now appears only when scheduled tasks are actually running late, and is much shorter. It used to appear straight after installing on hosts that run their own scheduler.
  • The warning about the weekly data clean-up now appears only when the clean-up is failing, not after a site has simply had no visitors for a while. Closing it now keeps it closed.
  • The erase-by-IP and erase-by-UUID tools now explain that report totals from more than a week ago may still include the erased visits.
  • Clearer privacy wording: the suggested privacy-policy text now describes location accurately and only mentions browser privacy signals when your site honours them; the consent setting no longer calls the visitor hash “no personal data”; and the visitor cookie is described to cookie-banner plugins as a random ID that recognises a returning visitor.

1.0.5

  • Fixed: the returning-visitor cookie could be set before a visitor had given consent, and on sites where the cookie option was switched off. It is now set only after a visitor accepts statistics cookies, and is removed if they later withdraw consent. Visits are still counted without it, as before.
  • Fixed: on quieter sites, the daily totals could occasionally miss a day. Any days already missed are filled in automatically over the next few days.
  • Developers: the greenorb_statistics_idle_grace_seconds filter now takes effect.

1.0.4 — Pro only

The free plugin is unchanged at 1.0.3.

Install this one by hand. It repairs the updater itself, and an update always runs on the version being replaced — so pressing Update on 1.0.3 can still fail with the old error. Download the ZIP from your customer portal and install it through Plugins → Add New → Upload Plugin. WordPress will offer Replace current with uploaded — take it. Your settings, licence and statistics are kept, and updates work normally from this version onward.

  • Fixed: pressing Update could fail with “Update failed: Forbidden”. The download link was prepared hours before you asked for it, and had usually expired by the time you did. It is now fetched at the moment you update — which also means automatic updates, which ran into this every time, now work.
  • Fixed: the View version details window could show the previous release’s notes, with a download link that had already expired. It now asks for fresh details when you open it.
  • New on 5-site and 50-site licences: branding. Replace the plugin’s name and logo with your own — in the admin menu, page headers, admin bar, Dashboard widget, emailed reports, printed exports and the Plugins screen — so your clients see your name rather than ours. See Branding the plugin as your own.

1.0.3

  • Fixed: closing one of the plugin’s compatibility warnings did nothing — the warning came straight back on the next page you opened. Dismissing one now keeps it dismissed, and each warning is remembered separately. If the problem it describes is fixed and later comes back, so does the warning, so nothing is hidden for good.
  • The “Upgrade to Pro” link has moved to the left of the plugin’s row on the Plugins screen, beside Deactivate, where it can actually be seen — it used to sit at the end of the small grey text on the right. With a licence active you never see it at all.

1.0.2 — Pro only

The free plugin was unchanged, and went from 1.0.1 straight to 1.0.3.

  • The Licence screen now simply confirms Pro is active, and keeps your licence details behind a Manage licence section. If you install Pro on sites you build for clients, their dashboard no longer shows your licence tier or a link to your billing.
  • A licence key that has been replaced now says so, and points you at your customer portal for the new one — instead of reporting a bare “Not found”.
  • The customer portal link now appears where it is actually useful: when a licence needs fixing. It also says what it is for — finding your key, or releasing a site you no longer have.

1.0.1

  • Visitor and session timelines now show the clicks a visitor actually made, alongside their page views.
  • Fixed: the setup wizard offered traffic-spike email alerts, which are a Pro feature. The option is no longer shown on the free plugin.
  • Added an “Upgrade to Pro” link to the plugins list and a line on the Settings screen, so the paid version is findable from inside the plugin.

1.0.0

Initial public release.

Pin It on Pinterest