WPSOLR
Forum Replies Created
-
Sorry for the delay—I missed your notification.
is there a way to ensure that content in protected areas of a site?
No, not with the On The Shelf plugin. This behaviour depends on the protection plugin in use (e.g., Groups).
on certain pages I would like a search bar which only searches for items in a particular category
Yes—if you can add a hidden field to your search forms that includes a WPSolr filter for your category.Sorry for the delay—I missed your notification.
Yes, you can remove all posts of a specific post type from your index:
- Open the “3. Process data” tab
- Unselect all post types except the one you want to remove from the index
- Click the “Delete selected documents” button
Sorry for the delay—I missed your notification.
You’ll need to enable the_skucustom field for the product post type in screen 2.2 and then reindex all products.👍
WPSOLR Free 24.0.2, without Monolog, is out.
Thank you for your feedback. I’ll test WPSOLR Free without Monolog and deploy a new version if the results are conclusive.
I’ll leave this thread open until then.
Dear @flaviusv,
I appreciate your interest in using WPSOLR.
While we’re glad to support your efforts, please note that with the WPSOLR Free version, we unfortunately do not offer assistance with setting up or troubleshooting Elasticsearch servers, nor do we provide in-depth configuration support. This is primarily due to the technical complexity involved in properly managing a local Elasticsearch installation.
Patrice
(deleted)
3. “No Mapping Found for Field” / “Fielddata is Disabled” Errors
These are related to field configurations in your Elasticsearch mappings.
Solutions:
- “No mapping found for field [spell]” → This suggests WPSOLR or a query is looking for a non-existent field. Ensure the field
spellis enabled in your WPSOLR search schema or remove it from the query. - “Fielddata is disabled” → Elasticsearch does not allow sorting/aggregations on
textfields by default.
Fix: the index was probably created outside of WPSOLR. Please create the index in WPSOLR first, then index.
2. Search Error:
max_analyzed_offsetExceededCause:
Elasticsearch has a default limit of 1,000,000 characters for highlighted fields. One of your posts has a very largecontentfield (over 2 million characters), which triggers this.Solution:
- Option B: Increase Limit in Elasticsearch Increase the limit by updating the index settings in the Kibana dev tool:
PUT /xxxsearch/_settings { "index.highlight.max_analyzed_offset": 5000000 }This allows longer fields to be highlighted but may affect performance.
Hi Flavius,
1. Index Disappeared – “Index Not Found” Error
Cause:
This typically occurs when the Elasticsearch index was deleted (manually, automatically by retention settings, or due to storage issues).Solution:
- Recreate the index from WPSOLR, then reindex from “Synchronize with index”.
- Ensure your Elasticsearch instance is not restarting or clearing indices, and there’s enough disk space and memory.
- If you’re using a VDS, check if there’s any cronjob or backup process that might be removing old indices.
You can check the contents of your Elasticsearch index, to verify if the author is present.
The contact form is located in the header and footer of our website. We don’t typically sell ready-made plugins, but we offer a complete service for search, recommendations, and AI data integration.
(like ingesting pdfs, docx, xlsx, pptx with undefined.io or Docling. Or ColPali)
WPSolr free is only working with self-hosted engines.
Using Kubernetes gives you scalability and fault resistance, as data and queries are distributed across nodes.
But Docker is great. The plugin description has a link to install Weaviate on Docker.