Forum Replies Created
-
AuthorPosts
-
Ernest Marcinko
KeymasterHi,
Thank you very much for the details, it helps a lot!
From looking at the front-end, I suspect the minimum character trigger is set to 3 or more characters instead of the default 0, can you please make sure to set it to 0 here: https://i.imgur.com/RT2xrgb.png
That will resolve the issue.As for the publications, while there is no option for that, it should be still possible with a small custom snippet:
add_filter( 'asp_results', function ( $results ) { foreach ( $results as $r ) { if ( $r->content_type !== 'attachment' ) { continue; } $parent_id = wp_get_post_parent_id( $r->id ); if ( !is_wp_error($parent_id) ) { $r->title = get_the_title($parent_id); } } return $results; }, 10, 1 );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.
Ernest Marcinko
KeymasterYou cannot access this content.
Ernest Marcinko
KeymasterHi!
Thanks for the details, it helps a lot.
The answer is yes, you can achieve something similar. To save you some time, I recommend checking this video tutorial.
While it’s for a WooCommerce setup, it does not matter, it works the same way for any other custom post type.I think it’s covered in the video as well, but you can use the settings and the search results shortcodes to move the live results to a different position.
Ernest Marcinko
KeymasterHi,
I’m very sorry but we can only offer refunds for 7 days after your purchase, and yours was over 27 days ago.
Your license is a lifetime license though, so no further charges will be made.
April 8, 2025 at 10:55 am in reply to: Prioritization of custom fields in index table mode does not work as expected. #53624Ernest Marcinko
KeymasterYou cannot access this content.
Ernest Marcinko
KeymasterHi Erika,
Well, it might be possible with a custom code snippet, but I’m not a 100% sure. In the code below, change the $folder variable to the folder name where of where you want the attachments to be indexed from:
add_filter( 'asp_index_post', function ( WP_Post $post ) { $folder = 'included_folder_name'; // Change this to the attachment folder to include if ( $post->post_type !== 'attachment' ) { return $post; } if ( strpos($post->guid, $folder) !== false ) { return $post; } return null; } );After adding this code, please make a new index.
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.
Ernest Marcinko
KeymasterYou cannot access this content.
Ernest Marcinko
KeymasterYou cannot access this content.
Ernest Marcinko
KeymasterYou cannot access this content.
Ernest Marcinko
KeymasterYou cannot access this content.
April 7, 2025 at 2:12 pm in reply to: Post title missing in a custom field frontend search setting #53609Ernest Marcinko
KeymasterThanks!
Luckily this wasn’t a bug, there was only a parameter missing from the get_values so it treats the values as post IDs: https://i.imgur.com/c7qRMB1.png
I completely forgot about telling you, and on my test I was already using it. I have added it for you, now everything should be all right 🙂
April 7, 2025 at 12:23 pm in reply to: Post title missing in a custom field frontend search setting #53606Ernest Marcinko
KeymasterHi!
Thank you very much for all the details, looks like there is a mix up when fetching the post titles, I’m not sure why though, it works on my local test server.
Can you please add a temporary back-end access? I would like to investigate this further, it’s probably a very minor bug somewhere hiding from me 🙂
April 7, 2025 at 12:19 pm in reply to: I want to make it such that autocomplete can be activated using tab also #53605Ernest Marcinko
KeymasterHi,
Sure! You will need a tiny bit of custom javascript code for that:
document.addEventListener("DOMContentLoaded", () => { document.querySelectorAll('input.orig').forEach(function(el){ el.addEventListener('keydown', function(e) { console.log(e.key); if ( e.key === 'Tab' ) { e.preventDefault(); const ev = new Event("keyup"); ev.which = 39; el.dispatchEvent(ev); } }) }); });Try adding this code via the Code Snippets plugin.
If you want to use the functions.php file in your theme/child theme directory, then use this variation:
add_action( 'wp_footer', function () { ?> <script> document.addEventListener("DOMContentLoaded", () => { document.querySelectorAll('input.orig').forEach(function(el){ el.addEventListener('keydown', function(e) { console.log(e.key); if ( e.key === 'Tab' ) { e.preventDefault(); const ev = new Event("keyup"); ev.which = 39; el.dispatchEvent(ev); } }) }); }); </script> <?php } );For more details you can check the safe coding guidelines.
April 5, 2025 at 12:14 pm in reply to: Prioritization of custom fields in index table mode does not work as expected. #53602Ernest Marcinko
KeymasterYou cannot access this content.
April 5, 2025 at 11:53 am in reply to: Search Results page not working if Query Loop is set to Custom #53601Ernest Marcinko
KeymasterYes, that’s exactly what I was about to say. But I think this is the expected behavior though. Using “custom” as the source, you are basically telling the query loop to use the custom query, and not the archive (current) one – so it’s doing the right thing. I strongly believe this is how it’s supposed to work, but you may want to ask Elementor support to confirm.
-
AuthorPosts