Why Has W3 Total Cache Stopped Development?

I started testing WP Super Cache and Autoptimize for minification. Too early for a conclusion.

Autoptimize does no work properly on my multisite setup.

I was on the verge of buying Total Cache Pro. I am glad I figured out how lazy the devs are before I spent money on it.

WP Super Cache works perfectly (it also predates W3 Total Cache and it has always been rock solid).

For me, Autoptimize is at 50%. Works just fine on one site, doesn’t work on another. It also doesn’t process @import in css. I haven’t tested in multisite.

Update: after running with WP Super Cache for a week, I see the site speed as reported by Google Analytics has improved considerably, see https://oi58.tinypic.com/muig4k.jpg

–double post–

I will make the switch today. W3 Total Cache was stopping me from upgrading to WP 4.0, glad I can do that now. Thanks for the info gaspy.

W3 Total Cache is both under active development and compatible with WordPress 4.0.

Well… then update the WP plugin page so people know.

https://www.ads-software.com/plugins/w3-total-cache/

Also, stop taking peoples money for “plugin configuration” without actually doing the work.

@Nickf4n: I don’t think you understand how that page works, we don’t “control” the rating.

If you’d like to discuss an issue with a professional services project, email is the appropriate channel.

I understand how it works.

You simply need to edit the readme.txt in the w3-total-cache folder so it says…

Requires at least: 3.2
Tested up to: 4.0

Yours currently says…

Requires at least: 3.2
Tested up to: 3.9

It would take you very little time to do this. It would also allow your thousands of users to update to 4.0 without concern of breaking their site.

Not sure why you are claiming you have no control over this. It is simple and takes no time at all.

Thanks for the feedback.

I catch you out in a lie and your only response is “Thanks for the feedback.”….

Stay classy Willie Jackson.

Probably going to post this to Reddit.

The rating I referred to is the user-reported component. Many people vote for W3TC “not working” when they misconfigure it (minify, for example) and it breaks their layout.

That’s what I was speaking to specifically, you’re exactly right about the update we can make.

We’re actually preparing to release the next version of the product (0.9.2.5) and I didn’t see much value in continuing exchanges here so I thanked you for your feedback and got back to work.