Age | Commit message (Collapse) | Author | |
---|---|---|---|
2015-03-03 | Refs #7290 Fix tests and JSlint | mattab | |
2015-03-03 | Refs #7290 Remove feature that sets the same UUID across trackers | mattab | |
2015-03-03 | Refs #7290 - Set Visitor UUID not as a constructor parameter, but initialise ↵ | mattab | |
it from first party cookies | |||
2015-03-02 | Refs #7290 Fixing wrong logic in the JS tracker: make sure Visitor ID is ↵ | mattab | |
initialised properly in all cases | |||
2015-02-27 | Add note informing developers that there is a tight coupling between header ↵ | mattab | |
size and another file | |||
2015-02-16 | refs #7220 fixes #7218 refs #4633 prevent double url encoded url and referrer. | Thomas Steur | |
location.href and top.document.referer are both already URL encoded. To prevent double encoding we need to decode them. | |||
2015-02-13 | Refs #7167 add .length and update minified piwik.js | mattab | |
2015-02-10 | Store visitorID related to userID to cookies | jantlwoomy | |
2015-01-27 | fixes #7056 apply userId first before tracking anything to make sure userId ↵ | Thomas Steur | |
is always set and does not randomly create new visits | |||
2015-01-19 | refs #7043 do not cast a null value in userId to string as it would result ↵ | Thomas Steur | |
in a string null, check whether it exists instead | |||
2015-01-19 | fixes #7043 prevent a type error if userId is null | Thomas Steur | |
2014-12-22 | Removed Piwik\Loader: Composer's autoloader is now included in ↵ | Matthieu Napoli | |
core/bootstrap.php | |||
2014-11-13 | refs #6577 Return HTTP 204 instead of GIF for JavaScript tracking. | Thomas Steur | |
added a new url parameter send_image=0 to disable sending an image and instead response with a 204 code | |||
2014-10-17 | Remove irrelevant reference to a "security best practice" | Osman Surkatty | |
This change includes three things: 1. Removing note about omitting version number due to "security best practices" as not including a version number is actually more [security through obscurity](https://en.wikipedia.org/wiki/Security_through_obscurity) rather than any real security. 2. Removed the irrelevant Stallman reference. 3. Syntax highlighting. | |||
2014-10-14 | refs #6341 always calculate the remaining visitor cookie lifetime. | Thomas Steur | |
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. | |||
2014-10-14 | refs #6415 we have to update cookie timeout whenever the cookie name changes | Thomas Steur | |
2014-10-14 | refs #6341 do not extend cookie lifetime on each pageload and expire already ↵ | Thomas Steur | |
after 13 months instead of 24months. This is the now done by default. If you want different behavior you can call setVisitorCookieTimeout() manually | |||
2014-10-14 | refs #6415 better workaround for possible empty visits | Thomas Steur | |
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. | |||
2014-10-14 | refs #6415 #4996 better protection for 0 actions if content tracking is used. | Thomas Steur | |
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. | |||
2014-10-13 | refs #5940 moved files into a subfolder framework, added autoloader to ↵ | Thomas Steur | |
remove duplicated code to load autoload.php and to be able to register more autoloaders (eg for test files) on demand. This I got read of many includes that had to be updated all the time and that had to be updated all the time when moving iles | |||
2014-10-05 | refs #5940 databaseTestCase => integrationTestCase. Fixed some mentions of ↵ | Thomas Steur | |
integration => system | |||
2014-09-26 | Merge pull request #6258 from a4tunado/6257 | Matthieu Aubry | |
refs #6257 visitorUUID equal by default for each new Piwik.Tracker | |||
2014-09-26 | refs #6257 removed getVisitorId() from Piwik API | Vjacheslav Murashkin | |
2014-09-24 | refs #6257 Piwik.getVisitorId() function | Vjacheslav Murashkin | |
2014-09-22 | Refs #3490 Add `getUserId` Javascript helper + test | mattab | |
2014-09-21 | refs #6257 visitorUUID equal by default for each new Piwik.Tracker | Vjacheslav Murashkin | |
2014-09-19 | refs #4996 there is a difference between link tracking enabled and ↵ | Thomas Steur | |
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 | |||
2014-09-15 | refs #4996 do not fallback to GET if POST fails otherwise we might track twice | Thomas Steur | |
2014-09-15 | refs #4996 make sure we always track same content name and piece in an ↵ | Thomas Steur | |
interaction and also have to use default values | |||
2014-09-15 | refs #4996 tests should now work in case Piwik is installed in a ↵ | Thomas Steur | |
subdirectory although could not really test it. Also encode redirect uri | |||
2014-09-14 | refs #4996 also display URL of media on hover next to the image. added some ↵ | Thomas Steur | |
documentation | |||
2014-09-14 | refs #4996 in case we are in an overlay session we should not track. Check ↵ | Thomas Steur | |
could be maybe moved to trackCallback in general? | |||
2014-09-14 | refs #4996 we have to add build a fully qualified URL of the content piece ↵ | Thomas Steur | |
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 | |||
2014-09-14 | refs #4996 some fixes, prevent JS errors on FF<9 and IE6, add random string ↵ | Thomas Steur | |
to piwik.js to prevent caching sometimes | |||
2014-09-13 | refs #4996 fix js error on IE6-IE8 because indexOf is not defined there. ↵ | Thomas Steur | |
also added removed update script again | |||
2014-09-13 | might fix an issue on IE6 | Thomas Steur | |
2014-09-13 | refs #4996 content JS tests do now run on IE10, latest FF + Chrome + Safari ↵ | Thomas Steur | |
+ Opera and on my local phantomjs but not on travis phantomjs | |||
2014-09-13 | refs #4996 better cross browser compatible tests. should now run on phantomjs | Thomas Steur | |
2014-09-12 | refs #4996 apply enableLinkTracking first before trackContentImpressions or so | Thomas Steur | |
2014-09-10 | merged userid | Thomas Steur | |
2014-09-10 | refs #4996 many new tests and many bugfixes. Tests should be done now except ↵ | Thomas Steur | |
for cross browser support. I fixed many issues as I did not consider that link tracking may be disabled or enabled and the behavior should be different in such a case. | |||
2014-09-09 | refs #4996 fix some tests in latest safari and opera | Thomas Steur | |
2014-09-09 | refs #4996 more bugfixes, more work on cross browser, added possibility to ↵ | Thomas Steur | |
track content via php tracker (not tested yet) | |||
2014-09-09 | refs #4996 more tests and bugfixes, improved API, some work on crossbrowser ↵ | Thomas Steur | |
support | |||
2014-09-09 | refs #4996 many new tests and bugfixes, worked around some JSLint regexp ↵ | Thomas Steur | |
issues and disabled the whitespace check which makes no sense to me. The tests do now run again in PhantomJS but report a lot of failures and I have not looked yet into it. | |||
2014-09-08 | refs #4996 many new tests and bugfixes. Also fixed > 100 JSlint errors but ↵ | Thomas Steur | |
still 4 or 5 errors I could not fix so far | |||
2014-09-05 | refs #4996 do not track an interaction as an event | Thomas Steur | |
2014-09-05 | refs #4996 more tests and bugfixes. I am no longer so sure whether we ↵ | Thomas Steur | |
actually should track the redirects as an event. I do not really see an advantage here as the pageview will be tracked later anyway. Makes it rather confusing... | |||
2014-09-05 | refs #4996 changed methods to have them better testable, instead of sending ↵ | Thomas Steur | |
the request directly in the helper / private methods we return the request and send the request in the actual tracker callback method | |||
2014-09-05 | refs #4996 and even more tests and more bugfixes | Thomas Steur | |