Slimstat Analytics

Changelog

4.9.3.3

• [Fix] Disabled shortcode’s filtering WHERE statement and make security harder.

4.9.3.2

• [Fix] The filtering issue

4.9.3.1

• [Fix] Query issue in UTF-8 slugs

4.9.3

• [Update] New logo and icon for the plugin!
• [Fix] Hardened plugin security and sanitization of user input and escaped output

4.9.2

• [Fix] Fixed tweak notice errors while activating the plugin in fresh installation
• [Update] Tested up to WordPress v6.1

4.9.0.1

• [Fix] Entries in the Top Referring Domains report were pointing to broken links (thank you, s7ech).
• [Fix] The new Browscap Library requires at least PHP 7.4, up from 7.1. (thank you, Daniel Jaraud).

4.9

• [New] Browscap Library is now bundled with the main plugin, only definition files are downloaded dynamically.
• [New] Support MaxMind License Key for GeoLite2 database downloads.
• [New] Speedup Browscap version check when repository site is down.
• [New] Delete plugin settings and stats only if explicitly enabled in settings
• [Fix] Addressed a PHP warning of undefined variable when parsing a query string looking for search term keywords (thank you, inndesign).
• [Fix] Fixed SQL error when Events Manager plugin is installed, ‘Posts and Pages’ is enabled, and no events are existing (thank you, lwangamaman.
• [Fix] Starting with 4.9, PHP 7.4+ is required (thank you, stephanie-mitchell.
• [Fix] Opt-Out cookie does not delete slimstat cookie.

4.8.8.1

• [Update] The Privacy Mode option under Slimstat > Settings > Tracker now controls the fingerprint collection mechanism as well. If you have this option enabled to comply with European privacy laws, your visitors’ IP addresses will be masked and they won’t be fingerprinted (thank you, Peter).
• [Update] Improved handling of our local DNS cache to store hostnames when the option to convert IP addresses is enabled in the settings.
• [Fix] Redirects from the canonical URL to its corresponding nice permalink were being affected by a new feature introduce in version 4.8.7 (thank you, Brookjnk).
• [Fix] The new tracker was throwing a Javascript error when handling events attached to DOM elements without a proper hierarchy (thank , you pollensteyn).
• [Fix] Tracking downloads using third-party solutions like Download Attachments was not working as expected (thank you, damianomalorzo).
• [Fix] Inverted stacking order of dots on the map so that the most recent pageviews are always on top, when dots are really close to each other.
• [Fix] A warning message was being returned by the function looking for search keywords in the URL (thank you, Ryan).

4.8.8

• [New] Implemented new FingerPrintJs2 library in the tracker. Your visitors are now associated with a unique identifier that does not rely on cookies, IP address or other unreliable information. This will allow Slimstat to produce more accurate results in terms of session lenghts, user patterns and much more.
• [New] Added event handler for ‘beforeunload’, which will allow the tracker to better meausure the time spent by your visitors on each page. This will make our upcoming new charts even more accurate.
• [Update] Improved algorithm that scans referrer URLs for search terms, and introduced a new list of search engines. Please help us improve this list by submitting your missing search engine entries.
• [Update] Added title field to Slimstat widgets (thank you, jaroslawistok).
• [Update] Reverted a change to the Top Web Pages report that was now combining URLs with a trailing slash and ones without one into one result. As James pointed out, this is a less accurate measure and hides the fact that people might be accessing the website in different ways.
• [Update] The event tracker now annotates each event with information about the mouse button that was clicked and other useful data.
• [Fix] The Country shortcode was not working as expected because of a change in how we handle localization files.
• [Fix] Renamed slim_i18n class to avoid conflict with external libraries.

4.8.7.3

• [New] Implemented a simple query cache to minimize the number of requests needed to crunch and display the data in the reports.
• [Update] Extended tracker to also record the ‘fragment’ portion of the URL, if available (this feature is only available in Client Mode).
• [Update] Do not show the resource title in Network View mode.
• [Fix] Some reports were not optimized for our Network Analytics add-on (thank you, Peter).
• [Fix] The notice displayed to share the latest news with our users would not disappear even after clicking the X button to close it (thank you, Anton).
• [Fix] The ‘Top Web Pages’ reports was listing duplicate entries.
• [Fix] A regression bug was affecting the Currently Online report, by showing incorrect information for the IP addresses.
• [Fix] After resetting the Customizer view, all reports were being listed twice (thank you, Anton).
• [Fix] A new feature introduced by our Javascript tracker was not working as expected in IE11 (thank you, 51nullacht).

4.8.7.2

• [Fix] The new tracker was having problems recording clicks on SVG elements within a link (thank you, pollensteyn).
• [Fix] The event handler is now capable of tracking events on BUTTONs within FORM elements.
• [Fix] Permalinks containing post query strings were not being recorded as expected.

4.8.7.1

• [Note] We are in the process of deprecating the two columns type and event_description in the events table, and consolidating that information in the notes field. Code will be added to Slimstat in a few released to actually drop these columns from the database. If you are using those two columns in your custom code, please feel free to contact our support team to discuss your options and how to update your code using the information collected by the new tracker.
• [Fix] A warning message was being displayed when enabling the opt-out feature with certain versions of PHP.
• [Fix] PHP warning being displayed when trying to update some of the add-ons’ settings.
• [Fix] The new tracker was recording the number of posts on an archive page even when the single article was being displayed.
• [Fix] License keys for premium add-ons were not being saved as expected, due to a side effect of the new security features we implemented in the Settings.

4.8.7

• [New] With this update, we are introducing an updated tracker (both server and client-side): a new simplified codebase that gets rid of a few layers of convoluted functions and algorithms accumulated over the years. We have been working on this update for quite a while, and the recent conflict with another plugin discovered by some users convinced us to make this our top priority. Even though we have tested our new code using a variety of scenarios, you can understand how it would be impossible to cover all the possible environments available out there. Make sure to clear your caches (local, Cloudflare, WP plugins, etc), to allow Slimstat to append the new tracking script to your pages. Also, if you are using Slimstat to track external pages (outside of your WP install), please make sure to update the code you’re using on those pages with the new one you can find in Slimstat > Settings > Tracker > External Pages.
• [New] Increased minimum WordPress requirements to version 4.9, given that we are now using some more modern functions to enqueue the tracker and implement the customizer feature.
• [Update] We tweaked the SQL query to retrieve ‘recent’ results, and added a GROUP BY clause to remove duplicates. This might affect some custom reports you might have created, so please don’t hesitate to contact us if you have any question or experience any issues.
• [Update] The columns to store event type and description are being deprecated, and consolidated into the existing ‘notes’ column. Our function ss_track() will only accept the note parameter moving forward. Please update your custom code accordingly. In a few releases, we are going to drop those columns from the database.
• [Update] Changed wording on Traffic Sources report to explain what kind of search engine result pages are being counted (thank you, Nina).
• [Fix] The button to delete all the records from the database was not working as expected (thank you, Softfully).
• [Fix] When the plugin was network activated on a group of existing blogs, the tables used to store all the records were not initialized as expected, under given circumstances.
• [Fix] A bug was affecting certain shortcodes when PHP 7.2 was enabled (thank you, Peter).
• [Fix] Emptying one of the settings and saving did not produce the desired effect.