WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] [Plugin: W3 Total Cache] Browser Cache error (7 posts)

  1. pxlar8
    Member
    Posted 4 years ago #

    Having just now upgraded to the latest version of TotalCache using the automatic update (0.9) and WP 3.0, I'm having trouble enabling the browser cache. Whenever I enable it from the General settings page and hit save changes I get a bunch of warnings like this:

    Warning: array_keys() [function.array-keys]: The first argument should be an array in /MY-URL/wp-content/plugins/w3-total-cache/lib/W3/Plugin/BrowserCache.php on line 282

    Warning: implode() [function.implode]: Invalid arguments passed in /MY-URL/wp-content/plugins/w3-total-cache/lib/W3/Plugin/BrowserCache.php on line 282

    (MY-URL is subbed in, of course). That's with all of the options unchecked on the dedicated Browser Cache settings page. If any of them are checked, I get more similar errors.

  2. kenwiesner
    Member
    Posted 4 years ago #

    I'm having the exact same issue as well. Same setup, 3.0 / 0.9.

  3. rashadow
    Member
    Posted 4 years ago #

    It seems the latest version is still the development version - there was a mix-up in the readme file - 0.9 is not a true stable release. According to Fred Townes, you can still use it as there has only been a couple of bugs reported so far, but you may want to revert to the previous version for stability. If you check the plugin page, you'll see that it's reverted back to 8.5 as the latest release.

    https://twitter.com/w3edge
    https://twitter.com/w3edge/status/16422120995

  4. Frederick Townes
    Member
    Posted 4 years ago #

    That's correct.

  5. pxlar8
    Member
    Posted 4 years ago #

    Okay, thanks. For what it's worth, it looks like the next version is going to have some really useful features. Looking forward to it.

  6. vikingjs
    Member
    Posted 4 years ago #

    For what it's worth, I found that setting line 110 of BrowserCache.php to read

    return array(

    fixes this issue.

  7. Frederick Townes
    Member
    Posted 4 years ago #

    The issue is already resolved in the latest development release.

Topic Closed

This topic has been closed to new replies.

About this Topic