Changelog

4.7.7

• [New] We’ve completely rewritten the portion of code that handles the date ranges in the Filter Bar. In order to simplify things, we have deprecated the interval_direction filter, which is now expressed by the sign in front of the interval value (positive for going forward from a given start date, and negative for going back in time). Please note that this change affect your existing shortcodes, if they use the aforementioned filter. We will update our documentation in the next few days to remove any reference to this filter, and to avoid any confusion. Please feel free to contact us if you have any questions or to report any issues.
• [New] The comparison chart is now always displayed, using new criteria to determine the range to use. You may want to update your settings (Settings > Reports > Default Time Span > Days, and Reports > Comparison Chart) to mimic the old behavior or hide the comparison chart altogether, if you like.
• [Update] We’ve reintroduced the various levels of granularity for our charts: hourly (when a single day is selected), daily (for ranges up to 120 days) and monthly. Also, the comparison chart is now always available, regardless of the selected time range. Thank you, WebsiteOpzetten.
• [Update] Tooltips across the interface have a more uniform behavior.

4.7.6.1

• [Fix] The new Javascript library was interfering with the dropdown menus on the WordPress Dashboard. Thanks to all of those who helped us troubleshoot the issue.

4.7.6

• [Note] As we mentioned earlier, we’ve been working on streamlining and cleaning up our source code. It’s incredible how layers of code can deposit on top of each other, until they form a thick layer that prevents developers from seeing clearly what’s happening. It was time to apply some virtual citric acid to descale our code. If you’re using any kind of server caching functionality, please make sure to clear your cache before opening a support request. Also, do not hesitate to reach out to us if you notice any strange or unusual behaviors.
• [New] You can now download the geolocation map as a PDF file or PNG image. Thank you, Steve, for suggesting this feature!
• [New] You can now exclude pageviews by content type, like 404, taxonomy, search, etc. Thank you, victor50g.
• [Update] Deprecated the ‘direction’ filter, which was a leftover from over 5 years ago, when we used our old interface.
• [Fix] The cron job to archive old records was not firing as expected under certain circumstances.
• [Fix] Charts did not render correctly, if no data was available for that specific view.

4.7.5.3

• [New] For those who can’t manage to automatically update their local copy of our premium add-ons, we’ve added a link to manually download the zip file. You’ll find it under the Plugins screen, once you’ve entered and saved the corresponding license key under Slimstat > Add-ons.
• [Update] The Update Checker library has been updated to version 4.4.
• [Fix] The world map was not being displayed correctly if no data points were available for the selected time range (thank you, Michel).

4.7.5.2

• [Update] You can now customize the amount of dots displayed on the World Map, under Slimstat > Settings > Reports > Access Log and World Map. Thank you, service4.
• [Fix] A dependency error was being highlighted for one of our premium add-ons under certain circumstances. Thank you, Peter.
• [Fix] The option to not set the session cookie was not working as expected. Thank you, Bjarne.

4.7.5.1

• [Update] Implemented a workaround to try and fix the “Forbidden” error that a few users are experiencing when trying to download the MaxMind Geolite2 data file.
• [Fix] Updated the link to manually download the MaxMind data file from their servers, and added a new page to our knowledge base to explain how to manually install it.

4.7.5

• [New] Now that Slimstat is capable of geolocating visitors at the city level, wouldn’t it make sense to display those visitors on the map? Well, of course! Go check out this new feature by accessing the Geolocation tab in Slimstat.
• [New] Updated the tracking script to handle events triggered by external libraries, like the Vimeo API. Thank you, Max.
• [New] Added new operator “included_in_set”, which allows you to list multiple values to match against, when composing a shortcode.
• [New] Added new option to avoid that Slimstat assigns a COOKIE to your visitors. Thank you, dragon013.
• [Fix] A bug was preventing the feature to “restrict users” to only see their reports from working as expected.

4.7.4.1

• [Update] The Browscap data file is now loaded only when needed, thus removing its inherent overhead when unnecessary.
• [Update] The Browscap data file has been updated to the latest version available on their repository (ver 6026).
• [Fix] Addressed a remote XSS Vulnerability responsibly disclosed by one of our customers. Thank you, riscybusiness.
• [Fix] Reintroduced the WHOIS pin, which has been removed by mistake because of a regression bug. Thank you, brachialis.

4.7.4

