[Ernest Marcinko]

Hi!

I just double checked and it worked for me without issue for both engines you have on that page.

This is what I did:
1. Typed in “operation” on your main page search, clicked the magnifier. It took me to the advanced search results page. So far so good.
2. Then I deselected content and excerpt on the left search and typed in “operation” again: http://i.imgur.com/L8ai5IR.png
3. I got 3 results: http://i.imgur.com/Q0raY7m.png

Am I missing something?

I don’t think I understand the issue with the $ symbol. Could you please perhaps make a screenshot of the problem? I don’t know where to look for it or where it should appear, I think I just don’t understand, I’m sorry.

[Ernest Marcinko]

Hi!

The best solution would be to completely disable that foundation script, it looks very agressive to me, but I might be wrong.

Try to remove the javascript I gave you and try this CSS instead:
[html]
.searchsettings span.checked + label:after {
opacity: 1 !important;
}
[/html]

This should not lag at all, but I’m not sure if it works. Let me know, and I will integrate it to the next version.

[Ernest Marcinko]

Hi!

If you have Advanced Ajax Page Loader settings activated, deactivate all of them, and it should work.

General Options -> Advanced Ajax Page Loader tab.

[Ernest Marcinko]

Hi!

Thank you for the detailed ticket. I think I have figured it out: the slick and slide div cannot handle the rtl direction, so it needs to force the ltr instead and it will work. Put the following CSS code to the Custom CSS field on the plugins Theme Options panel (http://i.imgur.com/kU3C89A.png):

[html]
.rpp_slick {
direction: ltr;
}
[/html]

[Ernest Marcinko]

Yes. I see you are using the ACF plugin. In this case I think you need the extended version of the function, because you are not in the main loop

so instead of:

[php]
get_field(‘fieldname’)
[/php]

use the:

[php]
get_field(‘fieldname’, $pageposts[$k]->id)
[/php]

it might work.

[Ernest Marcinko]

As I said before it’s just a guidance.

It changes nothing, but you can check the XHR request with your browser developer tools, where besides the regular request you will see the dumped structure of the $pageposts variable.

If you want to change the results, you need to change the content of the $pageposts variable, but before you can do that, you need to understand what’s in there, that’s why I suggested that function.

I highly recommend reading about filters and actions first before you proceed: http://codex.wordpress.org/Plugin_API

I don’t know what you are trying to achieve exactly, so that’s why I suggested the guidelines.

[Ernest Marcinko]

Hi Adam!

The plugin uses an entirely different method to parse results than the built in queries. I do not recommend modifying the code, as you will loose the changes if you upgrade the plugin.

There are however filters and actions available, that you can use to customize the results or add/remove new ones.

Here is a knowledgebase article about adding category titles to the result titles: https://wp-dreams.com/knowledge-base/showing-the-category-titles-in-the-result-title/
It’s a good starting point to understand how the results structure looks like.

Based on the example above you can replace the ‘asp_add_category_titles’ function body with something like:
[php]
function asp_add_category_titles( $pageposts ) {
var_dump($pageposts);
return $pageposts;
}
[/php]
..and then examining the xhr/ajax request you will see the structure of the $pageposts variable, which is an array of objects, where the objects are the results.

Another example: https://wp-dreams.com/knowledge-base/showing-the-post-type-name-in-post-title/

The full action and filter list is available in the plugins main directory in the actions.txt and filters.txt files.

So using this filter you can do whatever you want with the result list. It requires a bit PHP knowledge though.

[Ernest Marcinko]

Hi!

I just checked your site with iPhone5 and iPad and it worked for me: http://i.imgur.com/C2pbG1q.png

Also tried to simulated multiple widths and multiple devices, but all of them worked for me. On what mobile device is it now showing? Could you send me a screenshot of the issue?

[Ernest Marcinko]

Hi!

Yes, there is a newer version available, it was updated just Yesterday 😉

You can download the updated files from codecanyon. Please follow the update steps in the documentation for the safe update.

I will then revise this ticket, the update might solve some of the issues.

[Ernest Marcinko]

Could you link me to a page where the search is visible? It might be only a stylesheet issue 😉

[Ernest Marcinko]

Hi!

Plugin version 3.5 just got accepted on codecanyon. May I ask you to upgrade it? If you download the plugin again, you should now get the newer version. It might solve the issue with the random results, as I thing I might know what have caused it.

There is a guide in the documentation on how to safely upgrade (1. chapter).

Don’t delete the current version installer, in case it won’t work or something 😉

I need to get some sleep, I will get back to you tomorrow morning. Let me know if the new version fixed anything.

[Ernest Marcinko]

You can edit your first post, or you can attach a text file with private details. It will be visible only to me and you.

I understand, but I can’t seem to reproduce the issue on my local test servers. It works fine there, no weird results.

I need to see this somewhere to check the ajax requests, parameters, etc..

[Ernest Marcinko]

Hi!

I see now. So the keywords are stored in the search_terms custom field as “keyword 1, keyword 2, keyword x” – thus comma+space separated.

I made a few modifications on the source code that should respect this rule, so only the whole keyword matches should be returned.
I think it should work now as you described.

I’m attaching the changed lines here for future reference to myself. file search_content.class.php line 167 custom_field search related:
[php]
// NOTES: whole word, comma-space-WORD-comma, BOL-word-comma, comma-space-word-EOL
$parts[] = "($wpdb->postmeta.meta_key=’$cfield’ AND
(
lower($wpdb->postmeta.meta_value) LIKE ‘".$s."’
OR lower($wpdb->postmeta.meta_value) LIKE ‘%, ".$s.",%’
OR lower($wpdb->postmeta.meta_value) LIKE ‘".$s.",%’
OR lower($wpdb->postmeta.meta_value) LIKE ‘, ".$s."’
)
)";
[/php]

[Ernest Marcinko]

Hi!

I think you are using an outdated version of the plugin. I believe the term title bug was fixed back in version 3.1. You can download version 3.2 from codecanyon. Please carefully follow the steps from the documentation when upgrading.

As for the taxonomies, there is indeed a limitation for 50 terms per taxonomy. (someone had like hundreds of thousands of them and the browser could not handle it)

You can disable it by disabling lines 109-110 in the ajax-search-pro/backend/settings/class/customtaxonomyterm.class.php.
[php]
if (is_array($terms[$taxonomy]))
$terms[$taxonomy] = array_slice($terms[$taxonomy], 0, 50, true);
[/php]

[Ernest Marcinko]

Hi!

Ajax search pro offers numerous action and filter hooks. These hooks can be used to achieve such tasks. These actions/filters can be found in the actions.txt and filters.txt file. The asp_result_title_after_prostproc filter is what will possibly help.

Based on this knowledgebase article, I will try to implement some kind of solution: https://wp-dreams.com/knowledge-base/showing-the-post-type-name-in-post-title/

Try to paste this code to your themes functions.php file:

[php]
add_filter( "asp_result_title_after_prostproc", "asp_show_the_blog_title", 1, 1 );

function asp_show_the_blog_title( $title ) {
$current_site = get_current_site();

return $current_site->site_name . " – " . $title;
}
[/php]

I have never tried this, but I think it will work.

[Author]

Posts