Searches not returning pages built out in the Pro page builder

[cglobal]

Simply put, searching for content on a page built out in the Pro page builder is not returning that page in the search results. After a lot of research and testing, including on a clean WordPress install with the Pro theme added, it appears that the V2 elements are not indexed. I did try several of the popular search plugins, but not one of them helped.

Did I miss something / am I doing something wrong, or are V2 elements indeed not indexed?

[mldarshana]

Hi There @cwsglobal

Thanks for writing in! First of all, please make sure that you’re using the latest version of X/Pro theme on your site. You can check the latest versions and update information from here (https://theme.co/apex/forum/t/troubleshooting-version-compatibility/195) and update your site accordingly if required (https://theme.co/apex/forum/t/troubleshooting-version-compatibility/195),

Then with regard to your original question, please review the following thread (https://theme.co/apex/forum/t/v2-elements-not-searchable/28752/2).

Thanks!

[cglobal]

Hi @mldarshana, thank you for reply. I am using the latest version of X/Pro, and I reviewed the other thread even before I started this thread.

It seems the best that can be done with search as it relates to the V2 elements is indexing the page content so that the title appears in search results, and only if using a third-party search plugin. This is unacceptable.

Is there a way to make the page’s content show up in the search results, as it does when using pretty much anything other than X/Pro, including the default WordPress page editor, without resorting to enabling and crafting excerpts for pages?

The few threads I found on the matter are from more than six months ago, and in each thread, Themeco staff indicated this is a bug, which implies a forthcoming fix. But six months later, nothing.

As I said, this is unacceptable…

[rad]

Hi @cwsglobal,

Yes, it’s a known bug which has no fix as of yet. The v2 elements data are protected and restricted, we need to implement a way to make it visible from search queries.

I really like to fix this as well even with some workaround but it’s complex so it’s currently not doable this time.

Please stay tuned for the updates, I’m also adding this thread to our issue tracker where this bug is originally posted.

Thanks!