Instant Search

[delia]

To regroup here :

the dropdown is not showing.

In the instructions:
Dropdown - Input Box Selector : CSS selector of the search input box(es). You might need to change it if you're using a custom template and the results dropdown is not showing.

Default: input[name="keyword"]

So the default input listed as name / keyword WHICH IS NOT A CSS SELECTOR and is also present in my template.

The instant search css has css starting with instantSearchInputWrapper

The template does have a file for the ajax instant search dropdown that matches the CSS.

So I am having difficulty seeing that CSS actually is the problem. Yes, I'm using my own template based on the original sidebox files with no core changes and some additional CSS but mostly default zencart template. I have no added jquery in the site. I see no conflict or issues using the browser console.

I also just installed it on a default 15.8 cart with the responsive template and it doesn't work on it either.

[lat9]

To regroup here :

the dropdown is not showing.

In the instructions:
Dropdown - Input Box Selector : CSS selector of the search input box(es). You might need to change it if you're using a custom template and the results dropdown is not showing.

Default: input[name="keyword"]

So the default input listed as name / keyword WHICH IS NOT A CSS SELECTOR and is also present in my template.

The instant search css has css starting with instantSearchInputWrapper

The template does have a file for the ajax instant search dropdown that matches the CSS.

So I am having difficulty seeing that CSS actually is the problem. Yes, I'm using my own template based on the original sidebox files with no core changes and some additional CSS but mostly default zencart template. I have no added jquery in the site. I see no conflict or issues using the browser console.

I also just installed it on a default 15.8 cart with the responsive template and it doesn't work on it either.

er, the input[name="keyword"] is a valid CSS selector; see this (https://www.w3schools.com/cssref/sel...bute_value.php) link.

[delia]

er, the input[name="keyword"] is a valid CSS selector; see this (https://www.w3schools.com/cssref/sel...bute_value.php) link.

So why does it not work? I know how to troubleshoot CSS problems but there's nothing showing for me to look at.

AND if it doesn't work "out of the box" or for the responsive template and stumps an experienced person, I'm not sure I see the value here. I'm not accustomed to giving up but ....

[lat9]

So why does it not work? I know how to troubleshoot CSS problems but there's nothing showing for me to look at.

AND if it doesn't work "out of the box" or for the responsive template and stumps an experienced person, I'm not sure I see the value here. I'm not accustomed to giving up but ....

Do you have a customized template? The Instant Search plugin's jQuery/javascript is looking for changes to, by default, an input field named 'keyword' in order to send changes from that keyword-entry back to the site to gather matching products.

FWIW, the default responsive_classic uses the template_default/sideboxes/tpl_search.php and tpl_search_header.php to render the search-related sideboxes'. In both cases, an input field named 'keyword' is created to accept the customer's search keywords.

[delia]

Do you have a customized template? The Instant Search plugin's jQuery/javascript is looking for changes to, by default, an input field named 'keyword' in order to send changes from that keyword-entry back to the site to gather matching products.

FWIW, the default responsive_classic uses the template_default/sideboxes/tpl_search.php and tpl_search_header.php to render the search-related sideboxes'. In both cases, an input field named 'keyword' is created to accept the customer's search keywords.

Keyword is created.... how and where? Are you saying the mod does that or that is what is needed to be done? In the instructions it mentions keyword only as a name - not input but attribute of input. So you are saying there needs to be an actual input field (assumedly then hidden from view) that is called name?

No, no error logs or console errors.

People, no one has offered any sample - any code, any site. I don't maintain or create mods anymore but instructions are important. There are no instructions, just that one thing in the configuration.

I was interested when looking at github that there was a suggestion this mod be added into the template. I'm all for that - if only to ge the dang code etc.

[torvista]

Is there a site to look at?

[lat9]

Keyword is created.... how and where? Are you saying the mod does that or that is what is needed to be done? In the instructions it mentions keyword only as a name - not input but attribute of input. So you are saying there needs to be an actual input field (assumedly then hidden from view) that is called name?

No, no error logs or console errors.

People, no one has offered any sample - any code, any site. I don't maintain or create mods anymore but instructions are important. There are no instructions, just that one thing in the configuration.

I was interested when looking at github that there was a suggestion this mod be added into the template. I'm all for that - if only to ge the dang code etc.

If you're using a template based on the built-in responsive classic, make sure that you have (in the admin's Layout Boxes Controller) the search_header or search sidebox enabled for the template.

Each of those sideboxes includes an input field named keywords, which is what Instant Search's jQuery/javascript is looking for.

[delia]

If you're using a template based on the built-in responsive classic, make sure that you have (in the admin's Layout Boxes Controller) the search_header or search sidebox enabled for the template.

Each of those sideboxes includes an input field named keywords, which is what Instant Search's jQuery/javascript is looking for.

And yes, the side boxes are enabled.

@torvista will send url via pm. Site is being readied for upgrade/with new branding.