seb30303
Forum Replies Created
-
Does the error stop if you disable the Shield Security plugin?
Hi Paul,
Thanks again for your reply.
I’m not particularly familiar with the internals of WordPress but if you are using their DB class then one would think that it should take care of the low level stuff like freeing query results.
I will add some more logging and see if we can get to the bottom of it. If there’s anything relevant to Shield Security, I’ll update this thread.
I couldn’t see any WP constant which would enabled database query logging – only SAVEQUERIES which saves queries to an array. But there was a link to this plugin which looks like it will do the job: https://ww.wp.xz.cn/plugins/query-monitor/
All the best,
SebHi Paul,
Thanks for the quick reply. I realise that this error occurs in the *next* database query after an incomplete query using mode MYSQLI_USE_RESULT, where either the full query didn’t get read or mysqli_result::free() wasn’t called.
I still strongly suspect the Shield Security plugin as it is doing the query literally every time this error occurs, so it’s fair to assume it’s the most likely candidate to have done the previous query.
Also, aside from the core WordPress itself, it is the only thing which has updated recently on the server. The only other plugins present are Akismet Anti-spam and XML Sitemap Generator for Google. The WordPress site is actually quite a small / low traffic site which lives on a powerful VPS (many GB), mainly used for hosting other things.
Anyway, I thought I’d let you know in case you want to check the recent changes in your code.
I’ll keep an eye on the error and see if we can narrow down the cause more specifically. Do you know if it’s possible to enable logging of database queries within WordPress so we can find the preceding query?
Thank you,
Seb