Issues with PRO version

[hiltonjrParticipant]

Hi,

I implemented the LITE version at http://bit.ly/2Vu9HYe and bought the PRO version to improve the tool. I installed the PRO on dev.***** http://bit.ly/2KqnE7c

The search is not working as it should, when using a preposition the result is different from when I don’t use it, when in fact it shouldn’t make a difference. For example, in Portuguese Brazil, we search for “benefits of pumpkin” (benefícios da abóbora), which returns different results from searching for “pumpkin benefits” (benefícios abóbora).

Besides that, when saving there is an error message from Cloudflare (see attached). It happens when I disable “Search and return password protected posts?” and save.

Could you help?

• This topic was modified 1 year, 5 months ago by  hiltonjr.

Attachments:

You must be logged in to view attached files.

[hiltonjrParticipant]

By the way, this is the custom CSS I am using on LITE version:

/* Busca header desktop */
nav#site-navigation .asl_w_container {
    width: 174px;
    order: 10;
}

.asl_w_container .asl_m .probox .proclose svg {
    background: unset;
    fill: #595959 !important
}

div.asl_r .results .item .asl_content h3, 
div.asl_r .results .item .asl_content h3 a {
    font-style: normal;
    font-weight: 400 !important;
    font-size: 14px !important;
    line-height: 18px !important;
    color: #595959 !important;
    display: block;
}

nav#site-navigation .asl_image {
    display: none;
}

div[id*='ajaxsearchlite'].asl_m {
    width: 100%;
    border-radius: 2px;
    border: none !important;
    padding: 2px 0;
    background: rgba(255, 255, 255, 0.9) !important;
}

.probox {
    background: none !important;
}

p.showmore a {
    font-weight: 600 !important;
    font-size: 15px !important;
    line-height: 20px !important;
    color: #008EB2 !important;
    border: none !important;
    padding: 12px 0;
    border-top: 1px solid #eaeaea !important;
}

div.asl_r.vertical {
    background: #FFFFFF;
    box-shadow: 0px 4px 15px rgb(74 74 74 / 25%);
    border-radius: 2px;
    padding: 0 !important;
    width: 258px !important;
    margin-left: -30px !important;
}

.item.asl_r_pagepost:before {
    content: "";
    background-image: url('assets/img/search-icon.png');
    height: 15px;
    background-size: contain;
    background-repeat: no-repeat;
    background-position: center center;
    top: 11px;
    position: absolute;
    left: 17px;
    width: 15px;
    opacity: 0.5;
}
.item.asl_r_pagepost {
    padding-left: 45px  !important;
    display: flex !important;
}

#ajaxsearchlite1 .probox .proinput input, div.asl_w .probox .proinput input {
    font-weight: 600;
    font-size: 14px;
    line-height: 20px;
    color: #595959 !important;
}

#ajaxsearchliteres2.asl_r.vertical {
    box-shadow: 0px 4px 15px rgb(74 74 74 / 25%);
    border-radius: 3px;
    border: unset !important;
}

div#ajaxsearchliteres2:before {
    content: "";
    background-image: url("assets/img/seta.svg");
    height: 13px;
    background-size: contain;
    background-repeat: no-repeat;
    background-position: center center;
    top: -11px;
    left: 12px;
    width: 50px;
    display: block;
    position: relative;
    margin: 0 auto;
}

div.asl_r.vertical {
    overflow: unset;
    margin-top: 10px !important;
}

nav#site-navigation .asl_w_container  .asl_w .probox .promagnifier .innericon svg {
    fill: #595959 !important;
    width: 20px;
}

div.asl_m .probox .proclose svg {
    box-shadow: none !important;
    background: #595959
}

/* Mobile */
.mobile-icon-search {
    display: none;
}
.mobile-bar-items {
    display: none !important;
}

.asl_w_container.asl_w_container_1 {
    display: none;
}

