The reported bug is a mismatch between two update paths: an SSH/CLI route passes ignored plugins to WP-CLI, while a Playwright browser route selects every plugin update checkbox without applying that exclusion list. The same browser flow can also report “plugin updates remaining” when only intentionally excluded plugins are left. The account describes a proposed code fix, but does not establish that it was merged or released.
What the reported symptoms mean
An article published August 20, 2026, describes two symptoms in a WordPress maintenance tool: plugins marked as “excluded from update checks” were still being updated in browser mode, and a later check could send a misleading “plugin updates remaining” WARNING email even when the remaining updates belonged only to excluded plugins. These phrases describe the reported tool behavior, not a universal WordPress setting or warning.
As an Amazon Associate I earn from qualifying purchases.
According to that account, the tool’s SSH-capable path used WP-CLI and carried the ignored-plugin list into its update command. Its Playwright path instead opened WordPress’s update-core.php page and selected all plugin update checkboxes. The same browser update function was used both for direct browser updates and for a residual pass after SSH updates, so the browser selection behavior could affect sites maintained through either route. These details are reported by the article and have not been independently verified.
Why the browser path could update excluded plugins
Selecting every checked plugin-update box is not equivalent to applying an exclusion list. The reported gap is that the browser routine selected the page’s checked[] boxes without first identifying which plugins should be ignored. In the described fix, the routine reads each checkbox value, extracts its plugin slug—for example, contact-form-7 from contact-form-7/wp-contact-form-7.php—normalizes the configured ignored slugs, and selects only entries that are not excluded.
#1 Best Overall
- easy to use
- Free app
- Compatible with all devices
- It gives the best comparison between ten different hosts
The account says the earlier select-all behavior would remain when no exclusions were configured. That distinction matters: the proposed change is not to stop browser updates altogether, but to make the checkbox selection respect the configured list when one exists.
Why excluded updates can trigger a false residual warning
A page that still contains update forms does not necessarily mean actionable work remains. If the only remaining update entries are intentionally excluded, a residual check that treats any remaining form as pending will produce a misleading warning.
The reported remediation evaluates the remaining plugin slugs against the exclusion list. At least one non-excluded plugin remaining means work is pending; if all remaining plugins are excluded, the browser residual check should treat the update state as not pending. This is separate from filtering the initial update selection: a correct selection routine alone does not make a later status check exclusion-aware.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11What to check before running updates
- Confirm whether the maintenance tool is using its browser/Playwright route or a WP-CLI route; the reported discrepancy concerns the tool’s browser path.
- Check that the ignored list contains the plugin slugs the tool expects, rather than assuming that a displayed plugin name and its slug are interchangeable.
- Before allowing a browser-mode run to proceed, verify that excluded plugins are not selected on the WordPress update page. If they are selected, the reported selection gap may apply.
- After a run, inspect which plugins actually remain available for update. A warning based only on the presence of remaining forms can include intentionally deferred plugins.
The article describes a proposed code change and says its tests covered single and multiple exclusions, all-excluded and no-exclusion cases, nonexistent slugs, and residual-state combinations. Those test descriptions were not independently inspected or run, so they do not establish that the fix works in a released build.
WP-CLI: explicitly exclude plugins and preview the target set
For a CLI workflow, WP-CLI documents wp plugin update with an --exclude=<name> option for a comma-separated list of plugin names to exclude. Its --dry-run option previews which plugins would be updated without performing the update. Consult the WP-CLI plugin update reference for command details.
For example, to preview an update of all plugins while excluding specified names, use:
wp plugin update --all --exclude=plugin-slug-one,plugin-slug-two --dry-runRemove --dry-run only when you intend to carry out the update. WP-CLI’s global --skip-plugins[=<plugins>] option is different: it skips plugin loading, with must-use plugins still loaded. It is not the option for excluding plugins from updates.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Browser mode or WP-CLI: what the evidence supports
| Question | Browser/Playwright route described | WP-CLI route documented or reported |
|---|---|---|
| Can the workflow apply exclusions? | The article reports that the described browser routine selected all plugin checkboxes without filtering; its proposed fix filters by slug. | wp plugin update documents --exclude=<name> for excluded plugin names. |
| Can the target set be previewed? | Not stated in the available account. | --dry-run previews which plugins would be updated, according to the WP-CLI reference. |
| Does the residual check distinguish excluded updates? | The article reports a misleading warning and proposes treating only non-excluded remaining plugins as pending. | Not stated in the cited command reference. |
| Is comparative reliability established? | No comparative reliability measurements are provided. | No comparative reliability measurements are provided. |
What is—and is not—confirmed about the fix
The available account describes the defect and a proposed change, but does not establish a merged upstream patch, a release date, a supported tool version, or a public repository containing the change. It also does not independently verify the described tests. Until the relevant project confirms a release, treat the fix as a reported proposal rather than a guaranteed behavior. The WP-CLI option behavior above is documented separately by the official reference.
Quick Recap
Best Value
- Free WordPress Hosting Guide Android Application. It Contains: A Brief Overview of WordPress Hosting, 9 Major Benefits of Managed WordPress Hosting.
- 5 Simple Steps to Choose WordPress Hosting, How to Maximize Your WordPress Hosting and Blogging Success, How to Choose the Best WordPress Hosting Provider, Optimize Your Blog with VIP Word.
- Press Hosting, What You Should Know to Choose the Best WordPress Hosting and Much More.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
