BUG: pagination after index

[tbuA3web]

Describe the bug I have a pagination on my home page which is 2506 pages without using the module. When I use the module I only have 705 pages left. I restart an indexing with the command: "wp elasticpress index --setup --show-errors --allow-root" But nothing changes. If I deactivate the module, it works.

Steps to Reproduce

1. Activate module
2. index with "wp elasticpress index --setup --show-errors --allow-root"
3. Go to homepage
4. See problem

Expected behavior I thought it was going to work the same. Either 2506 pagination page

Environment information

• OS: Ubuntu 20.04.1 LTS
• WordPress version: 4.9.16 (I cannot increase)
• ElasticPress version: 3.5.6
• Elasticsearch version: 7.10.1
• Where do you host your Elasticsearch server? localhost
• What ElasticPress features do you have currently active? All posts
• Plugins and version: [Adminimize 1.11.7, Advanced Custom Fields PRO 5.8.4, Duplicate Post 3.2.2, ElasticPress 3.5.6, Images de catégories 2.5.4, Real 3D Flipbook 3.3.0, Redirect Post to URL 1.2, Shortcoder 5.4, Yoast SEO 11.3]
• Theme and version: CyberChimps Pro Starter 1.9.0

[felipeelia]

Hi @tbuA3web,

You will need to debug it further. Some questions:

1. What is the query you are running on your homepage? A simple list of posts, a specific search?
2. Did you already identify some characteristics of posts that are not returned when ElasticPress is enabled?

Also, to help you to debug problems like that, you can install the Debug Bar and the Debug Bar ElasticPress plugins. With both installed and active, you'll see a "Debug" link in your admin bar, clicking on that you'll see available an "ElasticPress" option. That will show you the query sent and the response returned.

[github-actions[bot]]

This issue has been automatically closed because there has been no response to our request for more information. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. See this blog post on bug reports and the importance of repro steps for more information about the kind of information that may be helpful.