Can Search adhere to menu visibility rules or some other visibility logic?

Hi Bill,

I assume you are using a plugin/custom code of some sort to make this restriction. It is very likely possible to remove these items from the search results list via a custom code snippet.

For that however I have to know how these items being excluded, and if the specific solution has an API function (or any other way) which let us check if the product is viewable for the current user (or hidden for logged out user). Let me know!

Thanks! That helps a lot. Based on their API I have made a custom code, which may do the trick. Unfortunately I have not been able to test it yet.

Try adding this code via the Code Snippets plugin or to the functions.php file in your theme/child theme directory – make sure to have a full server back-up first for safety. For more details you can check the safe coding guidelines.

add_filter('asp_results', 'asp_results_remove_restricted_woo', 10, 1);
function asp_results_remove_restricted_woo($results) {
	foreach ( $results as $k => &$r ) {
		if ( isset($r->post_type) && $r->post_type == 'product' ) {
			if ( !WC_Catalog_Restrictions_Filters::instance()->user_can_view_price( wc_get_product($r->id) ) ) {
				unset($results[$k]);
			}
		}
	}
	
	return $results;
}

Hi Bill,

Great!

The reason is, that the index does not update if the post is not saved, so the SKU is not being added to the database. I suggest triggering at least the save_post hook after each item is pushed, so that WordPress can run all the triggers related to that item. It is a best practice, because WordPress and plugins can have some hooks applied to this for maintenance (like Ajax Search Pro), so this way the index is kept up to date.

The SKU was added later on to the existing products right? So the titles were already indexed (if I understand correctly). If you were to change a product title, clone it to a site then it shouldn’t change in the index either if the save_post (or wp_insert_post) action hook is not triggered.

Okay – let me know if you find anything!

If the dev could somehow add the save_post trigger, that could very likely resolve everything. It is future proof, as if WooCommerce or any other plugin has any other maintenance hooks for that trigger, that will surely execute it.