fruitllama

Why is there no support for this broken plugin?

Thanks mucho for the reply mitcho.

Last question, promise.

With the improved caching performance in 3.2 beta 3, would it be better to switch back to custom table-based caching, or do the improvements apply to postmeta caching as well?

Thanks for your time.

mitcho

Thanks for the update on the beta. Quick couple of questions for you.

1. How does one clear the cache when using postmeta caching.

2. The “caching performance issues (one kind of major) have been resolved” are for postmeta-caching or custom table caching or both?

Thanks for your time. Looking forward to the final version of this.

PS I’ve been using 3.2 beta 3 with postmeta caching, and have not had any major issues so far with 5000 posts.

Thanks for the reply Frederick.

Quick follow up question,

What about the default WordPress rules, would the following work with no problems? Or do the default WordPress rules have to be on top of everything.

# CUSTOM rules
redirect 301 /url01 /url02
…
# BEGIN WordPress
……
# BEGIN W3TC Browser Cache
……
# BEGIN W3TC Page Cache
……

Thanks in advance.

Like I mentioned in another post,

Can we please have proper documentation on how to setup .htaccess for this plugin.

Pretty please, and thank you.

Frederick, can’t seem to find the instructions for fragment caching in the 0.9 FAQ.

I’ve also replied to a support ticket email from this morning.

Thanks.

Yes please.

Is this feature available in ver 0.9?

How do we enable it?

Where can we find instructions on configuration?

Peace be with you.

|_|

Absolutely dying for this feature.

This, with the existing code will kill all the other cache plugins.

Hi there.

Any idea when this will be implemented? Even just a rough timeline works too.

We won’t hold it against you if it slips. ??