0.9.5 fail -> Replace it with 0.9.4.1

What went wrong for you? Version 0.9.5 working fine for me

Thank you so much! I got my client’s website back thanks to this tip. They’re running an older version of PHP, and their previous developer who set up the web host went AWOL, so I was in the process of getting them moved over. This helps greatly to have figured out the issue and get a download link from you.

Thanks again!

I am running PHP 5.4 and PHP 5.6.26 and the plugin still broke our sites. 22 out of 25. 3 magically weren’t affected but run the same code, on the same server. Working to figure it out ??

• This reply was modified 8 years, 2 months ago by WPJEDI.

Funny story…

After I got it running again (by replacing it with the old stable version) I got me the following plugin (this is no advertisement, just what I did):

https://de.www.ads-software.com/plugins/wp-rollback/

Unfortunately I am using the wordpress.com site autoupdate service.

So I ran into the same problem again. As I still had the backend open, I could use the WP-Rollback plugin and it worked again (for me, just reporting here).

But sadly, I can not disable it for w3tc anymore within WordPress.com. When I try to disable it for w3tc it sneakily just updates it again. And after that I am not even able to list the plugins anymore within WordPress.com, as it gives me an error.

I tried other ways to disable updates, which unfortunately didn’t work:

https://www.wpbeginner.com/wp-tutorials/how-to-disable-automatic-updates-in-wordpress/

I was trying the following approach:

add_filter( ‘auto_update_plugin’, ‘__return_false’ );

So what did work this time: In the backend of my website (not WordPress.com), I:

* rolled back to 9.4.1
* disabled the plugin.

Now I logged into the WordPress.com backend and:

* disabled auto update for w3tc

By the time I reached the option, it had it updated to 0.9.5 already. But this time, it didn’t break the website.

Next step:

In the backend of my website I:

* Rolled back to 0.9.4.1 again.
* Activated the plugin.

Logged into WordPress.com:

* Checked the plugin state, and IT WORKED. No automatic update anymore.

Finally, using the private surfing function of my browser.

IT STILL WORKS!

Closing Time!
Finally leaving work for today, happily

W3TC does not update automatically this sounds like you were using the jetpack update service which is not a fault of W3TC. If you could say what the error was that is 1k times more useful than just saying its a fail.

Thank you, webrockers. 9.5 broke my homepage slider. Its a jquery feature built into WP theme 2014. Am running 4.6.1.

Before updating to the destructive 9.5 update, I backed up my settings. Deleting 9.5 and uploading the 9.4.1 zip eliminated my known issue. I uploaded my saved settings and am safely back to .9.4.1. I do notice that most reviewers of 9.5 rate it “broken”. Most as in 10/1 ratio of those who report.

It is hard decision to roll back into 4.6.1 since there is a High Risk XSS Vulnerability Discovered in W3 Total Cache Plugin

@destac

I was saying:

Unfortunately I am using the wordpress.com site autoupdate service.

I didn’t blame w3tc for the automatic update.

You are saying:

If you could say what the error was that is 1k times more useful than just saying its a fail.

V 0.9.5 seems to break websites for various reasons and I was under pressure to find a working solution for my website. This thread was created as a suggestion for others, as it works for me.

And IMO the release is a fail. I didn’t say the plugin itself is crap.

I am wondering how it could happen that such an experienced coder like Frederick Townes could release an obviously faulty and untested (or at least insufficent) version of a plugin that has 1+ million Active Installs.

• This reply was modified 8 years, 2 months ago by webrockers.