Forum Replies Created
-
AuthorPosts
-
Ernest Marcinko
KeymasterHi!
I have found out why it wasn’t displaying anything on the search results page. It wasn’t the plugins fault, neither the themes fault. It took me a while, but it turns out there is a an issue with the get_posts() core function. It basically has a parameter to tell it to return “any” post type from the give post array, and it fails to work. I’ve made a tiny change to the search code to bypass this issue. I’m going to notice the WordPress development team about this issue as well.
About the filter. As I can see you left “Feeds” in there, but I guess you are wondering why do you get Posts as well. The reason is that on the General Options -> Sources panel the Search In Posts option is enabled and the option is disabled. Therefore the plugin is configured not to display the “search in posts” checkbox, and to search in posts by default.
You can do two things to solve this:
1. Simply turning OFF the Search In Posts option on the General Options -> Sources panel
2. ..or leaving the Search In Posts as it is, and turning on the Show search in posts selector? on the Frontend Search Settings -> General panel panel – if you want to let the user decide to search/not to search in posts.-
This reply was modified 10 years, 6 months ago by
Ernest Marcinko.
Ernest Marcinko
KeymasterI don’t see the search in posts and pages option set on the front-end.
Make sure the configuration is correct on the General Options -> Sources panel.Ernest Marcinko
KeymasterI don’t see the search in posts and pages option set on the front-end.
Make sure the configuration is correct on the General Options -> Sources panel.Ernest Marcinko
KeymasterHi!
If you had a previous version installed before, make sure to follow the important update notes.
I can see the following error message in the console:
Warning: Illegal string offset ‘image_cropping’ in /home/south194/public_html/wp-content/plugins/ajax-search-pro/search.php on line 108
which indicates a data inconsistency, which usually happens if the plugin is updated by only overwriting the files. To fix this issue, open the Cache Settings submenu and just save it without chaning anything. That should get rid off the problem.
If the problem still persists, please add temporary admin and FTP access details to this ticket, and I will debug the code to see what’s causing it.
To safely add the details you can edit your initial post in this thread, or upload a .txt file attachment. Both methods are safe and visible to only me and you.Ernest Marcinko
KeymasterI see an error message in the console. Possibly the CDN script is adding a strange url inside one of the inline scripts, which is handling these keywords.
If you are not using the lates version of the plugin (4.5.5) I recommend updating it. That version uses a different method for handling the phrases, which might solve this problem. Safe update guide here.
Ernest Marcinko
KeymasterYes, it is possible because of that. Try changing the Search engine option to the Regular engine, but don’t save it. The Search in comments option now should become visible. Now turn it OFF and change the Search engine back to index table and now save the options.
This is probably a visual bug, I will look into it before the next version release.
Ernest Marcinko
KeymasterHi!
On the General Options -> Behavior panel try setting the Minimal character count to trigger search option to 0. That way it will send an empty keyword like there was no search phrase at all.
November 24, 2015 at 8:15 pm in reply to: Check/Uncheck all – taxonomy term selectors on frontend #6760Ernest Marcinko
KeymasterCurrently there it is not possible. In future updates however I’m going re-work these features and it will conaint a check/uncheck all box as well.
Ernest Marcinko
KeymasterHi!
There is no option for that, but here is a filter I quickly put together:
[php]add_filter("asp_results", "asp_top_keywords");
function asp_top_keywords( $results, $id ) {
$count = 20; // How many keywords?if ( !isset($results[‘nores’]) ) return $results;
global $wpdb;
$keywords = array();$_keywords = $wpdb->get_results("
SELECT keyword FROM ".$wpdb->base_prefix."ajaxsearchpro_statistics
ORDER BY num desc LIMIT " . $count, ARRAY_A);foreach($_keywords as $k=>$v) {
$keywords[] = $v[‘keyword’];
}$results[‘keywords’] = $keywords;
return $results;
}[/php]
Add this to the functions.php file in your active themes folder. Before using this, don’t forget to turn on the search statistics on the Search Statistics submenu. It will not work without it.
November 24, 2015 at 7:19 pm in reply to: Check/Uncheck all – taxonomy term selectors on frontend #6754Ernest Marcinko
KeymasterHi!
It’s determined based on which of the categories/terms are excluded from the search. If a term is excluded, it will appear as unchecked. You can exclude them on the Advanced Options panel: http://i.imgur.com/EOnJPq2.png
There are similar exclusion boxes on the Frontend search settings panel, but those only determine which of them should be visible at all.
Ernest Marcinko
KeymasterHi!
Pingbacks are essentially comments. If comments as results are not too important for you, I recommend turning off the Search in comments option on the General Options -> Sources panel: http://i.imgur.com/ytThJEq.png
Ernest Marcinko
KeymasterNever mind my previous post if you read it, I was wrong π
I’ve changed the keyword logic on the General Options -> Behavior panel, to AND, as it fits more your case. The default βORβ logic is designed more for small databases. I believe it’s going to give you much more accurate results now.
If you need more information about keyword logics you can read it in the documenation.
Ernest Marcinko
Keymaster**removed**
-
This reply was modified 10 years, 6 months ago by
Ernest Marcinko.
-
This reply was modified 10 years, 6 months ago by
Ernest Marcinko.
Ernest Marcinko
KeymasterHi!
Thanks! Try editing your initial post, there you can add them safely, or you can upload a .txt file with the details. Both methods are safe and visible only to me and you.
Ernest Marcinko
KeymasterHi!
I’ve checked the configuration and it turns out some shortcode in the content was causing the indexing to fail. I’m unable to tell which one, but on the Advanced Options I’ve disabled the Execute shortcodes? option to prevent the problem.
Then I tried again, and it went through nicely: http://i.imgur.com/vw9v5kC.png
It says 1 item is not indexed, but it’s just a miscalculation in the script, as the ajax responses in the console were successful.
-
This reply was modified 10 years, 6 months ago by
-
AuthorPosts