Warning: Attempt to Read Property on Null

Why it happens

• A theme or plugin reads a property, such as $post->ID, from a value that is empty. On a 404 page or an empty search, WordPress has no current post, so the global $post is null.
• A WordPress function found nothing and returned null or false. get_post(), get_page_by_path() and get_term() return null. get_user_by(), get_userdata() and get_term_by() return false. The code never checks.
• The host moved the site to PHP 8.0 or newer. PHP 7.4 reported the same mistake as a notice, which WordPress hides when WP_DEBUG is off. PHP 8 reports it as a warning.
• The server shows errors on the page (display_errors is on), or WP_DEBUG and WP_DEBUG_DISPLAY are on, so a message that used to stay in a log now reaches visitors.

How to fix it

Try the fixes in this order. Each one is independent: stop as soon as the error is gone.

The message means that some code tried to read a property, such as $post->ID, from something that holds nothing. It is a warning, not a fatal error: PHP carries on, the page loads, and the value comes out empty. The path in the message names the theme or plugin that wrote the code. The usual trigger is a page with no post, such as a 404 or an empty search, where the code assumed there was one. The fix belongs to the author, so update or replace it. You can stop visitors seeing the message by writing errors to a log instead of the page.

What you see#

The message is plain text with no styling. PHP prints it where the code runs, so it often lands in the footer or at the top of the page.

I made it with a small classic theme. This is its whole footer.php:

<footer><p>Footer for post <?php echo $post->ID; ?></p><?php wp_footer(); ?></footer></body></html>

I loaded four URLs with the same theme:

/hello-test/   [200] Footer for post 4/              [200] Footer for post 1/?s=zzz        [200] Footer for post  Warning: Attempt to read property "ID" on null in /var/www/html/wp-content/themes/my-theme/footer.php on line 2/nope-404/     [404] Footer for post  Warning: Attempt to read property "ID" on null in /var/www/html/wp-content/themes/my-theme/footer.php on line 2

The message shows on the pages that have no post. The page with a post is fine, and so is the home page. That is why theme authors miss it: it only shows on the pages they did not test.

How it works#

PHP does not complain when you ask an object for a property. It complains when the thing is not an object. null and false are not objects, so null->ID has nothing to read. PHP 8 says so with a warning and gives null for the result.

WordPress sets the global $post when it starts to build a page. In WP::register_globals() the line is $GLOBALS['post'] = $wp_query->post ?? null;. The query's first result goes in, and if the query found nothing, null goes in. A 404 and a search with no results have no posts, so $post is null on both.

The silent version of the same mistake#

When there are posts, $post is set but not always to the post you want. On the home page, the footer of my classic theme printed 1, which is the last post in the list. A block theme I tested the same code with printed 7, the first. Both are real posts, so no warning appears, and the code uses the wrong ID. Code that needs the post being viewed should check is_singular() first.

Where null and false come from#

The message ends in the type of the value. I called each of these on the lab site with a missing item and tried to read a property from the result:

Searches for "attempt to read property on bool" are the same problem. PHP 8.0 wrote bool where PHP 8.3 writes false. get_the_ID() does not fail like these. Its code is return ! empty( $post ) ? $post->ID : false;, so it gives false when there is no post.

What PHP 7.4 said#

The same mistake had a different message on the old PHP. I ran one file on three PHP versions:

$a = null; $b = false; $c = "str";echo $a->ID, $b->ID, $c->ID;

PHP's 8.0 notes list "attempting to read a property of a non-object" as a notice that became a warning. So code that ran quietly for years starts to talk after a PHP upgrade. Search for "trying to get property of non-object" and you will find the PHP 7 form of this page.

Why you may see it only sometimes#

PHP raises the warning. Whether it reaches the page depends on settings. I tested each on the 404 page:

[30-Oct-2026 12:02:52 UTC] PHP Warning:  Attempt to read property "ID" on null in /var/www/html/wp-content/themes/my-theme/footer.php on line 2

Unlike a deprecation, a warning is not dropped when WP_DEBUG is off. If the host shows errors, visitors see it. For the array version of the same idea, see the undefined array key page. For a property that was never declared, see the dynamic property page.

Each developer fix, tested#

I put each fix in place of the broken line and loaded a post, the home page, an empty search and a 404:

The nullsafe operator only short-circuits on null, as PHP's manual says. It is fine for a value that may be missing. It is the wrong tool for functions that return false.

If the page goes blank#

A warning never stops a page by itself. A blank page or a critical error message is a different problem: see the white screen of death.