• This may not be your problem but the following error is being flagged in your file which is filling up my error log:

    [17-Dec-2025 12:27:11 UTC] PHP Warning:  Undefined property: stdClass::$queries in /.../wp-content/themes/blocksy/inc/integrations/custom-post-types.php on line 225
    [17-Dec-2025 12:27:11 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

    Any help tracking down the problem will be most welcome.

    I am running 2.1.23 Theme and Companion

Viewing 6 replies - 1 through 6 (of 6 total)
  • Hello @joncon62

    We can investigate this for you. Please create a snapshot of your website using this plugin: https://wordpress.org/plugins/all-in-one-wp-migration/ and send the file via Google Drive through our website: https://creativethemes.com/blocksy/support/. Our engineers will review it and get back to you with their findings.

    Thanks,
    Eduard

    Thread Starter joncon62

    (@joncon62)

    Thanks for offering to help. I found the error to originate from the BetterDocs plugin and they are now investigating. I will mark this as resolved as it’s not your issue.

    Hello @joncon62

    Got it. Thank you for letting me know! 🙇‍♂️

    Thread Starter joncon62

    (@joncon62)

    Hi @cteduard,

    I have re-opened this thread as BetterDocs have now got back after investigating and say it is a problem with the Blocksy theme. This is their report:

    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.

    Hello @joncon62

    Thank you for the clarification.

    I’ve spoken with the developers, and they’ve confirmed that the warnings will be addressed in the next public Blocksy update. If you’d like to receive a pre-release version for a faster resolution, please submit a ticket through our website: https://creativethemes.com/blocksy/support/

    Additionally, the developers have informed me that this isn’t necessarily a theme issue, but rather relates to BetterDocs’ implementation. I’d recommend informing the BetterDocs team about this matter as well. Here’s what our developers had to say:

    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.wordpress.org/reference/classes/wp_tax_query/

    Hope this clears everything up!

    Thanks,
    Eduard

    Thread Starter joncon62

    (@joncon62)

    Hi @cteduard, thanks for your reply and the report. I will feed that back to BetterDocs. If you or any readers want to see the other thread you can find it HERE.

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

You must be logged in to reply to this topic.