| Age | Commit message (Collapse) | Author |
|---|
|
Segment, SegmentExpression, PluginsManager.
Removed some deprecated code.
|
|
|
|
Notice that auto refactoring has created a nested namespace. Not sure this is what we want - so we might have to edit those nested namespaces afterwards (I think they don't look so good)
|
|
Notice that auto refactoring has created a nested namespace. Not sure this is what we want - so we might have to edit those nested namespaces afterwards (I think they don't look so good)
|
|
|
|
2 steps required:
1. Refactor > Move > \Piwik\Core\Config (uncheck "Create new File")
2. Refactor > Rename > Piwik_Config to Config
|
|
Notes:
- Modified ManySitesImportedLogs fixture to add segments if desired.
- Switch to synchronous execution of curl requests until deadlocking issue in archive processing is dealt with.
- Fixed bug in LogAggregator where if a segment required a subquery, archiving would failed.
|
|
Refs #4019
|
|
|
|
prepended to the path even if the path already contains a protocol & host.
|
|
understand it (nearly there)
|
|
|
|
|
|
parameters name short.
Updated doc at: http://piwik.org/docs/tracking-api/reference/
and http://piwik.org/docs/page-speed/
|
|
Volgers for the suggestion!
|
|
|
|
Added support to Icecast2 HTTP logs format. NSCA_EXTENDED + SessionTime
|
|
* 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
|
|
makes all paths lowercase before importing hits.
|
|
|
|
|
|
make sure I don't lose it, since we want to apply it again (eg. every year or so))
This fixes #3895
the mass conversion was applied in: [ae4b03163792f0b6e933933e5d37df87dc3fd566]
|
|
Small update to log analytics readme
Fixes #1700
Awesome work Timo!
|
|
* 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
|
|
Converting Piwik core source files, PHP, JS, TPL, CSS
More info: http://piwik.org/participate/coding-standards/
|
|
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
|
|
after format regex match and modified format autodetection logic to pick the format based on whether the format matches and the number of groups returned in the match.
Notes:
* Added several more tests to log importer tests.py. Added tests for checking format of log files w/ extra junk info on log lines. Added individual tests for parsing regex format.
* Modified log files used in ImportLogs test, added extra junk info to end of some lines.
* Fixed failing test in tests.py for the S3 log file format.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
script).
|
|
Modify replay tracking to use site ID in query string when using replay-tracking option.
|
|
|
|
|
|
|
|
|
|
|
