Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, 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 minuteiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A reported Playwright browser-update flow selected every plugin update checkbox without applying its configured ignored-plugin list. That could update a plugin marked “excluded from update checks” and later trigger a misleading “plugin updates remaining” warning when only excluded updates were left. The report, published August 20, 2026, describes a proposed code fix; it does not establish that the change was merged or released.
Why can an excluded plugin still update in browser mode?
The reported problem was a mismatch between two update routes in a WordPress maintenance tool. Its SSH-capable route passed the ignored-plugin list to WP-CLI. Its Playwright route opened WordPress’s update-core.php page and selected all plugin checkboxes, without filtering out ignored plugins. Selecting every checkbox does not enforce an exclusion list, so the browser route could update a plugin the user intended to leave alone.
The report says the same browser update function handled both direct browser updates and a browser residual pass after SSH updates. As a result, using SSH for the main update did not necessarily avoid the browser selection behavior.
What change does the report propose for browser updates?
Instead of selecting every checkbox, the proposed logic examines each checkbox value, which may contain a plugin path such as contact-form-7/wp-contact-form-7.php. It derives the plugin slug, normalizes it, and selects the plugin only when its slug is not in the ignored list. The report says the prior select-all behavior is retained when no exclusions are configured.
#1 Best Overall
This is the reported implementation approach, not confirmation of a generally available fix. The available account does not establish a release, supported version, merged change, or public repository for it.
Why can the “plugin updates remaining” warning be false?
A remaining update form does not necessarily mean actionable work is unfinished. If every plugin still listed for an update is intentionally excluded, the form can remain visible even though the tool should not update those plugins. The report describes a residual check that treated remaining entries as pending without distinguishing excluded plugins from eligible ones.
The proposed residual logic treats work as pending if at least one remaining plugin is not excluded. If only excluded plugins remain, it treats the state as not pending. This separates the question “does WordPress still show an update?” from “does this maintenance run have an update it is supposed to perform?”
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteHow does WP-CLI handle exclusions?
The official WP-CLI reference documents wp plugin update for updating plugins, with --exclude=<name> for a comma-separated list of plugin names to exclude. Use --dry-run to preview which plugins would be updated before making changes. For example:
wp plugin update --all --exclude=plugin-one,plugin-two --dry-runReplace the example names with the actual plugin names recognized by your installation. Review the preview before running the command without --dry-run. WP-CLI separately defines the global --skip-plugins[=<plugins>] option as a way to skip loading plugins; it is not the update-exclusion option.
Browser mode or WP-CLI: what should you check?
| Workflow | Excluding plugins | Previewing changes | Residual status |
|---|---|---|---|
| WP-CLI | The documented wp plugin update command supports --exclude=<name>. |
The documented command supports --dry-run. |
The cited command reference does not establish how a separate maintenance tool evaluates residual updates. |
| Reported Playwright flow | The report says the flow selected all update checkboxes without applying the ignored list; it describes per-plugin filtering as a proposed fix. | Not stated in the report. | The report describes a proposed check that considers only non-excluded remaining plugins actionable. |
The available sources provide no comparative reliability measurements. If you rely on browser-driven maintenance, verify that its update-selection logic applies exclusions and that its residual check distinguishes excluded updates from work still due. If you use WP-CLI, preview the target set with --dry-run and use --exclude for plugins you intend to leave unchanged.
Quick Recap
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.
