Open Web Analytics Versions Save

Official repository for Open Web Analytics which is an open source alternative to commercial tools such as Google Analytics. Stay in control of the data you collect about the use of your website or app. Please consider sponsoring this project.

1.7.8

1 year ago

Breaking Changes

  • PHP tracker client has been removed. As mentioned in prior releases please use OWA's PHP SDK to add a tracker to your PHP based apps. https://github.com/Open-Web-Analytics/owa-php-sdk. If you have not migrated over to using the PHP SDK then this release will cause your PHP tracker to no longer work.

What's Changed

New Contributors

Full Changelog: https://github.com/Open-Web-Analytics/Open-Web-Analytics/compare/1.7.7...1.7.8

1.7.7

2 years ago

Fix for broken domstream playback under certain circumstances.

1.7.6

2 years ago

Fix for IP address validation and support for anonymizing ipv6 addresses.

1.7.5

2 years ago

Fix for the incorrect tracker location in JS tracker tag generated by admin interface.

1.7.4

2 years ago

This release makes breaking changes when updating from Git. See below for updating instructions.

CRITICAL SECURITY FIX

  1. fixes an exploit where it’s possible predetermine cache hashes in come cases.

Major Changes:

  1. We now use npm / webpack to build the tracker #693
  2. File cache is now it’s own module and disabled by default
  3. We’ve replaced a number of dependancies with composer packages. #587
  4. Search engine identification has moved to the server side #812

Refactoring:

  1. Modules can now have their own composer dependancies and composer.json files. #805

Bug Fixes:

#795 #809 #808 #700

Updating

This release requires an update package (base.011) be installed which can be done from the command line or via the admin interface.

To update grab the fully packaged tarball attached to the release below.

Alternatively, If you are updating from Git see the new updating instructions here: https://github.com/Open-Web-Analytics/Open-Web-Analytics/wiki/Updating . You now need to install and run npm in order to build the tracker... so do not just do a git pull and think you are done!

1.7.3

2 years ago

NOTE: This release contains a breaking change to API authentication. Read the release notes, new documentation on the wiki and test your API code in a staging environment before upgrading to this release in production.

NOTE: The old bundled WordPress plugin will not work with this release. You must update to the official integration plugin which should be installed from the Wordpress plugin repository.

NEW FEATURES

  • Signed Requests to REST Endpoints. A calculated signature must now be added to REST requests that use "API Key" based authentication. The signature relies on the secret OWA_AUTH_KEY contained in your config file. See the updated REST-API page on the wiki for how to manually compute the signature or use the latest version of the OWA PHP SDK when making your requests.
  • reset-secrets CLI command. There is now a new API command that you can use to reset the secrets contained in your config file.

BUG FIXES:

  • #769
  • #763
  • #637
  • #761
  • Added proper sort to geolocation report

REFACTORING

  • Refactored result set generation for better code reuse and separation of concerns
  • Standardized all result set to use paginated result set
  • Refactored heatmap and domstream JS libraries to use pre-signed URLs for REST calls instead of assembling their own request urls.
  • Added a more sane approach to controller registration within modules.

1.7.2

2 years ago

Security and bug fix release.

1.7.1

3 years ago

Bug Fixes:

  • Improve calling context checks on cli.php #694
  • install endpoint is not disabled after install #691
  • Undefined variable warning for remote_host #689
  • Funnel Visualization report not working #688
  • Issue with registration of new user #606
  • Issue with WordPress plugin and OWA admin user names getting out of sync.

1.7.0

3 years ago
  • BUG: Fix for broken login cookie handling under chrome.

1.6.9

4 years ago

! IMPORTANT: This release requires a schema update. The update can be applied via the browser (you will be prompted when viewing analytics/reporting) or you can use the command line interface (CLI). You must apply the update in order for API's and tracking to work.

! IMPORTANT: The WordPress plugin and integration have changed! As of this release, new installs must do a standalone install of OWA first before activating the WordPress plugin. Also, existing users of the plugin will need to reset their OWA admin user password in order for tracking to work properly.

! IMPORTANT: The API endpoint has changed!. This release changes the API endpoint, request methods, and response formats. It's a major change. If you rely on the existing endpoint for data access you will need to update your API calls before upgrading to this release! The good news is that you can do a lot more via the API and we won't have breaking changes like this anymore. see: https://github.com/Open-Web-Analytics/Open-Web-Analytics/wiki/REST-API

Reminder: You must install and run Composer to download dependencies when checking out code from GitHub. See https://github.com/Open-Web-Analytics/Open-Web-Analytics/wiki/Installing-from-Github for more details.

For a fully packaged distribution use: owa_1.6.9_packaged.tar

This release contains numerous changes to OWA's APIs and

  • Feature: Javascript Tracker Hooks Framework #579
  • Feature: Clean URLs under Apache for for REST API #563
  • Feature: WordPress Plugin Changes #560
  • Feature: Reporting Pages Design Refresh #557
  • Feature: CLI command to re-crawl document URLs. #523
  • Feature: Added Search engine duckduckgo #533
  • Feature: Domstream Screen resolution #534
  • Feature: More REST API Routes and Changes #535 #536
  • Bugfix: Clickstream timestamp zeros not get displayed #550
  • Bugifx: Proper link to P3P policy website. #551
  • Bugfix: Heatmap and Domstream fixes #567
  • Bugfix: Fixing random notice and adding admin notices to WP Plugin