[Ernest Marcinko]

Hi Mads,

To restrict items to a specific category only, check this documentation for a step-by-step guide. It should do the trick 🙂

There is no pop-up feature, however there is a compact (slide out) search box feature. However most themes or page builders nowadays have a pop-up feature built-in, if yours have that feature too, then I recommend using that and placing the search box to the pop-up itself.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Sure!

I have uploaded the image to this reply.

[Ernest Marcinko]

Usually the best option is the theme custom CSS box, but you can also use our plugin custom CSS input here: https://i.imgur.com/Grrpeqo.png

You should indeed not change any of the files as it will be overwritten during an update. The custom CSS input above should do the trick.

[Ernest Marcinko]

Hi,

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

You almost got it right. This is not yet officially fully supported (but it does work), that’s why there is no documentation for it yet.

To make it work both the column and the row has to have the class name. I have added the class to the column as well, now the search and filtering should start working as intended.

[Ernest Marcinko]

Hi,

It is an indended behavior for cases when the search results are not closed on blur events and the seleciton does not get covered up. It’s a bit problematic to get it right as both elements are fixed or absolute positioned, so one will hover over the other.

In your case if it fits better you can force it’s z position via this custom CSS:

.asp_select2-container {
    z-index: 10 !important;
}

This should place the selection container below the results container on the z axis.

It will however still hover over the search input, that is technically impossible to avoid. An absolute or fixed positioned element in a higher up relative descendant (the results and the floating selection in the body element) will always have precedence over elements lower down the DOM tree (the search box within the content).

• This reply was modified 7 months, 3 weeks ago by Ernest Marcinko.
• This reply was modified 7 months, 3 weeks ago by Ernest Marcinko.

[Ernest Marcinko]

Hi,

That unfortunately does not apply to the selection container, it applies to the filter box container only (when used with checkboxes or other non-floating elements).

Luckily it is very easiely adjustable via a bit of custom CSS:

.asp_select2-container .asp_select2-results__options {
    max-height: 300px !important;
}

I hope this helps!

[Ernest Marcinko]

Hi,

It is very likely due to the admin bar present on the page (it generates a negative margin relative to the body). If you test it on an incognito that it should look all right.

If this is a concern (ex.: your users see the admin bar), there is a way to offseet that via this custom CSS:

body:has(#wpadminbar)>span.asp_select2-container {
    margin-top: 32px !important;
} 

This should do the trick!

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Theoretically yes, via some custom CSS it should be possible to hide both the search and the settings boxes:

.asp_ss, .asp_m {
    display: none;
}

[Author]

Posts