[Ernest Marcinko]

Hi,

Thanks for the details, it helps a lot!

The input field is completely missing from the search input container. This is due to either a corrupted file or a modification to the code. If you haven’t changed anything on the search code, then I recommend reinstalling the plugin via the plugin manager to restore any file corruptions. (deactivate, delete, upload & install)

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

Thank you very much for all the details, it helps me a lot!

All right, I did a few adjustments for you on the architects-afs search instance, which I think fits better for your use case, as well as made a filter on the custom field too. Here is a step by step guide on what I did exactly:
– First on the page I noticed that you want the settings and the results, so I changed the order (so the filters are on top), by using the search and the result blocks.
– Then I made the custom field filter like so
– For a better output, I changed the basic theme to a horizontal layout, then turned off the scrollbar and adjusted the item widths by device, then changed the whole results layout to a block, then also enabled automated load more feature for an automated results loading

I think it fits better for your use case overall. I hope this helps!

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi Seamus,

Thank you for the details, it helps me understand the issue better.

You are looking for this hook:

apply_filters('asp_index_post', WP_Post $post, array $args);

In your case, the final code will look something like this:

add_filter('asp_index_post', function( $post ) {
	if ( $post === null ) {
		return $post;
	}
	$meta_key = 'available';

	if ( function_exists('get_field') ) {
		$available = get_field( $meta_key, $post->ID, true ); // ACF support
	} else {
		$available = get_post_meta( $post->ID, $meta_key, true );
	}

	if ( $available ) {
		return $post;
	}
	
	return null;
}, 10, 1);

Basically whenever the hooked function returns null, the post is skipped from the index. In the code above a check is made on the “available” custom field. If it is true, then the post is returned, otherwise null. It may need some testing to make sure the field values are that, but based on your description I assumed this solution.

[Author]

Posts