Recommendations for Third-Party Search Suite - Forum | JoomShaper
Solved SP Page Builder

Recommendations for Third-Party Search Suite

Asked by jeffery104623 1 month ago Last activity 1 month ago

I know Page Builder has issues finding long text fields. Since my data has been built into Page Builder since version 3.x, which third-party vendors would you recommend to ensure I can search for product IDs? My product IDs are in HTML code, and the products aren't created and published using articles; they're all separate Page Builder pages. I've found these two so far. What would you suggest? Thank you, or are there better solutions?

https://drive.google.com/file/d/1V5uH_NpT3twrDaGH4nYrcDrVsW1yL3hi/view?usp=sharing

EB Ajax Search

https://extensions.joomla.org/extension/eb-ajax-search/

Geek ElasticSearch

https://www.joomlageek.com/product/component-geek-elasticsearch

Accepted answer

Marked as the solution
Atick Eashrak Shuvo Staff
1 month ago

Thank you for reaching out and for sharing the details of your setup.

SP Page Builder currently works with Joomla’s Smart Search for indexing and searching its content. However, we cannot confirm whether a specific third-party search extension will be able to properly index and search product IDs stored within the HTML content of SP Page Builder pages.

We also recommend keeping in mind that SP Page Builder 3 is no longer under active development, so some functionality or compatibility with newer third-party extensions may not work as expected. We always recommend using the latest version of SP Page Builder to ensure you have the latest features, improvements, and compatibility updates.

Since the behavior of third-party search extensions depends on how they index SP Page Builder content, we recommend contacting the developers of EB Ajax Search or Geek ElasticSearch directly. Please share your specific requirements with them and ask whether their extension can index SP Page Builder pages and search for product IDs within the HTML content.

We appreciate your understanding.

Log in to reply.