I have a site using SiteOrigin Page Builder (https://wordpress.org/plugins/siteorigin-panels/) on some pages and not others.
It appears that re-indexing the site using the buttons provided in the site admin work fine. However, running wp algolia reindex –all for that same exact site has it so the last item with Page Builder being used has its content used for any/all non-Page Builder items after that (even though those items have their own content, excerpts, etc.)
I’m wondering if it’s the fact that ob_start() and ob_end_clean() are being used for the non-CLI reindex functionality whereas it isn’t for the CLI command, and the use of SiteOrigin Page Builder needs those two functions to be used to prevent the issues during indexing I mentioned.
I will simply opt to use the non-CLI reindex option for now, but it would be ideal if both options were to be available & problem-free.
Btw, this was posted on https://wordpress.org/support/topic/wp-cli-re-index-command-misbehaves-when-siteorigin-page-builder-is-used-on-site-2/ where it was suggested to post about it here. Even then, this request originates from https://wordpress.org/support/topic/wp-cli-re-index-command-misbehaves-when-siteorigin-page-builder-is-used-on-site/, but I figured it could be mentioned here since it’s still something worth addressing.
I have a site using SiteOrigin Page Builder (https://wordpress.org/plugins/siteorigin-panels/) on some pages and not others.
It appears that re-indexing the site using the buttons provided in the site admin work fine. However, running
wp algolia reindex –allfor that same exact site has it so the last item with Page Builder being used has its content used for any/all non-Page Builder items after that (even though those items have their own content, excerpts, etc.)I’m wondering if it’s the fact that
ob_start()andob_end_clean()are being used for the non-CLI reindex functionality whereas it isn’t for the CLI command, and the use of SiteOrigin Page Builder needs those two functions to be used to prevent the issues during indexing I mentioned.I will simply opt to use the non-CLI reindex option for now, but it would be ideal if both options were to be available & problem-free.
Btw, this was posted on https://wordpress.org/support/topic/wp-cli-re-index-command-misbehaves-when-siteorigin-page-builder-is-used-on-site-2/ where it was suggested to post about it here. Even then, this request originates from https://wordpress.org/support/topic/wp-cli-re-index-command-misbehaves-when-siteorigin-page-builder-is-used-on-site/, but I figured it could be mentioned here since it’s still something worth addressing.