I’ve tested the free version. But it seems it can’t search for Bricks content. May be PRO version works well, it has an index table feature, which can index the “rendered” post contents according to plugin author.
I’m glad someone brought this question up - I’m just getting ready to integrate the AJAX search pro plugin as well, primarily to search some custom post type content. In my last project, I ended up using Elementor-integration features, but obviously this time, that’s not an option. I’d love to hear of any other users’ experience with the plugin.
Thanks, Patric, that’s encouraging! I just installed and set basic configs now. I’ll work with it and report back how it goes for me, for anyone else who may want a review, too.
I think where I ended up having to use the Elementor features before was in customizing the search results page, but hopefully I can just plunk the results shortcode into a Bricks page and work with that.
So far, so good with AJAX Search Pro. It took me a while to figure out that if I wanted to have a custom search results page, I just needed to create a Bricks Template of the “Search Result” type, and that overrides the standard WordPress search result template. Amazing how inexpensive this plugin is for all that it does.
I recently had problems using Ajax Search Pro on a Bricks site. It was finding blog articles and page titles OK, but not indexing page content. After opening an issue with their support, the developer of Ajax Search Pro realized that Bricks was storing its page content in custom fields that needed to be added to the search index. Here is his response:
[Ernest Marcinko]
Thank you, I see the issue now.
It was due to how the Bricks builder stores the content. For some reason it’s in a custom field called _bricks_page_content_2, so I have added that (and some other fields too) to the index.
After reindexing the keywords have grown from 1k to 8k, and I’m getting results from phrases around the page, it should be okay now.
I’m guessing Bricks may have changed the content to that field, or something else may have changed. Either way, it should be fine now.
==================
I’m guessing probably only the _bricks_page_content_2 would need to be included, not the footer, header, or template_type, but wanted to include his original screenshot he shared.