ElasticSearch Essentials [Paid] 3.15.12

[sbj]

I've never seen an autocomplete use a close X on the top right and I think it shouldn't be there.

YouTube




Google





On mobile it is especially annoying NOT to have a close button for entries. Because deleting letters/words on phones are especially tedious so that button is very user-friendly. Anyone who says otherwise...

On desktop it is also very nice thing to have cause it is faster than marking/deleting.

 

[NealC]

That is a clear input box, this add-on places a close X at the top right of the drop down content.

 

[sbj]

Ah, I see what you mean.

In that case if you have set the results to a high number, like 50 or 100 (like I do), then the list is especially long. Having a close button is useful cause it overlays on top of other things and/or makes the page longer. Again, it is a user-friendly thing to have it. Especially I use the search as a widget on top of the page (instead hidden on right side).

 

[Xon]

The text styling matches the search dialog, which depending on configuration may not match the text entry field.

Getting that consistent across styles is next to impossible for me.

There are a number of search options which can improve search. I'ld recommend enabling the "exact text" matching option.

But complex manually tuning is something I've charged clients for as getting "good search" is highly site specific.

 

[NealC]

I noticed another potential issue today. When searching in the desktop forum search box (upper right) it defaults to searching "Everywhere". If I change to "Resources" the list should re-populate to only show matches in my desired search area otherwise we are confusing the user and not honoring their narrowed search selection.

 

[Xon]

It will do that if they type something else into the quick-search bar when autocomplete is enabled.

 

[Xon]

Xon updated ElasticSearch Essentials with a new update entry:

3.12.2 - Feature update

• Initial php 8.2 compatibility update
• If installed, require Search Improvements v2.6.0+
• Support Search Improvements v2.7.0+ search term display
• Add 'include deleted' status to URL constraints
• Do not autoconfigure the ESE similar thread widget for new installs with a position as XFES ships with one.
• Avoid triggering similar thread lookups for titles with single character titles

Read the rest of this update entry...

 

[benFF]

Getting loads of errors since upgrading to this version:

InvalidArgumentException: Unknown filter type unit src\XF\InputFilterer.php:428

#0 src\addons\SV\StandardLib\XF\InputFilterer.php(114): XF\InputFilterer->cleanInternal('', 'unit', Array)
#1 src\XF\InputFilterer.php(160): SV\StandardLib\XF\InputFilterer->cleanInternal('', 'unit', Array)
#2 src\XF\InputFilterer.php(422): XF\InputFilterer->filter('', 'unit', Array)
#3 src\addons\SV\StandardLib\XF\InputFilterer.php(114): XF\InputFilterer->cleanInternal(Array, 'array-unit', Array)
#4 src\XF\InputFilterer.php(160): SV\StandardLib\XF\InputFilterer->cleanInternal(Array, 'array-unit', Array)
#5 src\XF\Http\Request.php(778): XF\InputFilterer->filter(Array, 'array-unit')
#6 src\addons\SV\ElasticSearchEssentials\XFRM\Search\Data\ResourceItem.php(87): XF\Http\Request->filter('c.categories', 'array-unit')
#7 src\addons\SV\ElasticSearchEssentials\Service\AutoCompleter.php(528): SV\ElasticSearchEssentials\XFRM\Search\Data\ResourceItem->filterRequestForAutocomplete(Object(SV\ElasticSearchEssentials\XF\Search\Query\KeywordQuery), true, Object(XF\Http\Request))
#8 src\addons\SV\ElasticSearchEssentials\Service\AutoCompleter.php(442): SV\ElasticSearchEssentials\Service\AutoCompleter->applyConstraints(Array)
#9 src\addons\SV\ElasticSearchEssentials\XF\Pub\Controller\Search.php(461): SV\ElasticSearchEssentials\Service\AutoCompleter->prepare()
#10 src\XF\Mvc\Dispatcher.php(352): SV\ElasticSearchEssentials\XF\Pub\Controller\Search->actionSearch(Object(XF\Mvc\ParameterBag))
#11 src\XF\Mvc\Dispatcher.php(259): XF\Mvc\Dispatcher->dispatchClass('XF:Search', 'Search', Object(XF\Mvc\RouteMatch), Object(SV\ElasticSearchEssentials\XF\Pub\Controller\Search), NULL)
#12 src\XF\Mvc\Dispatcher.php(115): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(SV\ElasticSearchEssentials\XF\Pub\Controller\Search), NULL)
#13 src\XF\Mvc\Dispatcher.php(57): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#14 src\XF\App.php(2352): XF\Mvc\Dispatcher->run()
#15 src\XF.php(524): XF\App->run()
#16 index.php(20): XF::runApp('XF\\Pub\\App')
#17 {main}

Running latest standard lib 1.14 and search improvements 2.7.4

 

[Xon]

Xon updated ElasticSearch Essentials with a new update entry:

3.12.3 - Bugfix update

• Fix uninstaller (Missing function argument)
• Fix XFRM support ("Unknown filter type unit" error)

Read the rest of this update entry...

 

[bzcomputers]

Xon updated ElasticSearch Essentials with a new update entry:

2.12.3 - Bugfix update



Read the rest of this update entry...

Just a heads up... the add-on version is wrong on your post above and on your own site. Add-on download appears to reference the correct versioning (3.12.3).

 

[Xon]

Copy & paste error, should be fixed now.

The minimum required version of StandardLib is only v1.5.0, and doesn't require much more so it hasn't been bumped.

 

[NealC]

Something is not working properly on my site https://rvforums.com as I'm trying to do a search on "prusa" or "enclosure" and the content I'm looking for regarding prusa enclosure is not showing in the autocomplete list. I tried changing a setting or two, deleted and rebuilt the search index, no change. Can you tell me why entering "prusa" (without quotes shows no results in the search box top right?

Version 3.12.3

 

[Xon]

Please show the Enhanced Search setup page. The index mapping section (and if optimization needs to be done) and also the index configuration section at the bottom of the Enhanced Search setup page

 

[NealC]

Attached as requested.

 

[Xon]

Attached as requested.

I'ld recommend enabling stemming if you want the 'exact text' match options to-do anything. Having both enabled definitely helps search.

Something is not working properly on my site https://rvforums.com as I'm trying to do a search on "prusa" or "enclosure" and the content I'm looking for regarding prusa enclosure is not showing in the autocomplete list. I tried changing a setting or two, deleted and rebuilt the search index, no change. Can you tell me why entering "prusa" (without quotes shows no results in the search box top right?

Autocomplete only searches the titles (and tags). Searching for "prusa" with title-only doesn't find anything.

 

[NealC]

I'm not at my computer right now but I thought I had stemming enabled. The autocomplete only on title explains it though. Would be nice if it included body as well.

 

[NealC]

In further thought I think it's a negative that the autocomplete is only for titles. Someone will believe that there is no reason to further search as there are no results listed from their input. This is a negative behavior in my opinion.

 

[NealC]

I thought I enabled stemming in the past, maybe I didn't save it, re-enabled again and rebuilt the search index.

 

[NealC]

There is an option for this add-on:

Replace Enhanced Search 2.2's suggest threads implementation
If checked, suggest threads implementation will be replaced by Elastic Search Essentials add-on implementation.

Can you explain the difference in this vs the native option without this checked?

My concern is your add-on will limit similar threads to titles like the search discussion above (autocomplete) or will it improve upon the native implementation? Does it use full ES capability or are you limiting the scope the titles and tags?

 

[Xon]

My similar thread implementation uses title/tags, which works well enough for me. XFES does compare the first post, but this doesn't really give much better results for various reasons.