| Age | Commit message (Collapse) | Author |
|---|
|
|
|
* making tests pass!
* enabling DevicesDetection tests, even though DevicesDetection plugin is disabled by default.
|
|
* making some tests pass == fixing bugs
|
|
a client of Piwik Professional Services. A beautiful work of engineering, all released under GNU/GPL license!
Fixes #3612
* when enabled, the plugin will add a new submenu: Visitors> Devices
* the new devices report contains NEW reports:
* Much improved Device type (tracking 'car browser', 'console', 'desktop', 'feature phone', 'smartphone', 'tablet', 'tv')
* Device brand (tracking more than 100 brands such as Nokia, Nintendo, Lenovo or Apple.
* Device model (tracking hundreds of phone/console models)
* Operating System versions (tracking 70 variations of operating systems including Ubuntu vs Kubuntu vs Debian vs Lubuntu vs Xubuntu)
* Operating System families (Android vs Google TV vs Windows vs Windows mobile vs Mobile gaming consoles)
* Browser versions
* Browser families
Refs #3505 There is some basic TV detection included and maybe you can help contribute better detections (see the .yml data files containing the regular expressions in YAML format)
HOW DOES IT WORK
This is quite beautiful system. It is a plugin that disabled by default. when enabled, it will create additional columns in the DB. Also at tracking, it will look at the user agent, and try to match it against one browser we know in the databases. The databases of user agent matching are composed by 3 YML files, parsed by spyc.php into php array.
These 3 YML took dozens of hours of work and testing with dozens of mobile phones and devices for accuracy. We are happy with the result as they should cover > 80% of the devices commonly used. We hope the community will help us build up these YML files and make them better, so we can track accurately 90% or 95% of requests.
The performance overhead is pretty small, but parsing the YML files + running dozens of regex will add some overhead. This is why it is still disabled by default. We will think about how to integrate it in core, in the next few months.
Please let me know if you find any problem with this new awesome code!
|
|
|
|
Hiding row evolution graph URL from output for Referrer.getAll
Please double test it's all working!
|
|
is converted only once and is valid JSON. Also works in XML (not in CSV).
I updated the bulk request doc at: http://piwik.org/docs/analytics-api/reference/#toc-advanced-users-send-multiple-api-requests-at-once
|
|
|
|
process.
|
|
|
|
every day of one month.
|
|
to run benchmarks through VisualPHPUnit.
|
|
|
|
|
|
|
|
.gitingore.
|
|
|
|
updating README to clarifying workflow.
|
|
|
|
|
|
* you can now write browserCode==ff;referrerKeyword!= to select all visitors using firefox and that have a keyword set
* or you can write referrerKeyword==;browserCode==ff to select all visitors using firefox and that did not have any keyword set
Also fixes #3933
Refs #2135
* fixing last bugs with segment selector encoding (working on chrome + FF + opera) - I 'hope' it will work on iE...
|
|
translations whether the period is used in the sentence or standalone
|
|
|
|
|
|
refs #3913 Fixes API for dashboards + disabling Dashboard API tests for now
|
|
Adding future look ahead window to the SQL trying to detect the current visitor
+ fixing small bug discovered (in the tests) as a result of this fix
|
|
|
|
|
|
for now. Also moving to private unused methods (lets delete any unused method)
|
|
|
|
|
|
* 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
|
|
We should try to switch to filter_var in 2.x
|
|
|
|
|
|
* Speeding up the suggestion list by only selecting visitors that have a value set for the requested segment
|
|
* 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!
|
|
Piwik translator
|
|
makes all paths lowercase before importing hits.
|
|
adding correct label variation for those reports.
|
|
report metadata doesn't provide a translation for metrics, and make sure if no columns are displayed for a report, API.get doesn't fail.
|
|
|
|
labels for periods w/ no data.
|
|
when no labels are specified with multi-row evolution and make sure it has no effect in all other row evolution cases.
|
|
applied on the flattened datatable.
|
|
|
|
This will prevent random build failures such as https://travis-ci.org/piwik/piwik/jobs/6399322
|
|
|
|
|
|
evolution after generic filters (ie, Sort) are applied.
|
