A fast and flexible search and query engine for WordPress.
GPL-2.0 License
Bot releases are visible (Hide)
Published by tlovett1 almost 7 years ago
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:
WP_Query
fields
parameter. Props kallehauge.author_name
search field. Props ivankristianto.Published by tlovett1 over 7 years ago
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.
define( 'EP_DASHBOARD_SYNC', false );
. Props rveitch.product_type
taxonomy. Props kallehauge.--no-bulk
number of posts indexed message. Props ivankristianto.ep_integrate
in WooCommerce queries. Props ivankristianto.found_posts
set in query when ES is unavailable. Props lukaspawlik
Published by tlovett1 over 7 years ago
Version 2.2.1 is a bug fix release. Here are a listed of issues that have been resolved:
orderby
is correct for default WooCommerce sorting. Props ivankristianto.operator => AND
unneeded execution code.EP_INDEX_PREFIX
constant. If set, index names will be prefixed with the constant. Props allan23.Published by tlovett1 over 7 years ago
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.
register_module
in classes/class-ep-modules.php
.ep_search
function.Published by tlovett1 almost 8 years ago
Version 2.1.2 supports Elasticsearch 5.0. We've separated out index mappings for older versions of Elasticsearch to ensure legacy users can still upgrade.
Published by tlovett1 about 8 years ago
Version 2.1 marks a huge change in ElasticPress and even what's possible within WordPress. We have transformed the way the plugin works adding a modules system, completely redoing the user interface, adding a number of important WP_Query
functional enhancements, and more.
Previously, ElasticPress was a useful plugin for achieving awesome search. Now, ElasticPress is the fast and flexible search and query engine for WordPress. The plugin includes a number of powerful modules, some previously bundled as separate plugins, to supercharge WordPress performance and search. We are extremely excited to launch ElasticPress 2.1. We see it as a framework to completely transform search, performance, and scalability in WordPress.
Here is a list of new features, bug fixes, and backward compatibility breaks in 2.1:
meta_key
and meta_value
.meta_value_num
.post_parent = 0
. Props tuanmh.post_status
. Props sc0ttclark.ep_admin_wp_query_integration
to search integration only. ElasticPress integration by default is available everywhere.keep alive
setting.post__in
support.paged
overwriting offset
.sites
WP_Query processing. Props jaisgit.As always, ElasticPress is free, open source software. We are proud of the contributions every one has provided to make version 2.1 possible.
Published by tlovett1 over 8 years ago
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.
BETWEEN
queries.OR
relation for tax queries.ID
field to Elasticsearch mappingpost_parent
WP_Query arguments. Props tuanmh
category_name
when tax_query
is present.A special thanks goes out to Tuan Minh Huynh and everyone else for contributions to version 2.0.
Published by tlovett1 over 8 years ago
Quick bug fix version to address the GUI not working properly when plugin is not network enabled within multisite. Props to Ivan Lopez for the fix.
Published by dkotter over 8 years ago
ElasticPress 1.9 adds in an admin UI, where you can set your Elasticsearch Host and run your index commands, 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:
composer.lock
from the repo. Props ChrisWiegman.query_vars
, not query
to determine status. Props ChrisWiegman.post__in
and post__not_in
documentation. Props mgibbs189.--no-bulk
indexing option. Props lukaspawlik.Published by tlovett1 over 8 years ago
ElasticPress 1.8 adds a number 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. Here is a full list of enhancements and bug fixes:
posts_per_page = -1
possible.wp_cache_flush
. Props jstensved
raw
property instead of value
.One of the most exciting additions to version 1.8 is query logging as it enabled us to release a Debug Bar plugin for ElasticPress. The plugin allows you to examine all ElasticPress requests on each page load.
Version 1.8 requires a full re-index.
Published by tlovett1 almost 9 years ago
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:
meta.value
(string)meta.raw
(unanalyzed string)meta.long
(unanalyzed number)meta.double
(unanalyzed number)meta.boolean
(unanalyzed number)meta.date
(unanalyzed yyyy-MM-dd date)meta.datetime
(unanalyzed yyyy-MM-dd HH:mm:ss datetime)meta.time
(unanalyzed HH:mm:ss time)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:
Published by tlovett1 almost 9 years ago
This release fixes a few things missed in 1.6.1. 1.6.2 fixes ALL compatibility issues with Elasticsearch 2.0 and should be completely backwards compatible with 1.7.x. Specifically, this version:
fuzzy_like_this
query and uses multi_match
instead.Published by tlovett1 almost 9 years ago
This is a quick bug fix version to account for breaking changes in Elasticsearch 2.0.0. Specifically, the mapping has been adjusted like so:
Published by tlovett1 about 9 years ago
Version 1.6 contains a number of important enhancements and bug fixes. Most notably, we now support Elasticsearch fallback hosts and the indexing of attachments.
exclude_from_search
instead of public
when indexing post types. Props allan23 and ghosttoast.ep_post_sync_kill
filter in bulk indexing. Props Stayallive
ep_index_name
filter. Props kovshenin
ep_retrieve_the_post
filter to support relevancy score manipulation. Props matthewspencer
Published by tlovett1 over 9 years ago
A quick bug release version.
Published by tlovett1 over 9 years ago
This version includes 16 enhancements and 3 bug fixes across a total of 16 contributors. Only half of these contributors actually work for 10up! The focus of this version is performance. Most notably, ElasticPress queries now completely bypass MySQL yielding huge benefits. In the past ElasticPress was pulling from Elasticsearch but filling in some blanks with MySQL. ElasticPress queries also support the cache_results
parameter for storing pulled posts in the object cache.
Here is a full list of version changes:
cache_results
in WP_Query--offset
parameter to cli indexing command. Stayallive
Published by tlovett1 over 9 years ago
This version contains a number of bug fixes and small enhancements. The focus of this version is date query support. New date features will not work unless you do a reindex (wp elasticpress index --setup).
date_query
and date parameters now supported in WP_Query. Props joeyblake and eduardmaghakyan.Published by tlovett1 over 9 years ago
date
in WP_Query orderby
.Published by tlovett1 over 9 years ago
meta_query
in WP_Query integrationelasticsearch
property to global post object to assist in debuggingep_integrate
param added to allow for WP_Query integration without search. (Formally called ep_match_all)publish
). Change the sync mechanism to make sure it takes all post statuses into account. Props jonathanbardo
is_multisite()
if --network-wide
is provided. Props ivankruchkoff
exclude_from_search
flag from post type when running search queries. Props ryanboswell
post_status
to not_analyzed
to allow for filtering of the search query (will require a re-index). Props jonathanbardo
Published by tlovett1 almost 10 years ago
orderby
parameter in WP_Query
_boost
from mapping. _boost is deprecated by Elasticsearch.