Unneeded logs concerning not caching
-
Hello,
Even with debug disabled I’m getting a bunch of logs indicating pages weren’t served from cache either because of logged in cookie, it’s unsuitable (.xml) or The request method was not GET (POST).
These are filling my logs and seem unnecessary. If we’re reporting a page isn’t served from cache due to a reason I would suggest placing as an HTML comment on the page or in the Javascript console over the debug.log similar to how other cache plugins (Comet Cache, W3 Total Cache, etc) inform users.
All the best,
Cheers
-
Hello Garret,
As you suggest, those aren’t meant to be added to the error logs, but as HTML comment on the relevant page, and this only when WP_DEBUG is set to true.
This was reported before, and was supposed to be fixed.
Are you able to point when it’s happening? Previously, the logs were added during CRON events.Marc.
Hi Marc,
Looking at this again I realize they were logged to debug.log and just a little old as I’d disabled debug on production and didn’t realize when I found debug.log present that it was older logs. As I don’t see them in error_log I believe it’s adhering to the WP_DEBUG toggle.
That being said the logs I was seeing were mostly for GoogleBot hitting my .xml sitemaps generated by Yoast SEO. Some of the other logs were from logged in users just accessing the front end. And a few were normal traffic on pages in the exclude this. These were all being logged instead of appended to the HTML.
Cheers
Hi Garrett,
In version 3.0.12 we introduced a fix that was supposed to stop this logging, which was happening when wp-cron was triggered. V3.0.12 was released 24/Sep/2019.
Are those logs older than this?
Marc.
Hi Marc,
Trying to reproduce and haven’t been able to so most likely I updated my version of the plugin. Closing this for now and if it comes up again will dive deeper before reopening.
Cheers
Hi,
I am using WP 5.3 and WPO Version 3.0.13 and can not confirm this. I am still receiving plenty of messages in my debug.log
<!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: In the settings, caching is disabled for matches for one of the current request's GET parameters -->
is one of many messages that are currently flooding my log. I could not find anything in the settings do disable this, what am I missing?
Regards
JayHi Jay,
I’ve looked at this again, and it seems I had put a parenthesis in the wrong place. I’ve now fixed that, and will be in the next release (which should be next week).
Marc.
Hi guys, i am no technical expert and my problems sounds the same. not sure…
Some posts are not pre-cached and i dont know why? All pages or posts which are precached loading extremly fast – thats amazing. but why isnt the rest cached by wp optimize? Can you give me a hint how to figure that out?
Thanks, br,
ThomasHi Thomas,
Your issue is different. Could you open a new thread?
https://www.ads-software.com/support/plugin/wp-optimize/This will avoid spamming the other participants of this thread. ??
Thanks,
Marc.Another update has come and gone, and the debug.log is still flooded with these unnecessary messages. Please get them out of there!
Hi @hommealone,
Trying to get this sorted; could you please share some of the logs that were produced using the latest version of WP-Optimize?
Thanks.
Marc<!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD) --> [30-Nov-2019 00:58:24 UTC] <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: In the settings, caching is disabled for matches for one of the current request's GET parameters --> [30-Nov-2019 01:01:50 UTC] <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD) --> [30-Nov-2019 01:04:47 UTC] <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The file path is unsuitable for caching (/robots.txt) --> [30-Nov-2019 01:19:29 UTC] <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request extension is not suitable for caching --> [30-Nov-2019 01:19:32 UTC] <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request extension is not suitable for caching --> [30-Nov-2019 01:19:34 UTC] <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (POST), The request extension is not suitable for caching --> [30-Nov-2019 01:20:54 UTC] <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD) --> [30-Nov-2019 01:28:09 UTC] <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD) --> [30-Nov-2019 01:34:25 UTC] <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD) --> [30-Nov-2019 01:40:37 UTC] <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD) --> [30-Nov-2019 01:47:05 UTC] <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD) --> [30-Nov-2019 01:53:38 UTC] <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD) --> [30-Nov-2019 01:53:45 UTC] <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The file path is unsuitable for caching (/robots.txt) --> [30-Nov-2019 01:59:53 UTC] <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD) --> [30-Nov-2019 02:06:36 UTC] <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD) --> [30-Nov-2019 02:13:03 UTC] <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD) --> [30-Nov-2019 02:19:13 UTC] <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD) --> [30-Nov-2019 02:26:19 UTC] <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD) -->
etc, etc, ad infinitum
Hey Marc
In case in helps, here is a list of messages currently in my log:
<!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: In the settings, caching is disabled for matches for one of the current request's GET parameters --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: WordPress login cookies were detected, In the settings, caching is disabled for matches for one of the current request's GET parameters --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: WordPress login cookies were detected --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (POST), WordPress login cookies were detected --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The file path is unsuitable for caching (/robots.txt) --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (OPTIONS), In the settings, caching is disabled for matches for one of the current request's GET parameters --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request extension is not suitable for caching --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (POST) --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (POST), The request extension is not suitable for caching --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request extension is not suitable for caching, In the settings, caching is disabled for matches for one of the current request's GET parameters --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD) --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (POST), In the settings, caching is disabled for matches for one of the current request's GET parameters --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD), The request extension is not suitable for caching --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD), The request extension is not suitable for caching, In the settings, caching is disabled for matches for one of the current request's GET parameters -->
and many more for various sitemaps
Regards
Jayme to i got this messages :
!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (POST), The request extension is not suitable for caching --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: WordPress login cookies were detected --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: WordPress login cookies were detected, In the settings, caching is disabled for matches for one of the current request's GET parameters --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: WordPress login cookies were detected -->
- This reply was modified 4 years, 11 months ago by afadli.
Hi,
Thanks. I’ve found the issue and it will be in the next release.
Currently, these appear when WP_DEBUG is true. We’ve added an other conditions for them.Marc.
Thanks for that Marc! Looking forward to the update.
Wish list:
Rather than appearing in the debug.log file, it would be great if, as a user option, a WP Optimize-dedicated log file could be turned on when needed to help debug issues specifically related to this plugin. ??
- The topic ‘Unneeded logs concerning not caching’ is closed to new replies.