Burst Statistics – Privacy-Friendly Analytics for WordPress

Changelog

1.4.6.1

Fix: Build issue for our dashboard.

1.4.6

• New: Delete old data to manage your database disk usage.
• Improvement: Don’t add WordPress script dependencies if endpoint is working correctly, props @gauravtiwari.
• Improvement: Use fallback method for Burst endpoint test, props @ov3rfly.
• Fix: For when page id was always empty, props @huubl.

1.4.5

• Improvement: Tested up to WordPress 6.3

1.4.4

• Improvement: For checking if the endpoint works, we changed file_get_contents to wp_remote_get to prevent issues with some hosts. props @ov3rfly
• Fix: Tracking would sometimes not work properly when some data was missing like the user agent information. This has been resolved. props @ov3rfly
• Improvement: Added month to date and week to date to the datepicker. props @daanvandenbergh
• Fix: When tracking page visits as a goal, tracking would in some cases not work. This is now fixed.
• Fix: Some users could not load data due to a firewall issue. This has been resolved.
• Fix: Persian URLs would not show properly in the dashboard. This has been resolved.

1.4.3

• Fix: Fixed an issue where the REST API would not work properly and the AJAX fallback was used. This has been resolved.
• Fix: Fixed an issue where “Direct” referrers where not being displayed properly. In Czech language, this would result in referrers not showing all together. This has been resolved.
• Fix: When all tasks were completed, remaining tasks would still show 1. Now it will show 0.
• Fix: When activating Burst through the ‘bulk’ activate option, the plugin did not activate due to a fatal error. This has been resolved.
• Fix: Disabled some logs when debug mode is disabled.
• Fix: In some situations the ‘Statistics’ in the menu would not show an active state when visiting the Burst Dashboard.

1.4.2.1

• Fix: Upgrade script for 1.4.0 did not run properly. This has been resolved. The upgrade will run again.

1.4.2

• Fix: Fixed an issue where data was shown with bounces, even when bounces should be excluded.
• Fix: Fixed a fatal error in the REST API fallback. Props @helmar
• Fix: When inserting a goal, the statistics_id could be empty resulting in an error. This has been resolved.

1.4.1

• Fix: Added a fallback for when the REST API does not return a valid response.
• Fix: Translation strings were not being loaded properly.
• Fix: Date picker caused the dashboard to crash for some users. This has been resolved.
• Fix: IP block did not save IP addresses properly. This has been resolved.
• Fix: Datepicker did not select the right timezone. This has been fixed.

1.4.0

• Feature: Goals. You can now set goals for your website and track them in the dashboard.
• Feature: Filter your data by device, pages, referrers, and more.
• Improvement: Speed performance of statistics dashboard
• Improvement: WP and PHP version checks integrated with WP Core.

1.3.5

• Fix: Fixed timezone issue where there would be a mismatch between the selected date in the datepicker and the date shown up top.
• Fix: Fixed issue where referrers would not show up when Czech language was selected.
• Fix: RTL issue in some languages
• Improvement: Tested up to WordPress 6.2

1.3.4

• Fix: Removed caching of statistics due to causing multiple issues and not providing performance benefits.
• Fix: Timestamp bug where the time for today would be off by the client timezone offset has been resolved.
• Improvement: Obsolete output buffering has been removed.
• Fix: JS translations have been corrected.
• Fix: Unnecessary error logs have been removed.

1.3.3

• Fix: Timezones were not functioning correctly. Burst now utilizes the WordPress timezone setting to ensure the correct timezone is used for all dates.
• Fix: Translation plugins would occasionally alter the REST API URL, resulting in tracking with the REST API not working. This issue has been resolved by utilizing wp.apiFetch instead of fetch.
• Improvement: Previously, when an IP was blocked in the settings, a 403 error would be displayed. Now, a 202 response with a message indicating that the IP has been blocked is returned.
• Fix: Typos in the code have been corrected.
• Fix: PHP warnings that would appear upon dismissing the tour have been resolved.

