Title: PHP Warnings
Last modified: April 4, 2022

---

# PHP Warnings

 *  [The Servant](https://wordpress.org/support/users/avantprime/)
 * (@avantprime)
 * [4 years, 2 months ago](https://wordpress.org/support/topic/php-warnings-131/)
 * I am receiving these warnings in my log.
 * [04-Apr-2022 06:33:21 UTC] PHP Warning: Attempt to read property “post_type” 
   on null in …\wp-content\plugins\breadcrumb-navxt\class.bcn_breadcrumb_trail.php
   on line 1056
    [04-Apr-2022 06:33:21 UTC] PHP Warning: Attempt to read property“
   post_type” on null in …\wp-content\plugins\breadcrumb-navxt\class.bcn_breadcrumb_trail.
   php on line 1056 [04-Apr-2022 06:33:21 UTC] PHP Warning: Undefined array key “
   apost__root” in …\wp-content\plugins\breadcrumb-navxt\class.bcn_breadcrumb_trail.
   php on line 1056

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [John Havlik](https://wordpress.org/support/users/mtekk/)
 * (@mtekk)
 * [4 years, 2 months ago](https://wordpress.org/support/topic/php-warnings-131/#post-15530872)
 * What kind of page are you visiting when you see this warning? For some reason
   the queued object ended up being null instead of the expected instance of `WP_Post`.
 *  Thread Starter [The Servant](https://wordpress.org/support/users/avantprime/)
 * (@avantprime)
 * [4 years, 2 months ago](https://wordpress.org/support/topic/php-warnings-131/#post-15533106)
 * My viewers are visiting the page, so I am not sure which page they are looking
   at. I just looked in the PHP logs and saw these issues.
 * The breadcrumbs are visible on posts, pages and other types?
 * Would it be appropriate to apply some defensive coding here to ensure that if
   those properties are not available it chooses the appropriate path?
 *  Plugin Author [John Havlik](https://wordpress.org/support/users/mtekk/)
 * (@mtekk)
 * [4 years, 1 month ago](https://wordpress.org/support/topic/php-warnings-131/#post-15566412)
 * Ok, in the ideal case, knowing what exactly triggered the behavior can help try
   to prevent it (could be something that wasn’t caught properly elsewhere). I will
   be reworking that area of the codebase for the next release and can make it so
   this warning shouldn’t be possible.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘PHP Warnings’ is closed to new replies.

 * ![](https://ps.w.org/breadcrumb-navxt/assets/icon.svg?rev=1927103)
 * [Breadcrumb NavXT](https://wordpress.org/plugins/breadcrumb-navxt/)
 * [Support Threads](https://wordpress.org/support/plugin/breadcrumb-navxt/)
 * [Active Topics](https://wordpress.org/support/plugin/breadcrumb-navxt/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/breadcrumb-navxt/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/breadcrumb-navxt/reviews/)

## Tags

 * [php](https://wordpress.org/support/topic-tag/php/)
 * [warnings](https://wordpress.org/support/topic-tag/warnings/)

 * 3 replies
 * 2 participants
 * Last reply from: [John Havlik](https://wordpress.org/support/users/mtekk/)
 * Last activity: [4 years, 1 month ago](https://wordpress.org/support/topic/php-warnings-131/#post-15566412)
 * Status: not resolved