Age | Commit message (Collapse) | Author |
|
* Forbid unused use statements
* Fix some incorrect classnames
* fix tests
* remove unused use statements
|
|
* update doc blocks with new name
* submodule updates
* updates expected UI files
|
|
|
|
(#14622)
* Add more types of actions to ManyVisitsWithMockLocationProvider fixture.
* fix test change
* update expected test files
* Handle ranking query others row properly in contents & events archiver.
* Use custom ranking query specific others label and handle by default in DataArray::asDatatable().
* Updating expected test files.
* Use strict compare since label can be 0 apparently.
* Update expecred test files.
|
|
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(?)
|
|
* refactor archivers to support multiple idsites
* added a test to ensure multiple sites work
* add comment
|
|
* Improve memory performance of event queries
* also improve memory of action archive queries
* improve memory usage for content tracking
* fix typo
|
|
|
|
|
|
in SQL logic
|
|
|
|
track content via php tracker (not tested yet)
|
|
this I noticed a few things that need to be changed and that do not work, also many possible new features for V2. Already updated a few things but will need to adjust more things before writing tests
|
|
it simpler and now the correct label is displayed in a subtable. I should not copy/paste code that I do not understand :)
|
|
mandatory created a new column content_name for now (instead of existing idaction_name, will maybe remove it again). Otherwise it is hard to know whether it was a content action or not and the actual problem was that maybe other actions already define an idaction_name which might be different to content_name. We need the content_name along other actions to match an interaction with an impression. Next: The client side and the redirect...
|
|
should work (contentName => contentPiece and contentPiece => contentName). Next step: Matching interactions with impressions then this part is nearly done hopefully
|
|
a report
|