I completed the migration of the website and the issue is not reproduced on our server, you can check it here hidden link
I am not sure what on your server is causing this 307 response code. Please check with your hosting provider if he can provide help so we can understand what is the cause of this issue.
I've just tested you duplicated site and have the eaxct same issue.
When I enter textr in the "Recherche" textbox, the auto search doesn't launch, and the only available button in virtual keyboard is "NEXT" so I can't launch the search.
Thank you.
Hello and my apologies for the late reply. I can reproduce the same issue on my mobile and my colleague confirms that too.
It turns out that the search input expects an "Enter" clicked to trigger the search. The "NEXT" button does not seem to trigger the search. So, I come up with this custom Javascript code that will wait 3 seconds after the last keyboard input and then simulate an "Enter" key.
jQuery(function($){
var seconds_to_wait = 3;
var mytimeout = null;
$( document).on( 'keydown', '.js-wpv-ajax-results-enabled .js-wpv-filter-trigger-delayed, .js-wpv-ajax-results-submit-enabled .js-wpv-filter-trigger-delayed', function(e){
clearTimeout(mytimeout);
if ( e.which == 13 ) {
return;
}
var input = jQuery(this);
mytimeout = setTimeout(function(){
var ev = jQuery.Event("keypress");
ev.which = 13; // # Some key code value
ev.keyCode = 13;
input.trigger(ev);
}, seconds_to_wait * 1000)
});
})
I tested it on the test server on my mobile phone and it seems to work. Would you like to test it from your side and then implement it on your server and confirm if it is working.
In deed this works great; thank you.
Would it be possible to force explorers to detect the search field as an input field and therefore allow the "SEARCH" button instead of the "NEXT" one ?
Thank you.
From what I was able to find online so far, I think that there is no way to force the mobile virtual keyboard to use a "Search" button instead of the "Next". Mobile keyboards will always show the "Next" button until we get to the last input on the form.
So, if you put the search input field at the end of the form, instead of the beginning, it will not show "Next".
This has nothing to do with Toolset or WordPress, it is a decision made by the mobile system(Android, iOS).
My issue is then resolved now. Thank you very much!
