Undefined property: stdClass::$queries

  • Resolved joncon62

    (@joncon62)


    5 months, 2 weeks ago

    I’m sorry but I have another bug showing up. Here’s the error log.

    [17-Dec-2025 13:11:18 UTC] PHP Warning:  Undefined property: stdClass::$queries in /.../wp-content/themes/blocksy/inc/integrations/custom-post-types.php on line 225
    [17-Dec-2025 13:11:18 UTC] PHP Warning:  foreach() argument must be of type array|object, null given in /.../wp-content/themes/blocksy/inc/integrations/custom-post-types.php on line 225

    I am using BetterDocs 4.3.2. If I roll back to 4.2.7 the error goes away.

    Any ideas what is causing this?

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support Sadman Sakib Nadvi

    (@sadmansakibnadvi)

    5 months, 2 weeks ago

    Hello @joncon62,

    Thank you for reporting this and for sharing the error log.

    The issue has been identified on our end as well, and the development team is already investigating it. Please allow us a bit of time to prepare a fix; an update will be shared with you here as soon as it is ready.

    Wishing you a great day ahead.

    Plugin Support Sadman Sakib Nadvi

    (@sadmansakibnadvi)

    5 months, 1 week ago

    Hello @joncon62 ,

    Thank you for sharing the error details from your log.

    Our development team has thoroughly investigated this issue and confirmed it originates from the Blocksy theme’s file at wp-content/themes/blocksy/inc/integrations/custom-post-types.php on line 225. The error appears specifically when viewing single pages of custom post types like BetterDocs docs or WooCommerce products, as Blocksy attempts to access a non-existent $queries property on a stdClass object. We tested BetterDocs with block themes like TwentyTwentyFive and GeneratePress, where no errors occurred, isolating the problem to Blocksy’s code. Please check this: https://d.pr/i/289vTk Please report to Blocksy support. Good day.

    Thread Starter joncon62

    (@joncon62)

    5 months, 1 week ago

    Hi @sadmansakibnadvi, I have re-opened this thread as the developers at Blocksy have a response for you. They are going to make a change to their code, but it sounds like this is masking a problem with your implementation.

    This is their report.

    The override of tax_query with a class that doesn’t remotely resemble the actual WP_Tax_Query is unsafe: https://share.cleanshot.com/gYNkmddk

    The issue appears to be caused by BetterDocs in the first place, as they’re overriding a standard field with a non-standard object. This type of override is concerning, and a better approach would be to use the built-in hooks to modify the query behaviour. If this override method is necessary, all fields from the standard class should be included in the dummy object: https://developer.ww.wp.xz.cn/reference/classes/wp_tax_query/

    If you or other users want to view the other thread you can find it HERE.

    Plugin Support Sadman Sakib Nadvi

    (@sadmansakibnadvi)

    5 months, 1 week ago

    Hello @joncon62 ,

    Thanks a lot for sharing this and for passing along the detailed feedback from the Blocksy developers.​

    This has been forwarded to our development team so they can review the tax_query handling and adjust the implementation accordingly. Good day.

    Plugin Support Sadman Sakib Nadvi

    (@sadmansakibnadvi)

    5 months ago

    Hello @joncon62,

    Thank you for your patience.

    Our development team has implemented a fix for the issue you reported, and a dev build is now available here: https://d.pr/f/6khTkf. When you have a moment, please try it out and let us know if the warning is resolved on your end.

    Thank you.

    Thread Starter joncon62

    (@joncon62)

    5 months ago

    Thanks for the follow up. I can confirm that the development version the build no longer shows those Undefined property errors.

    Plugin Support Sadman Sakib Nadvi

    (@sadmansakibnadvi)

    4 months, 2 weeks ago

    Hello @joncon62 ,

    Thank you for your patience.

    We’ve released the fix, and the issue has been resolved in BetterDocs v4.3.5. Please update to the latest version and let us know if you notice anything unusual or need further assistance. We’ll be happy to help.

    If you don’t mind, could you please take about 30 seconds to leave us a quick review? Your feedback means a lot to us and helps us keep improving BetterDocs for you and other users.

    You can submit your review here: https://ww.wp.xz.cn/support/plugin/betterdocs/reviews/#new-post

    Thanks again for your cooperation and support. Have a great day!

    Thread Starter joncon62

    (@joncon62)

    4 months, 2 weeks ago

    Thanks for following this up with me. I can confirm the fix works.

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

You must be logged in to reply to this topic.