PHP Fatal Error: What It Means and How to Fix It

Something in your website's code went wrong so badly that the page stopped halfway, which leaves visitors with an empty or half-finished page. For your business that means lost trust and possibly lost orders until it is fixed. The message tells you which file went wrong, and that is where the steps below begin.

A PHPPHP is a programming language that builds your web pages on the computer that hosts your site, just before they reach the visitor. WordPress runs on it. fatal error is an error that PHP cannot recover from, so it stops running the script at that point. Whatever the page should have shown after that point is never produced, which is why a fatal error often leaves you with a half-built or empty page.

What the message means

A typical message reads "Fatal error: Uncaught Error" or "Fatal error: Uncaught Exception" followed by a description, a file path and a line number. The word uncaught means that no code handled the problem, so PHP gave up. The part after it describes what went wrong, for example a function that does not exist, a class that cannot be found or a value of the wrong type. Below that you often see a stack trace, which is a list of the calls that led to the error, with the most recent call first. Read the first line that points at a file in your pluginA WordPress plugin is an add-on you install in WordPress to give your site extra features, such as contact forms, SEO tools or a webshop., themeA WordPress theme is a ready-made package that decides how your WordPress site looks and how its pages are laid out. Change the theme and the design changes. or application, because that is where to start.

Common causes

Fatal errors often come from code that does not match the PHP versionA PHP version is a numbered edition of PHP, like 8.3. Each edition is looked after for a limited time, then gets security fixes only, then nothing., a plugin or theme that was updated or half removed, or a missing file or class. A mistake in custom code is another usual cause, and so is a PHP extension that is not installed on the server. After an upgrade to a newer PHP version, older code can call features that were removed.

How to check it safely

Before you change anything, back up the files and the database. Then read the error logAn error log is a file where your website's software writes down what went wrong, with the time and place. It is the first thing to check when a site breaks. instead of turning on visible errors on a live site, since on-screen messages can show server paths to visitors. Note three things: the error type, the file and the line number. Search the file name to see whether it belongs to a plugin, a theme or your own code. Check the PHP version the site runs now and compare it with the version the code was written for.

What you can try yourself

Try these steps in order.

First, if the file belongs to a plugin, deactivate that plugin, or rename its folder over SFTP if you cannot log in. Second, if it belongs to the theme, switch to a default theme. Third, if the message mentions a missing class or function, reinstall the plugin from a fresh copy, because an upload may have failed. Fourth, if the stack trace points at your own code, restore the last working version. Keep passwords to yourself and do not paste them into chats or tickets.

When the PHP version is the cause

If the error started after a PHP update, the code may use functions or behavior that the newer version no longer supports. Updating the plugin, theme or application to a release that supports your PHP version is usually the lasting fix. The supported versions page on this site shows which PHP versions the PHP project still maintains.

When to get help

If the stack trace is long, if the error sits in custom code you did not write, or if the site is down for customers, get a second pair of eyes. At Website Without PHP a human replies within 1 business day. A rush repair starts from $425, excluding VAT.