After updated theme I can see error message

This topic has 5 replies, 3 voices, and was last updated 1 hour, 6 minutes ago ago by Tony Rodriguez

  • Avatar: chutipao
    chutipao
    Participant
    April 17, 2026 at 12:26

    Hello,
    I found a PHP warning in my site
    Warning: Undefined property: WP_Post_Type::$taxonomy in …/functions.php on line 66

    Issue:
    It only appears when clicking a product from search results.
    It does not happen on regular category pages.
    It seems the code is missing an isset() check for the taxonomy property in the WP_Post_Type object.

    what should I do to fix this ?

    4 Answers
    Avatar: chutipao
    chutipao
    Participant
    April 17, 2026 at 12:27

    please see screenshot

    Files is visible for topic creator and
    support staff only.
    Avatar: Ayan Rahman
    Ayan Rahman
    Support staff
    April 17, 2026 at 12:41

    Hi,

    Thank you for your message.

    Your screenshot shows that the code in question belongs to the child theme. Therefore, this code was added either by you or by your developer. We kindly recommend that you contact the person who implemented this custom code, as it will not be present if you download the child theme from our website.

    Best regards,
    8Theme Team

    Avatar: chutipao
    chutipao
    Participant
    April 17, 2026 at 13:13

    Thanks for the support! My topic “after updated theme I can see error message” has been successfully resolved.

    Avatar: Tony Rodriguez
    Tony Rodriguez
    Support staff
    April 17, 2026 at 13:13

    Dear chutipao,

    We really appreciate your time and engagement within the WordPress & WooCommerce community

    Your feedback drives every improvement we make in XStore — helping us deliver a smoother and more flexible experience with each update.

    Your input makes a real difference.

    Topic closed.
    The 8Theme Team

  • Viewing 5 results - 1 through 5 (of 5 total)

The issue related to '‘after updated theme I can see error message’' has been successfully resolved, and the topic is now closed for further responses

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.