[Ernest Marcinko]

Oh, indeed. I think the problem is, that the resizing is done before the animation of the sidebar is complete, thus the search thinks the sidebar is 0px wide. So, I think a 1-2 second delay on the resize method would solve this:

jQuery(document).ready(function($){
   var scope = $;
   if (typeof aspjQuery != 'undefined')
       scope = aspjQuery;
   jQuery('#nks-tab-1').on('click', function(){
        setTimeout(function() {
          scope(window).resize();
        }, 1200);
   });
});

[Ernest Marcinko]

Hi!

Very nice implementation of the search, I like your site design!
I think, in your case it would be better to trigger a resize method, when the user clicks on the search icon on the left side of the screen. The new code should look something like:

jQuery(document).ready(function($){
   var scope = $;
   if (typeof aspjQuery != 'undefined')
       scope = aspjQuery;
   jQuery('#nks-tab-1').on('click', function(){
       scope(window).resize();
   });
});

I havent tested this snippet, I can only hope it works.

• This reply was modified 11 years, 9 months ago by Ernest Marcinko. Reason: code fix

[Ernest Marcinko]

Yes. It’s a recently discovered bug, which is not yet fixed in the current version on codecanyon. However here is an attachement of the latest working copy of the plugin, it will be uploaded to codecanyon in 2 days (after brief testing).
Please deactivate and delete the old one, and install this one instead.

[Ernest Marcinko]

Oh. Could you please open a topic, I didn’t see someone else opened this one, that’s why you can’t see the attachements – it’s only visible for the owner and me.

As for the front end drop down. If you disable everything on the Frontend search settings panel it will disappear. But the version I will attach to your new topic includes an option to hide the options panel.

[Ernest Marcinko]

Hi!

As I examined closely the code I sent you, it looks like the forum put a few extra spaces in it – yet that’s not what I copy pasted here. I will rather attach the fixed and packed plugin to this post, rather then copy pasting the code here. All you need to do deactivate the old one, delete it, install this one and save the settings once again, just to make sure.

As for the keywords: Do you have the search statistics activated? Because it’s disabled by default. If so, then try to de-activate and activate it again. Hopefully it’s just some kind of inconsistency of the settings towards the front-end.

Also, don’t forget, that there are two types of “keyword suggestions”:
First is the autocomplete, which can use the search statistics database or google as the source – this triggers while typing.
The second is the keyword suggestions when no results are found – this shows a dropdown when there are no results, but can only use google, not the statistics database. (hopefully in the future I can work out something to use the statistics as well)

I’m saying this, because a while ago someone mixed up the two options, and indeed it can be confusing because of the similar functions.

[Ernest Marcinko]

Szintén egy bug úgy nézem. Elvileg most már jónak kéne lennie. A gond az volt, hogy a kereső ugyanazzal a névvel használt egy másik icon packot.

[Ernest Marcinko]

Hoppá, jó hogy ezt észrevetted. Úgy nézem hogy valamiért ez a beállítás véletlenül kikerült az újból. Semmi gond, ftp-n keresztül belekódoltam, hogy mindig keressen buddypress csoportok közt. Elméletileg most már jónak kéne lennie, de azért próbáld ki.

[Ernest Marcinko]

Szia!

Vettem a bátorságot és updateltem neked a plugin a legújabb verzióra. Elképzelhető, hogy a meglévő kereső példányt törölnöd kell, aztán újat csinálni helyette a helyes működéshez. Ellenben ez az update elvileg mindkét problémát megoldja, sőt ha minden jó, akkor lényegesen gyorsabb lesz a kereső is.

Örülök, hogy van magyar vásárló is 🙂

Ha valami gond lenne, kérdezz, igyekszem válaszolni naponta, a ticketek mennyiségétől függően.

[Ernest Marcinko]

I think I do. I forgot to mention that if you use fulltext search, then this needs to be copied there as well.

Open up the search_content_fulltext.class.php file in the same directory as before, and go to lines 45-48, you should see exactly the same code as before:

            } else {
                $words = implode('|', $types);
                $post_types = "($wpdb->posts.post_type REGEXP '$words')";
            }

and replace it as before:

            } else {
                $words = implode('[[:>:]]|[[:<: ]]', $types);
                $post_types = "($wpdb->posts.post_type REGEXP '[[:<: ]]".$words."[[:>:]]')";
            }

I hope it finally solves the problem.

[Ernest Marcinko]

Hi!

Is this a default buddypress feature or achieved by plugins? If so, could you link me to the plugin?

[Ernest Marcinko]

Hi!

You were both right and I have found the cause if this problem. There was an error in the query, and the search looked for ever custom post type that matched “product”. Luckily it’s a minor issue, and it only happens in this case, but here is the solution:

1. open up the plugins/ajax-search-pro/includes/search_content.class.php file and go to line 46 to 49 you should see this:

            } else {
                $words = implode('|', $types);
                $post_types = "($wpdb->posts.post_type REGEXP '$words')";
            }

2. replace that code with:

            } else {
                $words = implode('[[:>:]]|[[:<:]]', $types);
                $post_types = "($wpdb->posts.post_type REGEXP '[[:<:]]".$words."[[:>:]]')";
            }

I just run a few tests on the test server, and it worked fine.

I will upload this fix to codecanyon as soon as possible as well. Thank you for reporting this issue, and sorry for the inconvenience!

[Ernest Marcinko]

Hi!

Does this happen if you put the search to a different position?

Do you have a working example page of this maybe? I would like to check the problem closely as I could not find missing closing tags in the code. Or you can copy/paste the whole header.php code to http://pastebin.com/ and maybe I can discover something.

[Ernest Marcinko]

Hi!

I have tried to reconfigure the search and run a quick debugging through the search code.

Unfortunately the problem is with the server low memory limit. Sometimes the site responds in 2-3 seconds, but most of the time it runs out of memory and throws an error message.
Sometimes it does not even reach the search plugin through ajax, it stops with an error 500.

I have tried to increase the memory limit through php (you have 128M defined), but I couldn’t do it. 128M ram is very very low for WordPress with a few plugins. You should increase it to at least 512M – or ask the server administrator to do it for you.

[Ernest Marcinko]

Hi!

Thank you for the details. You have a quite large database, so I made a few adjustments on the settings and the code. It should work much better now. I mostly got results in 1-2 seconds now.

[Ernest Marcinko]

Thank you. I got the details, I will take a look as soon as I can!

[Author]

Posts