Scout Search

clarkwinkelmann

zjmw00 can you try clearing the Flarum cache and disabling/re-enabling the extension?

There should be a set of inputs where it says "no settings".

zjmw00

clarkwinkelmann

That did it! Thanks!

It's importing now and I see the requests coming through.

zjmw00

clarkwinkelmann

It's working great now. My last question would be, is there a way to modify the maxTotalHits?

https://docs.meilisearch.com/reference/api/settings.html#pagination

It seems like either Meilisearch or Flarum is limiting the results to 2 pages.

clarkwinkelmann

zjmw00 I don't think it's possible at the moment. I implemented the max value for the similar setting in TNTSearch, I could try adding it for Meilisearch if it works in a similar way.

I haven't checked where settings are passed for Meilisearch yet. Maybe you can also customize that via the global Meilisearch configuration and thus not require any change on the Flarum side?

zjmw00

clarkwinkelmann

It looks like all of the configuration is passed in as arguments when starting Meilisearch - I don't see any args for adjusting that, but then again, it says the default return value should be 1000 results. I'm only getting 2 pages of 20 results, so maybe Flarum is the limiting factor here, but I haven't been able to find anything in regards to that yet.

fakruzaruret

Meilisearch seems have much more suporter and users. It is maintained and updated actively. I feel it is more reliable and scalable.

CyberGene

Meilisearch is great. It really "fixed" the default Flarum search. Unfortunately all these solutions require some additional computations and are not supported on a shared hosting, so I used it on a DigitalOcean droplet but that added expenses to my little forum where people admitted they almost didn't use search at all, so I disabled it. But I can wholeheartedly recommend this extension with Meilisearch 👍🏻

clarkwinkelmann

Version 0.3.0

Added extender to allow other extensions to add data to existing indexes.
Extensions can also make any Eloquent model compatible with Scout just by using the extender (and writing the appropriate full text gambit to fetch results from Scout).
Allowed customization of the number of search results requested from the search engine, if not specified, it will be 200 for Meilisearch and null for other engines to fall back to their own defaults.
Allowed usage of asynchronous queues to sync indexes, use new setting in admin to enable.
Fixed post index not being removed on discussion delete (would not cause problems, but creates a lot of stale records after a while).
All CLI commands can now be called with the native Eloquent model path instead of alternative model names, just like in Laravel.

You probably don't need to rebuild your indexes, their format has not changed. Check the README for the list of commands if needed.

This is a major update. You need to run composer require clarkwinkelmann/flarum-ext-scout to upgrade (update will not work unless you set the requirement to * which I do not recommend for this experimental extension)

Developers can read the documentation in the README file to integrate their own extensions with the index. Currently only my closed-source Formulaire extension uses the extender. Over the next few weeks, most of the Flamarkt extensions will get Scout support and can serve as implementation examples.

clarkwinkelmann

Version 0.3.1

Fix errors if an extension with Scout integration is installed but Scout is disabled. The event listeners would still be set and cause 500 errors when creating or updating compatible resources.

clarkwinkelmann

Version 0.3.2

Add new setting to override Search.MIN_SEARCH_LEN, the minimum query length Flarum requires before retrieving suggestions as you type. This does not affect the complete results page which will always work with any query length.

You must clear the cache after changing the setting. No additional javascript is inserted in the forum bundle if the feature is not used.

come2mejk

Hello, I have two sites A and B, deployed on the same server as Meilisearch,
A and B use the same MeilisearchAPI key but different Index name prefixes. A few days later, site A is unable to post. The reason is found to be Scout search. But site B is fine.
In the past two days, I have installed Post Stream Search, GB Password Strength, FoF Pretty Mail, and Confix Theme. I don’t know if it’s related to these

POST https://demo.gitzaai.com/api/discussions

Symfony\Component\HttpClient\Exception\InvalidArgumentException: Invalid URL: scheme is missing in "//127.0.0.1:7700/indexes/meili_flarumposts/documents?primaryKey=id". Did you forget to add "http(s)://"? in /home/wwwroot/demo.gitzaai.com/vendor/symfony/http-client/HttpClientTrait.php:449
Stack trace:
#0 /home/wwwroot/demo.gitzaai.com/vendor/symfony/http-client/HttpClientTrait.php(173): Symfony\Component\HttpClient\CurlHttpClient::resolveUrl()
#1 /home/wwwroot/demo.gitzaai.com/vendor/symfony/http-client/CurlHttpClient.php(89): Symfony\Component\HttpClient\CurlHttpClient::prepareRequest()
#2 /home/wwwroot/demo.gitzaai.com/vendor/symfony/http-client/Psr18Client.php(95): Symfony\Component\HttpClient\CurlHttpClient->request()
#3 /home/wwwroot/demo.gitzaai.com/vendor/meilisearch/meilisearch-php/src/Http/Client.php(162): Symfony\Component\HttpClient\Psr18Client->sendRequest()
#4 /home/wwwroot/demo.gitzaai.com/vendor/meilisearch/meilisearch-php/src/Http/Client.php(99):

luceos

come2mejk check the Host value for Meilli in your admin area for the site throwing the error. It seems not the full URL was copied over; //127.0.0.1 should be http://127.0.0.1.

clarkwinkelmann

Version 0.3.3

Send all quotes verbatim to the Scout driver to fix exact matching syntax (tested with Meilisearch)

You might no longer be able to use quotes in search fields that don't integrate with Scout, since those will also be sent verbatim to MySQL with this change.

« Previous Page