Closed adegans closed 1 year ago
It's a debug log and they're the only way to get insight in "issues" like #49 or #56. And it only happens during crossposting.
WordPress recommends disabling debug logging in production.
Only way to get rid of this is yet another flag which would have to be enabled together with both WP_DEBUG and WP_DEBUG_LOG, which is going to be even more confusing to users. It's certainly not easy to gather meaningful logging and I'd rather not make it harder.
On most hosts, when you set those two constants, WP will log errors and notices, etc., and debug statements to ~/public_html/wp-content/debug.log
, but on some they'll end up in ~/logs/php
or even ~/public_html/error_log
, maybe that's where some of the confusion comes from.
But WP_DEBUG is false. So something is going weird then.
Oh, that is weird.
So, the "normal" behavior is that nothing is ever logged if WP_DEBUG or WP_DEBUG_LOG is false.
But looking at what these constants do, it could be your host is set up to always log everything.
@adegans so you have WP_DEBUG
set to false
or 'false'
? https://wordpress.org/documentation/article/debugging-in-wordpress/#wp_debug
Bool. Not a string. Other errors such as fatal errors are logged as well. But all ‘WP stuff’ is off.
So, probably the server does log more than WP wants. And that’s fine it helps me keep track of the occasional issue. But these debug and ‘works as normal’ messages are not necessary for normal operation. Is there a way to turn it off for the plugin?
I just pushed v0.12.0, also to the WP.org repo, in which debug logging is/can be disabled. Settings > Share on Mastodon > Debugging tab. There, uncheck debug logging and hit "Save Settings."
Let me know if it somehow doesn't work.
Aha! I’ll check it out soon. 🙏
This isn't really necessary is it?
These are not errors, and certainly aren't relevant to put in the error_log.