Age | Commit message (Collapse) | Author |
|
* updating all variables/methods containing Referers
* RENAMING custom segments definition, and custom scheduled reports definition, so that when they load "Referers" segment/report it still works as expected
* RENAMING old archived data so that archived blobs are called Referrers
* Reverting part of 0deb2bbb8d5598200f7adfbc77b190516f919e48
* Update integration tests generating PDF+HTML with images on my dev box (GD 2.1 and PHP 5.5)
|
|
|
|
changed logging level on travis.
|
|
|
|
is backwards compatible.
|
|
|
|
|
|
|
|
will not be created if not necessary.
|
|
|
|
|
|
core/ conversion
|
|
Segment, SegmentExpression, PluginsManager.
Removed some deprecated code.
|
|
PluginsManager
|
|
|
|
|
|
|
|
|
|
|
|
refactoring and fixing bug in integration testing code which sets 'date' query param.
|
|
single column was requested (otherwise return array)
|
|
Piwik_Archive class.
Also moved some other const to Piwik class.
|
|
|
|
creating new archive entry
|
|
getMinTimeArchivedProcessed to make it clear.
Renaming class to Piwik_DataAccess_ArchiveSelector -- it will specialize in selecting archives
|
|
|
|
|
|
|
|
|
|
(and merge with Archive)
Moving Transitions logic from plugin class to API
Cleaning up some separation of concerns
NOTE: I'm breaking the Multisites API here, removing the _evolution. we should re-fix it...
|
|
understand it (nearly there)
|
|
such as removing duplicate code and a lot of refactoring, the code is now much more readable!
|
|
|
|
|
|
instead, with a visitorType==returning segment
Fixing a 4 year old bug which I'm happy about!
Also removing an old hack in Archive.php
|
|
plugin' in archive querying & processing. Also includes some mild refactoring of new Archive.php code.
|
|
Piwik_Archive, added memory optimizations for archiving (not storing archive processing instances), added optimization for querying data indexed by site + date, added ability to select multiple blobs/metrics at once (from different plugins), added optimization to Piwik_ArchiveProcessing_Period where numerics/records are selected all at once instead of one at a time.
Also added data access layer object for archive querying code, allowed anonymous function objects to be used as DataTable filters, and removed 'timestamp' DataTable metadata.
|
|
* 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
|
|
https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md#45-abstract-final-and-static
|
|
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
|
|
|
|
git-svn-id: http://dev.piwik.org/svn/trunk@7719 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
Added new parmeter &pattern= to MultiSites.getAll
Thomas let me know if any feedback on this!
git-svn-id: http://dev.piwik.org/svn/trunk@7717 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
git-svn-id: http://dev.piwik.org/svn/trunk@7687 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
git-svn-id: http://dev.piwik.org/svn/trunk@7621 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
git-svn-id: http://dev.piwik.org/svn/trunk@7593 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
in Piwik_Archive_Single::getRequestedReportFor and make sure Piwik_VisitsSummary_Controller::getVisitsSummary can handle case where Piwik_API_Request returns false.
git-svn-id: http://dev.piwik.org/svn/trunk@7500 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
Implementing Site Search tracking & reporting in Piwik core!
* New Admin UI to customize, for each site, wheter site search is enabled. Also options to set default values to use.
* New Reports: Searches, Searches with no result, Search categories, Top Pages Following a Search
* to track "No result keyword" users will have to tag their site with a JS call, or add a new parameter to the search result page &search_count=X (X being zero for no result searches)
* Reports works with Row evolution, PDF/HTML reports, Piwik Mobile
* idaction_url is now NULLable because, Site Search records a page with idaction_name == Keyword, and idaction_url == NULL. This ensures that the Site Searches don't create "Page URL Not defined" records.
* updates to Tracker JS API, new function trackSiteSearch, also added in PHP tracker
* New fields in log_visit to track searches
* new segment, "searches" which can be used to select visitors who did a search ie. searches>0 or those who searched a lot, ie searches>10
TODO:
* commmit integration test, TESTING, DOCS, FAQ, release, and a nice Prayer to the universe and the stars, hoping that I can code a major new feature without any bug...
* It would be awesome to have compatiblity with Transitions so we can see, for a given site search, what are the starting pages and Destination pages
Thank you for your patience Timo,
and thank in advance everyone for your help Testing this new feature!
git-svn-id: http://dev.piwik.org/svn/trunk@7190 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
git-svn-id: http://dev.piwik.org/svn/trunk@6605 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|