xF2 Add-on Search Improvements 2.17.0

• Require StandardLib v1.19.0+
• Code cleanup
• Add getSearchIdFromEntityId() helper method for transforming an XF entity id into the Elasticsearch index id

• Workaround XF2.2.13 does the search beforechecking it it can save it as a cached value, which can result in a query that is massively more complex than expected being sent to elasticsearch
  • This issue practically doesn't occur with stock XFES, but with additional search addons such as ElasticSearch Essentials this can generate unexpected errors

• Support tag/username autocomplete using XFES add-ons todo prefix matching on autocomplete

Click to expand...

• Fix viewing the index list could be blocked when elasticsearch is configured but inaccessible

Click to expand...

• Improve phrasing of custom search term on the advanced search page.
  • Change the phrase 'search only x' to 'search x only' to match XenForo.
  • Supports arbitrary phrases for 'search x only' by adding the phrase svSearchImprov_search_container.x where x is the content type. Ships with the current customizations:
    • svSearchImprov_search_container.thread: "Search titles and first posts only"
    • svSearchImprov_search_container.conversation: "Search titles and first messages only"

• During upgrades, fix " Access to undeclared static property " error.
• Do not show the "Tags will be searched" tooltip as part of "Search titles only" in advanced search for content types which do not implement tagging

• Cleanup add-on description & readme file
• Update XFES dependent option descriptions to include if they require XFES
• Improve styling of 'no results' search result in an overlay
• Fix search result terms do not display when search results are in an overlay
• Fix custom styling triggering "Your changes have been saved." when clicking a member search link

• Fix additional XFES index page would show even when XFES was not installed/active

Click to expand...

• Fix searching by member without a keyword for a guest

Click to expand...

• Fix "before" search result term would print an integer instead of a human readable yyyy-mm-dd formatted string
• Change 'no results found' handling to display search terms on the relevent page
  • If using ElasticSearch Essentials, recommend updating to v3.13.0+ as this change may impact some options which display on no results found.
• Fixes for search term on results page
  • Add missing "With X thread" search term
  • Fix "Users" search term could fail to render the list of usernames
  • Add the 'content type' search term