| Age | Commit message (Collapse) | Author |
|---|
|
refs https://github.com/PiwikPRO/plugin-MetaSites/issues/3
|
|
|
|
|
|
code, few refactorings, all as part of our code cleanup strategy
|
|
ArchiveProcessor\Rules and fix build.
|
|
|
|
for archives of multiple sites and add option to control whether unique visitors for multiple sites are processed.
|
|
this is not a valid operation.
|
|
Means "Active Users". Displayed in Visitors Overview, in metrics picker, in API response, in Metadata
|
|
|
|
|
|
|
|
ArchiveProcessor::aggregateDataTableRecord.
|
|
to use free/libre instead of open source
|
|
using phpstorm optimize imports feature
|
|
|
|
renamed after aggregation) are summed correctly. If period is for instance 2014-04-01,2014-05-01 we will sum two periods. The month of April 2014 and May 1st. The dataTable of the month will already contain the renamed column (as it was aggregated before) whereas May 1st datatable will not contain the renamend column but the original. Both columns cannot be summed therefore and the original column will overwrite the value of the renamed column. Meaning sum_daily_nb_uniq_visitors is in this case always the value of May 1st
|
|
archive sub-tables (only the parent table).
The sub-tables will be archived only when idSubtable is found, or flat=1, or expanded=1
|
|
refs #4609
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
visitors cross-sites for now)
|
|
|
|
only (code reuse)
|
|
|
|
|
|
|
|
|
|
* Moving Core visit metrics archiving logic to PluginsArchiver which is consistent
* Cutting down code that should be unused after refactoring
|
|
|
|
ArchiveProcessor\Loader
|
|
|
|
|
|
ArchiveProcessor\Loader
ArchiveProcessor becomes a helper class easier to understand for plugin developers
|
|
|
|
|
|
automatically detected.
|
|
|
|
aggregateMultipleReports
|
|
Range::removePeriod and replace w/ Date::addPeriod.
|
|
ArchiveProcessor.
|
|
|
|
DataTableMap::deleteRow and start documenting ArchiveProcessor.
|
|
|
|
|
