| Age | Commit message (Collapse) | Author |
|---|
|
generation time in Visitor Profile (#11095)
* Live API: New 'generationTimeMilliseconds' field used to process Average generation time in Visitor Profile
fixes #11066
* more precision
* Expected test files
* Reporting API: showColumns and hideColumns should be applied recursively (#11100)
* Recursively delete columns specified with hideColumns
* Custom Dimensions tests
* Invalid argument supplied for foreach() + Contents tests
* New unit test for ColumnDelete filter
* Submodules
|
|
|
|
|
|
code, few refactorings, all as part of our code cleanup strategy
|
|
|
|
|
|
filters on it will not work. Instead run the filters directly on the array. Therefore, to not have duplicated code the dataTable and row can be now treated as an array and we access them like an array in the ColumnDelete filter which will be for now the only filter is applied on arrays
|
|
|
|
to use free/libre instead of open source
|
|
refs #4609
|
|
defined on PHP 5.3.2"
|
|
|
|
|
|
|
|
Segment, SegmentExpression, PluginsManager.
Removed some deprecated code.
|
|
* 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!
|
|
|
|
Converting Piwik core source files, PHP, JS, TPL, CSS
More info: http://piwik.org/participate/coding-standards/
|
|
|
|
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
|
|
output & modified ColumnDelete filter to be more robust.
git-svn-id: http://dev.piwik.org/svn/trunk@6836 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
git-svn-id: http://dev.piwik.org/svn/trunk@6353 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
Now the filter object itself will take care of applying recursively when the table was recursively loaded indeed.
Leaving open until I can check that all occurences on demo are fixed
git-svn-id: http://dev.piwik.org/svn/trunk@4169 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
since it won't load the tables if they were not loaded in the API). Updating all filters to reflect new abstract class signature
git-svn-id: http://dev.piwik.org/svn/trunk@3764 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
git-svn-id: http://dev.piwik.org/svn/trunk@2968 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
git-svn-id: http://dev.piwik.org/svn/trunk@1600 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
