First identify what is failing: saving a theme or plugin file in WordPress’s built-in editor is different from updating WordPress core, a plugin, or a theme. For an editor save failure, check whether the selected file is writable and whether the host’s filesystem ownership permits WordPress to change it. For a software update failure, check Site Health, filesystem access, WP-Cron (for automatic updates), and network access. Back up your files—and, before upgrades, your database—before changing anything.
Identify which kind of update is failing
“File updating issues” can describe two separate tasks. The dashboard’s theme and plugin editors save changes directly to server files. The Updates screen installs WordPress core, plugin, or theme releases. Their causes overlap sometimes, but the fixes are not interchangeable.
- Saving code: You see “If this file were writable, you could edit it,” the “Update File” button is unavailable, or “file edited successfully” never appears. Start with file write access and the editor’s safety considerations.
- Installing an update: You see “Update failed: Could not copy file,” a “Connection Information” prompt, a lingering failed-update notice, or an update that never runs. Check filesystem access, ownership, scheduled tasks, and connectivity.
- PHP save error only: A PHP edit fails but other files save. PHP by itself does not identify the cause; check the host’s error logs and investigate plugin interference rather than assuming permissions are the problem.
WordPress’s official guidance covers the built-in editors and update process separately: editing WordPress files and updating WordPress.
Before you edit or update: make a recoverable backup
Back up the specific file before editing it. A syntax error in PHP can break the site, and the built-in plugin editor does not create a backup copy for you. WordPress recommends backing up files before editing; for an upgrade, back up both files and the database. See its file-editing guidance and upgrade troubleshooting guidance.
#1 Best Overall
- For a single-file edit, keep an untouched copy that you can upload to replace the edited file.
- For a site update, use a backup process that includes both the site files and database, and confirm you can restore it.
- If you do not have a backup or a reliable recovery route, postpone the change and ask your host how to create or restore one.
A copy on an external drive can be one storage location, but a drive alone is not necessarily a complete backup or a tested restore plan.
Fix a theme or plugin file that will not save
1. Confirm the file and editor
In the dashboard, make sure you are in the intended theme or plugin editor and have selected the correct file. The built-in editor changes the file on the server; editing a local copy and uploading it is a different workflow. WordPress documents both the built-in editor and external file-management options.
2. Check Site Health’s filesystem information
Open Tools > Site Health in the WordPress dashboard and review the filesystem permission information. Site Health checks whether WordPress can write to the main directory and important wp-content subdirectories. If a required directory is not writable, WordPress says you may need your hosting provider to resolve it; details are in the Site Health screen documentation.
If the editor says “If this file were writable, you could edit it” or the “Update File” action is missing, WordPress cannot write to that target file through the editor. The WordPress file-editing guide gives 604 as a minimum writable permission for files in this editor context. This is not a blanket instruction to recursively change permissions across your installation: correct permissions depend on ownership and hosting configuration. Ask the host to check the target file’s owner and permissions if Site Health or the editor indicates a write-access problem.
3. Use an access method supported by your host
If you need to change a file or permission outside the dashboard, WordPress lists an FTP client, the host’s web file manager, or SSH as possible methods. Availability and setup depend on your host. Download or copy the file, edit it in a plain-text editor, and upload it using the access method the host supports. Do not change broad directory permissions just to make one save work.
4. Consider why the dashboard editor is enabled
The built-in theme and plugin editors allow administrators to change code directly on a live site. If you do not need that capability, WordPress documents DISALLOW_FILE_EDIT as a way to disable it. Treat a missing editor or disabled editing control differently from a failed write: an administrator or site configuration may have intentionally disabled the feature. See WordPress’s file-editing documentation.
Fix a WordPress, plugin, or theme update that fails
Check filesystem permissions and ownership
For “Update failed: Could not copy file,” start at Tools > Site Health and check whether WordPress can write to the directories involved. If the access check points to server configuration or directory permissions, contact your host rather than guessing at a permission change.
WordPress can use different filesystem methods depending on file ownership. If the updater asks for “Connection Information,” that prompt can reflect the server’s ownership or configuration: WordPress may not be able to create files with the required ownership directly. The appropriate fix depends on how the host configured the server; see WordPress’s update guidance and ask the host to review ownership and filesystem access.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Check scheduled automatic updates
Automatic plugin and theme updates rely on scheduled WP-Cron tasks. If an automatic update does not run, open Tools > Site Health and look for WP-Cron errors. A host or plugin can also disable automatic-update controls. WordPress explains these dependencies in its plugin and theme auto-updates documentation.
Clear a failed core update safely
If a failed core update leaves a notice that the update did not complete, WordPress documents removing the stale .maintenance file using FTP. Follow the official Dashboard Updates instructions, back up first, and avoid deleting unrelated files. If the one-click update still does not work, use WordPress’s manual update procedure. Preserve wp-content, which contains themes and plugins, and follow the current official steps rather than improvising a replacement procedure.
Check network access for download or name-lookup timeouts
For a failed download or a name lookup timeout, WordPress says to confirm that the server has an internet connection and retry. If the error persists, contact the hosting provider: the issue may require investigation of server connectivity or configuration. See the updates troubleshooting guidance and Site Health documentation.
Choose the right way to work with server files
| Method | Where the change happens | When it fits | Key caution |
|---|---|---|---|
| WordPress theme or plugin editor | Directly in the server file through the dashboard | A small, deliberate edit when the target file is writable and you have a recovery copy | A faulty PHP change can break the site; the editor does not create a backup copy. |
| Host web file manager | Directly in the server file through the host’s control panel | Your host provides it and you need to manage or replace a file | Confirm the target path and keep an untouched copy before replacing a live file. |
| FTP client | Files are transferred between your computer and the server | Your host provides FTP access and the needed credentials | Use the host-supported connection details; ownership or permissions may still need host intervention. |
| SSH with a local plain-text editor | You manage server files through shell access | Your hosting account supports SSH and you know how to work safely with the relevant paths | Do not run broad, destructive permission or file operations to bypass a configuration issue. |
WordPress identifies these as possible file-management approaches but does not endorse a particular FTP client. The method your host supports, and your ability to restore the original file, matter more than the tool name. See WordPress’s file-editing guide.
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 errorsBest Value
When PHP edits fail but other files do not
A report in the WordPress support forum describes a PHP save problem, but an individual forum discussion does not establish a general cause. If only PHP edits fail, avoid treating that observation as proof of a permissions fault. Preserve the original file, check the host’s PHP or web-server error logs around the save attempt, and ask the host to identify the actual error. If appropriate, investigate whether a plugin interferes, changing one variable at a time. The report is available in the WordPress support discussion; it should be read as an example, not a universal diagnosis.
Common errors and the next action
| What you see | Likely area to check | Next action |
|---|---|---|
| “If this file were writable, you could edit it” or no “Update File” action | Target file write access, ownership, or editor availability | Check Tools > Site Health; ask the host to check the target file’s owner and permissions. |
| “Update failed: Could not copy file” | WordPress cannot write or copy in a required location | Review Site Health filesystem information and have the host check server access and ownership. |
| “Connection Information” prompt | Filesystem method, file ownership, or server setup | Use the host’s supported connection details or ask the host to resolve the underlying configuration. |
| Automatic plugin or theme update does not run | WP-Cron or disabled auto-update controls | Check Site Health for WP-Cron errors and confirm whether a host or plugin disabled the control. |
| Failed-update notice remains | Stale .maintenance file after a failed core update |
Follow WordPress’s documented FTP removal steps; back up and preserve wp-content. |
| Download or name lookup timeout | Server internet or DNS/network access | Confirm server connectivity, retry, and contact the host if the failure continues. |
| “Unable to communicate back with site to check for fatal errors” during a PHP save | The exact cause is not established by that message alone | Keep a recovery copy, inspect host logs, and ask the host to investigate; do not assume every case has the same cause. |
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server for developers. If your WordPress troubleshooting also calls for capturing a page, one GET request can return an image or PDF; it does not change WordPress files or fix filesystem permissions.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. Cookie banners are accepted and removed before the capture, along with supported newsletter popups and chat widgets; those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing status. An MCP server gives AI agents tools to take screenshots, get page information, and capture PDFs. The Free plan includes 1,000 screenshots per month without a card; paid plans start at $5 for 3,000 shots. Learn more at ScreenshotNeo.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Frequently asked questions
Does changing a file’s permissions to 604 always fix the editor?
No. WordPress gives 604 as a minimum writable permission for files in the built-in editor context, not as a universal setting for every file or server. Ownership and hosting configuration also matter, so ask your host before making permission changes.
Should I keep editing PHP in the dashboard?
Only if direct live editing is appropriate for your workflow and you can recover from a mistake. WordPress documents DISALLOW_FILE_EDIT for disabling the built-in editing facility; external editing and upload are alternatives.
Does a screenshot API resolve WordPress update errors?
No. A screenshot service captures a rendered page; it does not grant filesystem access, repair ownership, run WP-Cron, or complete a WordPress software update.
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.
Free tools Windows power users keep installed
One-click scans. No signup required.
