Support » Plugin: Lite Cache » Why a new plugin?

  • I’m just curious. Why did you make this plugin? When should I use this plugin and not HyperCache?

    I will say though that I’m very excited about it, in particular due to the bbPress support. To date this is the only bbPress-compatible caching plugin I’ve found. We will be testing it on during the next few days, fingers crossed!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Stefano Lissa


    I was in a hurry with a site and hyper cache has a big problem with paged comments. Lite cache solves that problem and probably is more efficient that hyper cache.

    About bbpress, you should never cache the bbpress pages: they uses (I believe even in latest version) a wp-nonce technique to block spam and that does not work with caches. Or, at least, set the cache expire time to less than 12 hours, usually it’s enough.

    I thought about using the same technique of lite cache in hyper cache, but it’s not an easy step :-).


    What do you mean never cache bbpress pages? Says right there in your changelog, “added bbPress integratoin” ^^

    And we’ve been running it on without a hitch. It drastically reduced the load time for unregistered users, and worst case scenario they just lose out on the latest reply to a topic. We set the expire time to 2 hours. I’m very happy with it:

    Recommended caching plugin for bbPress: Lite Cache

    Plugin Author Stefano Lissa


    Hi, actually the plugin contains code to intercept new topics or replies and invalidates the cache because a forum has tow possible for a topic: the one shown to logged in users and the one shown to anonymous users.

    The plugin should be set to not cache the pages when user are logged in (with a forum), otherwise they can see a topic without the box to reply.

    But worse, since the protect the new reply and new topic with wpnonce, if the wpnonce values (store in page) expires bbPress blocks the attempt to post something.

    So, Lite Cache works well with bbPress state that it is disabled for logged in users and the forum is limited to logged in users.

    At least… it should! 🙂

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Why a new plugin?’ is closed to new replies.