* column tweak

* fix install

* more tweaks

* rename column to dimension

* various fixes

* added new control expandable select

* starting to refactor segment selector

* make segment editor work again

* use translation keys

* defined some metrics

* set types

* simplify

* simplify

* fix join generator

* add possibility to use custom join table names when using query builder and it uses an inner query

* fix bug in query selector when selecting same field name from different tables twice

* more metadata

* more tweaks

* improve selector

* add possibility to use custom entity names

* also processed archived metrics

* generate sql filter, suggested values callback, and accept values automatically for columns with enums

* several tweaks

* focus search field when opening it

* various tweaks

* added missing method

* format and fix more metadata

* more fixes

* better definition

* define custom filter

* fix definition

* fix various tests

* fix more tests

* fix bug in logquery builder

* fix referrerurl segment was missing

* fix some tests

* fix more tests

* add group

* refactor for better definition

* fix a bug in log query builder when similar columns are used in archiver

* add goal metrics

* various fixes

* make datatable row more flexible

* various fixes and visualization enhancements

* simply segment editor and make it smaller

* remove trailing comma

* various fixes and added new dimension

* fix formatting of returning customer

* added missing primary key

* fixes

* various fixes and improvements

* make sure to update segment definition when selecting a value from auto complete list

* various fixes and more metrics

* more metrics

* more dimensions and fixes

* fix some tests

* fix some integration tests

* update submodule

* fix some system tests

* fix ui tests

* trigger new test run

* fix more ui tests

* fix system tests

* update submodule

* fix categories

* sort segments by category for more consistency

* add custom variables

* some translations and fixes

* add minute segment

* more segments

* added plurals

* added some docs

* fix test

* fix tests

* fix tests

* added suggested values

* fix some tests

* various fixes

* fix more tests

* allow to select segments on any site

* make sure to include file

* added doc block

* fix some system tests

* fix most system tests

* fix ui test

* fix system test

* adjust examples

* added more tests and docs

* no metrics for these dimensions

* added developer changelog and made some classes public api

* some fixes for entity names

* add possibility to set format metrics in test

* more consistency in defining the name

* get idsites only if provided

* fix integration tests

* added another segment for visit start hour and visit start minute

* more clear name for segment

* use old segment name to not break bc

* various fixes

* more test fixes

* fix no suggested values for new segment

* add event value

* for boolean dimensions only sum metric

* update available widgets when updating reporting menu

* Add new segments in developer changelog + typo

* fix system tests

* fix screenshot test

refs #5940 put tests in correct folders, better testsuite names, some tests still fail and I cannot figure out why

and restore Transitions tests which I deleted by mistake earlier

 * new segment 'siteSearchKeyword'
Fixes #3903, #3905:
 * adding few fields in the Live API output to accomodate getSuggestedValuesForSegment
 * renamed other fields for consistency with segment names
Fixes #3906:
 * new API: getSuggestedValuesForSegment which returns top suggested values for a particular segment. It uses the Live.getLastVisitsDetails API to fetch the most recently used values, and will show the most used values first

 * Adding tests for everything. The test case actually generates data for all segments so that VisitsSummary.get returns some data for each of the 47 segments being tested returns some data.
  How it works:
  * generate extended data in fixture
  * Tests (1) call getSuggestedValuesForSegment for each segment, check there is some data returned for each segment
  * get the first suggested value from the list,
  * Tests (2) call VisitsSummary.get with this segment value, eg. countryCode==ru.
    * I worked this way for all 47 segments until all tests had some data ==> now we know that all segments have been tested and that the auto suggest works for all segments. TDD FTW!

git-svn-id: http://dev.piwik.org/svn/trunk@7247 59fd770c-687e-43c8-a1e3-f5a4ff64c105

 * Ensuring column names stay in same order when idsites=all 
 * adding empty columns when they are not set

git-svn-id: http://dev.piwik.org/svn/trunk@5519 59fd770c-687e-43c8-a1e3-f5a4ff64c105

VisitsSummary API does NOT call Actions API now.

git-svn-id: http://dev.piwik.org/svn/trunk@5400 59fd770c-687e-43c8-a1e3-f5a4ff64c105

refs #1454 new action metrics are only accessed by actions plugin, bounce rate fix, changed color of second line chart series, updated expected test files

git-svn-id: http://dev.piwik.org/svn/trunk@5393 59fd770c-687e-43c8-a1e3-f5a4ff64c105

git-svn-id: http://dev.piwik.org/svn/trunk@5392 59fd770c-687e-43c8-a1e3-f5a4ff64c105

git-svn-id: http://dev.piwik.org/svn/trunk@2733 59fd770c-687e-43c8-a1e3-f5a4ff64c105

 * Example of a simple filter to apply to the datatable in the API method. Filters will automatically work on all dataTable are are easy to write /maintain

 * Fixing tests

git-svn-id: http://dev.piwik.org/svn/trunk@2595 59fd770c-687e-43c8-a1e3-f5a4ff64c105

 * now reporting Actions per visit 
 * reporting Average Visit duration instead of total visit duration
 * removed api getMaxActionsReturning() as it doesn't sound like a useful metric
 * udpated tests to test the new metrics 

git-svn-id: http://dev.piwik.org/svn/trunk@2494 59fd770c-687e-43c8-a1e3-f5a4ff64c105

Fixing bug in Archiving found with this new test suite (max_actions was incorrectly summed during archiving, rather than max() operation)
Updating expected file as naming convention changed in previous commit
Refs #1446


git-svn-id: http://dev.piwik.org/svn/trunk@2442 59fd770c-687e-43c8-a1e3-f5a4ff64c105

Also adding integration test suite in place.

 * Adding new mechanism to trigger known tracking requests, then call all API methods get* and compare XML to the previous 'expected' XML.
 * make sure overwritten config files are not read during tests. Use defaults from global.ini.php.
 * piwik.php Tracker allow calling script to force Datetime and user IP for a specific request. 
 * Wrote 3 main tests
  * wrong tracking requests should not return error and should not record anything 
  * standard one visitor, 2 visits, with page view, download, outlink and goal tracked
  * Added integration test as an example in the ExampleAPI plugin (pretty simple to add testing code)
TODO 
 * Finish PiwikTracker and show it in UI
 * Show how to use image based tracker in UI
 * Add more tests (multi periods and multi sites) in Main.test.php
 * Fix failing Config.test.php test (when ran via all_tests.php doesn't fail otherwise)

git-svn-id: http://dev.piwik.org/svn/trunk@2429 59fd770c-687e-43c8-a1e3-f5a4ff64c105