If a WordPress file edit uploaded over FTP appears to do nothing, the file is usually in the wrong installation, was not completely replaced, is not the file WordPress uses, or is hidden by a cache. Back up first, confirm the domain’s document root and active theme or plugin, verify the remote file, purge every relevant cache, and then check ownership and permissions. This sequence finds the problem without blindly changing files or setting unsafe permissions.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What “the edit did nothing” actually means
An FTP upload changes a file on a server; it does not guarantee that the browser will request that file or that WordPress will execute it. A page can remain unchanged when any link in this chain is wrong:
As an Amazon Associate I earn from qualifying purchases.
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- Location: You uploaded to a different site, staging copy, or directory than the one serving the domain.
- Transfer: The upload was interrupted, sent to the wrong filename, or left the previous remote copy in place.
- Execution: The active theme, child theme, plugin, template, or generated asset is somewhere else.
- Visibility: A browser, WordPress cache, host cache, reverse proxy, CDN, or PHP cache is returning an older result.
- Access: The FTP account or web-server process cannot read or replace the file because its owner, group, or permissions are unsuitable.
Treat the issue as a chain of checks rather than repeatedly uploading the same file. Change one variable at a time and use a distinctive, temporary marker so you can tell whether the new version is being served.
Use this diagnostic sequence first
- Back up before replacing anything. Download the current remote file and keep it unchanged. If the edit affects a live site, make a site-files and database backup when your hosting tools allow it. A backup gives you a known-good rollback if a PHP parse error or malformed stylesheet takes the site down.
- Confirm the connection and document root. Check the FTP account, server, domain, and directory you opened. Hosting accounts commonly contain separate production, staging, development, or add-on-domain installations. The folder named
public_html,www, or similar is not automatically the correct root for every domain. Use the hosting panel’s domain or document-root listing and compare it with the installation that containswp-admin,wp-content, andwp-includes. - Identify the file that generates this page. Check which theme is active under the WordPress Themes screen, whether a child theme is active, and which plugin or template supplies the feature you changed. A file with a familiar name in an inactive theme, an old plugin copy, or a staging folder will not affect the public page. For templates, follow WordPress’s template hierarchy instead of assuming that the visually similar file is selected.
- Edit as plain text or code. Use an editor designed for code. Word processors can replace straight quotes, alter characters, add formatting, or insert unwanted markup that breaks PHP, CSS, or JavaScript. Preserve the file’s encoding and extension.
- Upload the complete replacement and watch the transfer finish. Do not close the FTP client while it still reports an upload in progress or failed. If the client asks whether to overwrite the remote file, choose the intended replacement. When overwrite behavior is questionable, retain your backup, delete the old remote file, and upload the complete replacement rather than a partial fragment.
- Verify the remote copy independently. Refresh the remote directory listing, then compare the remote file’s size and modified timestamp with your local copy. Open the remote file in the client, if supported, and search for a distinctive test marker that exists only in the new version. This proves that the server contains the file you think you uploaded; it does not yet prove that WordPress is using it.
- Purge the caches that can serve the old response. Clear the browser cache or test in a private window, then purge any WordPress caching plugin, managed-host cache, CDN cache, reverse proxy such as Varnish, and applicable PHP or application cache. Reload the exact URL and look for your distinctive marker. Purging only the browser is insufficient when an upstream layer still holds the old HTML, CSS, or script.
- Check access after correctness and caching. If the remote file is definitely new but the site still cannot read it or the upload will not persist, ask the host to inspect owner, group, and read/write permissions for both the FTP account and the web-server account. Permissions vary by server. Do not “fix” the problem by blindly setting files or directories to
777; excessive access can expose content or take the site offline.
Find the installation WordPress is actually serving
Confirm the domain’s document root
A single hosting account can contain several WordPress trees. An FTP client may open your account’s home directory, while the domain points to a subdirectory. Another domain may point to a sibling directory, and a staging subdomain may have its own copy. In the hosting control panel, locate the domain’s document-root value and navigate to that exact path. The correct installation normally contains the WordPress core directories and the wp-config.php file (which you should not overwrite casually).
Use a harmless marker to validate the path. For a CSS test, add a temporary rule to the stylesheet you believe is active and give an existing element an unmistakable color or outline. For a PHP test, use a controlled marker in a safe location and remove it immediately after confirming the correct file; never print sensitive configuration values. If the marker never appears after cache purges, return to the document-root and active-file checks rather than making more edits.
Separate production from staging and duplicate copies
Look for directory names and subdomains that indicate staging, development, backups, or previous migrations. A staging copy can look identical in FTP and in the browser, especially when you use a bookmark or a hosts-file override. Compare the domain shown in the browser with the domain and server selected in the FTP client. If your host provides separate credentials for staging and production, verify that you used the production credentials for a public-site change.
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 →Prove that the edited file is the active one
Themes and child themes
WordPress loads the active theme, not every theme installed on the server. If a child theme is active, its templates and stylesheet can take precedence over the parent’s corresponding files. Editing the parent may therefore have no visible effect, while editing a parent file can also be lost when the theme is updated. Confirm the active theme in WordPress and inspect that theme’s directory under wp-content/themes.
A page may be generated by a more specific template than the generic file you changed. A single post, page, archive, front page, or custom post type can follow a different branch of the template hierarchy. Trace the page type and the template names it can select before deciding which file to replace.
Plugins and generated assets
Plugin functionality is executed from the active plugin directory, and multiple versions of a plugin can remain after a migration or manual copy. Confirm the plugin is active and that the file belongs to that installation. A file named style.css or script.js may be source code rather than the asset enqueued on the page. Build processes can produce minified or bundled files in another directory, so editing an unbuilt source file will not change the browser’s request until the project’s normal build and deployment step runs.
Inspect the page’s loaded resources in your browser’s developer tools when a visual or JavaScript change is missing. The requested URL identifies the actual stylesheet or script; compare that path with the file you uploaded. If the browser requests a versioned or bundled asset, work on the source-and-build process or the generated file that the site explicitly serves, according to your deployment setup.
Rank #3
Verify the upload instead of trusting the FTP client
An FTP client can report a completed session while you are looking at a stale directory listing, a different server, or a file with a similar name. After uploading, refresh the remote listing and check three independent signals:
- Size: The remote byte count should match the intended local file, allowing for any known line-ending conversion your client performs.
- Timestamp: The modified time should correspond to the upload. Server time zones can differ, so use it as a clue rather than sole proof.
- Content: Open or download the remote file and search for a unique marker from the new version. A marker is more reliable than a filename because it proves which contents are present.
If the size and content remain old, check the client’s transfer log for permission errors, failed overwrites, or a queue that was never completed. Keep the backup, remove the old remote copy only when you are certain you are in the right directory, and upload the full replacement. Never replace a PHP file with an empty or truncated transfer.
Clear every cache that can hide the change
| Layer | Typical symptom | Action | Proof after clearing |
|---|---|---|---|
| Browser cache | Your private window shows the change but the normal window does not. | Hard-reload or clear cached data for the site; test in a private window. | The marker appears in the private and normal windows. |
| WordPress cache plugin | Pages remain old even after the remote file is verified. | Use the plugin’s purge or clear-cache control, including page and asset caches if they are separate. | A fresh request returns the new HTML or asset. |
| Managed-host cache | Plugin purges do not change the public response. | Use the host’s cache-control or purge function, or ask support to clear it for the domain. | The host-served response contains the marker. |
| CDN or reverse proxy | Different networks or locations show different versions; a proxy such as Varnish is in front of the site. | Purge the affected URL or the appropriate cache zone according to the provider’s controls. | Requests through the public hostname show the new version. |
| PHP or application cache | PHP code is verified on disk but behavior remains unchanged. | Clear or restart the applicable PHP/application cache through the host; availability and controls differ by server. | The PHP result changes after a fresh request. |
Invalidate only what is necessary when the control allows a URL-level purge; a full-site purge can temporarily increase server load. After purging, request the exact page or asset again and use a temporary marker, not a vague visual impression, to judge the result.
Understand ownership and permissions
Two different accounts may be involved: the account used by FTP and the account used by the web server or PHP process. The FTP account must be able to upload or replace the file; the web process must be able to read it, and WordPress may need write access for updates or generated files. A migration, security hardening change, or manual copy can leave the owner or group assigned to an account that neither process can use.
Free tools Windows power users keep installed
One-click scans. No signup required.
Ask your host to inspect the file and its parent directories when an upload fails, reverts, or produces a permission error. Include the domain, full path, FTP username, and approximate upload time. The host can apply the server’s appropriate owner, group, and permission policy. Avoid recursive, blind permission changes and never use 777 as a generic remedy: it grants more access than most sites need and can create a security exposure or prevent the server from handling files correctly.
Use encrypted file transfer
Plain FTP sends credentials and file data without encryption. Prefer SFTP (FTP over SSH) or FTPS when your host supports it, and confirm the port and connection type in the hosting documentation before connecting. WordPress’s Advanced Administration Handbook states: “Using SFTP is the same as FTP, except your password and other data is encrypted as it is transmitted between your computer and your website.” Encryption protects the login and the PHP, configuration, CSS, or JavaScript files while they cross the network; it does not correct a wrong document root or stale cache, so the correctness checks still apply.
Use a unique, limited FTP or SFTP account for the intended site when your host allows it. Store credentials in the client’s secure credential store rather than in an unprotected text file, and remove access that is no longer needed.
File-specific checks when the replacement is present
PHP changes
A syntax error can prevent the edited file from loading or can trigger a recovery mode or server error. If the site fails after the upload, immediately restore the backed-up file through SFTP or the host’s file manager, then inspect the server’s PHP error log. Once the site is stable, make a smaller change and verify it in a non-production copy first. If the file on disk contains the new code but the old behavior persists, include the applicable PHP or application cache in the purge and ask the host whether a PHP process restart is required.
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 →Repair Windows errors before they cause bigger problemsFix Now →CSS changes
First confirm that the browser requests the stylesheet you edited. A theme can enqueue a child-theme stylesheet, a plugin can add another stylesheet later in the cascade, and a build system can serve a minified bundle. Browser developer tools can show the requested URL and which rule wins. If the new rule is present but crossed out, the issue is CSS specificity or order rather than FTP; if the old stylesheet is requested, return to the active-file and generated-asset checks.
JavaScript changes
Confirm the loaded script URL and check the browser console for syntax or runtime errors. A cached bundle, deferred script, or concatenated asset can make an edited source file invisible until the generated asset is rebuilt or its cache is purged. Keep the test marker temporary and remove it after verification.
Recovery when the site breaks after an upload
- Stop making additional edits and keep the failed file for diagnosis.
- Restore the backed-up remote file using SFTP or the host’s file manager.
- Reload the site in a private window and purge the relevant caches if the old error page remains.
- Check the PHP or web-server error log for the exact file and line reported.
- Recreate the change in a copy or staging installation, save a complete file, and upload it only after the replacement has been verified locally.
If you do not have a usable backup or cannot restore the file, contact the host with the domain, path, timestamp, and error message. Do not delete WordPress core directories or configuration files while trying to repair a theme or plugin edit.
Prevent the same problem on the next edit
- Record the production document root and the active theme or plugin path before connecting.
- Keep dated local backups of every file you replace and a current site backup for larger changes.
- Use SFTP or FTPS, a code editor, and a client that displays transfer errors and overwrite results.
- Make one small, identifiable change at a time; verify the remote size, timestamp, and content immediately.
- Keep a short cache checklist for browser, WordPress, host, CDN or reverse proxy, and PHP/application layers.
- Use staging for PHP, CSS, and JavaScript changes that could affect the whole site.
- Ask the host to document the expected owner, group, and permission policy instead of applying broad permissions yourself.
A compact decision table
| What you observe | Most likely area | Next check |
|---|---|---|
| The remote file has the old size and marker. | Wrong path or failed overwrite. | Reconfirm the document root and transfer log; upload the complete file. |
| The remote file is new, but the browser is old. | Cache or wrong public URL. | Verify the requested URL and purge browser, WordPress, host, CDN, and proxy layers as applicable. |
| The asset is new, but the page ignores it. | Inactive theme/plugin file or generated asset. | Check the active installation, template hierarchy, enqueued URL, and build output. |
| The upload fails or cannot be read. | Owner, group, or permissions. | Have the host inspect access for the FTP and web-server accounts; do not use 777. |
| The site errors immediately after the upload. | Malformed or incompatible code. | Restore the backup, read the error log, and retest a smaller change in staging. |
When to stop troubleshooting alone
Escalate to your host when the domain’s document root is unclear, the FTP account reaches a different server than the web process, ownership cannot be changed safely, cache controls are unavailable, or the site remains broken after restoring the backup. Provide the exact domain, remote path, connection type, transfer timestamp, observed file size, and error-log message. Those details let support distinguish a path problem from an access or cache problem without asking you to repeat risky uploads.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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.
