[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

Well, it is not possible to have 2 different index table configurations unfortunately.

I think the best and easiest option here is to not use the index table for one of the post types. I would probably choose the one where you only search the title/excerpt, and use the index table where the content is also searched. However if one post type has significantly more items and data, then use that for the index search regardless of the fields.

[Ernest Marcinko]

Hi Joe,

Sure, it is possible via using a small custom CSS snippet:

.asp_r .overlap {
    display: none !important;
}
.asp_r a {
    pointer-events: none !important;
}

Apply this code to your theme custom CSS field (if it supports it) or use the custom CSS field on the search plugin back-end.

[Ernest Marcinko]

Hi,

Sure!

Can you add a relevant URL where I could take a look? It looks like negative margin/transition on the container, but it’s impossible to tell only by screenshots.

[Ernest Marcinko]

I also notice on the theme that they have embeded the SearchWP Live Ajax Search plugin into the theme, maybe this is also causing possible problems?

Could be but unlikely. It is rather that the “load more” request is not an actual search query to the results page, but a custom made query to a custom handler somewhere on the server.

site search be able to use the live ajax search?
Very likely. First I would suggest trying the automatic replacement feature. If the search form is printed via the get_search_form() call, then it should be replaced automatically.
If no luck, then checking the theme customizer/editor might be the way. Most themes offer replacing the widget in the pop-up with anything, and there you could use the Ajax Search Pro shortcode.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Yes – follow this guide to exclude out-of stock items.

[Ernest Marcinko]

I see, then you are looking for this feature.

Based on your exact page structure, this is the configuration that may work: https://i.imgur.com/xPkKgIx.png
For the DOM selector use: #posts-container

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi Ian,

I only suggest using a load-more feature if it respects the current query string (the arguments in the browser URL). They usually do that, but not in every case, sometimes the load-more will try to load the next page without the query arguments, which may not trigger the search override. In worst cases they use a custom query via the ajax handler, in which case it’s not possible to override.

I have tried to enable that, and it is unfortunately using a custom search endpoint to load more results, not actually loading the next results page. It is not a bad practice, but it makes it nearly impossible to override as it is not recognized as a search query.

I suggest using regular pagination, it is usually much better in every aspec, as it does not require extra scripts and it is SEO and navigation friendly as well.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Author]

Posts