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)
Use .gitattributes to tell git what to ignore during exports.
This will prevent GitHub from adding those files to an archive.
Composer will use the GitHub archive as distribution while downloading.
This prevents none necessary files on production systems. This also
reduces file size of archive and should save disk space and other
resources.
TYPO3 queries information of translations.
The fix adds database indices which are also applied for tt_content
by TYPO3 itself.
This fixes slow loading times of the list module.
Require compatible version, no need to be to fancy.
The given version is compatible with same set of combinations.
We still ignore 7.3 as there is no compatible setup.
PHPStan was released with first stable public version 1.x.
The version is updated together with extensions.
The new version finds new issues which are solved right away to not
break CI.
Set COMPOSER_TOKEN in each step, as this broke some when.
Also disable "coverage", to improve speed, inspired from EXT:tea.
Use "include" to remove duplicate jobs with different versions, inspired
from EXT:tea.
Remove caches as they were not properly configured. Maybe add them later
inspired from EXT:tea?!
Merge multiple composer steps into one to circumvent mixed up state.
Otherwise some versions might be locked, preventing downgrades.
Also should save bandwidth and time by only installing dependencies once.
- Extend CI to test everything against PHP 7.3
- Update composer to allow installation with PHP 7.3
- Remove dependency checker, install loosely within CI to get compatible
version with actual PHP version.
- Adjust CI to use PHP compatible MySQL versions.
Relates: #69
Provide database index for widgets which is used by widget queries to
fetch data way faster, e.g. 0.1 instead of > 5 seconds in one concrete
project.
Relates: #63
Pages can not be copied by administrators as DataHandler will copy all
pages, including tx_tracking_* tables.
Those are not allowed on tables which will result in error messages.
A test is added to simulate the action and ensure it doesn't fail with
errors.
Results: #52
This allows configuration via PHP.
It also combines code sniffer and php cs fixer.
Used commands:
composer remove --dev squizlabs/php_codesniffer
composer req --dev symplify/easy-coding-standard
./vendor/bin/ecs --fix
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
It will report old TYPO3 versions which we support, but don't require.
Therefore it does not provide a benefit but breaks builds.
The package is intended for projects, not libraries.
Not all dev dependencies are v2 ready.
maglnet/composer-require-checker has a dependency to
ocramius/package-versions version which requires v1 composer API.
Once a newer version is required, we can use v2.
