Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: option to disable tracking failure notifications #14447

Closed
timodenissen opened this issue May 14, 2019 · 4 comments · Fixed by #14448
Closed

Feature request: option to disable tracking failure notifications #14447

timodenissen opened this issue May 14, 2019 · 4 comments · Fixed by #14448
Labels
not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org.

Comments

@timodenissen
Copy link

Hello,

as asked in the forum [1]: please add an option to disable the automatic notifications about tracking failures.

Cheers,
Timo

[1] https://forum.matomo.org/t/how-to-disable-e-mails-about-tracking-failures/32854

@fdellwing
Copy link
Contributor

Is it enough to provide an option via config.ini.php or do we need to make this configurable via UI?

@timodenissen
Copy link
Author

An option in config.ini.php is fine for me, perhaps at a later time an option via UI?

@fdellwing
Copy link
Contributor

Did a PR for this, but others have to decide if that is enough ;)

You can test the change by applying this patch: https://patch-diff.githubusercontent.com/raw/matomo-org/matomo/pull/14448.patch

@mattab mattab added the not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org. label Jul 23, 2019
@mattab
Copy link
Member

mattab commented Jul 30, 2019

documented in new FAQ: How do I disable tracking failure notification emails?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants