Low search not adding keywords to url (GET), not going to result page and keeps returning to my homepage.
this is my form tag, I tried with adding a collection name, keywords (loose), result page in hidden input..
{exp:low_search:form result_page="/nl/search-results" form_class="small-search"}
<div class="input-postfix">
<input type="text" value="" name="keywords" id="keywords" placeholder="Zoek op werk of kunstenaar" />
<button><span class="icon icon-looking-glass"></span></button>
</div>
{/exp:low_search:form}
my results tag (on search-results template):
{exp:low_search:results }
<li>{title}</li>
{/exp:low_search:results}
I'm using the latest version of low search, also EE 2.9.2, structure, transcribe,.. had no issues with older versions of transcribe.
Replies
Low 25 Mar 2015 18:06
What is the exact URL that you see in the address bar when you submitted the form?
It could be that the your server defaults to 'index.html' rather than 'index.php' when accessing the root.
Thomas Van Kerckvoorde 25 Mar 2015 18:09
http://dev.smak.be.glue03.priorweb.be/nl
Search form is on this page
http://dev.smak.be.glue03.priorweb.be...
Low 25 Mar 2015 18:13
That first URL is generated by EE's method to generate a form. It uses the site_url and site_index config values to determine it. Apparently, that results in a /nl in your case. This might be Transcribe's doing.
To exclude LS, try setting up a default search form and see where that submits to.
Thomas Van Kerckvoorde 25 Mar 2015 18:22
Doesn't work either, the thing is I have been using LS and transcribe before with no problems. I'll keep looking into it.
Low 25 Mar 2015 18:24
Well, maybe something changed on the Transcribe side which affects those config items. The action="" of the form should be /index.php or just /.
Thomas Van Kerckvoorde 25 Mar 2015 18:37
I actually disabled transcribe and didn't make much of a difference, I did update low search from 3.X to 4.x today.
Low 25 Mar 2015 18:39
Well, if the native search form has the same behaviour, that pretty much excludes LS... I reckon *any* form generated by EE will exhibit this issue.
Thomas Van Kerckvoorde 26 Mar 2015 13:04
Indeed, I got it fixed by adding: form_action="/" on my form tag. Never had to do that before. But anyway thank you!