These are chat archives for
Sign in to start talking
May 03 15:41
May 03 15:49
first, you can implement a basic search based on the
but you will only query the content entries
but if you had in mind to use Algolia, that’s another story
May 03 15:50
May 03 15:50
the main problem with Algolia is that it’s very flexible and really powerful and on the other site, content entries are highly flexible too.
so it makes really hard to implement something flexible :-)
yeah, it’s paradoxal, agreed with that
our initial Algolia implementation in v2 was okay but once you wanted to really use the power of Algolia, you were stuck.
with v3, things are not really different
what we could do is to index everything in Algolia and use different indices
May 03 15:57
, last week, we’ve started building a gem to make Locomotive as an e-commerce frontend component inside the Odoo platform (the biggest open source ERP).
the interesting part is that we’ve used Algolia as a kind of database which can be queried in liquid thanks to the with_scope tag.
It’s working really great.
but it requires custom code which will vary from one Locomotive site to another one.
May 03 16:01
I personally think its great
I have no idea how Odoo works so its hard for me to image the integration but I will take a look at it soon
I am fine with the idea of having to write custom code
per website that requires that integration
May 03 16:07
would be the name of the index
the algolia_service includes a lot of custom code