In general I always have auto updates for plugins switched off due to past experiences with fatal errors. Yesterday, my site received an enforced “security” update for the plugin “Updraftplus” because it has a large user base according to their support forum. They stated that this was by WordPress, not the plugin author. This update occurred just before a scheduled automated backup. There are other posts in their forum about fatal errors caused by this update. The update caused my site to go offline for a number of hours. When it returned, it was completely out of memory due to whatever changes had been pushed. I only became aware of the problem due a memory monitoring automated email I had set up just recently. This out of memory spike only occurred after the site went back online. The end result is that I managed to restore the site from a week old backup, and deactivating the plugin. Even after I downgraded and deactivated the plugin, the enforced update was still pushed, although it remained deactivated. Content is missing from the past week locked in an unresponsive out of memory instance. I don’t think there’s ever a scenario where plugin updates should be enforced unless they’re rigorously tested. Especially for a memory intensive operation like creating backups. The potential for taking sites down is high due to the infinite number of variations in configurations and other installed plugins, and themes.
- The topic ‘Enforced plugin update’ is closed to new replies.