Make WordPress Core

Opened 4 months ago

Closed 3 months ago

Last modified 3 months ago

#52198 closed defect (bug) (worksforme)

[PHP 8.0] Undefined property: stdClass::$post_status on /wp-admin/includes/misc.php

Reported by: GwynethLlewelyn Owned by:
Milestone: Priority: normal
Severity: trivial Version: 5.6
Component: Posts, Post Types Keywords: php8 close
Focuses: Cc:


I'm happily upgrading many of my WordPress installations to PHP 8.0.0 just to see what breaks.

Here is one 'warning' that I caught today on one of my websites:

PHP Warning:  Undefined property: stdClass::$post_status in <WP_PATH>/wp-admin/includes/misc.php on line 1433

The fix is trivial, instead of

if ( 'draft' === $page->post_status && 'privacy' === get_current_screen()->id ) {

just use

if ( !empty($page->post_status) && 'draft' === $page->post_status && 'privacy' === get_current_screen()->id ) {   

... or, alternatively, use property_exists(), isset(), etc.

It's a very trivial change to avoid a warning; possibly it's present under PHP 7.4 as well.

Change History (5)

#1 @ayeshrajans
4 months ago

Hi @GwynethLlewelyn,
Welcome to WordPress Trac, and I wish you a happy new year!

You are right, the warning is related to PHP 8, which was previously a notice, and it is possible that your previous configuration options was not logging/showing those notices (although PHP was configured to show notices by default; just not strict and deprecation notices).

Could you provide a stack trace of the warning message? debug_print_backtrace() output or an Xdebug output will do. Instead of fixing this when it is used, I think a more appropriate fix would be to fix it in upstream, where the post is constructed to make sure post_status is correctly populated.


#2 @SergeyBiryukov
4 months ago

  • Keywords php8 added

#3 @SergeyBiryukov
3 months ago

  • Keywords reporter-feedback added

Hi there, thanks for testing WordPress with PHP 8.0!

Does the issue still happen with all plugins disabled and a default theme (Twenty Twenty-One) activated?

The warning comes from the _wp_privacy_settings_filter_draft_page_titles() function, which is attached to the list_pages action in the admin, called from Walker_PageDropdown::start_el(). The action is supposed to always receive a valid page data object a its second argument, so it looks like some plugin or theme constructs an object with some properties missing, or uses the list_pages filter incorrectly, which seems like a developer error.

I don't think we should hide the warning in this case, as that would make debugging harder.

#4 @GwynethLlewelyn
3 months ago

  • Keywords close added; reporter-feedback removed
  • Resolution set to worksforme
  • Status changed from new to closed

Sorry for the delay in answering...

@SergeyBiryukov you're quite right!

Also, now I cannot reproduce the error on my own setup — I've updated/upgraded a few plugins, removed others, deactivated a few more... this is a work-in-progress, mind you... and probably at some point, I must have removed whatever plugin was causing the warning.

I'll close this ticket for now; I've kept debug_print_backtrace() in place, just in case that it pops up again...

Thanks anyway for looking into this! 😊

#5 @SergeyBiryukov
3 months ago

  • Milestone Awaiting Review deleted

Thanks for the follow-up!

Note: See TracTickets for help on using tickets.