Linux 软件免费装
Banner图

ElasticPress

开发者 tlovett1
vhauri
tott
oscarssanchez
cmmarslender
10up
更新时间 2021年3月19日 00:59
PHP版本: 3.7.1 及以上
WordPress版本: 5.7
版权: GPLv2 or later
版权网址: 版权信息

标签

performance woocommerce search related posts slow autosuggest suggest advanced search aggregation searching elasticsearch elastic fuzzy facet

下载

1.0 1.7 2.3 2.6.1 2.7 2.8 2.8.1 2.8.2 3.0 3.0.1 3.0.2 3.0.3 3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.2.6 3.3 3.4 3.4.1 3.4.2 3.4.3 3.5 3.5.1 3.5.2 3.5.3 3.5.4 3.5.5 3.5.6 trunk 1.1 1.2 1.3 1.3.1 1.4 1.5 1.5.1 1.6 1.6.1 1.6.2 1.8 1.9 1.9.1 2.0 2.0.1 2.1 2.1.1 2.1.2 2.2 2.2.1 2.3.1 2.3.2 2.4 2.4.1 2.4.2 2.5 2.5.1 2.5.2 2.6

详情介绍:

ElasticPress, a fast and flexible search and query engine for WordPress, enables WordPress to find or “query” relevant content extremely fast through a variety of highly customizable features. WordPress out-of-the-box struggles to analyze content relevancy and can be very slow. ElasticPress supercharges your WordPress website making for happier users and administrators. The plugin even contains features for popular plugins. Here is a list of the amazing ElasticPress features included in the plugin: Search: Instantly find the content you’re looking for. The first time. WooCommerce: “I want a cotton, woman’s t-shirt, for under $15 that’s in stock.” Faceted product browsing strains servers and increases load times. Your buyers can find the perfect product quickly, and buy it quickly. Related Posts: ElasticPress understands data in real time, so it can instantly deliver engaging and precise related content with no impact on site performance. Protected Content: Optionally index all of your content, including private and unpublished content, to speed up searches and queries in places like the administrative dashboard. Documents: Indexes text inside of popular file types, and adds those files types to search results. Autosuggest: Suggest relevant content as text is entered into the search field. Facets: Add controls to your website to filter content by one or more taxonomies. Users: Improve user search relevancy and query performance. Please refer to Github for detailed usage instructions and documentation.

安装:

  1. First, you will need to properly install and configure Elasticsearch.
  2. Activate the plugin in WordPress.
  3. In the ElasticPress settings page, input your Elasticsearch host.
  4. Sync your content by clicking the sync icon.
  5. Enjoy!

更新日志:

