Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Normal
XenForo generates an \XF\Entity\Search record for search once done, which has a length limit of 200 characters for the search keywords. However, searches are sent to the search backend before attempting to save the search results.This means the search can potentially send too long a query to the backend and will instead log a server error instead of reporting to the user the search was too long.This is most noticeable with the elasticsearch backend, a keyword search which is quite long but just under the limit and then a user who can't view a large number of forums when searching for body+title (ie not title-only), and also then uses a number of facet search terms.Related XFES error:[EMBED content="thread-218682"]https://xenforo.com/community/threads/xfess-getmaxkeywords-is-not-effective-depending-on-the-number-of-fields-being-searched.218682/[/EMBED]
XenForo generates an \XF\Entity\Search record for search once done, which has a length limit of 200 characters for the search keywords. However, searches are sent to the search backend before attempting to save the search results.
This means the search can potentially send too long a query to the backend and will instead log a server error instead of reporting to the user the search was too long.
This is most noticeable with the elasticsearch backend, a keyword search which is quite long but just under the limit and then a user who can't view a large number of forums when searching for body+title (ie not title-only), and also then uses a number of facet search terms.
Related XFES error:
[EMBED content="thread-218682"]https://xenforo.com/community/threads/xfess-getmaxkeywords-is-not-effective-depending-on-the-number-of-fields-being-searched.218682/[/EMBED]
We use essential cookies to make this site work, and optional cookies to enhance your experience.
See further information and configure your preferences