search

10up / ElasticPress

A fast and flexible search and query engine for WordPress.
https://elasticpress.io
GNU General Public License v2.0
1.23k stars 312 forks source link

BUG: Anyway to improve indexing of cpt's? #3938

Closed gwhitehead closed 4 weeks ago

gwhitehead commented 1 month ago

Describe the bug

Running a website that has WPML and ACF installed. Quite a few different post types set up within the website. Even if I do a wp-cli sync with the --setup flag and specifying certain post types it doesn't seem to completely index all items. After running the setup sync via the cli, I was only able to get it to index some of the Product post types by going into the product and hitting the save button.

So I am wondering is there a better way to tell the system to index or reindex an entire post type.

Steps to Reproduce

SSH into the box. Fire "wp elasticpress sync --post-type=product" or "wp wmpl_elasticpress sync --post-type=product" with or without the --setup flag to reset existing entries. Test search still didn't have some things showing in its results. Go into product and resaved and it then appeared into the search results.

Screenshots, screen recording, code snippet

No response

Environment information

No response

WordPress and ElasticPress information

No response

Code of Conduct

felipeelia commented 1 month ago

Hi @gwhitehead, what happens if you try to index those specific products passing --include=<post_id> to the WP-CLI command? Also, does it work if you completely disable WPML?

github-actions[bot] commented 1 month ago

It has been 3 days since more information was requested from you in this issue and we have not heard back. This issue is now marked as stale and will be closed in 3 days, but if you have more information to add then please comment and the issue will stay open.

github-actions[bot] commented 4 weeks ago

This issue has been automatically closed because there has been no response to our request for more information in the past 3 days. With only the information that is currently available, we are unable to take further action on this ticket. Please reach out if you have found or find the answer we need so that we can investigate further. When the information is ready, you can re-open this ticket to share it with us.