1.3.2

• Fix: Cookieless tracking was not working properly. Issue where some users were not tracked.
• Fix: Qtranslate caused an error where the dashboard could not load.
• Fix: DateTime object was not properly formatted in the dashboard.
• Fix: Issue where the tracking tests would crash and display the wrong information.
• Feature: DoNotTrack & Global Privacy Control support. Added setting to honor DoNotTrack & Global Privacy Control headers.

1.3.1

• Fix: auto updates causing critical error because a required function is only loaded for logged in users

1.3.0

• Improvement: React dashboard & settings page. This helps us speed up development and improve the user experience.
• Improvement: Settings for blocking IP addresses & user roles from tracking. Props @lowym
• Improvement: Improved endpoint path. Path is now dynamic with WP_CONTENT_DIR. Props @HubertGL
• Improvement: Improved performance because of REST API optimizer for the dashboard.
• Improvement: Show all results in the datatables. Props @alfanova
• Improvement: Added RTL support.
• Improvement: Added ‘plain’ permalinks support.
• Feature: Change metrics for insights chart.
• Feature: Show hourly stats in the insights chart. Props @perties
• Feature: Show data for today in the ‘Statistics’ tab. Props @perties

1.2.3

• Fix: Fixed an issue with a translatable string
• Tested up to WordPress 6.1

1.2.2

• Fix: Fixed an issue where duplicating a WooCommerce product would copy the total pageviews from the original product.

1.2.1

• Fix: Fixed an issue where adding role capabilities would result in a fatal error.
• Fix: Post and page counts did not update, this is fixed now.
• Fix: Changed endpoint DIR to URL to prevent 404 errors on subfolder installs.
• Improvement: Delete endpoint on uninstallation.

1.2.0

• Feature: Introducing defer/footer as option
• Feature: Introducing new improved tracking method
• Improvement: Feedback notices

1.1.5

• Improvement: Changed from .less to .scss because WordPress also uses .scss
• Improvement: Update option autoload turned off on front end for better performance
• Fix: Fixed bug where UID could be empty resulting in an SQL error
• Fix: Fixed last step of shepherd tour to be inside the viewport
• Improvement: Integration with Complianz that adds burst_uid to the cookie-scanner

1.1.4

• Fix: Bounce rate calculation
• Feature: Cookieless tracking

1.1.3

• Fix: Fatal error on PHP 7.2
• Improvement: Block IP address with MU Plugin
• Improvement: Notice for REST API failure

1.1.2

• Verbetering: dropdown toegevoegd aan datatabellen, props @topfgartenwelt

1.1.1

• Verbetering: mogelijkheden toegevoegd om uitbarstingen te bekijken en/of te bewerken
• Improvement: Added new devices to recognized devices
• Verbetering: filters toegevoegd om het decimaalteken en het duizendtallen scheidingsteken te wijzigen

1.1.0

• Opgelost: beter tracking script. Hits van één pageview kunnen nu niet meer meerdere keren geregistreerd worden
• Verbetering: bezoeken in pagina’s en berichten overzicht. Omdat deze hits anders worden opgeslagen,
  zullen ze ook bij bestaande setups op 0 beginnen. Props: Shayne
• Verbetering: parameter toegevoegd om de dashboard cache te wissen
• Verbetering: JS event toegevoegd zodat andere plugins kunnen integreren met Burst
• Verbetering: privacy annex toegevoegd
• Verbetering: widget toegevoegd aan het WordPress dashboard Props: Shayne

1.0.2

• Oplossing: typfout in generate_cached_data, props @seath
• Oplossing: sommige strings met een verkeerd tekstdomein
• Verbetering: link in readme, props @8725z4twhugias

1.0.1

• Opgelost: tekst domein, props @bonaldi
• Fix: parse_user_agent library prefix om compatibel te blijven met Rank Math

1.0.0

• Initiële release