Changelog

If you are using the view counter, you may not want visitors to see the count on your less popular pages. With this new option, you can limit the view counter to only display when a page has X views or more.

There is a new retry mechanism that can auto-fix database migrations when Independent Analytics is updated.

If the date range contained the beginning/end of DST and the site is in the Azores timezone, data after the beginning/end of DST wouldn’t show in the chart.

You can now see the number of views the shop page has had in the admin toolbar, like other pages.

Before now, authors/contributors/etc could see the View count for all published pages in the Posts menu.

It was possible for the option to delete all data to leave some tables on the site. That is now fixed.

It was possible for a cached DB value to cause the Overview report to repeatedly fetch the modules, leading to very high CPU usage.

The line charts could be displayed too short, but they now fill the available space.

There was a mistake that caused the buttons in each module to have an ugly white background show up behind them when hovering over the module header.

If resizing a pie chart from two columns to one column, it would display out of position.

Their layout was not working properly when made two columns wide, and a potential JS error was resolved.

The email report now always takes DST into consideration when scheduling and rescheduling.

Special characters like apostrophes and question marks were getting encoded in CSVs, making them difficult to read.

You can now see the number of views your dedicated blog (posts page) has in the Views column in the Pages menu.

The temporary loading UI in the Quick Stats wasn’t styled properly for dark mode.

There was an extreme edge case where a term or search results page could return the incorrect ID causing a fatal error to be triggered by IA.

If a system temp file was created for storing click data but then later became unreadable/unwritable, it would prevent clicks from getting tracked.

Referrers and Countries lists could be missing data when views from a session were both within and beyond the last five minutes.

When the stats refreshed, the Top 10 lists were not getting reordered correctly.

A bug in the calculation of session durations in the data table was causing them to be inaccurate by a small degree.

The links in the data table of the PDF report could be placed out of position and made difficult to click.

The Getting Started Guide notice was getting partially covered up by the WP sidebar for sites using an RTL language.

The entire plugin is now translated into Swedish for free and Pro users.

There was a PHP notice being triggered that the text domain was loaded too early. That has now been resolved.

An error was triggered when a view was recorded on the checkout success page. On most sites, the error was a silent PHP notice, but for some sites, this was returning an E_ERROR.

On sites that use the formal variation of German, an error was triggered when viewing the analytics.

A fatal error was triggered when activating both Independent Analytics and the latest version of GiveWP.

AnalyticsWP and Independent Analytics both use the same code library to detect the visitor’s device. This was causing an issue where device data went untracked in IA.

Under some conditions, the Complianz plugin would block the tracking script in IA. It has now been white-listed.

URLs longer than 256 characters could trigger a fatal error when IA tried to save these page views. URLs can now be as long as the true limit imposed by the web, which is 2,083 characters.

Click data was still getting retained when the other data was deleted. Now, click data is also removed by the option to automatically delete old data.

On some sites, the click-tracking request would return a 403 due to the temporary file being writable but not readable.

If a WooCommerce sale was refunded beyond its total so that it became a negative value, this would cause the eCommerce stats to report vastly incorrect numbers.