Switching Apps Certain Terms Fail

  • Resolved bmoredrew

    (@bmoredrew)


    2 years, 5 months ago

    In upgrading from the now deprecated Algolia supported plugin, we switched to the WDS supported plugin, and have had no issues with a semi-custom implementation built off the plugin until we switch from a TEST app in algolia to a PROD app. Indices are the same, codebase is the same.

    After switching, certain terms no longer get a response from algolia API. Even if they 200 OK from the post, no json response is returned. Or they won’t post at all sometimes it seems.

    This is the customization that has been done:

    https://gist.github.com/bmoredrew/dd7bd0205c3d5bc854d0eb0a7eb67d17

    Otherwise plugin is out of the box. Glad to provide more context.

    • This topic was modified 2 years, 5 months ago by bmoredrew. Reason: removed link to walkthrough video because of api keys
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Hey Drew,

    Do you have a public facing link that we could see the instantsearch results at?

    Thread Starter bmoredrew

    (@bmoredrew)

    Yes!

    Working: https://dc360uat.wpengine.com/?s=marketplace
    Not working: https://dc360staging.wpengine.com/?s=marketplace

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Hmm.

    One thing I’m definitely seeing, and I believe you highlight above, is that there’s no POST request even being issued.

    Screen Shot

    Left hand side has the POST request highlighted and is the working link. The right hand side does not have the POST.

    Out of curiosity, have you tried it out with the default templates being used instead of the customized version?

    I know you’ve mentioned, but i feel like I should double check, wp_searchable_posts_n2o has the index name. For example in the shipped template file, we specify algolia.indices.searchable_posts.name with the .name property from the overall algolia object.

    Thread Starter bmoredrew

    (@bmoredrew)

    Yeah I’ve tried everything you could possibly think of, it’s eluding me! I did try switching back to default stuff and no change.

    We found a workaround by directing users to an already instantiated page. Appreciate you looking at this though.

    Side question, and I can start a new topic if you like?

    When I click re-index on an individual index from the UI, I see delete requests in the algolia log but no push to add/update. I can it via CLI and same result (now empty index).

    Algolia log for a “batch”:
    https://gist.github.com/bmoredrew/33f05d7cf6166f4d3f5bd24928dfaf44

    It calls them batch but seems to send individually? So like 1500-ish requests. If I did this on the main index it would be over 200k.

    This is output from CLI w/ debug:
    https://gist.github.com/bmoredrew/c34564987d46087e0d07c547b67dd6c0

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Hmm, not sure on those parts regarding the logs, as I haven’t really ever had to delve into those topics.

    You’re referring to the XHR requests in your browser dev console, correct? For the delete requests but no add/updates?

    I just ran a re-index on a personal site where I’m using instantsearch as well, and I didn’t see any discerning details regarding if it was an add/update/delete, just that it was a reindex and what page it’s on, with the XHR requests.

    Thread Starter bmoredrew

    (@bmoredrew)

    Well, moved it to another env and it just started working fine… thanks for looking at it and appreciate all the help!

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Very odd, but glad it’s at least working finally.

    Let us know if you need anything else Drew.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Switching Apps Certain Terms Fail’ is closed to new replies.