3.5.6 This release fixes some bugs and also adds some new actions and filters. Security Fix: 3.5.5 This release fixes some bugs and also adds some new actions and filters. Bug Fixes: 3.5.4 This is primarily a security and bug fix release. PLEASE NOTE that versions 3.5.2 and 3.5.3 contain a vulnerability that allows a userto bypass the nonce check associated with re-sending the unaltered default search query to ElasticPress.io that is used for providing Autosuggest queries. If you are running version 3.5.2. or 3.5.3 please upgrade to 3.5.4 immediately. Security Fix: 3.5.3 This is a bug fix release. Bug Fixes: 3.5.2 This is a bug fix release. Bug Fixes: 3.5.1 A bug fix release. Bug fixes: 3.5 Version 3.5 is a very exciting release as it contains two major new features: a synonym dashboard and search term result highlighting. The synonym dashboard empowerers users to create synonym lists for searches. For example. searching "New York City" would return contain with "NYC". Search term highlighting will underline and add a CSS class to keywords within content that matches the current search. The new version also includes a revamp of the search algorithm. This is a backwards compatibility break. If you'd like to revert to the old search algorithm, you can use the following code: add_filter( 'ep_search_algorithm_version', function() { return '3.4'; } );. The new algorithm offers much more relevant search results and removes fuzziness which results in mostly unwanted results for most people. If you are hooking in and modifying the search query directly, it's possible this code might break and you might need to tweak it. Bug fixes: 3.4.3 Enhancements: 3.4.2 Bug fixes: 3.4.1 3.4 3.3 3.2.6 This is a bugfix release 3.2.5 This is a bug fix version. 3.2.4 This is a bug fix version. 3.2.3 This is a bug fix version. 3.2.2 This is a bug fix version with some feature additions. 3.2.1 This is a bug fix version. 3.2 ElasticPress 3.2 is a feature release. We've added quite a few useful features including an index health page, the ability to control which sites are indexed in a network activated multisite setup, a related posts Gutenberg block, and more. See https://github.com/10up/ElasticPress/pulls?utf8=%E2%9C%93&q=is%3Apr+milestone%3A3.2.0+is%3Aclosed+ 3.1.4 https://github.com/10up/ElasticPress/pulls?q=is%3Apr+milestone%3A3.1.4+is%3Aclosed 3.1.3 This is a bug fix release. 3.1.2 This is a bug fix release with some filter additions. 3.1.1 3.1.0 3.0.3 3.0.2 3.0.2 is a minor bug release version. Here is a list of fixes: 3.0.1 3.0.1 is a minor bug release version. Here is a list of fixes: 3.0 (Requires re-index) 3.0 is a refactor of ElasticPress for modern coding standards (PHP 5.4 required) as well as the introduction to indexables. Indexables abstracts out content types so data types other than post can be indexed and searched. 3.0 includes user indexing and search (integration with WP_User_Query). User features require at least WordPress version 5.1. The refactor changes a lot of ElasticPress internals. The biggest change is the feature registration API has completely changed. Now, new features should extend the ElasticPress\Feature class rather than calling ep_register_feature. Older features should be backwards compatible. Other Features: Actions Removed: Filters changed: Other changes: 2.8.2 2.8.1 2.8.0 ElasticPress 2.8 provides some new enhancements and bug fixes. 2.7.0 (Requires re-index) ElasticPress 2.7 provides some new enhancements and bug fixes. 2.6.1 2.6.0 ElasticPress 2.6 provides some new enhancements and bug fixes. 2.5.2 (Requires re-index) This is a small bug fix release. 2.5.1 (Requires re-index) This if a bug fix release. This version requires a re-index as we change the way data is being sent to Elasticsearch. It's also worth noting for ElasticPress version 2.5+, the Facets feature, which is on by default, will run post type archive and search page main queries through Elasticsearch. If Elasticsearch is out of sync with your content (possible in rare edge cases), this could result in incorrect content being shown. Turning off Facets would fix the problem. Bug Fixes 2.5 ElasticPress 2.5 includes a new Facets feature that makes it easy to add high performance content filtering controls to a website. A new Facets widget enables site administrators to add taxonomy facets to a sidebar (or any widgetized area). When viewing a content list on the front end of the website, the widget will display the name of the taxonomy – e.g. “Categories” – and a checklist with all of its terms. Visitors can narrow down content by selecting terms they are interested in. The Facets feature can be globally configured to narrow results to content that is tagged with any or all of the selected terms. The widget’s front end output contains carefully named CSS classes, so that designers and developers can apply unique styling. Version 2.5 also includes a number of smaller enhancements and fixes, including official support for Elasticsearch 6.2, and increased functional parity with the WP_Query API. Here is a detailed list of what's been included in the release: Enhancements Bugs 2.4.2 Version 2.4.2 is a bug fix version. 2.4.1 Version 2.4.1 is a bug fix and maintenance release. Here are a listed of issues that have been resolved: 2.4 Version 2.4 introduces the Autosuggest feature. When enabled, input fields of type "search" or with the CSS class "search-field" or "ep-autosuggest" will be enhanced with autosuggest functionality. As text is entered into the search field, suggested content will appear below it, based on top search results for the text. Suggestions link directly to the content. We also added hooks and filters to ElasticPress that make query logging possible. The Debug Bar ElasticPress plugin now adds a Query Log screen to the ElasticPress admin menu. The Query Log is an extremely powerful tool for diagnosing search and indexing issues. Here is a comphrensive list of changes: Enhancements Bug Fixes 2.3.1, 2.3.2 Version 2.3.1-2.3.2 is a bug fix release. Here are a listed of issues that have been resolved: 2.3 Version 2.3 introduces the Documents feature which indexes text inside of popular file types, and adds those files types to search results. We've also officially added support for Elasticsearch 5.3. Enhancements Bug Fixes 2.2.1 Version 2.2.1 is a bug fix release. Here are a listed of issues that have been resolved: 2.2 (Requires re-index) Version 2.2 rethinks the module process to make ElasticPress a more complete query engine solution. Modules are now auto-on and really just features. Why would anyone want to not use amazing functionality that improves speed and relevancy on their website? Features (previously modules) can of course be overridden and disabled. Features that don't have their minimum requirements met, such as a missing plugin dependency, are auto-disabled. We've bumped the minimum Elasticsearch version to 1.7 (although we strongly recommend 2+). The maximum tested version of Elasticsearch is version 5.2. If you are running Elasticsearch outside this version range, you will see a warning in the dashboard. Enhancements Bug Fixes 2.1.2 (Requires re-index) 2.1.1 2.1 Backward compat breaks: Bug fixes 2.0.1 Bug fixes 2.0 10up ships ElasticPress 2.0 with radical search algorithm improvements and a more comprehensive integration of WP_Query. ElasticPress is now even closer to supporting the complete WP_Query API. This version also improves upon post syncing ensuring that post meta updates are synced to Elasticsearch, adds a number of important hooks, and, of course, fixes some pesky bugs. Enhancements Bugs 1.9.1 Quick bug fix version to address the GUI not working properly when plugin is not network enabled within multisite. Props to Ivan Lopez 1.9 ElasticPress 1.9 adds in an admin UI, where you can set your Elasticsearch Host and run your index command, without needing to us WP-CLI. Version 1.9 also adds in some performance improvements to reduce memory consumption during indexing. Full list of enhancements and bug fixes: Enhancements: Bugs: 1.8 (Mapping change, requires reindex) ElasticPress 1.8 adds a bunch of mapping changes for accomplishing more complex WP_Query functions such as filtering by term id and sorting by any Elasticsearch property. Version 1.8 also speeds up post syncing dramatically through non-blocking queries. Full list of enhancements and bug fixes: Enhancements: Bugs: 1.7 (Mapping change, requires reindex) ElasticPress 1.7 restructures meta mapping for posts for much more flexible meta queries. The post_meta Elasticsearch post property has been left for backwards compatibility. As of this version, post meta will be stored in the meta Elasticsearch property. meta is structured as follows: When querying posts, you will get back meta.value. However, if you plan to mess with the new post mapping, it's important to understand the intricacies. The real implications of this is in meta_query. You can now effectively search by meta types. See the new section in README.md for details on this. 1.7 also contains the following bugs/enhancements: 1.6.2 (Mapping change, requires reindex) ElasticPress 1.6.2 fixes ALL backwards compatibility issues with Elasticsearch 2.0: 1.6.1 (Mapping change, requires reindex) ElasticPress 1.6.1 fixes mapping backwards compatibility issues with Elasticsearch 2.0: 1.6 ElasticPress 1.6 contains a number of important enhancements and bug fixes. Most notably, we now support Elasticsearch fallback hosts and the indexing of attachments. Bug Fixes: Enhancements: 1.5.1 Bug Fixes: 1.5 Bug Fixes: Enhancements: 1.4 Bug Fixes: Enhancements: 1.3.1 1.3 1.2 1.1 1.0 0.1.2 0.1.0