Weave Code
Ezsolrsearchextrabundle Laravel Package
novactive/ezsolrsearchextrabundle
An eZ Platform bundle that extends the Solr search handler with binary file text indexing, a configurable FullText criterion with field and date boosts, custom field setup, exact-match boosting, and admin-managed stopwords and synonyms.
An eZ Platform bundle which extend the solr search handler.
Frequently asked questions about Ezsolrsearchextrabundle
- Is novactive/ezsolrsearchextrabundle a Laravel package?
- No. It is a Symfony bundle built for eZ Platform and Ibexa (the legacy eZ Systems lineage) that decorates the platform's native Solr search handler. It has no service provider, no Laravel facades, and no adapter layer, so it will not install into or run inside a Laravel application. If your roadmap item is 'add Solr boosting to our Laravel app', use a first-party Solr client or a Scout driver instead.
- How do I install novactive/ezsolrsearchextrabundle?
- Install it with composer require novactive/ezsolrsearchextrabundle, then register EzSolrSearchExtraBundle in your bundles.php (or app/AppKernel.php on older skeletons). You also need to add the bundle's routing config for the admin controllers and configure or override the Solr search handler. After that, reindex your content so the extended fields are populated, otherwise the new criteria will not match anything.
- What features does this bundle add to the eZ Platform Solr search handler?
- It adds plain-text indexation of binary file contents into the full-text field, a parameterized FullText criterion that can search and boost multiple fields, boost by publish date, boost phrase matches, and boost exact matches. It also supports custom field configuration, exact-match boosting configuration, and managing stopwords and synonyms from the eZ Platform admin interface. Date-based scoring and highlighting are listed as work in progress.
- Does this bundle support Laravel 10/11 or a plain Symfony application?
- Neither. The bundle is coupled to eZ Platform/Ibexa search handler contracts, index schema, and content model, so it only fits an application that already runs eZ Platform or Ibexa with the eZ Solr search engine in the stack. There is no compatibility layer for vanilla Symfony or Laravel, and the README does not assert supported Laravel versions because none exist.
- Which Ibexa, eZ Platform, and Solr versions are supported?
- The README does not publish a compatibility matrix, which is a real gap given that the bundle extends the Solr handler at schema level. Verify supported platform and Solr 7/8/9 versions directly against the monorepo and Packagist before planning an upgrade. Handler and schema extensions are exactly the kind of change that breaks silently across platform upgrades, so pin versions and retest search behaviour after every bump.
- How do I configure the FullText criterion with field and date boosts?
- The FullText criterion accepts extra parameters so you can search and boost multiple fields, boost results by publish date, boost phrase matches, and boost exact matches. Configuration details live in doc/fulltext_criterion.md rather than the README, so read the per-feature markdown files before wiring it into your controllers. Because the docs are versioned independently of the code you pin, check them against your installed tag.
- How do I manage stopwords and synonyms?
- Stopwords and synonyms are managed from the eZ Platform admin interface rather than by editing Solr configuration files by hand. That is one of the bundle's more practical features, since it lets content editors tune search relevance without a deploy. You still need to verify the changes propagate to your Solr core as expected.
- Does binary file text indexing require Apache Tika or another external service?
- Yes, in practice. Extracting text from PDFs, Office documents, and similar binaries requires an extractor such as Tika or an equivalent service, and that runtime dependency lives outside this bundle and is not managed by it. You must provision, secure, and size that service yourself. Plan for it as part of the deployment footprint, not as a free feature.
- Where do I report bugs or contribute a fix?
- This repository is a read-only subtree split of Novactive/Nova-eZPlatform-Bundles, so issues and pull requests must be opened on the monorepo. That means you cannot patch in place without either landing an upstream PR and waiting on an external maintainer, or vendoring and forking the package. Treat this as a change-control risk: it caps your ability to hotfix a production search defect quickly.
- What is the license, and is the bundle safe to adopt in production?
- The license shows as NOASSERTION, meaning it could not be machine-identified, so legal must confirm the actual terms and whether the monorepo's license governs the split before you distribute or ship it commercially. Adoption signal is effectively zero: 1 star, 0 dependents, single-vendor maintenance, and release metadata that looks unreliable. For production search in Laravel, prefer Solarium or a Laravel Scout driver; for Ibexa, evaluate the native handler first.
Weaver
How can I help you explore Laravel packages today?