I found your support site. I’m still lost about about question 1. With question 2, I guess with caching logged in users, my question is what happens when the specific user’s information is updated in WordPress? For example, when the user get’s a new feature which should appear within a WordPress page, does ZenCache create a new cache for that user? Thanks for any clarification.
@andrew55 Please see my replies below:
1. Is there a method of caching a page, but not caching certain elements on that page (such as html within the page, html within a widget, etc.). If so, does this involve including the html (we don’t want to cache) in tags, or another method?
We refer to this feature as “dynamic fragmentation”. We have a feature request open here. See also this related KB Article that explains things further and offers a few alternate solutions.
2. Could you please explain a bit more about how the plugin provides caching for logged-in members. We use aMember (membership site) in WordPress and are looking for a method to accomplish partial caching.
ZenCache detects many common changes that may affect a user-cache and then clears the user-cache when appropriate. However, other plugins that affect users, such as aMember, would need to be made compatible with WordPress caching plugins so that when something changes on the user-side, the plugin tells WordPress that the cache should be cleared.
ZenCache includes an API that allows you to write the necessary hooks so that when another plugin, such as aMember, makes a change to a user, you can tell ZenCache to clear the cache for that particular user. See the last example in this tutorial: Clearing the Cache Dynamically
