matomo-org / matomo-org/plugin-QueuedTracking
When enabling queued tracking in plugin settings, perform the tests from Test command
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 87
- Forks
- 41
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 7
Description
This way we will proactively let the user know when there are some issues. Eg we could detect whether the `eval` command was disabled see https://github.com/piwik/plugin-QueuedTracking/issues/24#issuecomment-164672172
We won't detect all errors since some errors might occur when there is no memory left but at least we can be more or less sure the tracking will work.
If a test fails, we won't enable the queued tracking and instead show an error in the plugin settings page.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the plugin settings page and the existing Test command. Trace how queued tracking is enabled and how test failures are currently reported. Done means enabling queued tracking runs those tests, leaves it disabled when a test fails, and shows an error in the plugin settings page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100