From Open Web Analytics Wiki
This major release delivers many new features, significant database schema changes, and lots of bug fixes.
Major New Features
- Segmentation - it is now possible to generate data result sets for a segment of visitors. Segmentation is applied to the result set prior to any filtering or grouping function delivering a true segmented data set. Segments can only be applied to result sets via the data access API at this time.
- Live View - it is now possible to display live updates to data in all reports as new tracking events occur and are processes by OWA. Live view can be controlled by a switch at the top of all reports.
- Result Set Filtering - filtering result sets has always been possible by applying constraints via the data access API but now it is now possible for analysts to filter the data contained in any data table/grid displayed on any report via the GUI. Constraints can be made up of both metrics & dimensions.
- More Metric and Dimension Combinations - the number of dimensions and metrics that can be combined to generate result sets via the API and reports has been greatly expanded in this release. See the metric and dimension combinations page for more information.
- Site Level Access Control - it is now possible to control which users can access data and reports for each tracked sites.
- Logo Skinning - you can now customize the logo that appears on the reporting interface.
- IP Address Exclusion - it is now possible to exclude specific IP addresses for being tracked via the general configuration UI or via the new excluded_ips config setting.
- IP Address Anonymization - it is now possible to anonymize IP addresses by removing the last octet prior to storing them in the database. Anonymization can be controlled via the general configuration UI and the anonymize_ips config setting.
- 20+ new dimensions - lots of new dimensions have been added including:
- 64bit keys - OWA now uses 64 bit numbers for all fact table keys. There is also a new config setting that you can turn on to use 64bit keys for dimensions. See the ticket in Trac for how that works.
- OWA now uses jQuery 1.6.4 and jQuery UI 1.8.12
- OWA should now run fine under Windows servers
- Reporting components such as KPI boxes, area charts, and data grids can now be embedded into external applications by including the new owa.reporting-combined-min.js and owa.reporting-css-combined.css files from within your application.
- The update CLI command now supports a --force param that can be used to force the re-application of an update that you have already applied. This is very handy for development or when you are running trunk code and need to re-apply the same update throughout the development cycle as it evolves.
- a new flush-processed-events CLI command has been added that will delete all processed events from the database event queue.
Changes Since 1.5.0rc3
Changes Since 1.5.0rc2
If you are updating from 1.5.0rc2 you must re-run the base.007 schema update from the command line using:
/your/path/to/php5 php cli.php cmd=update apply=base.007 --force
Changes Since 1.5.0rc1
Backwards Incompatible Changes
See the installation page for how to install OWA for the first time.
This release contains significant database schema changes. See the updating page for more details on how to upgrade your existing OWA instance.
This release is dependent on applying the base.007 and base.008 schema updates. The base.007 update adds a significant number of new columns to all fact tables. If your tables contain a large number of rows, this update could take a long time to apply so be prepared.
Upgrading from Prior 1.5.0 RC or SVN Trunk
If you are upgrading from a prior 1.5.0 release candidate or from SVN trunk pulled during the 1.5.0 development cycle you MUST re-apply the base.007 update using the following command:
php cli.php cmd=update apply=base.007 --force
Once that update is complete you need to apply the 'base.008 update which you can do by using the following command:
php cli.php cmd=update apply=base.008