• [Update] New fields added to the Email Report and Export to Excel add-ons, by extending how certain reports are defined in core.
• [Fix] The false positive alert related to a virus in our code was fixed by updating AmChart to the latest version available (thank you, Sasa).
• [Fix] Removed a PHP warning of undefined index (thank you, slewis1000 and Sasa)
• [Fix] The MozScape report was causing connectivity issues for some users, and it is now set as “hidden” by default.
• [Fix] Regression bug related to our Export to Excel add-on.

4.7.3.1

• [Fix] Apparently more people than we initially thought have issues with the MaxMind data file not being saved as expected. We are introducing a temporary fix while we try to investigate this issue further.

4.7.3

• [Fix] A few users pointed out a weird behavior when installing the MaxMind Geolocation data file, where an empty folder would be created instead of the actual file. If you still experience issues related to this problem, please make sure to delete the empty folder “maxmind.mmdb” under wp-content/uploads/wp-slimstat/.
• [Fix] Apparently Microsoft Security Essentials was not pleased with our code, and was returning a false positive alert that a virus was included with the source code (thank you, Sasa).
• [Fix] The “content_id” filter could not be used in a shortcode to reference other pages (i.e. [slimstat f='count-all' w='id']content_id equals 2012[/slimstat]). Thank you, Felipe.
• [Fix] Country flags were not being displayed properly under certain circumstances (thank you, Catmaniax).
• [Fix] Bug preventing the new Heatmap Add-on from working as expected.

4.7.2.2

• [New] Added support for SCRIPT_DEBUG: by defining this constant in your wp-config.php will make Slimstat load the unminified version of the javascript tracker (thank you, Sasa)
• [Update] Added new parameter to make the admin-ajax.php URL relative, to solve issues like this one.
• [Fix] The Network Settings premium add-on was not working because of a bug in the main plugin. Thank you, Steve, for pointing us into the right direction.
• [Fix] Updated the schema (columns) for the archive table.

4.7.2.1

• [Fix] The new table columns “location” and “city” were not being created on a fresh install (thank you, nielsgoossens)
• [Fix] Async mode was not working as expected (thank you, keithgbcc)

4.7.2

• [New] As those who have been using Slimstat for a while know, we never stop doing our good share of research and development to improve our plugin. One feature on our wishlist was to make the geolocation functionality more accurate. Specifically, users have been asking us to track not just the Country of origin, but possibly the state and city. In order to geolocate visitors, our code has been leveraging a third-party data file provided by MaxMind.com. A while ago, they launched a new data format, which improves performance and offers a way to quickly determine the city of origin. However, the new library required a higher version of PHP, and up until now we had been hesitant to adopt it, to allow more people to use our plugin, over the chance of offering this feature. Now, after spending some time combing through their code, we found a way to get the best of both worlds: by customizing their PHP library, we were able to make it work with PHP 5.3! Which means that now Slimstat is able to tell you your visitors’ city of origin (and State, when applicable) right out of the box. This information is available in the Access Log report and in a new ‘Top Cities’ report under the Audience tab. Please note: the MaxMind data file to enable this feature is approximately 60 Mb, and for this reason this new functionality is not enabled by default. You must go to Slimstat > Settings > Tracker and turn on the corresponding option. Then go to Slimstat > Settings > Maintenance and uninstall/install the GeoLite file to download the one that contains the city data. Please feel free to contact us if you have any questions.
• [Update] Removed backward compatibility code for those updating from a version prior to 4.2. Hopefully most of our users are using a newer version that that. If you’re not, please contact our support service for instructions on how to upgrade.
• [Update] The format used to save your settings in the database has been changed. You MUST update your premium add-ons as soon as possible, and get the version compatible with this new format, or you might notice unexpected behaviors. Please contact us if you experience difficulties updating your add-ons.
• [Update] Cleaned up some old CSS code affecting the reports.

4.7.1

• [Fix] The new feature introduced in version 4.6.9.1 to allow our users to customize the default time range for the reports, had introduced a regression bug. Thank you to all our users who volunteered to test the bugfix.
• [Fix] A vulnerability has been disclosed by Pluginvulnerabilities.com: an attacker with admin credentials could leverage the import/export mechanism for the plugin’s settings to inject some malicious code. We recommend that you upgrade to the latest version of Slimstat as soon as possible.
• [Fix] The new version of the Add-on Update Checker library, bundled with the previous release, was returning a fatal error under certain circumstances (thank you, Pepe).