Bug #17343
closed
[TYPO3 V4.0] - Pagecount not correct in indexed_search
Added by Guillaume Bourreau over 17 years ago.
Updated about 6 years ago.
Description
Hi,
I have already read a post like this, but i can't find the solution wrote in the post, which tell me to go in the CVS.
The post have the number : 0000939
It is about the number of the results which is changing when we change the page with the page browser.
Logically this total number of results should always be the same, on all the results pages, but it is not.
Could you tell me how to know the solution ? I don't understand how to see it in the CVS.
Maybe i can solve the problem without using the CVS... So, could tell me how ?
Thanks a lot.
(issue imported from #M5714)
Files
I can confirm this for 4.1.1. Result number of indexed search results decreases on page 2, page 3 ....
then this bug should be closed?
I had the same problem. I commented out line 597 in class.tx_indexed_search.php
//if (($c+1) > ($pointer+1)*$this->piVars['results']) break;
and the total result count was displayed correct.
I didn't dig deeper in it, but there's a comment at this line saying:
// This may lead to a problem: If the result check is not stopped here, the search will take longer. However the result counter will not filter out grouped cHashes/pHashes that were not processed yet.
Looks like same as Google does :D
@Georg - this wasn't fixed with Michaels commit #4470, result count is still wrong
I tested it like Nico and this helped indeed, result count is correct after that change.
again:
The commit from Michael solves the result count, but display is wrong.
To get this setting is needed: exactCount = 1
but
I have a search with 30 results
1st page: shows result 1 - 30
2nd page shows result 11-30
3rd page shows result 21-30
very strange fiddling with the result rows, i don't find any conf of resultsPerPage, i will investigate more.
Hey Steffen,
Let me know if you need some help. I think Dmitry also investigated and did a little bit about it. It also troubles some of our sites. So in the end it needs too get fixed anyway.
Hi Ben,
i need to fix this within this week because of client. I will talk to Dmitry, thx!
I think i got it. Attached patch works for me with setting
exactCount = 1
Committed to Trunk (rev. 4446)
- Status changed from Resolved to Closed
Also available in: Atom
PDF