[TYPO3-core] RFC: Bug 4470: indexed search pagebrowser shows wrong numbers
Michael Stucki
michael at typo3.org
Fri Aug 31 14:36:02 CEST 2007
Committed to Trunk. Documentation page was updated accordingly.
- michael
Michael Stucki wrote:
> Reminder!
>
> After all this is a no-brainer: If the (new) configuration property is
> set, the loop just doesn't stop after $pointer is reached.
>
> - michael
>
> Michael Stucki schrieb:
>> This is a SVN patch request.
>>
>> Problem:
>> The Indexed Search plugin usually finds the number of search results by
>> counting all results of the database query, and then walking through all
>> of them, doing a check if the user is really allowed to display this
>> result. If he had no access, this match will be subtracted from the
>> result.
>>
>> (This can be controlled using the "show.forbiddenRecords" property, btw.)
>>
>> However, the usual scenario is that indexed search counts these results
>> only up to the page that is displayed, and then stops. This is reasonable
>> because the difference of the result count is usually just a minor one.
>> However, one may be surprised why indexed_search shows a different result
>> number at every result page.
>>
>> The rule is: The closer he gets to the last page of the result browser,
>> the more precise the counter will be.
>>
>> Solution:
>> Add a new property to force exact counting, which simply means that
>> indexed search checks permissions for _every_ search record, not only up
>> to the current page.
>>
>> Documentation changes for Indexed Search manual:
>> Property: exact_count
>> Type: boolean
>> Description:
>> Force permission checking for every record. Otherwise, records are only
>> checked up to the current result page. This will cause a slowdown of your
>> website search, but the results counter will work precisely therefor.
>>
>> Branches:
>> Trunk only
>>
>> - michael
--
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/
More information about the TYPO3-team-core
mailing list