Weave Code
Node Search Bundle Laravel Package
kunstmaan/node-search-bundle
KunstmaanNodeSearchBundle adds Elasticsearch-powered search to Kunstmaan CMS nodes, letting you index and query page content with configurable search services and Symfony integration.
Kunstmaan Node Search Bundle provides a powerful, extensible search layer for node-based content in Symfony applications. It indexes nodes and exposes a configurable search service, letting developers query content by keywords, filters, and relevance without writing custom search logic. The bundle is designed to integrate seamlessly with the Kunstmaan CMS ecosystem while remaining flexible enough for standalone Symfony projects.
- Pluggable search backends and indexers
- Configurable node indexing with custom fields and weights
- Keyword search with relevance-based result ordering
- Twig helpers and controller integration for frontend search
- Extensible architecture for custom search adapters
Frequently asked questions about Node Search Bundle
- Can I install kunstmaan/node-search-bundle in a Laravel application?
- No. This is a Symfony bundle built for the Kunstmaan CMS stack, not a Laravel package. It depends on KunstmaanNodeBundle and KunstmaanSearchBundle, which rely on Symfony's dependency injection container and bundle registration rather than Laravel's service container. Installing it in a Laravel app would mean pulling in the entire Kunstmaan CMS, and Composer will very likely fail on PHP version constraints anyway.
- What does KunstmaanNodeSearchBundle actually do?
- It adds Elasticsearch-powered site search to Kunstmaan CMS sites. It indexes page nodes as they are saved, builds a configurable search index from those nodes, and exposes a frontend search service with paging, highlighting, and filters. Architecturally it is a thin glue layer between KunstmaanNodeBundle and KunstmaanSearchBundle, so most of the real work happens in those upstream packages.
- Is it compatible with Laravel Scout or Eloquent models?
- No. The bundle indexes Kunstmaan node entities through Symfony event subscribers, not Eloquent models, so there is nothing for Laravel Scout's searchable trait to hook into. There is no Scout driver, no queue integration with Laravel's queue system, and no Artisan commands. For Laravel you would reimplement the indexing contract against Scout or a direct search client.
- Which PHP and Symfony versions does it support?
- Expect a 2014-era ceiling of PHP 5.x and Symfony 2.x. The last release was 2014-04-05, long before PHP 8 and modern Symfony, and the transitive constraints from its parent bundles will conflict with a current runtime. This makes Composer resolution the first blocker on any modern project.
- Is kunstmaan/node-search-bundle still maintained, and does it get security fixes?
- No. The repository has no maintainer activity, roughly 8 stars, and zero dependents, with the last release in April 2014. There is no CVE response process and no compatibility work being done. The bus factor is effectively one historical author, so there is no community to escalate issues to.
- What license is the package under, and can I use it commercially?
- Composer reports the license as NOASSERTION, and there is no clear license file in the repository. That leaves redistribution and commercial use legally unresolved. Resolve this with legal review before vendoring, forking, or shipping any of the code.
- What should I use instead of this bundle in a Laravel app?
- Use Laravel Scout with Meilisearch, Typesense, or Algolia for the common full-text search case. If you specifically need Elasticsearch features, use the official elasticsearch/elasticsearch client with a custom indexer and queued jobs. Either path gives you supported dependencies, active maintenance, and integration with Eloquent models and Laravel queues.
- Will the bundled Elasticsearch client work with Elasticsearch 7 or 8?
- No. A 2014-era Elasticsearch client will not negotiate the protocol with a current cluster, and the server APIs have changed substantially since then. Index mappings and analyzers would need rewriting regardless of the client. Treat the old configuration as a design reference, not something you can port verbatim.
- How do I migrate away from KunstmaanNodeSearchBundle?
- If you are inheriting a Kunstmaan application, freeze the bundle at its current version and extract the search contract: what gets indexed, which node fields and translation variants are included, and which query shapes the frontend uses. Read the node-indexing subscribers to recover that mapping, then rebuild indexing and querying against a supported client. Treat the bundle as a specification rather than a dependency.
- Does the frontend search service support paging, highlighting, filters, and typo tolerance?
- The bundle's frontend search service provides paging, highlighting, and filters over the indexed node documents. Typo tolerance and relevance quality come from the search engine and its analyzers rather than the bundle itself. Indexing happens as nodes are saved, so plan for queued or asynchronous indexing if save latency matters to you.
Weaver
How can I help you explore Laravel packages today?