PHP Warnings Related to Undefined Properties in Plugin/Theme

Hi,

I am currently encountering several PHP warnings related to undefined properties in your plugin/theme on my WordPress site. I wanted to bring this to your attention and seek your guidance on how to resolve it.

### Issue Details:

The following warnings are appearing in my server logs repeatedly:

`
2024/09/24 12:37:02 [error] 677#677: *15397 FastCGI sent in stderr: “PHP message: PHP Warning: Undefined property: WP_Post_Type::$slug in wp-content/plugins/td-cloud-library/includes/tdb_functions.php on line 835; PHP message: PHP Warning: Undefined property: WP_Post_Type::$slug in wp-content/plugins/td-cloud-library/includes/tdb_functions.php on line 1586; PHP message: PHP Warning: Undefined property: WP_Post_Type::$term_id in wp-content/plugins/wordpress-seo/src/helpers/current-page-helper.php on line 135; PHP message: PHP Warning: Undefined property: WP_Post_Type::$slug in wp-content/plugins/td-composer/legacy/common/wp_booster/td_util.php on line 1230
`

These warnings occur while accessing certain pages that use custom post types or taxonomies. Below is more specific information:
– **NGINX**
– **PHP Version**: 8.2 (using FastCGI with Nginx)

### Logs:
The errors seem to originate from the following files and lines:

– /wp-content/plugins/td-cloud-library/includes/tdb_functions.php on lines 835 and 1586
– /wp-content/plugins/td-composer/legacy/common/wp_booster/td_util.php on line 1230
– /wp-content/plugins/wordpress-seo/src/helpers/current-page-helper.php on line 135

The warnings mention undefined properties like WP_Post_Type::$slug and WP_Post_Type::$term_id. This seems to suggest there might be an issue with accessing properties that don’t exist in the WP_Post_Type class.

### Site Setup:
– **Custom Post Types**: I am using custom post types, but they are registered with valid slugs. The issue seems to arise when your plugin/theme is trying to interact with these post types.

### Request:
Could you kindly investigate these warnings and suggest a possible fix or workaround? Additionally, if this is something that could be addressed in a future update, please let me know.

If you require any further information or access to my environment to assist in troubleshooting, I would be happy to provide it.

Thank you
—