Viewing 13 replies - 31 through 43 (of 43 total)
  • This is a bigger problem than I thought. It happens in basic mode to and our site is being slowly delisted from search results.

    WTH? Why hasn’t the author acknowledged this? Traffic is falling and we cannot operate without a page cache.

    This plugin is broken for everyone using basic file cache or advanced file cache. Because that happens on shared hosting this plugin is broken for most of the users.

    INSANE!

    Thread Starter Nic Windley

    (@nisiwi)

    Try adding this (below) to your top level (root) htaccess

    AddDefaultCharset utf-8

    Rules were still getting replaced by W3TC for me so not always reliable.
    I fixed it with a permanent rule.

    That didn’t work. We’re still getting errors. I’ve been told to remove W3tc and replace with WP-Supercache which works fine. The author had two months to address this and didn’t.

    Thats not good at all.

    Thread Starter Nic Windley

    (@nisiwi)

    Firstly remember that its free – although I agree the troubles with caching plugins are frustating especially as they are becoming so essential.

    Secondly it could be a server config issue so make sure you’ve checked all those things that could cause an encoding error.

    Also are you GZIPPing twice ? i.e. is something already compressing parts of your site ?

    i want create new cache server. how this possible. and how was create this????????

    Server config? No way. Not after years of use and this one update messing everything up.

    I’ve said before compression is turned off completely. Serverwide and in WordPress.

    We aren’t having any problems now that we are using WP-Supercache. So for us its resolved. We can’t use a product that doesn’t QA but I hope its finally fixed.

    Adding

    AddDefaultCharset utf-8

    to the htaccess file in the wp-content/cache/page_enhanced folder fixes it for me, except that every time I disable and then activate W3TC the plugin re-writes the code, and I have to add it back again. I hope Frederick with address this in the next update.

    Thread Starter Nic Windley

    (@nisiwi)

    add AddDefaultCharset utf-8 to your top level / root htaccess and you no long need to worry about W3TC overwriting it robnalexpress

    @ Nic Windley- Thanks! That seems to have done the trick!

    I had this problem too except that my entire page had nothing but crazy random characters whenever the W3 Total Cache was enabled. The above fix using .htaccess did not work.

    After countless googling, I found out that Bluehost where I host my sites, had updated all WordPress installations on their servers as well as updated all W3 Total Cache plugins because of a security vulnerability. They did so without warning.

    My site is a custom theme that used an old TwentyTen theme as the starting point. So what I did was copied the code from my header.php file and pasted it into the header.php file of a newer theme. I only copied the code after <body <?php body_class(); ?>> and pasted it accordingly. That did the trick.

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    Have you guys tried enabling compability mode on the Page Cache settings page when using Disc:Enhanced?

    @jimario Your original problem looked ?like a case of having multiple gzip features enabled. Perhaps some other plugin or some setting in htaccess. Those random chars is due to gzip being run twice. The random chars in those cases covers the whole cached pages.

    This fixed my problem in Joomla! too!! Whey hey!

    Yohan Perera

    (@thevirtualpreacher)

    I had the same problem and adding AddDefaultCharset utf-8 to wp-content/cache/page-enhance/.htaccess did not work. (I did not try adding it to /.htaccess though). However I tried completely uninstalling the plugin and re-installing and the problem vanished.

Viewing 13 replies - 31 through 43 (of 43 total)
  • The topic ‘page cache disk enhanced – ? characters appear’ is closed to new replies.