Hi,
1. Well, this was never requested before – the plugin offers taxonomy term filters, which is what users are usually after. I can add this to the possible features list, but I am not sure if it’s possible, as taxonomies are in relation with post types, and not the actual post objects.
4. Sure, but I think it might be doable to some extent with a small custom code snippet. I have constructed something that may help. Try adding this custom code to the functions.php in your theme/child theme directory. Before editing, please make sure to have a full site back-up just in case!
add_action('wp_footer', 'asp_add_to_footer');
function asp_add_to_footer() {
?>
<script>
jQuery(function($){
$('.prosettings').on('hover', function(){
var id = $(this).closest('.asp_m').data('id');
var instance = $(this).closest('.asp_m').data('instance');
ASP.api(id, instance, 'toggleSettings', 'show');
});
});
</script>
<?php
}5. Yes unfortunately. It tries to get the actual post content, but it is not available.
6. Actually, it should. I have been able to replicate this issue on our test servers as well. It is related to the content type filters – they are mistakenly recongized as “unchecked” when searching via the default search bar. In this case it causes the missing taxonomies.
There is a very simple fix, but a core plugin file needs to be edited for that. If you wish, you can add temporary FTP details, and I can do it for you.
If you want to fix it manually, then please follow these instructions:
a) open up the wp-content/plugins/ajax-search-pro/includes/classes/etc/class-asp_helpers.php on your server
b) scroll to line 1159, it should be:
self::toQueryArgs_ContentTypes($sd, $o, $args);
c) change that line to this:
if ( $o !== false ) self::toQueryArgs_ContentTypes($sd, $o, $args);
d) save the file, and it is done
7. No, because that would completely freeze the page due to the loop that repeatedly checks for the visibility. This should be fixed via the integration, this is only the next best solution that can be done from the plugins perspective.
9. It was due to a misconfiguration, you had content excluded from all users. I have corrected that for you.
10. The results page is fully controlled by the theme you are using.
We are rolling out an udpate later this week, that will feature a custom results page feature via Elementor Pro posts widgets.