| Age | Commit message (Collapse) | Author |
|---|
|
Otherwise the behavior whether lifetime will be extended or whether
remaining will be calculated would depend on the time at which
setVisitorCookieTimeout is called which is very confusing. Also makes
sure in case the page is open for an hour and there is a tracking
request the lifetime will not be extended by an hour.
|
|
|
|
after 13 months
instead of 24months. This is the now done by default. If you want different
behavior you can call setVisitorCookieTimeout() manually
|
|
We will now always wait 800ms after a first tracking request was issued.
This should give enough time to create a visitor before any other request
is executed. Ideally we will resolve this issue on the server side as
this problem can occur using other SDKs as well and for some servers or
sometimes the 800ms might be not long enough.
|
|
Delay first content tracking request a bit to make kinda sure a possible
previous pageview request is already executed. If there is a new visitor
and there are 2 tracking requests at nearly same time (eg trackPageView
and trackContentImpression) 2 visits will be created as both visitors
are basically at the same time. This is only a workaround and it this
problem might still occur. Also delay a link earlier in case an
interaction is happening to make sure the browser waits for the
interaction to be tracked.
|
|
|
|
|
|
installed. When replacing the initial link urls link tracking might not be installed yet but enabled (will be installed on load event). When a click is happening on a content block we still need to use linkTrackingInstalled since then the credirect/tracking request is actually happening and we need to know whether outlink/download will track it or whether we have to do it separately. Make sure to call enableLinkTracking before trackContentImpressions although there should be no huge difference as both will be delayed until ready/load event anyway
|
|
|
|
interaction and also have to use default values
|
|
subdirectory although could not really test it. Also encode redirect uri
|
|
documentation
|
|
could be maybe moved to trackCallback in general?
|
|
in case we detect the URL of an image, video or audio, pdf, ... automatically. Otherwise we cannot display a preview in the UI and one would not know which URL was actually meant. Thinking about using //domain/path instead of http://domain/path as it would track different content pieces for http and https otherwise
|
|
|
|
+ Opera and on my local phantomjs but not on travis phantomjs
|
|
|
|
|
|
and restore Transitions tests which I deleted by mistake earlier
|
|
|
|
|
|
|
|
refs https://github.com/piwik/piwik/pull/336
|
|
refs https://github.com/piwik/piwik/pull/325/files
|
|
|
|
https://www.gnu.org/software/librejs/free-your-javascript.html#magnet-link-license
|
|
|
|
AnalyticsTracker.getTracker" instead of "Piwik.getTracker". Variable will be set only if no such variable is defined yet
|
|
|
|
|
|
registered multiple times. We do not throw an error as this would prevent script execution
|
|
HTTP request + tests
Close PR#243
|
|
|
|
Should make the JavascriptTests build green again
|
|
request is sent.
|
|
Conflicts:
piwik.js
plugins/SegmentEditor/javascripts/Segmentation.js
|
|
|
|
- change idsite to idSite in Overlay URLs in piwik.js
- don't init top controls if top controls container can't be found
- add default parameter for $urls in SitesManager.setSiteAliasUrls so site alias URLs can be reset
- fix bugs in UI tests database setup (including moving dashboard setup to UITestFixture class & keeping outside of
setUp function so --persist-fixture-data will work in case the super user is deleted)
- Add queryParamOverride testingEnvironment variable.
- fix screenshot testing page renderer's method of waiting for CSS images
- add margin bottom & left for widgetized controls for tests
- add diagnostics to upload_artifacts.sh script
|
|
|
|
|
|
daysSinceLastVisit more accurate!
|
|
|
|
(cherry picked from commit 1dc0e11)
|
|
|
|
|
|
(note to self: we should have a unit test checking the minified version is matching original piwik.js)
|
|
parameters name short.
Updated doc at: http://piwik.org/docs/tracking-api/reference/
and http://piwik.org/docs/page-speed/
|
|
* by default, send performance.timing.responseEnd - performance.timing.requestStart as generation time with the tracking request
* if the performance.timing API is not supported by the browser, don't send the metric
* new method disablePerformanceTracking()
* new method setGenerationTimeMs(generationTime) to set the generation after measuring it on the server side
|
|
|
|
D.C.'s changes thru-out, including the defense against window.prototype (which I think refers to var declarations shadowing window.prototype)
|
