Die TYPO3 Mailingliste - nicht fragen: lesen!
This is a discussion on [TYPO3] Indexed Search, limiting to specific categories within the typo3-english@lists.netfielders.de forums, part of the TYPO3-Mailinglists: ENGLISH category; I would like to limit some search results to specific categories. I have several indexing configurations set up. They're ...
|
|||||||
| Registrieren | Hilfe | Benutzerliste | Kalender | Suchen | Heutige Beiträge | Alle Foren als gelesen markieren |
|
#1
|
|||
|
|||
|
I would like to limit some search results to specific categories. I
have several indexing configurations set up. They're working properly. Pages are being indexed regularly by the crawler. Doing a regular search displays results that were indexed by all index configurations. What I want to do is add another indexing configuration, and have the ability to include or exclude its records from search results. The indexed search document (doc_indexed_search) gives these examples to enable grouping: plugin.tx_indexedsearch.search.defaultFreeIndexUid List = 0,6,7,8 plugin.tx_indexedsearch.blind.freeIndexUid = 0 (I think that the "0" means "everything") And for limiting to specific categories, the document suggests this: index.php?id=78&tx_indexedsearch[sword]=level&tx_indexedsearch[_freeIndexUid]=7,8 the important part being: &tx_indexedsearch[_freeIndexUid]=7,8 My Indexing Config IDs are 1,2,3,4,5,6,7,8. I have added this typoscript to test search page: plugin.tx_indexedsearch.search.defaultFreeIndexUid List = 8,7,6,5,4,3,2,1,0 plugin.tx_indexedsearch.blind.freeIndexUid = 0 I view that search page from the frontend by this URL: index.php?id=1234&tx_indexedsearch[sword]=contact&tx_indexedsearch[_freeIndexUid]=8,7,6,5,4,3,2,1 The search results displayed are only eight headers (one for each indexing config requested by the URL) with "No results found." under each header. I get the same result when I try fewer numbers too. &tx_indexedsearch[_freeIndexUid]=4,3,2,1 &tx_indexedsearch[_freeIndexUid]=8,7,6,5 But of course, what I'm expecting are results that are limited the indexing configurations specified in the URL. When I remove the numbers from the end, or the _freeIndexUid variable completely, I get a lot of results from all over the site. index.php?id=1234&tx_indexedsearch[sword]=contact&tx_indexedsearch[_freeIndexUid]= index.php?id=1234&tx_indexedsearch[sword]=contact Does anybody have any suggestions as to what I might be missing? Thanks in advance, David Lanier _______________________________________________ TYPO3-english mailing list TYPO3-english (AT) lists (DOT) netfielders.de http://lists.netfielders.de/cgi-bin/.../typo3-english |
|
#2
|
|||
|
|||
|
I have discovered a piece of the issue.
No data is being entered in the database field index_phash.freeIndexUid. There are plenty of records in that table. Everything that is in that table was entered as a result of an indexing configuration, used by the crawler extension. The value of freeIndexUid for every record is 0. I manually changed one record to a 1 (using phpMyAdmin) and that record now appears in the expected category of the search results. So, on to my next specific question: How can I get this field to be set properly automatically? The only three relevant things I see in tsref are: index_enable index_externals (whether to index linked media - pdfs, etc.) index_descrLgd (length of description text to store) But that doesn't affect this issue. any suggestions would be appreciated! David Lanier David Lanier wrote: > I would like to limit some search results to specific categories. > > ... > > I view that search page from the frontend by this URL: > index.php?id=1234&tx_indexedsearch[sword]=contact&tx_indexedsearch[_freeIndexUid]=8,7,6,5,4,3,2,1 > > The search results displayed are only eight headers (one for each > indexing config requested by the URL) with "No results found." under > each header. > _______________________________________________ TYPO3-english mailing list TYPO3-english (AT) lists (DOT) netfielders.de http://lists.netfielders.de/cgi-bin/.../typo3-english |
|
#3
|
|||
|
|||
|
It turns out this is a known bug.
http://bugs.typo3.org/print_bug_page.php?bug_id=5115 David Lanier wrote: > I have discovered a piece of the issue. > > No data is being entered in the database field index_phash.freeIndexUid. > _______________________________________________ TYPO3-english mailing list TYPO3-english (AT) lists (DOT) netfielders.de http://lists.netfielders.de/cgi-bin/.../typo3-english |
| Themen-Optionen | Thema durchsuchen |
| Ansicht | Thema bewerten |
|
|
|
||||
| Thema | Autor | Forum | Antworten | Letzter Beitrag |
| [TYPO3-shop] rturning search result in a specific content element | Corrado | typo3-project-tt-products@lists.netfielders.de | 2 | 26.05.2007 19:21 |
| [TYPO3] Indexed Search - pages that should not to be indexed | Lasse Guldsborg | typo3-english@lists.netfielders.de | 2 | 09.04.2007 15:47 |
| [TYPO3] Indexed Search | PEF | typo3-english@lists.netfielders.de | 0 | 26.02.2007 12:20 |
| [TYPO3] problem: indexed search results: search result title wronglanguage / default language | Bernhard Welzel | typo3-english@lists.netfielders.de | 0 | 01.02.2007 09:10 |
| [TYPO3] can you make dam referenced image categories correspond toa specific page? | dave typo | typo3-english@lists.netfielders.de | 0 | 04.01.2007 10:55 |