You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately the 'no' gets rendered as 0 in the admin ui (check "data-value"):
<divclass="selectize-input items full has-options has-items"><divclass="item" data-value="0">Disabled</div><inputtype="select-one" autocomplete="off" tabindex="" style="width: 4px;"></div>
If you click on save in admin ui, the value 0 will be stored in user/config/plugins/tntsearch.yaml which ultimately lead to the following exeception when you start the indexer:
Fatal error: Uncaught Error: Class "TeamTNT\TNTSearch\Stemmer\0Stemmer" not found in /var/www/html/user/plugins/tntsearch/vendor/teamtnt/tntsearch/src/Indexer/TNTIndexer.php:139
Stack trace:
#0 /var/www/html/user/plugins/tntsearch/classes/GravTNTSearch.php(237): TeamTNT\TNTSearch\Indexer\TNTIndexer->setLanguage('0')
// ...
To get an actual no into the config file via the admin ui, I propose to change the blueprint.yaml from
default: nooptions:
no: Disabled
to
default: 'no'options:
'no': Disabled
The text was updated successfully, but these errors were encountered:
Confirm that, using Grav v1.7.43, Admin v1.10.43, TNT Search v3.4.0.
After having tried the German stemmer, I wanted to switch it off again and got a '0' in user/config/plugins/tntsearch.yaml as value for stemmer. And the error shown above.
My quick-n-dirty solution was to look up the original in user/plugins/tntsearch/tntsearch.yaml and use stemmer: default. This showed "Disabled" in the Admin panel and worked for reindexing.
I also tried your solution (quote the no’s), which works fine here.
I may have found a bug. The value for the stemmer setting "Default" should be
no
. (At least as far as I can see from code.)For the dropdown in the admin panel the value for stemmer->default is defined here:
grav-plugin-tntsearch/blueprints.yaml
Line 184 in 9299fec
grav-plugin-tntsearch/blueprints.yaml
Line 186 in 9299fec
Unfortunately the 'no' gets rendered as
0
in the admin ui (check "data-value"):If you click on save in admin ui, the value
0
will be stored inuser/config/plugins/tntsearch.yaml
which ultimately lead to the following exeception when you start the indexer:To get an actual
no
into the config file via the admin ui, I propose to change the blueprint.yaml fromto
The text was updated successfully, but these errors were encountered: