tag: ezfind

While the usage of Apache Solr through the eZ Platform Search API is pretty much straightforward and well documented, where do we fall short is on how to set it up.

Solr is an excellent search engine. We are using it for years through eZ Find (its an eZ Publish extension for searching) and its really powerful and flexible solution. Our use cases are not that complex so we never actually hit into a wall with Solr. But there is one problem when building search solutions in general which we encountered few times and for which Solr has no feature. It happens when the language of the indexed content is some language that we as integrators don't understand.  

Few years back when eZ Find (on github) showed up we soon started to deploy it on almost every site we were implementing. The hearth of eZ Find is Solr - a Lucene based java search engine with REST interface. Bundled wit eZ Find comes Jetty for running the whole java stack with one command to keep the usage as simple as possible. We switched to Apache Tomcat instead. Learn why.

Since we tagged eZ Tags extension as stable on GitHub few weeks ago, we thought this would be a good time to write something about how to install eZ Tags extension and common usages.

Some of us at Netgen attended eZ Conference a few weeks ago in Berlin (and had a great time there :-), so we would like to present eZ developers with a small summary on few topics that we think are important.

In this blog post we present a simple example on how to build a spatial search with eZFind. The most common usage of the spatial search would be finding  the nearest locations available and this is what we are describing here.