| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
* Better detection for cookies for browser plugins report
* rebuilt piwik.js
* improve comment
* Add method to enable cookies
* rebuilt piwik.js
* fix test
* no longer include cookie in fingerprint
* only ignore cookies in fingerprint for IE
* fix tests
* fix test
* tweak enablecookies
* rebuilt piwik.js
* send tracking request if needed when enable cookies
* rebuilt piwik.js
* tweak code
* update docs
* rebuilt piwik.js
* Update Visit.php
* fix tests
* rebuilt piwik.js
Co-authored-by: diosmosis <diosmosis@users.noreply.github.com>
|
|
|
|
* update doc blocks with new name
* submodule updates
* updates expected UI files
|
|
* many typo fixes in the code thanks to codespell
* reset submodules
I really need to stop using `git commit -a`
* reset change in library
* rebuilt piwik.js
* fix test
* updates expected UI file
Co-authored-by: sgiehl <sgiehl@users.noreply.github.com>
Co-authored-by: Stefan Giehl <stefan@matomo.org>
|
|
Problem I'm having is that I'm using a different DB backend which logs/shows errors in their DB layer. In this case what happens is that we're often calling `Option::set()` and the value doesn't actually change. In this case because no row changed, the update `$result` will be `0` and therefore it will try to insert the value which will fail because of duplicate entry.
I know we're catching the exception but in this case we can as well IGNORE any failure when we catch any exception anyway. This way there will be no more errors shown in the UI when using a different DB layer. I know the same problem can happen in other queries we do as well but it's particularly annoying with the option queries currently.
|
|
* various performance tweaks
* tweak so tests dont fail
* Update Manager.php
* Update Plugin.php
* cache custom variables properly
|
|
I updated the link tag for all php files with the new matomo link.
Not sure if it is realistic that this will get merged but I though that someday someone has to do this(?)
|
|
slow (#12550)
|
|
Conflicts:
tests/PHPUnit/phpunit.xml.dist
|
|
http://developer.piwik.org/api-reference/classes
|
|
|
|
still fail and I cannot figure out why
|
|
code, few refactorings, all as part of our code cleanup strategy
|
|
|
|
|
|
|
|
to use free/libre instead of open source
|
|
|
|
a Mysql reserved word.
Add quote identifier to prevent error: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corr
|
|
core/Option.php getValue function
|
|
parallel for faster archiving. There were multiple issues, for instance there were arrays of siteIds read and written in Options but options do cache all values in a class property so an update of an option does not get updated on another running archiver. Also all sites were reprocessed because of the time_before_today_archive_considered_outdated setting if the last archiving by another archivier was 10 seconds or longer ago. To prevent this only maintaining a list of to be processed siteids in db / filesystem helps so far
|
|
|
|
refs #4609
|
|
|
|
|
|
|
|
Option::get and Option::set and Option::delete
|
|
|
|
directories
|
|
|
|
|
|
Removed many Piwik_ functions, in Piwik 2 it is best practise to use the methods calls instead
Todo: finish converting core/ classes + convert plugins/ classes to use \Piwik\Plugin namespace + fix build + Merge master
|
|
|
|
Notice that auto refactoring has created a nested namespace. Not sure this is what we want - so we might have to edit those nested namespaces afterwards (I think they don't look so good)
|
|
Notice that auto refactoring has created a nested namespace. Not sure this is what we want - so we might have to edit those nested namespaces afterwards (I think they don't look so good)
|
|
creating new archive entry
|
|
Converting Piwik core source files, PHP, JS, TPL, CSS
More info: http://piwik.org/participate/coding-standards/
|
|
|
|
git-svn-id: http://dev.piwik.org/svn/trunk@6325 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
git-svn-id: http://dev.piwik.org/svn/trunk@6300 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
git-svn-id: http://dev.piwik.org/svn/trunk@4303 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
git-svn-id: http://dev.piwik.org/svn/trunk@4030 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
git-svn-id: http://dev.piwik.org/svn/trunk@4027 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
git-svn-id: http://dev.piwik.org/svn/trunk@3270 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
git-svn-id: http://dev.piwik.org/svn/trunk@2968 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
* Adding XML export of multi dim arrays
* Adding metadata for all plugins that define the API functions, metrics, dimensions, category, report name, metrics translations
* Could well be extended to include 100% of Piwik report metadata later
* cleaning up Goals API returned values to ensure consistency with other responses in piwik APIs
git-svn-id: http://dev.piwik.org/svn/trunk@2549 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
Also adding integration test suite in place.
* Adding new mechanism to trigger known tracking requests, then call all API methods get* and compare XML to the previous 'expected' XML.
* make sure overwritten config files are not read during tests. Use defaults from global.ini.php.
* piwik.php Tracker allow calling script to force Datetime and user IP for a specific request.
* Wrote 3 main tests
* wrong tracking requests should not return error and should not record anything
* standard one visitor, 2 visits, with page view, download, outlink and goal tracked
* Added integration test as an example in the ExampleAPI plugin (pretty simple to add testing code)
TODO
* Finish PiwikTracker and show it in UI
* Show how to use image based tracker in UI
* Add more tests (multi periods and multi sites) in Main.test.php
* Fix failing Config.test.php test (when ran via all_tests.php doesn't fail otherwise)
git-svn-id: http://dev.piwik.org/svn/trunk@2429 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
git-svn-id: http://dev.piwik.org/svn/trunk@2266 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
