Closed paulchen closed 6 months ago
Additional to this I also get init
spammed into my debug.log file:
[26-Mar-2024 13:01:53 UTC] init
[26-Mar-2024 13:03:53 UTC] init
[26-Mar-2024 13:07:06 UTC] init
[26-Mar-2024 13:08:06 UTC] init
[26-Mar-2024 13:10:06 UTC] init
Hey! Thanks for reporting this bug. It's entirely my fault, these debugging statements should not have made their way into the released version of the plugin. I will release a new version of the plugin with these removed right away.
I have released version v3.1.1 of the plugin which addresses this issue. It is available on the WordPress plugin directory.
Thank you for the quick response. I have just applied the fix, and the log messages are now gone :)
@joppuyo Thanks for fixing this, after updating the plugin the log messages do not appear anymore. :)
Today at 20:51, the plugin on my WordPress instance was updated from 3.0.5 to 3.1.0. Since that time, entries containing only the string
set_404
started to appear in the error log:At each of these timestamps, the access log shows an access to a location that does not exist (nothing related to an attachment), leading to a 404 error, e.g.:
I traced this down to https://github.com/joppuyo/disable-media-pages/blob/master/lib/Plugin.php#L53 which was added recently.
Is that (together with a similar statement on line 33) some debug output that should actually be replaced by a call to the
debug()
function?