Viewing 3 replies - 1 through 3 (of 3 total)
  • Ramanan

    (@superpoincare)

    Thread Starter LordSilver

    (@lordsilver)

    Well, that’s a big lie.

    Updating from 4.2.3 to 4.2.4 breaks the “Prevent caching of objects after settings change” feature: so now every resource is followed by a query. Not to mention the others well known bugs like CloudFlare API not working and so on. How can they even state it’s compatible? Ridiculous.

    Another thing I’ve recently discovered is that the “Cache Preload” feature doesn’t use any user-agent (they usually put “W3 Total Cache/0.9.X.X”) for fetching the pages on the web-site, thus it generates 500 errors in the access_log if you have rules for blocking that kind of requests, which happened to me having iTSec plugin installed for security.

    Honestly I’m quite disappointed seeing how poorly supported is this plugin, which is just the most popular one for caching on WordPress.

    Ramanan

    (@superpoincare)

    LordSilver,

    There are issues of course but the advantages far outweigh these issues.

    There are known conflicts between various plugins. Perhaps the iThemes developers should have taken it into consideration.

    Yep seems like the query string is no longer generated after the WordPress update. So agree it should have been resolved before having changed the readme text.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Fake New 0.9.4.1 Version?’ is closed to new replies.