| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
* BETA release of Segment editor.
* API to add/update/delete/get recorded segments
* cron script will pre-process segments marked as such
* UI to create, update, apply segments
TODOs @mattab
- test with NON super user (anon/view/admin)
- testing (and more testing)-- try to break it (it's not hard...)
- UI: Saving the segment for reuse / pre-processing
- Loading message: "This can take a while based on the amount of data that needs to be pre-archived"
- i18n
- Save & Apply this segment ==> "Test this segment" which would call VisitsSummary.get for early feedback ?
+ hoping for Piotr superJS Ninjas skills with some jquery/js that I can't figure out
|
|
|
|
|
|
* 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!
|
|
|
|
|
|
|
|
|
|
is less than 5.3.
|
|
|
|
strings fully translatable?
|
|
|
|
* DataTable_Row::sumRow has a new parameter $aggregationOperations which allows treating columns as min or max (not only sum)
* The aggregation operations can be set on any data table or passed to ArchiveProcessing_Period::archiveDataTable()
* The Actions plugin uses the mechanism to aggregate the new metrics as min and max
* The metrics are in the API output but not in processed reports
* The min/max values are shown in the tooltip that appears when hovering the average generation times
* Integration test updates
|
|
|
|
* adding avg_time_generation to Actions.get + integration tests
* adding sparkline for average generation time to Visitors > Overview
* changing number formatting to 0.XXs instead of XXXms + test cases
* tooltip for reports with avg. generation time: "average based on X hit(s)"
* log import: support generation_time_milli (not only generation_time_micro)
* example for importing generation time from logs in read me
|
|
|
|
the no plugins version
|
|
|
|
* linking on metric value
* Display + linking on "Majestic"
|
|
|
|
* rename custom_float_1 DB field to custom_float (further time tracking can be tracked as events)
* fix regression missing auth in Live
* remove extra comma in javascript which breaks IE parsing
|
|
|
|
each page and page title
CORE
* formatting sub-second times
* getColumn() method on data table array (in order to behave the same as the regular data table class)
* data tables can store in their meta data, which columns are empty (this is used in order to dynamically hide the new "generation time" column)
* ViewDataTable and Api.getProcessedReport act according to the empty column meta data
SCHEMA
* new column custom_float_1 in log_link_visit_action
* new version to apply the change
TRACKER
* Piwik_Tracker::setGenerationTime
* tracking parameter "generation_time_me"
* value is stored in new custom_float_1 column
* the log importer can handle a group "generation_time_micro" which can be used in a custom log format. _micro is used because apache can log the time in microseconds but piwik processes milliseconds.
* note: extension of JS tracker still missing
ACTIONS PLUGIN
* for pages and page titles, add new columns sum_time_generation and nb_hits_with_time_generation to the blob archives
* if they are set, compute avg_time_generation on the API level. if not, remove the columns and mark them as empty in the data table meta data.
* show new column "avg. generation time" in the pages and page titles reports
plus TESTS for everything
|
|
|
|
widget via Majestic SEO API.
|
|
visitors, visits and actions in the last N minutes.
Notes:
- Added visitors metric to result of Live.getCounters.
|
|
Add new translation to document the setting.
fixes #3828
|
|
|
|
|
|
element ID for all DataTable in browser, instead of using report as element ID.
|
|
in geoip updater setup.
|
|
|
|
alias option description and in group by domain description.
|
|
|
|
|
|
|
|
|
|
* the tests/js is now passing following Benaka's commit, sweeet
* Adding setsiteId to the "special case" so that setSiteId can be called after trackpageView and it still works
* Adding pathname in the generated JS
* HTML entity the & in the IMG src
|
|
|
|
and add note for when server-side DoNotTrack support is enabled.
Note:
* Modified i18n strings that were added about two days ago.
|
|
|
|
|
|
* Opening up real time map to anonymous user
* refactoring couple translations (note: I deleted them from otrance)
|
|
|
|
used async JavaScript for tracking code. Also, tweaked and applied some fixes for JavaScript Tracking code admin page.
|
