[Ernest Marcinko]

I’m afraid a PHP sinppet will not help in this case, this requires a core file change.

Well I don’t have a timeframe, the next update is a major rework on the inner file structure, and it takes a huge amount of time unfortunately.

I might be able to do this via back-end access as well, but in that case please make sure to have a full site back-up that you can revert back, as changing a file via the wp plugin editor could lead to an unusable back-end (if the file change is not successful).

[Ernest Marcinko]

Hi,

This is a known issue with a very specific setup, where Elementor shows double results from the override. They are aware of the problem, but they have not addressed it.

I made a possible solution, which is going to be available in the upcoming release. If you want to, you can add temporary FTP and back-end access, and I will integrate this change, it only affects 3 lines of code in a single file.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Well, I’m afraid these are only possible with major modifications to the core code.

The issue with the flow and multiselect is likely only something with either the configuration or a CSS conflict. Can you please make sure to have rows set to flex here: https://i.imgur.com/rvDWg3h.png
That should very likely fix the flow for the new items.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

Thank you for the details!

I checked the configuration, and the only issue I noticed was the search override was disabled on that form. After enabling and searching for SKUs, I am seemingly getting the correct results.

I generally do not recommend using live page loaders, there is no guarantee that they account for proper header changes and trigger the right events, usually it’s trouble on the long term.
However when I checked it seemed to work okay, aside from minor styling issues, but that is from the custom CSS, not the plugin itself.

In the _search.scss, you have a group starting with:

#ajaxsearchpro1_1 {

.. but that is not correct, because that only targets the first instance of the first search bar, but when using the live loader, it will change, so instead of that you should use:

.asp_m_1 {

..or maybe even this could work:

#ajaxsearchpro1_1, #ajaxsearchpro1_2 {

But the first one is much more generic. I suggest avoiding using IDs, because if there are shadow duplicates (from for example the live page loader), the plugin will fix it’s own ID to avoid duplicate node IDs.

Please note that I can’t guarantee anything for customizations, that includes style changes as well.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

Thank you for the details!

For that, try the following settings: https://i.imgur.com/3lx85pN.png
This will place the search to an absolute position, where it is removed from the document flow. The closest relative parent will be the “anchor” point for the search position then. You may have to play around with the “top” and “right” position values to get the correct alignment, but this is the setup we use in our demo header search.

[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.

[Author]

Posts