| 开发者 | quentinldd |
|---|---|
| 更新时间 | 2026年9月5日 15:37 |
| 捐献地址: | 去捐款 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/updatronix/.Open Tools → Updatronix. The first tab is the log: date, item, version change, and outcome. Click any row to see the full detail. Logging is on by default.
Yes. Filter the log however you like, then click Export logs. You get a clean report you can drop into an email to your team, a client, or whoever you've called in to help.
Yes. In Settings, turn on Disable all update notification emails. Recovery mode emails are deliberately kept on: without them, you could lock yourself out of your own site.
Yes. In Schedule, enable Delay updates and choose how many days WordPress should wait after a release appears. Updates stay automatic; they're simply deferred, so unstable builds get fixed before they reach you.
Yes. Updatronix hooks into the same update pipeline WordPress already runs, so everything that updates through the standard system gets logged, whether it comes from WordPress.org, a private source, or your host's mirror.
No. Updatronix builds on WordPress's update engine without replacing it. Everything that goes through the standard update system keeps working exactly as before; Updatronix logs and manages, nothing more.
No, and that's not its purpose. When an update fails, Updatronix captures the WordPress error and the version snapshot before WordPress moves on. That's the data you need to recover by hand, or to hand to your host's support. For extra peace of mind, schedule updates right after a backup.
Nowhere. Logs and settings stay on your site. The plugin makes no outbound network calls of its own: every API it touches is one WordPress was already going to call without it.
Up to you. In Settings, set the retention window between 1 and 365 days. The default is 90 days; a daily cleanup drops anything older.
Yes. Network-activate Updatronix and manage everything as a Super Admin from the Network Admin. Settings, schedule, email controls, and update history are shared across every site in one unified log.
ob_start() buffers safely.