Download the PHP package signify-nz/silverstripe-solr-search without Composer

SilverStripe Solr Search

Advanced, Solr-powered search for SilverStripe 4 and 5, built on Solarium. Define what to index in PHP, configure connections in YAML, and query Solr with a fluent API.

Based on firesphere/solr-search. This is the signify-nz maintained fork.

Features

• Code-defined indexes — declare indexed classes and fields in a PHP index class.
• Rich field types — full-text, filter, facet, sort, stored and copy fields.
• Faceting, boosting, fuzzy search, elevation and advanced filters/excludes.
• Spellcheck & suggestions for "did you mean" experiences.
• View-permission aware — results are filtered by each member's canView rights.
• ShowInSearch handled automatically — hidden pages/files are removed from the core.
• Queued indexing via silverstripe/queuedjobs, indexing live content only.
• Subsites, Fluent, Elemental and Fulltext-Search compatibility submodule support.
• Pluggable config stores — file-based or HTTP POST to a remote Solr.
• Works with Solr 4 (backward compatible), 8 (default) and 9.

Requirements

• PHP 7.3+
• SilverStripe Framework 4 or 5
• symbiote/silverstripe-queuedjobs
• A running Solr instance (4 / 8 / 9) reachable from the application
• Solarium (installed automatically via Composer)

Installation

See docs/01-Installation.md for details.

Quick start

1. Configure the Solr connection

Connection details are set in YAML. Defaults assume a Solr instance on localhost:8983, so this step can be skipped for local development.

See docs/03-Set-up-and-Configuration.md for authentication, config stores and all available options.

2. Define an index

Create an index extending Firesphere\SolrSearch\Indexes\BaseIndex. The init() method declares what is indexed; getIndexName() names the Solr core.

3. Configure the core and index your content

Make sure the queued-jobs runner is processing jobs (and restart long-running workers after deploying code changes, so they pick up the new classes).

4. Run a search

5. Render the results

A fuller example (facets, sorting, spellcheck) is in docs/04-Searching.md.

Tasks

Indexing reads from the live stage, so only published content is added to the search index. A standard SolrIndexTask adds/updates documents but does not clear the core, so after changing index definitions run SolrConfigureTask (or a clearing reindex) to drop stale documents.

Key concepts

• ShowInSearch is managed by the module. Setting it to 0/false removes the page or file from the core via onAfterPublish/onAfterWrite or the next index run — do not add it as a custom indexed field, as that causes unexpected behaviour. See docs/03-Set-up-and-Configuration.md.
• View permissions — each document stores a view-status field so results are filtered to what the current member may canView. See docs/11-View-Permissions.md.
• Dirty classes — records that fail to push to Solr are tracked so they can be retried rather than silently lost. See docs/12-Dirty-classes.md.
• Config stores — FileConfigStore (local path) or PostConfigStore (HTTP POST to a remote Solr). See docs/06-Advanced-Options/06-Stores.md.

Documentation

Full documentation lives in the docs folder:

• Setup & configuration
• Customisation
• Advanced options: Stores
• Subsites
• Submodules: Elemental

Please read the documentation before raising questions — most are answered there.

Solr version support

Solarium

This module is built on Solarium; its documentation is a useful reference for lower-level query behaviour.

Contributing

Contributions are welcome — please raise an issue and, ideally, an accompanying pull request. See the code of conduct and contributing guide.

Security

Please report security issues responsibly as described in our security policy.

License

LGPL v3.

Disclaimer

If this module breaks your website, you get to keep all the pieces.