Sachyya

Hello @innovative4082 ,

Yes, it does hook into the WordPress Search too. We also provide the shortcode for easy customization too.

Yes, embedding the shortcode into the template should work.

Hello @innovative4082 ,

We haven’t tested with WP Grid Builder but our GridBuilder facet couldn’t work with our Typesense implementation. Since our implementation approach is that, we index data from WordPress website to Typesense server and the faceting works on the results from Typesense. We looked into the demo but we didn’t see the search results from the Typesense.

You can keep the shortcode provided by our plugin inside the Bricks Builder template and style to your need.

Moreover, we have our custom templating and provide template overriding option detailed here: https://docs.wptypesense.com/template-overriding/

Regarding showing images in the search dropdown, you can show the images too. But you would need to customize the default template provided by the default.

Hello @innovative4082 ,

Thank you for your query!

When enabled through its options, the plugin replaces the default WordPress search field. You won’t need WP Grid Builder for faceted search, as Search with Typesense will manage it.

The free version includes instant search and autocomplete shortcodes, offering faceted instant search and autocomplete search for default post types like posts and pages. We’ve also provided detailed hooks and documentation to help you integrate search functionality for custom post types.
Demo for Autocomplete
Demo for Instant search

For WooCommerce, our premium version, Search with Typesense for WooCommerce, delivers seamless integration with features like instant faceted search and autocomplete.
Demo for WooCommerce

Regards,

Sachyya

Hello @edjeavons

Glad that you like our plugin and using it. Really appreciate it.

I verified the issue and yes, there is issue with routing enabled on custom post types. We are working on the fix for this. As a workaround, you can prefix the schema slug like this and the issue should be resolved:

Please change the schema name and the unique prefix to yours.

/*Add a custom prefix to fix the issue with routing*/
function your_slud_add_schema_prefix($schema){
	if( 'antenna' == $schema['name'] ) {
		$schema['name'] = 'my_unique_prefix_name_' . $schema['name']; //replace prefix name with your preferred name
	}
	return $schema;
}
add_filter( 'cm_typesense_schema', 'your_slud_add_schema_prefix', 20 );

Regards,

Sachyya

Hello @flexer06,

The key being exposed is Search Only API key. Search only API key is fine for being exposed publicly if the data is public anyway. It only allows searches and not any other read/write operation. For general search, it won’t matter.

Hello @braino ,

We have updated the plugin to 1.9.3with implementation of the routing feature.

Please do update to latest version to get advantage of routing feature and provide your feedback.

Just implementing is easy but that will provide an ugly URL. To make a pretty URL, it would take longer to develop. That is why we are delaying it to make sure we provide a fully-fledged proper solution with pretty URLs.

Given the high demand for the routing feature, we plan to integrate it using a hook, and this update will be included in the plugin by the upcoming Thursday.

Hope this is helpful.

Hello @braino ,

Yes, it is not currently supported in the base plugin.

However, we are actively working on it. Although it’s not in active development at the moment, it is on our to-do list.

Hello @lajumia ,

I looked into your site and it’s not showing the loading=”lazy” attribute on the images which this plugins removes so it should be working. The “lazyloaded” class could have been added by any other plugins.

Can you verify if the class “lazyloaded” added is causing to lazy load?

Hello @jamiepantling ,

You would have to run a cron job to do it automatically at midnight.

You can try something like this:

// Schedule the event when WordPress initializes
add_action('wp', 'schedule_CMTypesenseBulkImport');

function schedule_CMTypesenseBulkImport() {
	// Check if the scheduled event already exists
	if (!wp_next_scheduled('run_CMTypesenseBulkImport')) {
		// Schedule the event to run daily at midnight
		wp_schedule_event(strtotime('midnight'), 'daily', 'run_CMTypesenseBulkImport');
	}
}

// Hook your function to the scheduled event
add_action('run_CMTypesenseBulkImport', array( Admin::getInstance (), 'CMTypesenseBulkImport') );

Hello @braino

Currently it’s not on our roadmap but once Typesense implements it, we will most likely implement it on our plugin.

There’s a thread for this feature in Typesense’s github here: https://github.com/typesense/typesense/issues/637 in which they have suggested a workaround.

Hello,

Yes,, you can use the swtInstance an object which stores the instance of the current Instant Search that provides a helper function clearRefinements

You can use it like this: swtInstance.cm_swt_instant_search_1.helper.clearRefinements

Hope this helps.

Hello @sokien ,

We appreciate your positive feedback, and we are delighted to hear that the plugin has proven useful to you.

As for the “Clear All Filters” option, its current implementation is not feasible as it would require customizations in the JavaScript code as well. Rest assured, we have plans to include this feature in the future, but at the moment, we are focused on addressing other high-priority issues and implementing essential features. We will keep you informed as soon as it becomes available. Thank you for your understanding.

Hello @tommy94

To index two custom post types into one single index, you have to follow these steps below:
1. Create a new schema that matches both post types using cm_typesense_schema hook
2. Then format the data as per the schema using cm_typesense_data_before_entry

Here’s a sample gist for that: https://gist.github.com/sachyya/3be2d1e970684749a482320f6868fe89

Hope this helps!!!

Regards

Hello @dimqen ,

We appreciate your usage of our plugin.

Concerning the GET query, opting for Replace with Autocomplete instead of Replace with Instant Search in the Replace WordPress Search option allows you to bypass the query.

When utilizing Replace with Instant Search, it is necessary to load the search instance in the footer for the popup to function correctly, resulting in a request being made on every page. Therefore, using Autocomplete could be a potential solution.

Please inform us if this suggestion proves beneficial.

Regards,
Sachyya