--- title: WordPress auto-update audit description: WP_AUTO_UPDATE_CORE can be silently disabled and your dashboard will not say so. This plugin reads the actual update configuration and shows it. source: https://steem.dev/blog/wordpress-auto-update-audit-plugin published: 2026-10-01 updated: 2026-10-31 alternative_to: ManageWP site: Steem — AI WordPress plugin generator --- # WordPress auto-update audit WordPress has updated itself automatically since version 3.7, and site owners tend to assume it still does. That assumption breaks when a developer sets `WP_AUTO_UPDATE_CORE` to false in wp-config.php, a common step during a build that rarely gets undone on launch day. The site looks maintained and the dashboard shows a version number, with nothing to say the machinery behind auto-updates was switched off. `DISABLE_WP_CRON` gets there from another direction. When a host promises to run cron at server level, developers often disable WordPress's own cron to avoid duplicate runs. If the server cron is never set up, no scheduled task runs, the update check included, and the site stops updating just as quietly. A plugin that reads these constants and the current version state puts the real configuration on the dashboard, without opening wp-config or running WP-CLI. ## What one build covers - Whether WP_AUTO_UPDATE_CORE is set and what its value means in plain language - Whether AUTOMATIC_UPDATER_DISABLED is blocking all automatic updates - Whether WP-Cron is disabled, which would prevent the update check from running - Whether the installed WordPress version matches the latest available from the update API - All four checks in a single dashboard widget with no configuration required ## What it does not cover - Plugin and theme auto-update settings, which are stored separately in site options - Whether a server cron is actually configured when DISABLE_WP_CRON is true - Multisite networks: the plugin audits the site it is installed on, not the whole network - Email alerts or scheduled notifications when the site falls behind - Any remediation: the plugin reads and reports configuration, it does not change it ## The prompt ```text Build a WordPress plugin called Update Config Audit. Plugin Name: Update Config Audit. Description: Dashboard widget showing your WordPress auto-update configuration at a glance. Single PHP file. No dependencies beyond WordPress core. Register a dashboard widget using wp_add_dashboard_widget with id uca_dashboard_widget, title Update Configuration, callback uca_render_widget. Hook the registration into wp_dashboard_setup. In uca_render_widget, output a table element with style width:100%;border-collapse:collapse. The table has a thead row with two th cells: Check and Status, both left-aligned. The tbody has four rows. Row 1 - Check cell: Core auto-updates. Status cell: Read WP_AUTO_UPDATE_CORE. If not defined: output Minor updates only (WordPress default) in color #46b450. If true (boolean true, string true, or string 1): output All updates enabled in color #46b450. If the string minor: output Minor updates only in color #46b450. If false (boolean false, string false, or string 0 or integer 0): output Disabled (WP_AUTO_UPDATE_CORE is false) in color #d63638. Row 2 - Check cell: Updater disabled. Status cell: Read AUTOMATIC_UPDATER_DISABLED. If defined and evaluates to true: output Yes - all automatic updates are blocked in color #d63638. Otherwise: output No in color #46b450. Row 3 - Check cell: WP-Cron. Status cell: Read DISABLE_WP_CRON. If defined and evaluates to true: output Disabled - verify a server cron is calling wp-cron.php in color #dba617. Otherwise: output Enabled in color #46b450. Row 4 - Check cell: WordPress version. Status cell: Call get_site_transient('update_core') into $update_data. Get current version with get_bloginfo('version') into $current. If $update_data is empty or $update_data->updates is empty or not set: output Current: [version] - update check has not run yet in color #dba617. Otherwise read $update_data->updates[0]->current into $latest. If $latest equals $current: output Up to date ([version]) in color #46b450. Otherwise output Current: [current] / Latest: [latest] - update available in color #d63638. Apply inline style color:[hex] to each status td. Escape all dynamic values with esc_html. Give each tr a style border-bottom:1px solid #f0f0f0 and each td and th a style padding:6px 4px. ``` ## Why the dashboard does not tell you auto-updates are off Dashboard > Updates lists available plugin, theme and core updates. It says nothing about whether auto-updates will ever fire, so two sites can show identical update screens while one updates overnight and the other has not since launch. `WP_AUTO_UPDATE_CORE` lives in wp-config.php, outside the database and outside anything the dashboard reads. Setting it to false during development is reasonable, because you want to control when core changes. The trouble is that the constant travels with wp-config.php into production and stays until someone removes it. WordPress cron runs on page load, which is wasteful on busy sites, so hosts and developers disable it in favour of a real server cron. That is sensible, until the server cron is never created or is lost in a migration. Then the update check never runs, with no error, no notice and nothing in the admin. ## Four checks in one dashboard widget An Update Configuration widget reads four things: `WP_AUTO_UPDATE_CORE` and what its value means, whether `AUTOMATIC_UPDATER_DISABLED` is set, whether WP-Cron is disabled, and whether the installed WordPress version matches the latest from the update API. Each shows green when healthy and a coloured warning when it would stop updates running. There is no settings screen. It only reads: it does not edit wp-config.php, change options or apply updates. The version check uses the same transient WordPress fills when it looks for updates. An empty transient means the update check has never run, which is itself a sign of a cron problem. It covers core only. Plugin and theme auto-updates are a separate site option, toggled per plugin under Dashboard > Plugins. ## A staging wp-config.php in production A developer disables core auto-updates during a build. The site launches with the constant still there. Two years later it is running a version that stopped auto-updating on day one, and nobody noticed because one version number looks like another. It happens when a staging wp-config.php with auto-updates off becomes the production one, when a migration script copies configuration files without anyone reading them, and when a developer leaves and the next one inherits an undocumented site. The widget shows the configuration in under a minute. For anyone managing client sites or taking over someone else's, that is a quicker audit than reading wp-config by hand. ## When ManageWP or MainWP is the better answer This reports on one site, and on a Multisite network only on the site it is installed on. With ten or fifty sites, checking a widget on each is not practical. ManageWP and MainWP collect update state across a portfolio and let you apply or skip updates from one screen. ManageWP also wraps the update workflow in scheduling, staging environments and backups, which is worth the overhead for an agency whose clients expect managed updates. If you already have either tool on a site, this audit is a small subset of what it shows; if you do not, run this during an audit and uninstall it afterwards. ## Questions ### WP_AUTO_UPDATE_CORE shows as disabled. What should I do? Open wp-config.php and find the line that sets it. Remove the line to restore the default (minor updates on), or set it to true to enable all core updates. The widget shows the new state on the next page load. ### WP-Cron shows as disabled. Is that a problem? Only if nothing at server level calls wp-cron.php on a schedule. `DISABLE_WP_CRON` is correct when a server cron replaces it. If there is none, scheduled tasks, the update check included, never run. Ask your host, or look for a crontab entry pointing at your site's wp-cron.php. --- Source: https://steem.dev/blog/wordpress-auto-update-audit-plugin Build this plugin: https://steem.dev/app