Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • robjakedorsett 11 posts 61 karma points
    1 week ago
    robjakedorsett
    0

    ExamineX - Price Picker

    Hi Matt, We have moved over to ExamineX due to the known issues with hosting Umbraco on azure.

    Everything seems to be working swimmingly, except this has started appearing: Vendr Price issue

    We typically got this when the internal index was having issues, internal index with ExamineX seems fine, and I have even rebuilt it, with no joy.

    I'm wondering if this is a known issue with ExamineX & Vendr?

    Thanks, Rob

  • Matt Brailsford 3343 posts 17706 karma points MVP 8x c-trib
    1 week ago
    Matt Brailsford
    0

    Hi Rob,

    Hmm, no, I've never head of this issue with ExamineX before (but granted, you're the first person I've heard using ExamineX and Vendr together).

    To be honest, I have no idea what ExamineX does / how it affects things but I'd be surprised if it changed the search API.

    Ultimately what Vendr does is use the internal index to search the current pages ancestry to locate to node with a store picker. For some reason it looks like that query is failing. That query is built up using a raw lucene query though so maybe something isn't supported in ExamineX?

    I'm not exactly sure how to resolve this one though, might need a bit of input from Shan on this one. 🤔

  • robjakedorsett 11 posts 61 karma points
    1 week ago
    robjakedorsett
    0

    Thanks for the response Matt,

    Yeah it looks like ExamineX auto converts Lucene queries into something Azure Search will understand (https://examinex.online/querying).

    But my guess is you are correct regarding the raw lucene. I guess there must be an issue somewhere.

    Is there any way for us to extend/override the default with this?

  • Matt Brailsford 3343 posts 17706 karma points MVP 8x c-trib
    1 week ago
    Matt Brailsford
    0

    Hmm, unfortunately not. It's currently all just hard coded into a helper.

    I have spoken with some other devs about the possibility of creating a "StoreLocator" of sorts which would be responsible for looking up a store from a node ID, but it's only discussions atm. It still needs thoroughly investigating to see what is involved and what changes would be needed.

    Even so, this would ultimately just make it your problem though needing to replace the implementation.

    I could do with knowing if there is a way to make our query compatible, or whether it's down to the fact I'm using a raw query and that just isn't supported?

  • robjakedorsett 11 posts 61 karma points
    1 week ago
    robjakedorsett
    0

    Hey Matt, I've raised the question with Shan can be followed here - https://github.com/SDKits/ExamineX/issues/54

    Thanks, Rob

Please Sign in or register to post replies

Write your reply to:

Draft