Allow each tracking record to contain arbitrary tags.
Those tags are generated via an API and can be extended by foreign
extensions or for individual projects.
Existing operating_system was moved to this new feature.
The update command allows to migrate existing records to this new
feature.
Those flags can be used when configuring widgets.
A new flag was added bot:yes and bot:no.
Bots are now tracked but flagged.
That new feature allows to build fine grained reports and makes the
extension way more flexible. Possible new implications:
- Show visits from none bots
- Show visits from bots
- Show visits from specific bot
- Add color to page views per page (bar chart)
to color bot or none bot
WIP:
- Update Yaml file to work like before, no bots in widgets
- Add documentation (widgets)
- Add documentation (migration *.yaml)
This is required by list module, As we define a languageField.
Might be a bug, but BackendUtility::translationCount() will fail if 2nd
field is missing.
Fixed in current TYPO3 master and therefore with v11.3,
see: https://review.typo3.org/c/Packages/TYPO3.CMS/+/69180
Allow Integrator to define rules to track views of records.
This allows to add tracking to extensions like tx_news.
Integrators are able to define matching rules on current request. If a
request matches, the record is stored as individual view beside existing
pageview.
Relates: #14
Extract operating system from user agent and store it in database
record.
Another widget is added which displays the page views per operating
system.
An command is provided which will update existing data.
TYPO3 would otherwise run into trouble.
TYPO3 expects pid to be an integer or string.
Resolving pid due to a configured pid column via select or groups,
would result in an php array.
