-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
"set_404" in error log #42
Comments
Additional to this I also get
|
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?The text was updated successfully, but these errors were encountered: