• Resolved tonyp83

    (@tonyp83)


    Hi,

    I’ve got my sitewide search menu working in the header and it looks and works great.

    I have a custom post type for People which also has its own filtering page that works with Search. This is currently also being linked to Algolia and not the page itself – which makes sense as I have Algolia set to hijack all search forms and be applied.

    My question is, is it possible to have the second instance not use Algolia via the plugin in an easy way to implement? I’m guessing it’ll be a case of using instantsearch.js but thought I’d ask as someone else may have had the same requirement.

Viewing 3 replies - 1 through 3 (of 3 total)
Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Second Search Instance NOT to use Algolia’ is closed to new replies.