{"id":377,"date":"2015-03-09T19:04:23","date_gmt":"2015-03-09T18:04:23","guid":{"rendered":"https:\/\/wp-rocket.me\/blog\/?p=377"},"modified":"2021-06-25T10:55:02","modified_gmt":"2021-06-25T08:55:02","slug":"why-we-disable-the-autoupdate-option","status":"publish","type":"post","link":"https:\/\/wp-rocket.me\/blog\/why-we-disable-the-autoupdate-option\/","title":{"rendered":"Why Are we Disabling the Auto-Update Option?"},"content":{"rendered":"

In January 2015 we launched\u00a0the Auto Update feature in WP Rocket 2.4<\/a>.<\/p>\n

Soon, we will launch WP Rocket 2.5 without the Auto Update Feature<\/strong> and before you update to 2.5 you must\u00a0first\u00a0deactivate this feature.<\/p>\n

Why Are\u00a0we Removing this Awesome Feature?<\/h2>\n

No doubt this question will be asked because for many\u00a0of you, this feature worked fine and saved you time.<\/p>\n

But for many others, this feature created\u00a0issues like the non-desirable deactivation of the plugin, or worse, some fatal errors on update<\/strong>.<\/p>\n

We don’t want this to happen again, so we decided to remove it<\/strong>. Removal seemed to be the best option since auto-update\u00a0is\u00a0not a caching feature, and therefore not critical to\u00a0the functioning of the plugin. \u00a0It\u00a0was “just” a convenience for some of you.<\/p>\n

We know that it can be disturbing to remove a such feature, but we want the best for you and we don’t want to cause any issues on\u00a0your websites<\/strong>.<\/p>\n

Technically, What Was Wrong?<\/h2>\n

First, I’m the developer in charge of this feature, and since WP Rocket is backward compatible to WordPress 3.1, I wanted that feature to be backward compatible to WP 3.1 too.<\/p>\n

But as you may know, the auto-update feature in WordPress core was\u00a0added in WordPress 3.7<\/strong>.<\/p>\n

So I decided to create my own way of auto-updating<\/strong> and it worked perfectly from 3.1 to 4.1. Well, it worked perfectly for me, but not for all 18,000 of our customers’ websites<\/strong>. I can’t test all servers and configurations of course.<\/p>\n

In reality there are\u00a0too many factors that can lead to a plugin deactivation<\/strong> and we don’t want this!<\/p>\n

Earlier in 2.5-beta1, I tried to only support WP 3.7+ using the hook auto_update_plugin<\/em> but for some reason, some plugins like Contact Form 7 were also deactivated after the upgrade…<\/strong><\/p>\n

So this is why we decided to remove auto-update entirely.<\/p>\n

<\/div>\n\t