Since the update the results do not match. There are bugs with Twig Tweak. The calculation of the results does not correspond to the results displayed.

The views no longer display all the results.

https://www.drupal.org/project/twig_tweak/issues/3086582

CommentFileSizeAuthor
#9 Capture d’écran du 2019-10-20 05-12-03.png26.77 KBzenimagine
#8 Capture d’écran du 2019-10-20 05-14-18.png23.54 KBzenimagine

Comments

zenimagine created an issue. See original summary.

mkalkbrenner’s picture

mkalkbrenner
Primary language German
Location 🇩🇪
commented
Category: Bug report » Support request
Priority: Major » Normal
mkalkbrenner’s picture

mkalkbrenner
Primary language German
Location 🇩🇪
commented

Update from which version?
Provide more details.

zenimagine’s picture

zenimagine commented
Related issues: +#3084031: How to update the module ?

@mkalkbrenner I had the update from 2.7 to 3.7

I have updated the schema archive on my server.

But I find that the results of the views that used a search index are not correct.

If I create the same views without a search index, the results are correct.

mkalkbrenner’s picture

mkalkbrenner
Primary language German
Location 🇩🇪
commented

Did you re-index?
Any messages min the status report or the logs?
Enable search_api_solr_devel to see the number of results from Solr directly.

zenimagine’s picture

zenimagine commented

@mkalkbrenner Yes I recreated the index and there is no error in the logs. I just activated the Devel module.
What should I do ?

Here is a page of my site.There must be 36 elements, but there are only 10 of them displayed (if I create a view without an index, it works) :
https://dev.s1biose.com/fr/question

Here is a page of my site. There must be 38 items in "Contenus", but the counter only shows 10 (if I create a view without an index, it works) :
https://dev.s1biose.com/fr/membre/mathieu

All index-based views remain stuck at 10 since the update. I deleted Solr 7.4.0 and installed Solr 8.2.0 but it does not correct.

zenimagine’s picture

zenimagine commented

@mkalkbrenner Do you have an idea of what to do or if it's a module bug ?

zenimagine’s picture

zenimagine commented
StatusFileSize
new Capture d’écran du 2019-10-20 05-14-18.png23.54 KB

@mkalkbrenner The view counter displays the correct result only if I use paging with a defined number of results :

Otherwise it remains stuck at 10 :

zenimagine’s picture

zenimagine commented
StatusFileSize
new Capture d’écran du 2019-10-20 05-12-03.png26.77 KB
zenimagine’s picture

zenimagine commented

In a block view based on a search index, all items are correctly displayed but "Global: Result summary (Global: Result summary)" remains stuck at 10.

In a page view based on a search index, all items are not correctly displayed and remains stuck at 10, but "Global: Result summary (Global: Result summary)" displays the correct results.

mkalkbrenner’s picture

mkalkbrenner
Primary language German
Location 🇩🇪
commented
Status: Active » Fixed
Related issues: +#3051411: out of memory on Solr Cloud, +#3068714: Views without a pager are now limited to 10 results, make the default rows parameter configurable

It's not a bug but a missing configuration.
The reason for that "change" was a bugfix: #3051411: out of memory on Solr Cloud
The new config option for your problem was introduced by: #3068714: Views without a pager are now limited to 10 results, make the default rows parameter configurable

Increase the "rows" default limit in the "advanced" section of the Search API Server settings.

Solr always requires to limit the search results. This default value will be set if the Search API query itself is not limited. 2147483630 is the theoretical maximum since the result pointer is an integer. But be careful! Especially in Solr Cloud setups too high values might cause an OutOfMemoryException because Solr reserves this rows limit per shard for sorting the combined result. This sum must not exceed the maximum integer value! And even if there is no exception any too high memory consumption per query on your server is a bad thing in general.

zenimagine’s picture

zenimagine commented

OK, thanks

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.