Categories, custom categories (Series, channel, playlist) show image in search

[Ernest Marcinko]

Hi,

It’s because of this theme CSS rule, it makes it invisible with 0 opacity:

[html].cactus-header-search-form form {visibility: hidden; opacity: 0; position: absolute;top: 0;left: 0;bottom: 0;right: 0;background-color:rgba(38,38,38,1.0);transition: all 0.2s ease-in-out;-webkit-transition:all 0.2s ease-in-out;}[/html]

Try adding this rule:

[html].probox .proinput form {
opacity: 1 !important;
display: block;
visibility: visible;
background: transparent !important;
}[/html]

[Ernest Marcinko]

Also, on mobile devices the widget container is too small, just a few pixels, and it does not fit correctly.
I would suggest the following rule:

[html]@media screen and (max-width: 436px) {
.cactus-header-search-form {
display: block !important;
}
}[/html]

It will ‘drop’ the search below the menu on low-width devices: http://i.imgur.com/uBnHnBn.png

[golasze]

You cannot access this content.

[golasze]

No working when sticky menu option is enabled

[Ernest Marcinko]

Hi,

It is because the sticky menu makes a DOM copy of the search HTML and places it into itself. This results in invalid HTML and loss of attached event handlers, as copying HTML elements does not copy the event handlers as well.

Unfortunately this is not possible to resolve with any custom code, as making duplicate elements of same IDs and names is not valid, and there is no way around it. It is not related to ajax search pro, unfortunately, if you would place any script powered element into the sticky menu, it would very likely fail as well.

[golasze]

Why in default theme sticky search bar is working correctly, but in custom build up plugin not?

[Ernest Marcinko]

Probably because it was developed with the theme, and the script was made to handle that.

[golasze]

You cannot access this content.

[Ernest Marcinko]

Hi,

1. Could you please try this variation:

This will only affect the live results.

2. Make sure to update the plugin to the latest release (4.11.10), as this was a known issue with the previous one.

[golasze]

You cannot access this content.

[Ernest Marcinko]

Hi,

There seems to be invalid HTML within the results, that causes the problem. It happens when there is an unclosed tag within the content, but it’s hard to tell. I can see some ‘a’ and ‘strong’ tags unclosed there in the results.

If you use the advanced title or content fields, make sure to check if there is no unclosed or invalid tag there (scroll down fo the options): https://i.imgur.com/49880D3.png

On the same panel, if there is any exception for the HTML tags to strip, I recommend disabling those as well: https://i.imgur.com/fxgeMj1.png

Don’t forget to clear the search cache as well, after changing these options.

[golasze]

working, thanks

[golasze]

You cannot access this content.

[Ernest Marcinko]

Hi!

I believe that is due to a javascript issue, I think it is caused by a previous code suggestion. On those pages the login form is not visible at all times, and the custom code malfunctions.

Please try replacing it with this one, and make sure to clear the cache as well. This will check the form existence first:

[golasze]

You cannot access this content.

[Author]

Posts