Reproduce: Drupal 8.4.0, search_api 8.x-1.5, database backend, index of nodes, taxonomy terms and users, view with mini pager.

The problem doesn't occur on single entity type index view.

CommentFileSizeAuthor
#3 search_api-2924237.jpg110.27 KBgraber

Comments

Graber created an issue. See original summary.

drunken monkey’s picture

Component: Framework » Views integration
Status: Active » Postponed (maintainer needs more info)

I can't reproduce this problem, the Mini pager works for me correctly in all cases I tried. There must be something else specific about your setup that triggers this problem.
Are you sure that there is more than one page of results?
The perfect help would be if you could provide a failing test case that shows the problem. Otherwise, maybe try it from a clean install without any additional modules and see if you can also reproduce the problem that way. If not, then maybe some other module interferes. (Might be Facets? Or maybe this: #2923976: Search API Database random order facets lost?)

graber’s picture

StatusFileSize
new110.27 KB

You can test here: https://dujrl.ply.st/multitype-test admin:admin, there are 65 entities.

One more strange thing (image attached), I'm not sure if it's related or not.

It seems to be some view caching problem, but the strange thing is that it occurs even with caching set to none on my environment, while on the test one with cache set to none all seems fine. The only difference I see is that mine is 8.4.0 and the test one 8.4.3. Also tried to set caching to "tag-based (Search API)" with the same effect.

To reproduce after changes and CR click the pager links a few times and go back to the previous page.

drunken monkey’s picture

You can test here: https://dujrl.ply.st/multitype-test admin:admin, there are 65 entities.

That just gives me a 404.
Also, this might help me reproduce locally, if I can just duplicate the settings from there – but if I can't reproduce it locally, this would still not help much, as I couldn't use it to find out what's going wrong.

One more strange thing (image attached), I'm not sure if it's related or not.

No, that's a known bug and has been there quite a while now.

It seems to be some view caching problem, but the strange thing is that it occurs even with caching set to none on my environment, while on the test one with cache set to none all seems fine.

Could it be one of Core's Page Cache modules that interferes?

legolasbo’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

I am closing this issue because information was requested over a year ago, but no new information has been provided since. Please reopen this issue with the requested information if you think that this issue is still relevant.