• Compatibility fix when using relevancy search order with the "Enhanced Search Syntax" feature
• Remove dependency on ElasticSearch Essentials which crept in.
• Ensure add-on is fully activated when bulk-indexing
• Support HTTPS, on upgrading to XF2 will need to reconfigure.

• ElasticSearch v6 single-type index compatibility update - take #4

• Compatibility bugfix - prevent Undefined index on checking if ElasticSearch type mappings are optimized when using ElasticSearch's single type index

• Compatibility bugfix - prevent Undefined index on checking if ElasticSearch type mappings are optimized

• Fix for "Enhanced Search Syntax" searches failing, documentation claims simple_query_string will not throw exceptions but it does.

• Minor update for Elasticsearch 6 support

• Allow search query logging to work outside of debug mode

To support Elasticsearch v6 single-type, all add-ons I maintain or develop have been adjusted to rely on this add-on (or Elastic Search Essentials v2.4.x) to provide the infrastructure to apply updated type mappings.

• This add-on is not hard required, the add-ons with a soft-requirement may not extend type mapping quite as expected.

• Update for XFES 1.1.7
• Installer now enforces minimum php & XF requirements.
• Initial support for ElasticSearch +6, single type indexes

Implement the ability to use unescaped simple_query_string syntax (disabled by default)

• The simple_query_string supports the following special characters:
  • + signifies AND operation
  • | signifies OR operation
  • - negates a single token
  • " wraps a number of tokens to signify a phrase for searching
  • * at the end of a term signifies a prefix query
  • ( and ) signify precedence
  • ~N after a word signifies edit distance (fuzziness)
  • ~N after a phrase signifies slop amount
  In order to search for any of these special characters, they will need to be escaped with \.