[Ernest Marcinko]

Yes, that’s exactly what I was about to say. But I think this is the expected behavior though. Using “custom” as the source, you are basically telling the query loop to use the custom query, and not the archive (current) one – so it’s doing the right thing. I strongly believe this is how it’s supposed to work, but you may want to ask Elementor support to confirm.

[Ernest Marcinko]

Hi,

Yes, it is possible. You can do that via the advanced content fields.

[Ernest Marcinko]

Hi,

On typography settings you can change all of the fonts to inherit, you can use this custom CSS too, it’s faster:

.asp_w {
   font-family: inherit !important;
}

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

I think yes, something similar. Please check this example, and the tutorial for it.

[Ernest Marcinko]

Interesting, I don’t know if there is another way then. Can you please add temporary back-end access? I will try to experiment with the configuration.

[Ernest Marcinko]

Hi,

Sure!

If you set it to Post titles it will automatically get the titles from the selected post types under the general options. So if you are searching for products, it will suggest product titles.

[Ernest Marcinko]

I see – those are only from the predictive keyword suggestions, the exclusions does not apply to them. You can turn it off here: https://i.imgur.com/k9hvPJi.png

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

Well, there is no feature for that as of yet, but it might be possible via using the search and the results shorcodes and some custom CSS:

1. Place the results shorctcode or block before the search shortcode, so it looks something like this:

[wpdreams_ajaxsearchpro_results id=1 element='div']
[wd_asp id=1]

This will place the results container above the search.

2. Then use this custom CSS to force the correct position:

div[id*="wpdreams_asp_results_"] {
    position: relative;
}

.asp_r {
    bottom: 0 !important;
    top: auto !important;
    left: auto !important;
    position: absolute !important;
}

It should place the search results floating above the search input.

[Ernest Marcinko]

Hi,

Thank you very much for all the details, it helps a lot!

I’ve logged in to check, and I have found that the “Magazine” custom post type was not selected on the search instance panel, so I have selected it for you. Now it will suggest the seemingly missing magazines as well.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi!

1. Make sure that the compact box layout is disabled, you may have enabled it by accident. That will do the trick.

2. Set the following settings: https://i.imgur.com/6zMZx7w.png

3. Sure! Make sure the magnifier and return actions are set to the default “Redirect to the results page” option.

4. You can solve this two ways
– one is to create another search bar and use that on the results page, then you don’t need any custom code.
– The other one is to use this custom CSS on the results page to hide the search settings area.
I don’t recommend making direct changes to the plugin files, as plugin updates will automatically overwrite them. Usually the search results page has the “search” class appended on the body element, so this custom CSS should isolate it:

body.search .asp_ss {
    display: none !important;
}

[Author]

Posts