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.

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.

refs #4996 there is a difference between link tracking enabled and 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

refs #4996 make sure we always track same content name and piece in an interaction and also have to use default values

refs #4996 tests should now work in case Piwik is installed in a subdirectory although could not really test it. Also encode redirect uri

refs #4996 in case we are in an overlay session we should not track. Check could be maybe moved to trackCallback in general?

refs #4996 we have to add build a fully qualified URL of the content piece 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

refs #4996 content JS tests do now run on IE10, latest FF + Chrome + Safari + Opera and on my local phantomjs but not on travis phantomjs

and restore Transitions tests which I deleted by mistake earlier

refs #4996 worked on detecting content name, piece and target. Next: Sending the impressions to Piwik via bulk tracking

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

added possibility to get/create a tracker by using "Tracker = AnalyticsTracker.getTracker" instead of "Piwik.getTracker". Variable will be set only if no such variable is defined yet

refs #5049 log to console (if exist) if methods, that are applied first, are registered multiple times. We do not throw an error as this would prevent script execution

Close PR#243

Should make the JavascriptTests build green again

- 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