Eric Saner

Algolia settings use the $index->setSettings method, but rules use [$index->saveRule](https://www.algolia.com/doc/guides/managing-results/rules/merchandising-and-promoting/how-to/combining-multiple-consequences/#using-the-api), so I don't think your settings hooks would work.

Pushing settings does not delete Rules added via the Algolia dashboard. So I can do it that way for now. Would be great if I could set this via the...

Thanks for looking more into it! I think at this point it's just easier to use the Algolia dashboard, though I'd much prefer using the API. Consider this a feature...

@tw2113 any progress to report on this? Would love to see it resolved. Removing jQuery as a dependency for templates would be great, but even just a filter to control...

I replaced the jQuery in autocomplete.php and have it working now with jQuery loaded in the footer. But note that under /* Setup dropdown menus */ in autocomplete.php `document.querySelectorAll(algolia.autocomplete.input_selector);` didn't...

+1 This would be great, especially for long forms. Both options would be helpful, but if only one were done first, I think providing a default message with all fields...

Any update on this feature? It'd be helpful to have built in payment options. Could be a good feature for HTML Forms Premium.

Experiencing this same issue. @sandipeq did you ever resolve it?

This would be helpful! Please also include a simple option for logged-in/not-logged-in (which would cover all user roles).

`chart.data(data).setCentered(results[0]).initialZoom(1).render()` worked for me, where `results[]` gets filled as nodes are highlighted. Just need to add a conditional to make sure there's only one result. ``` let chart; function filterChart(e)...