Files that could not be checked
Why some files are listed as “could not be checked”, why that matters for the verdict, and what you can do.
The report ends with Files that could not be checked. For these files, the report cannot say whether they are ready for the new PHP version.
Such a file may hide a problem. That’s why, while any active file could not be checked, the verdict never says “Safe to upgrade”. It says “Nothing found that will break”, together with the number of files that could not be checked.
The reasons, and what to do
| The report says | What to do |
|---|---|
| Could not be read as PHP code | If your site uses this file, it already fails on your current PHP version. Often it is an unused leftover or a template. Mention it to the plugin’s developer. |
| Too large and complex to check within the memory PHP has on this server | Ask your host to raise PHP’s memory limit (the report says how much is needed when it knows), then scan again. |
| The check stopped on this file / The scanner stopped while reading this file | The file is probably very large or complex for your server’s limits. Scan again later; if it stays, ask your host about PHP’s memory and time limits. |
| Larger than 2 MB, so it was not checked | Nothing you can change. Ask the plugin’s developer whether the file is ready for the new PHP version. |
| Could not be read (check the file permissions) | Ask your host to check the file permissions, then scan again. |
| The file name uses an unusual character encoding | Renaming the file to plain letters lets CompatNav check it. Only do this if you wrote the code: other files may load it by its name. Otherwise, ask the developer. |
| A link to another location; links are not followed | The file points to a file somewhere else on the server, and CompatNav doesn’t follow links. Ask your host or developer what it points to; if that code runs on your site, ask its developer whether it is ready. |
Skipped on purpose
Some files are listed under Skipped on purpose. They don’t affect the verdict:
- Test and development folders (tests, node_modules, hidden folders) are not part of the running site.
- Test files in a bundled library are not loaded when the site runs.
- Bundled libraries skipped because of your setting: turn off Skip bundled libraries under Scan settings and scan again. Outdated bundled libraries are a common reason sites break after a PHP upgrade.
Inactive plugins and themes
Files of inactive plugins and themes that could not be checked don’t affect the verdict. They only matter if you activate the plugin or theme.