This website uses cookies to personalize your experience. By using this website you agree to our cookie policy.

Forum Replies Created

Viewing 15 posts - 17,806 through 17,820 (of 18,415 total)
  • Author
    Posts
  • in reply to: Character #2921
    Ernest MarcinkoErnest Marcinko
    Keymaster

    Hi!

    Try to turn on the “Use fulltext search when possible” option on the Fulltext Search Settings menu. It should solve this issue. (http://i.imgur.com/X6tiiWA.png)

    in reply to: Blog Multisite section doesn't appear any Blog #2919
    Ernest MarcinkoErnest Marcinko
    Keymaster

    Hi!

    1. It’s probably because the blogs are flagged differently for the parser. There is a very quick solution, that helped someone last week. In the next version this is changed of course:

    i) Open up the wp-content/plugins/ajax-search-pro/functions.php and go to line 245, where you should see this:
    [php]
    $blogs = $wpdb->get_results( $wpdb->prepare("SELECT blog_id, domain, path FROM $wpdb->blogs WHERE site_id = %d AND public = ‘1’ AND archived = ‘0’ AND mature = ‘0’ AND spam = ‘0’ AND deleted = ‘0’ ORDER BY registered DESC", $wpdb->siteid), ARRAY_A );
    [/php]

    ii) Modify that line to:
    [php]
    $blogs = $wpdb->get_results( $wpdb->prepare("SELECT blog_id, domain, path FROM $wpdb->blogs WHERE site_id = %d ORDER BY registered DESC", $wpdb->siteid), ARRAY_A );
    [/php]

    2. The search speed highly depends on the database size and server speed. So if you have a larger database, then the best performance tweaks for the search configuration are the following:

    – Disable the search in terms – the terms table can be insanely big if you have thousands of posts: (General Options -> Sources http://i.imgur.com/VCIlQ6e.png)

    – Disable the search in content and excerpt – if you have long content strings, it may take a while for the database to respond. (General Options -> Sources http://i.imgur.com/E2ESzWB.png)

    – Disable the relevance ordering – this is highly related to the previous two. In some cases it helps a lot, in some cases it has no effect, but it’s worth a try: (Relevance Options -> Sort results by relevance)

    – Enable fulltext search – this option is is mainly for big databases. It’s worth a try. (You can find it under the Fulltext Search settings submenu)

    One or a combination of these options will definitely make a difference. Thank you for the login details, I haven’t used them yet. Let me know if these options make any difference.

    in reply to: Plugin working in the back end but not the front end #2916
    Ernest MarcinkoErnest Marcinko
    Keymaster

    Hi!

    I just checked that link, and everything looks normal and it’s working for me. I tried several search terms, and I got results back without problems.

    in reply to: Plugin working in the back end but not the front end #2913
    Ernest MarcinkoErnest Marcinko
    Keymaster

    Hi!

    Could you please link me a to a page where the search shortcode is present? I can’t seem to find it on your page.

    Additionally please update your ticket with proper login information if you can, that usually makes my work much faster.

    If you are having trouble inserting the search to your page, then please take a look at the documentation, there is a very detailed description on how to do these things: http://wp-dreams.com/demo/wp-ajax-search-pro3/docs/

    It’s also a good insight on how the plugin works and other very useful informations.

    Also, the knowledgebase offers you a few tips for known problems, like permission issues, javascript issues etc.: https://wp-dreams.com/knowledgebase/

    Currently I’m way out of my work schedule, I need to get some sleep. I will get back to you tomorrow morning. Good luck until then!

    in reply to: Concerning multiple keyword search #2911
    Ernest MarcinkoErnest Marcinko
    Keymaster

    Hi!

    I see what you are trying to achieve. I thought through it, looked at the code, but I see no good solution, because there are some problems:

    – If the user enters the keywords in different order like “anglais isabelle”, then the search would look in the wrong fields, because there is no way to distinguish the meaning of each word for the search.
    – If the user enters more keywords, then what would happen with the rest? “isabelle rose anglais” for example. The problem is almost the same, it’s hard to tell which field to look where for a program.

    The keyword logic is exclusive for each field, thus probably the best solution for you is to change it to “OR with exact keyword matches”. That way each word individually is compared to each field.

    However the next update will have something that might solve this for you – dropdowns and radio buttons from custom fields on the settings dropdown. In your case for example you will be able to create a dropdown or radio field with languages.

    in reply to: Woocommerce tags less strict search results #2909
    Ernest MarcinkoErnest Marcinko
    Keymaster

    Great πŸ˜‰

    Thank you very much for the donation! I appreciate it!

    in reply to: Woocommerce tags less strict search results #2907
    Ernest MarcinkoErnest Marcinko
    Keymaster

    No problems πŸ˜‰

    That’s my bad, the string-check checks for a character followed by at least 3 numbers. I guess I don’t know much about printers after all πŸ™‚

    Here is a final edit, this should work with the ‘n92’ type of printer names as well: http://pastebin.com/raw.php?i=BumFnQB5

    I will try work out something or some way to integrate this thing there, or if I can’t, then I’m still going make a knowledgebase article on this one.

    Thank you very much, customer support is number 1 priority to me πŸ˜‰

    in reply to: Woocommerce tags less strict search results #2905
    Ernest MarcinkoErnest Marcinko
    Keymaster

    + 1 edit

    In case you are using exact matches, you should rather try this file instad: http://pastebin.com/raw.php?i=Dtpg9qqX

    in reply to: Woocommerce tags less strict search results #2904
    Ernest MarcinkoErnest Marcinko
    Keymaster

    Hi!

    Well, I made something that might work, I’m not sure at all. This time you need to alter a different file.

    Instructions:
    0. Make a backup copy of the wp-content/plugins/ajax-search-pro/ directory, just in case.
    1. Open up the wp-content/plugins/ajax-search-pro/includes/search.class.php file and replace it’s contents with this: http://pastebin.com/raw.php?i=DBQg2j8d
    2. That’s it, you should try it.

    You are the first one to ever offer me donation, thank you very much for that, it means a lot to me. I would have still helped you without your offering.

    Here is my paypal email address: [email protected]

    Let me know if the solution works, I had only tried it on my test server!

    in reply to: Woocommerce tags less strict search results #2902
    Ernest MarcinkoErnest Marcinko
    Keymaster

    Hi!

    I need a little bit more information on this. I rememeber I solved something similar for you, it was something about product tags. Could you please link a result which should be shown?

    Then I will see what I can do for you.

    in reply to: Multisite: Not all sites showing up #2899
    Ernest MarcinkoErnest Marcinko
    Keymaster

    Hi!

    Yes, I have an idea why. If the site flags are different from public/non spam/non archive then they won’t show up by default. This restriction is going to be removed from the next version, but until then, here is a quick fix:

    1. Open up the wp-content/plugins/ajax-search-pro/functions.php and go to line 245, where you should see this:
    [php]
    $blogs = $wpdb->get_results( $wpdb->prepare("SELECT blog_id, domain, path FROM $wpdb->blogs WHERE site_id = %d AND public = ‘1’ AND archived = ‘0’ AND mature = ‘0’ AND spam = ‘0’ AND deleted = ‘0’ ORDER BY registered DESC", $wpdb->siteid), ARRAY_A );
    [/php]

    2. Modify that line to:
    [php]
    $blogs = $wpdb->get_results( $wpdb->prepare("SELECT blog_id, domain, path FROM $wpdb->blogs WHERE site_id = %d ORDER BY registered DESC", $wpdb->siteid), ARRAY_A );
    [/php]

    It should most likely solve the issue.

    in reply to: Plugin won't activate…. #2896
    Ernest MarcinkoErnest Marcinko
    Keymaster

    Hi!

    Thanks for the proper details, it helped me a lot. I’m not sure why was this happening. I uninstalled the lite version just in case, tried to activate, then it worked. It was maybe a temporary server issue, I can’t think of anything else.
    It should be working now.

    in reply to: Can\'t install ajax search plugin via ftp or dashboard #2888
    Ernest MarcinkoErnest Marcinko
    Keymaster

    Hi!

    I just checked the problem and fixed it. It was actually the theme causing the issue. The theme functions are declared without checking for existing function names, and the search plugin happened to have already a function with the same name. The search plugin checks for duplicate entries, however it is executed earlier then the theme, so the only way to avoid this conflict, I had to add 2 extra lines to the themes functions.php file.

    Please notifiy the theme developer to implement function name checks, as it may cause similar issues with any other plugin, and there is no way to avoid it in the plugin code.
    Here is the simple method used, you can show it to the theme developer, but I’m sure he just forgot it:
    [php]
    if (!function_exists(‘function_name’)) {
    function function_name() {

    }
    [/php]

    The extra lines to the themes functions.php file were added to line 1008 and 1022.

    in reply to: Plugin not Working on HTTPS? #2858
    Ernest MarcinkoErnest Marcinko
    Keymaster

    This is the first time I heard of it. The biggest issue I see there, is that it’s not maintained anymore, the git repository was updated 3 years ago. Simply because of that I would not recommend using it – it may contain security issues.

    in reply to: Include numbers in Search (Problem?) #2857
    Ernest MarcinkoErnest Marcinko
    Keymaster

    Hi!

    Thank you for the detailed ticket. I found the issue immediately. It was the fulltext search. MySQL fulltext search has this “feature” where it ignores common words and stuff. I guess that numbers are no exception, so the database just simply ignored the numbers in the search term. I turned off the fulltext options under the “Fulltext search settings” submenu. It should work properly now.

Viewing 15 posts - 17,806 through 17,820 (of 18,415 total)