Michael Beckwith

Closing this for the time being as it feels more like an isolated individual issue with templates rather than an overarching issue.

@asharirfan Do we want to get this merged in via the 2.6.0 release?

@asharirfan re-nudge about if we want to get this included as part of any upcoming release. Given that it's all sysadmin style changes, and not user facing, I'm good with...

I haven't tried this out at all, but I do know https://wordpress.org/plugins/search-with-algolia-instantsearch-blocks/ exists, and they recommend installing our plugin as part of the process.

Moving #355 to this issue. Extra thoughts: this probably won't be a case of modifying the existing PHP files, but making FSE compatible equivalents that we could perhaps ship with...

Been toying with this at least a little bit today. I am managing to get custom template files from a theme loaded by instantsearch, but it's definitely going to be...

Momentary last ditch effort failed when I tried to make a shortcode out of our template output, and include that as part of a block template. I believe it was...

Wouldn't necessarily be something we immediately ship with the plugin, but I believe I have an example setup working with TwentyTwentyTwo theme explained over at https://wordpress.org/support/topic/customize-instantsearch-php-with-fse-theme/#post-17319232 Basically it splits the...

I believe it's https://academy.algolia.com/training/3a0e7ce4-7782-11ec-91df-02aea812ea2d/overview where they talk about optimizing relevance and how too many searchable things can actually be detrimental than too few. 250 searchable attributes, I must believe would...

Are you creating these indexes via the Autocomplete settings page? That's the only place I can think of where WooCommerce attributes would potentially get their own index. Otherwise, they'd just...