Frequently asked questions

Short answers about what CompatNav does, what it doesn’t do, and what its results mean.

Does CompatNav change my code?

No. It only reads the files of your plugins and themes. It never changes them, never runs them, and never applies fixes. The report explains each issue and shows a before/after example for whoever maintains the code.

Does any data leave my site?

No. The scan and the report are made entirely on your own server, and CompatNav makes no external requests. The “update available” information comes from WordPress’s own update check, which is already stored on your site. More in Privacy.

Why so few results?

CompatNav reports only what changes when you move from your current PHP version to the one you chose, and only exact patterns, so it does not flag code that is fine. Code that already protects itself with a version check is not reported either. Well-maintained plugins often have nothing to report. The report always shows how many files were checked, so few results means good news, not a skipped scan.

What about files that could not be checked?

They are listed in the report with the reason, for example a file that already contains a syntax error, or one that is too large or too complex for your server’s memory. Such a file may hide a problem, so while any active file could not be checked, the verdict says “Nothing found that will break” together with the number of files that could not be checked, never “Safe to upgrade”. See Files that could not be checked.

Does it work on multisite?

Yes. On a multisite network only super admins can use CompatNav, because plugins, themes and the PHP version are shared by the whole network. The report is made per site, and “active” means active on that site.

Which PHP versions does it support?

It checks upgrades to PHP 8.0, 8.1, 8.2, 8.3, 8.4 and 8.5. CompatNav itself needs PHP 7.4 or newer and WordPress 6.0 or newer. If your site still runs PHP 7.2 or 7.3, ask your host to move it to PHP 7.4 first (current WordPress needs PHP 7.4 too), then use CompatNav to prepare the move to PHP 8.

Is “Safe to upgrade” a guarantee?

No tool can promise that. CompatNav reads code; it does not run it. Some problems only appear when code runs with real data, and no code reader can see those. Make a backup before upgrading and check your site afterwards. See Not ready yet: what to do.

Does updating a plugin fix the problem?

Often, but not always. When an update is available, the report says so: updating is the recommended first step. Then click Scan this plugin again to see whether the findings are gone.

Does a scan slow down my site?

The scan runs in short background steps while you keep the CompatNav page open, with a progress bar. You can pause it and resume it later, for example at a quieter time of day.

Can I check a plugin before I activate it?

Yes. Install it without activating it, then scan: inactive plugins and themes are checked too. They are listed separately in the report.

What does “bundled library” mean?

Code the plugin’s or theme’s developer included from another project. It still belongs to that plugin or theme, so its developer is the one to update it.

What does “likely, not certain” mean?

CompatNav is fairly sure about this finding, but not completely. Whoever maintains the code can confirm it.

What happens to my data when I remove CompatNav?

Deactivating the plugin keeps your last report. Deleting it (Plugins → Delete) removes everything it stored: its database tables and its settings, on every site of a multisite network.

Is there a paid version?

Not now. We are thinking about CompatNav Pro for agencies and freelancers. It is planned, not available, and the free plugin stays fully functional forever.

Where can I get help?

See Getting help.