This website uses cookies to personalize your experience. By using this website you agree to our cookie policy.

Front-end search Error After Update from 4.22.5

Home Forums Product Support Forums Ajax Search Pro for WordPress Support Front-end search Error After Update from 4.22.5

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #39308
    SourojitSourojit
    Participant

    Hi Ernest,

    I am facing a weird issue. After the latest, the search stopped working. it is giving an error as attached. I tried clearing the cache and downgrading the WPRocket plugin as they all got updated together, but nothing worked.

    I then downgraded ASP to 4.22.5 from my backup and it is working as intended with the updated Cache plugin as well.

    So, 4.23 or even 4.23.1 both are throwing the same error as in the screenshot. I did a basic check, admin-ajax is working.

    #39313
    Ernest MarcinkoErnest Marcinko
    Keymaster

    Hi,

    This error is caused by an uncleared browser, minify or CDN cache. The older version javascript files (which must be heavily cached), while the response from the server is from the newer release – and the old version of the script can not verify that.
    This very rarely happens, as we don’t change the output significantly, but in this case we had to change the response delimiters for compatibility reasons, and the cached script from 4.22.5 and below will throw this exact error for the new server response.

    If you clear all layers of cache – including minify, asset, CDN, page, browser etc.. it will resolve the issue for sure.

    #39314
    SourojitSourojit
    Participant

    Hello,

    The only thing that I did not clear is the CDN Cache. Will give it a try as well. I hope all goes well.

    #39315
    SourojitSourojit
    Participant

    Hello,

    Yup, CDN cache clearing fixed it. Thanks 🙂

    #39316
    Ernest MarcinkoErnest Marcinko
    Keymaster

    You cannot access this content.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.