Welcome to our FAQ section dedicated to Findstr. Here, you’ll find answers to common questions, practical tips to fully utilize its features, and quick solutions to resolve any potential issues.
Yes, our promise is to deliver an Open Source product. In addition to the text extraction feature, which is a separate module, all of Findstr’s functionalities are available within the Open Source extension.
Of course! You can use Findstr without subscribing to Findstr Cloud. To do so, you’ll need to deploy a search server that meets Meilisearch’s requirements. The advantage of Findstr Cloud is that you can access all the extension’s features instantly. Our Findstr Cloud service provides hosting for your search results and a ready-to-use solution. Don’t hesitate to contact us!
Currently, Findstr is fully compatible with Gutenberg. Our team is currently working on adapting it to Elementor with the generation of ShortCodes. In the meantime, the solution is compatible with Elementor’s block manager.
FacetWP does not natively allow text search. It is an extension primarily focused on filters. You need to add an extension like Relevanssi for that, whereas Findstr handles both cases.
Additionally, FacetWP relies on WP Query to execute its filters, thus using PHP, while Findstr uses JavaScript directly without using server resources.
Findstr is currently compatible with simple product catalogs. We are currently working on compatibility for variable products.
The Event Calendar does not use WordPress’s native loop, unlike Findstr. Findstr is (not yet) compatible.
Yes, Findstr allows you to create content catalogs (listings) either through code. Our team is currently working on implementing Gutenberg blocks to make it easier to display content catalogs.
