iPad Guy

I disabled automatic updates in WordPress (link). I got burned by bugs in JetPack 3.5, rolled it back to 3.4.3, only to discover 3.5.3 is now running, and CPU cycles on the web host are too high, again.

Now this? Too many bugs, too many hassles from Hostgator…

I had the same issue. I rolled-back the updated theme, but it came back a few hours later, leaving two warning in the back office and redering my users unable to approve comments. The main blog gets ~5,000 visitors a day. This is not cool.

I’m going to create a child them to prevent this from happening in the future.

Brian,

No, WP Super Cache was deactivated before the Falcon engine was activated.

Yes, I use those modules and a few others, like Mobile Themes, Publicize, Shortcode Embeds, Site Verification, and WP.me Shortlinks.

Even with these running in 3.4.3, CPU usage appears to be less than half of 3.5.

In this chart, I reactivated JetPack 3.5 shortly after 9:00, with only the previously mentioned modules running. I rolled it back to 3.4.3 shortly after 14:00. Nothing else changed on the site during that time.

Thanks.

Hi Jeremy,

In order to do that, I would need to re-apply the 3.5 upgrade.

The best that I can do is tell you the modules that I had running, which were the following:

1. Likes
2. Notifications
3. Related Postes
4. Sharing
5. Subscriptions
6. WordPress.com Stats

Thanks.