FAQ #

What do you mean not fast enough? #

All indexing, as well as the search, requires disk space. If the disk can not respond fast enough to a write, either PHP or Java will stop and throw an error

Do you support synonyms? #

Yes! Including US to UK spelling synonyms by default!

Fast? #

Yes, very fast

Compatible with the Fulltext Search Module? #

99% and counting! Have a look at the compatibility module

Why do I need to name my index? #

You have a name yourself, don’t you? It makes sense to name the index too.

Only File storage? #

Currently, this is indeed the only storage mode supported.

My core.properties won’t persist, what gives? #

Most likely, you’re running a vagrant or docker machine? And even more likely running it on Linux.

A solution is to create a symlink in /var/solr/data/{your-policy-name}/ to /var/www/{yoursite}/.solr/conf, so the conf folder points to your locally-writable folder for Vagrant.

In your search.yml, add the following as the location of your FileStore config:

Firesphere\SolrSearch\Services\SolrCoreService:
  store:
    path: '/var/solr/data'

That way, Solr will write its own files to the correct core folder where it can write, but your config can still live inside your project.

Or, a better way for production environments is described in Known issues

I would like a feature to be added! #

I would like an issue to be created

Dealing with errors #

Especially when using facets, you should not redeclare fields to be filterable as well. If you run in to an error saying you have duplicate fields, check your configuration for overlaps e.g. FilterFields does not have an overlap with FacetFields

@package tag #

The package tag is to help the API documentation to stay up to date.

We are aware it’s a bit of overkill and redundant, but it does not have any impact on the actual code.

GitStore #

As you may know, Open Source Software is written by volunteers. We volunteer a lot of our free time to work on this (and other) software.

If you can afford it, we would appreciate it a lot if you would sponsor us through GitStore.

But your software is free and open, isn’t it? #

Yes, but it still costs us time to respond to issues, look at pull requests or even support you with problems outside of the module.

We are happy to help you, but we have put a lot of time and effort in to writing software that is useful to you, the community. We ask you, would you give something back? It is not mandatory, of course.

We will add you to the list of sponsors, if you decide to thank the maintainers for this work.