Updatronix 3000 is the Pro edition of Updatronix. It runs on top of the Updatronix plugin and adds the Update Shield feature set, for agencies, developers, and site owners who want incompatible updates kept off their sites.

What Updatronix 3000 adds

  • Update Shield checks every pending plugin, theme, and core update against your site’s WordPress and PHP versions before an automatic update runs. Incompatible updates are blocked, their auto-update setting is turned off, and a plain-text email goes out.
  • Safe mode is the enforcement engine behind it. Safe mode blocks the incompatible automatic updates and locks their native WordPress auto-update toggles, marks the affected items on the Plugins, Themes, and Dashboard → Updates screens, and records everything in the Updatronix plugin’s Update logs.

Two smaller pieces complete the set. License management activates, checks, and deactivates your license from the Updatronix screen, with the key stored encrypted and bound to the registered domain. Pro update delivery gives Updatronix 3000 its own updates through the native WordPress system, from the license server, with a 12-hour cache.

One license covers one site, with updates for life. Roadmap features (Update Flow, Development Tools, Advanced Exports, Queue List, White Label) are planned and sit outside this documentation.

Requirements

You need WordPress 6.2 or later, PHP 8.1 or later, and Updatronix 1.1.1 or later.

The pages

Topics shared with the Updatronix plugin stay in the Updatronix documentation: installation basics, the Update logs screen, the Auto-updates tab, the Schedule tab, settings, multisite behavior, and uninstall.

About the interface labels

Interface labels, settings, and messages are quoted exactly as they appear in the plugin.

Author

Photo de Quentin Le Duff

Quentin Le Duff

Quentin Le Duff is a WordPress developer for ten years, Opquast® Expert & ISTQB certified. He works with WordPress every day: developing open source plugins and themes, hosting and maintaining his clients’ websites, and writing about the WP ecosystem.