@media (max-width: 1160px) {
    .asl_w_container {
        width: 100% !important;
        padding: 15px;
    }
    #ajaxsearchliteres2.asl_r.vertical {
        width: 97% !important;
        left: 0 !important;
        margin-left: 15px !important;
    }
}
@media (max-width: 895px) {
    .mobile-icon-search {
        height: 60px;
        width: 60px;
        position: absolute;
        right: 0;
        display: flex;
        justify-content: center;
        align-items: center;
        cursor: pointer;
        z-index: 99;
    }

    .mobile-icon-search:before {
        content: "\f002";
        font-family: GeneratePress;
        width: 1.28571429em;
        text-align: center;
        display: inline-block;
        color: #fff;
     }

    .search-open-header::before {
        background-color: #fff;
        content: "";
        display: block;
        height: 100%;
        left: 0;
        position: fixed;
        top: 0;
        width: 100%;
        z-index: 100;
        transition: all 0.3s ease-in-out;
    }

    .search-open-header .mobile-icon-close {
        z-index: 9999;
        position: absolute;
        width: 40px;
        height: 33px;
        top: 19px;
        display: flex;
        align-content: center;
        justify-content: center;
        left: 5px;
    }

    .search-open-header .asl_r.vertical {
        width: 100% !important;
        left: 0 !important;
        padding: 0 !important;
        margin: 0 !important;
        top: 65px !important;
        box-shadow: none;
    }
    .search-open-header .asl_w_container.asl_w_container_1 {
        display: block;
    }
    
    .search-open-header .asl_r.vertical .results {
        height: 35vh !important;
    }
    .search-open-header #ajaxsearchlite1 {
        left: 0px;
        background: #F7F7F7 !important;
        border-bottom: 1px solid #DEDEDE !important;
        box-shadow: unset !important;
    }

    .search-open-header .probox .proinput input, div.asl_w .probox .proinput input {
        height: 60px !important;
    }
    
    .search-open-header #ajaxsearchlite1 {
        height: 60px;
    }
    
    .search-open-header #ajaxsearchlite1 .probox, div.asl_w .probox {
        height: 60px;
    }
    
    .search-open-header div.asl_m .probox .proinput {
        padding: 0 45px;
    }
    
    .search-open-header div.asl_w .probox .promagnifier {
        top: 15px;
        position: relative;
        right: 15px;
    }
    .asl_w_container .asl_m .probox .proclose svg {
        top: 28px;
        left: -5px;
    }
    div.asl_w .probox .proloading {
        position: relative;
        top: 14px;
        left: -10px;
    }
    .item.asl_r_pagepost {
        padding: 11px 25px 8px 44px !important;
    }
    .asl_w_container {
        width: 100% !important;
        padding: 0;
    }

    .search-open-header .mobile-icon-close:before {
        content: "";
        background-image: url('assets/img/arrow.svg');
        height: 20px;
        background-size: contain;
        background-repeat: no-repeat;
        background-position: center center;
        top: 2px;
        position: absolute;
        left: 17px;
        width: 22px;
    } 
    .search-open-header {
        cursor: pointer;
    }

    .search-open-header .header-wrap {
        position: initial !important;
    }
    .item.asl_r_pagepost:before {
        top: 17px;
    }

	div.asl_r.vertical {
	    margin-left: 25px !important;
	}

}

[hiltonjrParticipant]

And this is the function I enabled on LITE version

// generate_navigation_search_menu_item_output
add_filter( 'generate_navigation_search_menu_item_output', function () {
	echo  do_shortcode( '[wpdreams_ajaxsearchlite]' ) ;
} );

[Ernest MarcinkoKeymaster]

Hi,

The pro version has a slightly different query structure, given the plugins are completely separate in terms of performance as well as features.
There is actually difference in keywords order, it makes a difference. First keywords and second, third etc.. are weighted a bit differently, the first keyword is has a bit bigger impact. In this specific case “benefícios da abóbora” and “benefícios abóbora” also differs in a keyword “da”. If you want, you can make an exception for this keyword to be ignored completely, and then the search phrases become equal: https://i.imgur.com/BX3VS0P.png

As for the custom CSS, the lite version has a bit different strucute and node names. Replacing asl_ with asp_ and #ajaxsearchlite with #ajaxsearchpro will mosty help. While custom coding is beyond our support, I did a few replacments for you, this is the corrected version for PRO. You will have to test for the rule specificities if some of them does not apply.

The correct code for the Pro version for the nav menu (search ID=1):

// generate_navigation_search_menu_item_output
add_filter( 'generate_navigation_search_menu_item_output', function () {
	echo  do_shortcode( '[wd_asp id=1]' ) ;
} );

Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)

[hiltonjrParticipant]

Hello, unfortunately what’s more important is not working for me. When looking for beneficios da abobora and beneficios abobora, the results are very different. I must not have configured correctly, I would like if possible you help me to do this.

[Ernest MarcinkoKeymaster]

In that case I suggest simply adding the “da” keyword to the exceptions list, and both queries will yield the same exact results: https://i.imgur.com/BX3VS0P.png
That is probably the simplest and cleanest solution to ignore the conjunctive word.

Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)

[hiltonjrParticipant]

I believe that this is not the point, since this change did not change the results at all. In fact, the search has to understand that when looking for “beneficios abobora” it has to look for titles that have the 2 words, before any other result. So it can’t show a result for example “beneficios do cogumelo” before showing all titles that have “beneficios” and “abobora” in the title before.

[Ernest MarcinkoKeymaster]

In that case, I strongly recommend switching to the index table engine – especially if you have a lot of items to search for. Don’t forget to switch to the index table engine when the indexing is finished.

If you have over 10 000 items to index, then I usually suggest only indexing the titles only – as the content and the excerpt may generate a lot of unneccessary search data – if the titles are descriptive.

This configuration will give you the best possible relevant matches for the keywords for the titles.

• This reply was modified 1 year, 5 months ago by  Ernest Marcinko.

Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)

[Author]

Posts