3.0: Multiple search issues
See original GitHub issueDescribe the bug
- The task
node app @apostrophecms/search:index
fails withTypeError: self.indexDoc is not a function
- Pieces types are not registered programmatically as stated in the source documentation even with explicit
searchable: true
settings. - I’m unable to include a desired field in the search index even via explicit
searchable: true
field option (tested withstring
textarea field type). - The implementation of
addSearchTexts
disallows any weight configuration, and there are valid cases when a specific area text field might be of typehighSearchText
. I haven’t tested if the rich-text widgets are searchable yet, and the above is obviously not a bug. - The
silent
option for fields is not documented anywhere and it’s unclear how it would affect the search. It’s definitely not a part of the search result UI, my guess is it has something to do with API result set? (again not a search related bug report)
Expected behavior
- It looks to be a typo.
indexDoc
is defined in thehandlers
configuration and not inmethods
. - I’m unable to find a registered handler for the
determineTypes
event in the pieces source but only dedicated methodself.searchDetermineTypes(types)
which in turn is not invoked anywhere (but I might miss something here). The only way to enable a piece for a search is via the explicittypes
option of the search module. - There is a trace to this feature in the
schema
module (indexFields
method) andstring
field type has a dedicatedindex
method.
Details
Apostrophe v3.0.1
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Is there a better way to search for multiple issues at once?
We are having some user adoption issues due to the inability to quickly search for multiple item keys at once. It is possible...
Read more >[Bug Report][3.0.0-beta.3] VCombobox search not working if ...
Environment Vuetify Version: 3.0.0-beta.3 Vue Version: 3.2.36 Browsers: ... The search of v-combobox without multiple prop is not working ...
Read more >All versions after (3.0.9) does NOT honor the (Multiple Words ...
Do a multiple keywords search, the returned search results will show/highlight only individual keywords and ignore the full sentence.
Read more >Connexion client known issues - OCLC Support
Workaround: Using the View > Pinned menu option within Connexion Client when looking at multiple records at a time or using a virtual...
Read more >Exercise 3 - How to Export multiple issues
Current Filter Name used to search Issues. FilterJQL. Current JQL statement used on the issues Filter. The fields with the notation to be...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t know the cause of searchable and silent not working for string fields, areas, etc. as expected, but they should work and I do consider it a bug if they don’t. Hoping that was the question.
Interesting enough, my second thought was to extend (improve)
getSearchTexts
in order to add my precious tag titles to the article search index 😃 It seems if this is a desired behavior of the search index event, the solution is simple. I’ll just wait for a repair 😃