WordPress troubleshooting

Critical error on your WordPress site: actions to take now

The “critical error” message is WordPress protecting itself from a PHP error. It does not automatically reveal the cause and is no reason to delete files at random.

Keep the exact message.
The time, URL and error text can link the outage to a plugin, theme, update or suspicious change.

Safe first actions

  1. Capture the message, note the time and keep the WordPress recovery email if one exists.
  2. Back up files and database before an update, restoration or deactivation attempt.
  3. Ask your host for the PHP log at that exact time; do not expose technical errors publicly.
  4. Run Free to check files without modifying them. Use Saver if altered files or an infection must be handled.

What the tools provide

Free produces a detection report. Saver guides core restoration, review of plugins, themes, suspicious files and database, then checks the return to service.

A critical error can come from hosting or a legitimate incompatible component. Saver does not guarantee third-party compatibility or recreate data or code destroyed without a clean copy.

Frequently asked questions

Should I enable WP_DEBUG on the public site?

No. Error details can reveal paths or technical information. Review the log through your host instead.

Can an update be enough?

Sometimes, but back up and identify the cause first. An update does not address an infection or an unknown change.

What if Saver stops?

Keep the report and message, then submit the situation. Possible help is reviewed on request; permanently lost content without a backup cannot be recreated.

Free

Check before changing anything.

Free

Saver

Handle recovery with a record of operations.

Saver