Multiple Search Pages Based on Post Type

  • Resolved schwindt14

    (@schwindt14)


    1 year, 4 months ago

    Does this plugin have the flexibility to deploy multiple search pages based on specific post types? For examples, I’ll use our current site, which I’d like to migrate over to Algolia if possible:

    1. We need the ability to search/browse/filter a post type “Products” like this: https://www.newageindustrial.com/shop/
    2. We also need the ability to search/browse/filter a post type “Resources” like this: https://www.newageindustrial.com/resources/

    From what I can tell, the plugin currently allows you to index multiple post types, but does not allow you to deploy separate search pages of different scope based on post type (as the examples above). Am I correct? If I’m mistaken, perhaps you could point me in the direction of some relevant documents.

    NOTE: I’ll add that although the examples above are built around WooCommerce, we’re rebuilding the site in a way that discards WooCommerce and just uses custom post types.

    I’m posting here because I have reached out to WebDevStudios to ask about contracting them to help with this functionality, but they said I should ask here first in case there’s a simple answer. I assumed that this functionality was not readily available with the plugin as it stands, without coding knowledge that is beyond my own abilities

    Thanks!

    • This topic was modified 1 year, 4 months ago by schwindt14.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    1 year, 4 months ago

    Hi,

    I know I previously blogged about a similar topic, and it may be a great match for you here.

    https://michaelbox.net/2022/10/change-algolia-autocomplete-sources-by-location-in-wordpress/

    That said, I think any example making use of filters would also work. For example, our docs on WPML https://github.com/WebDevStudios/wp-search-with-algolia/wiki/WPML where it’s demo’ing storing the current language displayed, and limiting results to that language, after storing the record’s language.

    For you, i think the only parts you’d need to cover is making sure the post_type property is marked as an attribute for faceting, which the wiki page above shows how to do for locale, edit as needed and push settings if handling settings via code. Algolia Dashboard otherwise.

    Then it’s just a matter of getting the current shown post type stored in a javascript variable to pass via Algolia filter, like towards the bottom of the wiki page shows.

    Try things out, let us know if you have questions or hit road bumps.

    Thread Starter schwindt14

    (@schwindt14)

    1 year, 4 months ago

    Thank you Michael, I appreciate this. I’ve read through the articles once, and while I understand some of what’s going on, it’s probably over my head in many respects. I’ll see if I can make any headway by experimentation and post my questions here. Or, if it turns out to be too much, I’ll reach back out of your sales folks. Thank you for your time.

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    1 year, 4 months ago

    Since my brain is going “whirrrr” a bit here. Is this for autocomplete or instantsearch, or both?

    Thread Starter schwindt14

    (@schwindt14)

    1 year, 4 months ago

    Hi Michael, here’s a clarification on what I’m after, also showing an example from the Algolia website that I really liked: http://somup.com/cTneraKtXu

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    1 year, 4 months ago

    Thanks for that video, and it all makes overall sense. Definitely think that my advice from earlier is a way forward still but also understand getting in over one’s head as well. I have also kept the folks who pointed you here first, in the loop in case we do need to go about working together at that more hands on level.

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

The topic ‘Multiple Search Pages Based on Post Type’ is closed to new replies.