Bug #76142
closedIndexed Search - $this->conf['index_descrLgd'] seems to be null/not set
0%
Description
I wanted to XCLASS the following class to make the item description a little bit longer:
\TYPO3\CMS\IndexedSearch\Indexer::class
I adpated the functions backend_initIndexer and bodyDescription to fit my needs.
I set:
$this->conf['index_descrLgd'] = 500;
and:
$maxL = MathUtility::forceIntegerInRange($this->conf['index_descrLgd'], 0, 500, 200);
But nothing happened - still only 200 characters in database. I also changed the according template settings to store more than 200 characters and to show more than 200 characters in the FE output of the search results.
At last I changed these values also in the source code of indexed_search system extension to exclude possible mistakes I could have made in XCLASS - but also only 200 characters where stored in the database. But if I change the default value for
MathUtility::forceIntegerInRangeto 500 I see 500 characters in the database. So I suppose
$this->['index_descrLgd']is null or not set.
Expected: Correct value of index_descrLgd available in function bodyDescription.
Updated by Tymoteusz Motylewski about 8 years ago
- Status changed from New to Needs Feedback
Thanks for the report. Unfortunatelly I can not reproduce it on v8.
I have added the setting index_descrLgd to typoscript (config.index_descrLgd), and it was reflected in the record stored in the db (column item_description has correct number of letters).
Please provide more detailed steps to reproduce the issue.
How do you index the page? on rendering or using crawler?
Updated by Andreas Fragner about 8 years ago
Hello,
the page is indexed by crawler process and it should index records of an extension.
Updated by Riccardo De Contardi almost 8 years ago
- Status changed from Needs Feedback to New
Updated by Andreas Fragner almost 8 years ago
Using 7.6.14 - still no chance to get more than 200 characters. The config option you described is not provided in indexed_search in Typo3 7.6.14
Updated by Benni Mack over 4 years ago
- Status changed from New to Needs Feedback
So this issue only exists in TYPO3 v7?
Updated by Andreas Fragner over 4 years ago
I did not use indexed search in 8.x or 9.x - sorry I cannot help with your question.
But I think we can close here as Typo3 V7 is EOL. If it is appearing in V8, V9 or V10 I think we can open a separate bug.
Updated by Benni Mack over 4 years ago
- Status changed from Needs Feedback to Closed
Thanks for the info!