Only log messages with certain log level

Hi @preliot

thanks for bringing this up and happy to look into this. We have partially different log levels but not fully everywhere yet. Are there maybe some entries that cause the most clutter?

Note that Matomo will only log it currently if WP_DEBUG is enabled.

For my project(s) i always enable WP_DEBUG & WP_DEBUG_LOG to catch all possible errors before users complain about them. The most simplest solution i see is to create a seperate constant for logging, something like MATOMO_DEBUG.

Or if you prefer to be on the safe side, first check the existince and value of MATOMO_DEBUG and then fallback to WP_DEBUG. ??

To answer your questions: I’ve checked the codebase and see about 83 calls to $this->logger->log. The ones that pop up often in my debug.log are the once mentioned.
They originate at:

Trackingcode.php

method add_javascript_code()

line 93
line 100

method add_noscript_code()

line 131

Thank you for your work on this excellent plugin!

• This reply was modified 4 years, 2 months ago by Preliot.

.

• This reply was modified 4 years, 2 months ago by jicks83.

Thanks for this @preliot

I have prepared a fix for this in https://github.com/matomo-org/wp-matomo/pull/355 where by default we now log less. Additionally we now support the ability to disable all logging and to force the logging of all messages. It’s documented in above link as well as in https://github.com/matomo-org/wp-matomo/pull/355

It will be included in the next release.

Thanks for mentioning it I could see how much it was actually logging ??

@tsteur I’m impressed by the speed! Thanks!

No longer “miles” of debug.log, i’m looking forward to it ??

Hope it helps ?? Let us know in case there’s still an issue afterwards.

BTW here’s the link to the FAQ where it’s documented also in case someone is looking for it: https://matomo.org/faq/wordpress/i-have-a-problem-how-do-i-troubleshoot-and-enable-wp_debug/