AFTER XSTORE UPDATE, AJAX SEARCH SHOWING CRITICAL ERROR

This topic has 6 replies, 2 voices, and was last updated 2 years, 6 months ago ago by ibukun

  • Avatar: ibukun
    ibukun
    Participant
    June 21, 2022 at 13:10

    Hello,

    Once you search for any product on the website, for instance, “cerave” via ajax search, it goes into critical error and this started after the xstore update to the latest version.
    Please could you look at it, i’ve sent the screenshot via the private content area.

    Please, contact administrator
    for this information.
    5 Answers
    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    June 22, 2022 at 08:20

    Hello,

    Enable debug mode in WordPress – https://wordpress.org/support/article/debugging-in-wordpress/ to find out what error appears on your site, it will point you in the right direction what needs to be fixed.
    Also, check server error log.
    Let us know results.

    Regards

    Avatar: ibukun
    ibukun
    Participant
    June 22, 2022 at 09:43

    Hello,

    I’ve debugged the site and i’ve attached the error. Please let me know how this can be fixed.

    Please contact administrator
    for this information.
    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    June 22, 2022 at 12:10

    Hello,

    Thanks for the reply.
    Contact support of WooCommerce plugin.
    Also, provide us with FTP access, so we can take a closer look. If you do not know how to create FTP contact with your hosting provider, they will help you.

    Regards

    Avatar: ibukun
    ibukun
    Participant
    June 22, 2022 at 12:34

    Hello, I’ve attached the ftp details, please let me know what’s next.
    Regards.

    Please contact administrator
    for this information.
    Avatar: ibukun
    ibukun
    Participant
    June 22, 2022 at 12:44

    Hello, I’ve updated woocommerce and that seems to have fixed the issue. Thank you.

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

The issue related to '‘AFTER XSTORE UPDATE, AJAX SEARCH SHOWING CRITICAL ERROR’' 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.