Error seems to have popped up after 4.5.1 update

  • Resolved davebach

    (@davebach)


    8 years, 5 months ago

    Recently updated to WP 4.5.1 and current version of W3TC is 0.9.4.1. When not logged in, I am seeing the following error at the top of all pages before and after the page renders:

    Warning: mysqli_num_fields() expects parameter 1 to be mysqli_result, boolean given in /home/########/public_html/wp-includes/wp-db.php on line 3021

    This error is not seen when I view the website while logged in.

    When I disable W3TC, the error goes away. If I switch themes to Twenty Fifteen the error is still there. I am using Page, Database, Object and Browser caches. No settings have been changed recently. Web host is InMotion.

    Any thoughts are appreciated.

    Dave

    https://www.ads-software.com/plugins/w3-total-cache/

Viewing 7 replies - 1 through 7 (of 7 total)

  • Yeah, I got the same message especially when I installed iThemes Security plugin

    If you are on a shared host disable object and database caching.

    Thread Starter davebach

    (@davebach)

    Yes, shared hosting. Turning off just database caching fixed it. Thanks.

    Two additional sites on the same host have both database and object (and page and browser) caches enabled, so I’m not sure why it works on some. Nor do I remember why they are on in the first place, it was probably set it and forget it a year ago.

    I have seen that minify does not work with some themes, so perhaps database is the same.

    I also use iThemes Security as israa2010 mentioned, but I couldn’t say if that’s a factor since I have that on every site.

    how can you turn of database caching? I got the same error

    Ashok

    (@bappidgreat)

    Hello csandreas1

    Please go to Dashboard > Performance > General Settings > Database Cache and uncheck the box for enable > Save.

    https://take.ms/LTmKH

    Have an awesome day!

    Cheers
    Ash

    Matt

    (@mugwumpman)

    I had to disable all caching. Database & object wasn’t enough, all of them had to be disabled. Do we know if this error will be fixed with an update some point soon, so we can start making use of caching again?

    Ashok

    (@bappidgreat)

    Hello Matt

    As far I have seen in an article that the developer is working on the fixes, so I believe very soon we will see something good ??

    https://wptavern.com/frederick-townes-confirms-w3-total-cache-is-not-abandoned

    Have a good day!

    Cheers
    Ash

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Error seems to have popped up after 4.5.1 update’ is closed to new replies.