When a WordPress change saves but is not visible, first determine whether the site is serving an old cached copy or whether the change was made in the wrong page, template, or source. For a missing plugin, theme, or core update notice, allow for WordPress’s randomized update check, then use Dashboard > Updates and Tools > Site Health to identify connection, Cron, permission, or filesystem problems.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Start by identifying what “not showing” means
WordPress can appear unchanged for several unrelated reasons. A visitor may receive an old cached page while the editor sees the new version; an update may be available but not yet listed in the dashboard; or an update may have started and failed before completion. Treating every symptom as a cache problem wastes time and can make a failed update worse.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
WordPress Multisite Administration | $34.38 | Buy on Amazon |
| 2 |
|
Mon Site WordPress – Volume 2 – Administration & Utilisation (French Edition) | $9.90 | Buy on Amazon |
| 3 |
|
WordPress 24-Hour Trainer | $3.95 | Buy on Amazon |
| 4 |
|
Teacher Record Book | $4.89 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
| What you see | Most likely area | First check |
|---|---|---|
| A logged-in administrator sees new content, but logged-out visitors do not | Browser, WordPress plugin, hosting, or CDN cache | Open the exact public URL in a private window, then purge each cache layer that actually exists |
| The editor’s success notice appears, but the public page is unchanged in every browser | Wrong page, homepage assignment, template, theme, upload, or server/CDN cache | Verify the public address and the template or source that renders it |
| A newly released plugin, theme, or core update is absent from the dashboard | Scheduled update check or blocked connection to WordPress.org | Refresh Dashboard > Updates later and inspect Tools > Site Health |
| An update reports a download or installation failure | HTTP connection, filesystem ownership, permissions, disk space, or an interrupted update | Back up files and the database, read the dashboard error, and check Site Health |
| The site shows a fatal error immediately after updating | Incompatible plugin or theme code | Use the Recovery Mode link sent by WordPress and identify the paused component |
| The dashboard appears stuck on updating and never returns to normal | Interrupted update and a leftover root .maintenance file |
Confirm the update failed, remove the stale file through FTP or a file manager, then retry safely |
How WordPress update visibility works
WordPress does not cache pages by itself
A standard WordPress installation does not include a page cache by default. An older page can nevertheless be stored in several places: your browser, a WordPress caching or performance plugin, the hosting server, or a reverse proxy/CDN. A managed host can serve a server-level copy even when no cache plugin is installed. Each layer has its own expiration and purge control, so clearing only the browser may change nothing for visitors.
Update checks are not continuous
WordPress’s troubleshooting FAQ says that a site is programmed to check for updates about every 12 hours, and that the timing is randomized. A release can therefore be genuine while your dashboard still has no notice. This delay is different from a failed installation: no error may appear because the site has simply not performed its next check. Refresh Dashboard > Updates later, and use Site Health to determine whether the site can contact WordPress.org.
#1 Best Overall
The Updates screen is the control center
Open Dashboard > Updates to review available WordPress core, plugin, theme, and translation updates. The same screen reports download and installation failures. Read the exact message before retrying; a connection error points toward HTTP access, while a permission or filesystem message requires a different fix.
Safe troubleshooting sequence
Work through these steps in order. Do not repeatedly click Update before you know whether the previous attempt completed, and create a current backup before any manual file operation.
1. Confirm that the change was actually saved
- In the editor, look for the normal success notice and confirm that the item is published or updated, not merely left as a draft or scheduled.
- Copy the exact public URL and open it in a private or incognito window while logged out. This removes your normal session and reduces the chance that a logged-in preview is misleading you.
- Check the page in a second browser or on a different connection. If the private view shows the new version, the browser’s local cache is the likely cause; clear that browser cache and reload.
Browsers can reuse an older local copy when they do not consider a small change significant. A successful editor notice proves that WordPress accepted the save, not that every cache has already expired.
2. Purge only the cache layers that exist
- Clear the cache in any WordPress caching or performance plugin currently installed. Use that plugin’s purge or clear-all action rather than deleting random files.
- Check the hosting control panel for a server or managed-page cache and purge it there. Managed hosts may cache pages outside WordPress.
- If the site uses a CDN or reverse proxy, purge the affected URL or the configured cache zone according to that service’s controls.
- Reload the public URL in a private window after each layer is purged. This identifies which layer was serving the old response.
Do not install a cache plugin merely to clear a cache that is not present. Adding another caching layer can create a second source of stale output and complicate diagnosis.
3. Verify the page, template, and source being rendered
A technically successful edit has no visible effect if the public page is built somewhere else. Confirm the address in the browser, then check:
- Whether the site’s assigned homepage is the page you edited.
- Whether the visible section comes from a different page, reusable block, widget, or theme template.
- Whether a block theme template or a classic theme file controls the output instead of the page body.
- Whether an image, script, stylesheet, or other upload was placed in the intended location and is the file the page actually references.
- Whether the page source contains the new text or asset reference. If it does, the browser, server, or CDN may still be displaying an older rendered copy; if it does not, inspect the page assignment or template again.
This check separates a content-routing mistake from a cache problem before you change any server settings.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →4. Allow for the randomized update-check window
If a vendor has announced a release but no notice appears, wait for the next check and revisit Dashboard > Updates. WordPress documents an approximately 12-hour interval with randomized timing, so two sites will not necessarily display the notice at the same moment.
Do not confuse a delayed notice with a blocked update service. In Tools > Site Health, look for a warning that WordPress could not reach WordPress.org or that HTTP requests are blocked. Those findings justify investigating the host firewall, DNS, outbound-request policy, or security plugin rather than simply waiting.
5. Back up before retrying a failed or stuck update
Before another attempt, make a restorable backup of the database and WordPress files. A plugin or theme update can alter code and database data; a backup gives you a way to return to the pre-update state if the retry fails.
Then return to Dashboard > Updates and note whether WordPress reports a download failure, an installation failure, a connection error, or a permissions problem. Those labels are useful clues:
- Download or connection failure: check Site Health for blocked HTTP requests and inability to reach WordPress.org.
- Installation or permissions failure: check filesystem ownership and whether WordPress can write to the required directories.
- Interrupted update: check for a stale root
.maintenancefile before attempting another update.
6. Remove a stale .maintenance file only after confirming an interrupted update
During an update, WordPress can place a hidden .maintenance file in the site’s root directory. If an update fails and that file remains, visitors may see a maintenance message and the dashboard can appear stuck.
- Confirm that no update process is still running and that the dashboard identifies a failed or interrupted update.
- Use your host’s FTP connection or file manager to open the WordPress root directory—the directory containing
wp-admin,wp-content, andwp-includes. - Locate the file named exactly
.maintenanceand delete that file only. - Reload the site and dashboard. If the update did not complete, follow the official manual-update procedure or retry from the dashboard after checking the original error.
Do not delete unrelated hidden files, and do not treat removal of .maintenance as a repair for a code incompatibility or a permissions problem. It only clears the maintenance flag left by an interrupted process.
Rank #3
7. Inspect Site Health and automatic-update prerequisites
Open Tools > Site Health and review both the status tests and the information sections. Pay particular attention to:
- Could not reach WordPress.org: the site may be unable to resolve or connect to the update service.
- Blocked HTTP requests: a firewall, security plugin, hosting policy, or server configuration may prevent outbound requests.
- Background-update failures: scheduled tasks may be failing even when a manual update appears available.
- Filesystem permissions: WordPress may not be able to write to plugin, theme, upgrade, or other required directories.
- Cron symptoms: scheduled events may be late or failing, which prevents automatic plugin and theme updates.
Plugin and theme automatic-update controls were introduced in WordPress 5.5. A host or plugin can disable those controls, and they depend on WordPress Cron being able to run. If automatic updates never execute, fix the Site Health and Cron findings or ask the host whether scheduled tasks are restricted; repeatedly refreshing the dashboard will not repair a disabled scheduler.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Fixing common update errors
Download and connection errors
When WordPress cannot download an update, first check the Site Health tests described above. A temporary WordPress.org or network problem can clear on its own, but a persistent failure usually indicates blocked outbound HTTP, DNS trouble, a host firewall, or a security rule. Record the full dashboard message and have the host verify that the server can make the required outbound requests. Do not disable all security controls permanently; identify and allow the necessary request instead.
Installation failures and permissions
WordPress must be able to create, replace, and remove files in its installation and content directories. Incorrect ownership or restrictive permissions can allow downloads but prevent extraction or replacement. Site Health may show that directories are not writable, while the update screen reports an installation failure. Ask the host to correct ownership and permissions for the web server user using its supported configuration, then retry from the dashboard. Avoid granting broad write access as a blind fix.
Manual updates after a failed automatic update
If the dashboard cannot complete an update after the connection and filesystem issues are resolved, use WordPress’s documented manual-update process for the affected component. Keep the backup, download the correct package for the installed version and component, and follow the replacement instructions carefully. A manual update is a recovery path, not a reason to overwrite the entire site without checking which component failed.
Updates that finish but break the site
A completed update can expose a fatal PHP error caused by an incompatible plugin or theme. This is different from stale content: the updated code is being loaded, but execution stops. Use Recovery Mode rather than editing code immediately.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #4
- Keep track of everything from attendance to test scores
- Spiral bound
- Measures 8-1/2" x 11"
Use Recovery Mode for a fatal plugin or theme error
Recovery Mode was introduced in WordPress 5.2. When WordPress detects a fatal PHP error during a normal page load, it can send the administrator a recovery link. The feature pauses the component responsible for the error for that administrator session so the dashboard can be reached without FTP or direct code edits.
“Recovery Mode is a built-in WordPress feature (introduced in version 5.2) that in some cases may help you regain access to your site when a fatal error occurs, without the need for FTP and/or editing code directly.”
- Open the recovery email sent to the site administrator and follow its link.
- Read the error details to identify the paused plugin or theme.
- Deactivate, update, replace, or repair that component while in Recovery Mode. If its compatibility is unknown, leave it deactivated until you can confirm a compatible release.
- Exit Recovery Mode and load the site in a normal browser session.
- Test the front end, login, and key forms. Re-enable components one at a time only after the site is stable.
Recovery Mode does not catch every failure. Problems that occur only in Cron, background updates, or another non-page request may not trigger the recovery email. For those cases, Site Health, the dashboard’s update message, and the hosting server’s PHP or web-server logs are the relevant evidence.
Compare competing explanations instead of guessing
When two causes seem plausible, classify the symptom on five axes:
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors- Visibility: Is the new version visible to the administrator, to logged-out visitors, to every browser, or nowhere?
- Layer: Does the evidence point to the browser, a WordPress plugin, the host, a CDN, or WordPress core?
- Timing: Did the problem begin immediately after saving, or is a release notice merely delayed?
- Scope: Is one page, one plugin, or one theme affected, or is the entire Updates screen stale?
- Error evidence: Is there a dashboard error, a Site Health warning, a PHP fatal error, or a filesystem/HTTP message?
For example, a new paragraph visible to logged-in editors but absent for visitors points first to caching. A plugin release missing from every administrator’s Updates screen with a “Could not reach WordPress.org” Site Health warning points to connectivity. A white screen and a recovery email immediately after installation point to a fatal component error, not a CDN cache.
Prevention checklist
- Keep current backups of both database and files before core, plugin, or theme updates.
- Know where each active cache is controlled: browser, WordPress plugin, host, and CDN or reverse proxy.
- After publishing, verify the exact public URL while logged out.
- Review Tools > Site Health periodically for HTTP, Cron, background-update, and filesystem warnings.
- Keep automatic-update settings intentional. Remember that plugin and theme controls require WordPress 5.5 or later and can be disabled by a host or plugin.
- Keep access to the host’s FTP or file manager so a documented
.maintenancecleanup or manual update is possible when the dashboard cannot recover. - Keep the site administrator email current so Recovery Mode links can be received after a fatal error.
When to contact your host or developer
Escalate when Site Health repeatedly reports blocked HTTP requests, the server cannot reach WordPress.org, directories remain unwritable after the host’s standard permission repair, Cron events do not run, or a manual update still fails with the same error. Provide the exact dashboard message, the affected component and version, the time of the failure, and the relevant Site Health result. That information is more useful than reporting only that an update is “not showing.”
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.
