Hi!
That’s odd. Does the same thing happen if you switch to another theme temporarily? For example, try the default Twenty Sixteen theme to see. Let me know how it goes!
Hello Ricard
Many thanks for your reply.
Yes it does the same thing. Please keep in mind that I had to manually add the search button in the job-filters.php (through a child theme) because the search button isn’t in the job-filters.php by default.
<div class="search_submit">
<input type="submit" name="submit" value="Search">
</div>
Kind Regards
Wim
Can you post the full content of job-filters.php on https://pastebin.com/ or somewhere similar, and then give me the link to it? I presume there won’t be any private or proprietary information in the file but if there is, make sure to remove it before posting it. Thanks!
Hi Richard
Here you are: https://pastebin.com/tT1rx8M9
Many thanks for looking further into it.
Kind Regards
Wim
Hi! Thanks for the file. I’ve passed this along to the developers because I don’t know what’s happening. For my own internal reference, it’s issue #2075. I’ll get back to you when I hear from them!
Hi! It looks like the problem is the Submit button you added:
<div class="search_submit">
<input type="submit" name="submit" value="Search">
</div>
WPJM will search automatically via javascript when people enter terms, without the need for a Search button. Explanation from the developer:
WPJM’s filter form tries to be Javascript based. It listens for the return key or for field changes and then automatically submits the form. It can prevent traditional (page reload) form submission on Enter/Return using the build-in template because there is no Submit button. When a person hits Enter/Return when there is the submit button (from within a text field), JS fires the update and then the browser submits the form in the traditional way. If they just click Submit (without having changed the fields), you’ll see it just submit the form traditionally (without using JS).
So, our suggestion is to remove the button.
Thanks for the reply Richard.
Just to be sure. It isn’t possible to remove the onchange-event filter?
Kind regards
Wim
Hi! You’d have to edit the plugin files / javascript files for that. There’s no filter or anything that allows you to remove it, no.
