Forum Replies Created
-
AuthorPosts
-
Ernest Marcinko
KeymasterHi!
Currently only regular custom fields (for posts, pages, and custom post types) are supported due to the very different structure of buddypress.
Are you using any plugin for custom fields or the built in ones? I’m currently working on the upcoming version of the plugin, I can add your request to the list if you want to. I can’t promise the implementation, but I can try.
Ernest Marcinko
KeymasterYes I do, but it’s not possible to do with the same search instance. By excluding a category will exclude both the category and the posts as well.
Ernest Marcinko
KeymasterIt should return categories, it must have been only the cache. Please try again.
Ernest Marcinko
KeymasterOn the “Advanced Options” panel, “Exclude categories” option: http://i.imgur.com/E4xdgaJ.png
Ernest Marcinko
KeymasterSure, you can have those settings of course. If you check the “Frontend Search Settings -> General” panel, you can choose which custom post types you want to show. Also make sure you have the “Show search settings switch on the frontend?” enabled on the same panel as well.
Ernest Marcinko
KeymasterIdeed, there was something wrong. I activated/deactivated debug mode and now it works.
Ernest Marcinko
KeymasterHi!
It’s because that is only for the fronted search settings box, it does not actually exclude the category, it only makes it invisible on the frontend. To exclude the category go to the Advanced Option panel, and there you can do it. It’s all explained in the documentation.
I already excluded the Hidden Category so you should not see the posts from there now.
Ernest Marcinko
KeymasterHi!
The debugging process revealed that the priorities table was not created. Your designer might have missed a step, he should have deactivated the plugin before uploading. After deactivating/activating it again the necessary table has been created and the plugin should now work fine.
Ernest Marcinko
KeymasterHi!
Please carefully follow the steps of safe update described in the first chapter of the documentation, or you can also find it in the knowledge base: https://wp-dreams.com/knowledge-base/updating-from-older-versions/
Ernest Marcinko
KeymasterThat’s most likely because the function I got from the other plugins documentation might not work as I expect (or not exist at all) and the function fails, thus throwing an error. I suppose that the “fifc_get_tax_thumbnail” function does not exist or does not work, or a different function is used.
If you can ask the plugin developer how to retrieve the featured category image based on it’s ID, then all we need to do is replace that line in my code with that, and it’s going to work.
Ernest Marcinko
KeymasterHi!
The only solution is to use a custom filter function. I did a quick search on that plugin, and did a basic code based on this documentation: http://helpforwp.com/plugins/featured-images-for-categories/
Try to put this code to your themes functions.php file:
[php]
add_filter( "asp_results", "asp_cfi_image_results", 1, 1 );function asp_cfi_image_results( $results ) {
foreach ($results as $k=>$v) {
// get the category images
if ($results[$k]->image != null && $results[$k]->image != "")
continue;
if ($results[$k]->date == null || $results[$k]->date == "")
$results[$k]->image = fifc_get_tax_thumbnail( $results[$k]->id, "category", "thumbnail");
}return $results;
}
[/php]If the documentation is correct, then this should work. Please note however that I can’t provide 3rd party plugin support, so you might need to check with the plugin developer for the correct function to retrieve the category images. (if his documentation is incorrect or his code changed)
Ernest Marcinko
KeymasterHi!
This is actually a hard coded thing in the current version, but with a very quick modification you can change the order. If you open up the wp-content/plugins/ajax-search-pro/search.php file and go to lines 342-351, you should see this:
[php]
} else {
$results = array_merge(
$alltermsresults,
$blogresults,
$allbuddypresults["activityresults"],
$allcommentsresults,
$allbuddypresults["groupresults"],
$allbuddypresults["userresults"],
$allpageposts
);
[/php]As you can see the $alltermsresults variable is merged into the results sooner than anything. Let’s move that variable to the end and the terms will appear after the contents:
[php]
} else {
$results = array_merge(
$blogresults,
$allbuddypresults["activityresults"],
$allcommentsresults,
$allbuddypresults["groupresults"],
$allbuddypresults["userresults"],
$allpageposts,
$alltermsresults
);
[/php]Save the file. The terms should appear now after the regular results.
Ernest Marcinko
KeymasterHi!
You can adjust the width of the search bar on the plugins “Theme Options” tab. If the container element is too small, then you should try increase it’s width via CSS. I can’t see the search anywhere so I can’t advice.
For the correct placement you should also consult with the theme developer, he probably knows exactly which spot is the best in the code for the search bar.Ernest Marcinko
KeymasterHi!
There was an error coming from one of the adf plugins javascript files named jquery.flot.js as you can see here:http://i.imgur.com/J8nx3pA.png
I have switched the js source on the search compatibility options submenu to “Minified Scoped”, that way this 3rd party plugin issue is resolved. Please note the other plugin developer, because this error may cause malfunctions in other plugins as well. I’m sure it wasn’t intentional.
The search preview should work now. Please note that the preview might differ a bit from the actual result, as some stylesheets from the theme might not be loaded on the backend.
I wish you a successful and happy new year!
Ernest Marcinko
KeymasterIndeed, you are right.
Misteriously it was not related to the characters. If you try the topic search, it will work now. The problem was, that the search was unexpectedly excluding some of the categories. But I don’t think that’s the issue there with you, because you get unexpected results.
Are you by any chance using fulltext search? Fulltext mysql database queries are highly sensitive to these special characters and often they percieve them as regular expression operators. If so, then please turn off the fulltext search on the Fulltext search settings submenu: http://i.imgur.com/bmGk51p.png
-
AuthorPosts