SwiftSearch for Typesense
| 开发者 | loopstates |
|---|---|
| 更新时间 | 2026年6月25日 21:44 |
| PHP版本: | 8.0.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
SwiftSearch for Typesense is a search engine replacement for WordPress and WooCommerce. By replacing the default, resource-heavy WordPress database query search with a fast, typo-tolerant engine powered by Typesense, SwiftSearch delivers an autocomplete experience that loads quickly.
Built by Loopstates, SwiftSearch is architected for privacy and direct connectivity. Unlike other search plugins that route queries through a heavy middle-layer proxy, SwiftSearch connects directly from your visitors' browser to your Typesense cluster. No heavy PHP processes are loaded, no database queries are executed on your server, and your customer data remains secure and GDPR-compliant.
Why SwiftSearch & Typesense?
Native WordPress search lacks typo tolerance and can affect database performance under high traffic. SwiftSearch connects your site to Typesense—an open-source, developer-friendly alternative to Algolia.
Whether you run a blog, a directory site, or a WooCommerce store, SwiftSearch ensures your visitors find exactly what they are looking for in real-time.
Official Documentation: https://docs.loopstates.com/swift-search-typesense/
安装:
- Standard installation: Upload
swift-search-typesenseto your/wp-content/plugins/directory or install via the WordPress 'Plugins' screen. - Activate the plugin and navigate to SwiftSearch in your admin menu.
- Follow our 8-Step Setup Wizard in the sidebar:
- Step 1: Connect - Enter your Typesense host, port, and API keys.
- Step 2: Content - select your Post Types (Posts, Products, etc.) and enable the global search override.
- Step 3: Relevance - Manage synonyms and global ranking scores.
- Step 4: Search UI - Configure your instant search behavior and visual result toggles.
- Step 5: Styling - Pick your accent colors and border radius.
- Step 6: Analytics - Review your search trend dashboard.
- Step 7: Pinning - Merchandise specific results to the top.
- Step 8: Sync - Perform your initial bulk index to build the Typesense collection.
屏幕截图:
常见问题:
Do I need a Typesense server?
Yes. You need a running Typesense instance. This can be Typesense Cloud or a self-hosted node on your own VPS.
Is Typesense free?
Typesense is open-source and free to self-host. If you prefer a managed solution, Typesense Cloud offers a paid tier.
Does this work with WooCommerce?
Absolutely. SwiftSearch is WooCommerce-native, indexing product titles, prices, SKUs, and thumbnails automatically.
How fast is the search?
Because of our "Zero-Middleware" architecture, search results are typically returned directly from the browser to your nearest Typesense node.
What is Result Pinning?
Result Pinning (Merchandising) allows you to manually force specific items to the top of results for a given keyword—ideal for boosting sales of specific products or featured content.
How do Synonym Sets improve search?
They allow you to link similar terms together (e.g., "watch", "clock", "timepiece"). If a user searches for one, results for all are returned, improving discovery.
Is the Background Indexing free?
Yes! Our background sync engine is included to ensure every user has a stable search experience.
What is the Facet Configurator?
It's a visual builder found in Step 4 that allows you to easily create and manage multi-select sidebar filters for categories, tags, and custom meta.
Does it work with Elementor or Divi?
Yes. You can use the [swift_search] shortcode in any page builder module, or enable the "Override Default" toggle to automatically replace your theme's search form.
Is my user's data secure?
Yes. We do NOT use a proxy server. All search interactions happen locally between your visitor and your Typesense cluster. No search data is sent to Loopstates.
Does it handle variable products?
Yes, you can map custom metadata (like variation SKUs and prices) to ensure users can find exact product variations in one click.
What insights does Search Analytics provide?
Track your Most Searched Keywords. Our dashboard provides an overview of user trends, keyword volume, and search behavior. It also identifies "Zero Result" queries, giving you a roadmap to optimize your product catalog and content strategy.
更新日志:
1.5.0
- Feature: Dedicated Shop & Catalog Page Mode replacing WooCommerce default shop page with horizontal sorting, sticky pagination, and flat card aesthetics.
- Developer: Added custom JavaScript DOM events (
swift-search:hit-renderedandswift-search:results-rendered) to support custom integrations (wishlists, ratings, ajax cart). - Fix: Resolved price sorting returning zero results by indexing price as a float and utilizing Typesense
missing_valuesparameter support.
- Library: Upgraded Chart.js to v4.5.1.
- Security: Resolved REST API permission callback warning for the /log endpoint.
- Library: Upgraded Chart.js to v4.4.4.
- UI: Removed inactive Coming Soon settings placeholders from styling card.
- Documentation: Consolidated key features and capabilities in the readme file.
- Design: Introduced Plus Jakarta Sans font family.
- Design: Modernized overall admin UI dashboard variables, card borders, radii, and shadows.
- Fix: Unified text/number inputs and select elements heights to prevent alignment mismatch in connection settings card.
- Fix: Resolved a bug where browser-driven indexing fallback ran recursively in an infinite loop upon completion.
- Fix: Set active flag to false in the database when completing index types that are disabled (e.g. user indexing).
- Feature: Added automatic browser-driven AJAX fallback for servers with local loopback or cURL block restrictions (e.g. OpenResty WAF 403 Forbidden blocks).
- Improvement: Added real-time loopback diagnostics printed to the browser developer tools console.
- Maintenance: Force-bust CSS/JS browser cache by appending dynamic version timestamps in admin.
- Security: Implemented universal sanitization for all background processes and REST API inputs.
- Compliance: Refined admin asset enqueuing logic to use official WordPress Screen IDs instead of URL parameters.
- Compliance: Added proper PHPCS logic annotations for all direct database queries on custom tables.
- Compliance: Finalized template variable prefixing ($swift_search_pt) across the entire admin dashboard.
- Security: Complete SQL hardening by removing all variable interpolation from $wpdb->prepare statements.
- Security: Implemented mandatory nonce verification and strict input sanitization for all processes.
- Compliance: Prefixed all internal hooks and variables to ensures zero collisions.
- Compliance: Replaced legacy strip_tags() with wp_strip_all_tags() and fixed deprecated parameters.
- Maintenance: Truncated short description to <150 characters as per repository requirements.
- Fix: Resolved a "ReferenceError: resolve is not defined" in the frontend search script that caused search clusters to fail during user input.
- Improved: Hardened frontend fetch logic to gracefully handle network timeouts and server errors.
- Fix: Resolved a critical JavaScript syntax error in the admin dashboard that caused the "Connect" button to fail silently.
- Improved: Enhanced REST API error reporting for Typesense connection handshakes to provide localized, actionable feedback.
- Stability: Properly scoped variables and added robust XHR error parsing to prevent UI lockups.
- Security: Hardened all database interactions with $wpdb->prepare() for SQL injection prevention.
- Security: Implemented wp_unslash() and safe input handling for background indexing processes.
- Compliance: Replaced legacy strip_tags() with wp_strip_all_tags().
- Compliance: Removed redundant textdomain loading to follow WP.org central translation policy.
- Maintenance: Updated wp_count_terms() and date functions for WordPress 6.7 compatibility.
- Security: Hardened server-side validation for Synonyms, Weights, and Facet parameters.
- Security: Implemented frontend data masking to prevent configuration leakage.
- Security: Optimized Indexer protection to block unauthorized metadata extraction.
- Performance: Optimized connection checking with static caching in Gatekeeper.
- Fix: Corrected accidental "faded" disabled style from the "Show Excerpts" setting.
- Fix: Resolved critical "undefined" JavaScript error when loading the admin dashboard.
- Maintenance: Removed orphaned references to legacy shortcode overrides.
- UX: Reordered Search UI tab to place Experience Options at the top.
- Feature: Fully implemented Frontend visibility toggles for Thumbnails, Prices, and Excerpts.
- Roadmap: Added "Coming Soon" placeholders for Sort Results and Floating Mobile Button.
- Fix: Cleaned up redundant Instant Search override from Shortcode Generator.
- Refactor: Reorganized Experience settings to prioritize Global defaults over overrides.
- Feature: Moved Thumbnail, Price, and Excerpt toggles to Global Experience Options.
- Fix: Consolidate Shortcode Generator to only output attributes for explicit overrides.
- Fix: Resolved a structural JavaScript error in
admin.jsthat was breaking state restoration.
- UI Optimization: Consolidated redundant "Instant Search" setting in the admin dashboard.
- Roadmap: Labeled Sort and Mobile experience options as "Coming Soon" to accurately reflect current implementation status.
- Improved UX: Corrected feature descriptions and added visual states for disabled roadmap settings.
- Fix: Resolved a critical JavaScript ReferenceError in search results processing.
- Improved: Stabilized organic match counting for analytics.
- Fix: Improved search analytics accuracy by excluding pinned items from organic match counts.
- Improvement: Added CSS hooks for identifying pinned items in search results.
- Fix: Search tracking for zero-result queries (previously skipped, now correctly populates analytics dashboard).
- UI: Removed redundant synonym path debug buttons to clean up settings dashboard.
- Fix: Modernized Typesense v0.30+ Global Synonym linking via collection schema patching.
- Improvement: Dynamic admin UI for collection management (cached for performance).
- UI: Fixed layout breakage in Relevance settings tab.
- New: Full support for Typesense v0.30.1+ Global Synonym Sets.
- Fix: Resolved 404 errors during synonym synchronization on modern Cloud clusters.
- Improvement: Enhanced error reporting in Admin UI.
- Improvement: Multi-way synonym support for better search expansion.
- Fix: Resolved synonym saving and Typesense synchronization logic mismatch.
- Fix: Prevented 'undefined' string rendering in the admin synonyms list.
- Fix: 'Advanced Data' custom fields now correctly persist deletions in the database.
- New: Dynamic Search Results heading based on active post types (e.g. 'Products' vs 'Products & Posts').
- New: Strict Post-Type filtering in search queries to prevent old content from appearing.
- UX: Added 'Re-index Required' warning when searchable content types are changed.
- Fix: Critical configuration bottleneck in ConfigLoader.php resolved.
- Improvement: Enhanced Typesense Response logging for diagnostic transparency.
- Version: Synced core logic with Universal Facet Registration Bridge.
- Fix: Resolved an issue where some enabled facets were hidden in the frontend sidebar due to redundant validation logic.
- New: Universal Facet Registration Bridge.
- New: Advanced Facet Settings (Target Mapping & Data Types).
- Fix: Zero-results for numeric/boolean facets by implementing type-safe filtering.
- Improvement: Unified schema and indexing logic for all WordPress plugins.
- Fix: Facet configuration freezing on load due to data type mismatch.
- Fix: Security warning persistence after saving settings.
- Fix: Improved error handling for PHP-to-JS data serialization.
- Fix: Saved Custom Fields button visibility.
- Improvement: Connection workflow.
- Initial release.