Return key set behavior works only a couple of times and then crashes

Hi,

Is there any specific way I can replicate this? I tried a few search phrases, then hit enter, and did it again and again.. but nothing strange happened. I was redirected to the results page every time.

What is the URL of the broken search page? That might help with debugging this issue.

Best,
Ernest M.

Hi.Yes, it does happen eventually after a few attempts. It had happened every time for me and other colleagues trying.
This is the URL while I was searching for the search phrase “gathering”, which is also a name of a product https://oroeditions.com/?s=gathering

Okay. The results page looks like this when I click on that link: https://i.imgur.com/AVCqB3H.png
(I blurred out the details and the URL for privacy) I guess that menu part is not correct?
That is labeled as “sidebar” in the page source, but no styling is applied to it whatsoever, so it’s just printed as is. Unfortunately that is not printed by the plugin, it can’t do that. It looks like as a sidebar widget, but not styled properly – perhaps a stylesheet file is missing.

Try turning off the plugin temporarily, to see if it makes any difference. It should look exactly the same.

Best,
Ernest M.

Hey Ernest, yes but remember that it does that only after a number of attempts. If you go back to the homepage you’ll see the plugin works and looks just fine but the issue arises only when the enter button search is performed a few times in a row. So, it doesn’t seem to me like a style sheet problem. Hope that make sense.

I am seeing that broken page every single time, on every browser. Every attempt, even if I simply visit the results page.

The broken search bar in the screenshot is not the Ajax Search Pro search bar.
That whole section is marked as the sidebar content – which is probably a template part, or a widgetized area of some sort.

You know, the issue is that when the enter button is pressed I would like the plugin to ‘do nothing’ not to display a list, but that option doesn’t seem to take effect. Like I mentioned, it does work a few times but then it reverts back to that broken search results page. But again, it shouldn’t go there at all since I selected the ‘do nothing’ behavior. Make sense?

Hey Ernest, any ideas about this? It looks like the plugin doesn’t pick up the settings as it should. It would be greatly appreciated any help about this. For this company the search is vital and at the current moment a lot of their clients are experiencing the issue. Thanks for your help.

Hi,

Okay, the settings are set to do nothing for both the magnifier and the return buttons?
I just tested this exact configuration, and it seems to work correctly.

When I visit your page, the front-end configuration says it is set to “Results page” for both the magnifier and the return key actions.

If the configuration does not reflect to the front-end, that means, it is very heavily cached. Make sure to double check the configuration (set both to “Do nothing”), and clear all layers of cache – including CDN, page etc.

Best,
Ernest M.

We tried this custom script to disable the enter key and it still did not work, it still reverts back to default settings. Also tried updating the database directly and did not solve the problem

<script>
var el = document.getElementsByClassName("orig");
for (var i = 0; i < el.length; i++) {
el.item(i).addEventListener("keypress", function(event) {
if (event.key === "Enter") {
//console.log(event.key + " " + event.which);
event.preventDefault();
event.stopImmediatePropagation();
}
});
}
</script>

Actually, I reset both magnifier and enter btn to ‘trigger live search’ and it seems to be working for now, hopefully won’t reset again

• This reply was modified 2 years, 7 months ago by reverberation.
• This reply was modified 2 years, 7 months ago by reverberation.

Nevermind. It reverted back again. So, I think we tried everything youve said at this point… anything else you can think of?

Wait, do the options reset back on the plugin back-end as well? As if it rolls back to a previous value? I thought it just does not populate to the front-end.
That may indicate a more complicated issue. The plugin does not roll back the options whatsoever, it can’t do that.

There might be some sort of a database replication/rollback feature installed somewhere, maybe server side, but this is impossible to tell.

I suggest trying a full plugin wipe. Maybe that moves the option keys to a new database partition file. Running a table optimization command could be a good idea too. If this is a database related issue, it is very unlikely to be exclusive to a certain database record only.

I hope the plugin wipe will resolve this.

All the best,
Ernest M.

Yes, that’s what I’ve been trying to explain. No matter how many times we try to set the behavior parameters to whatever it only reverts back to it’s default setting in the back-end as well.

• This reply was modified 2 years, 7 months ago by reverberation.

If it changed, and then reverted back after some time, then this is not an issue with the plugin for sure. I double checked every piece of code altering the settings.

The only piece of code in the plugin to reset all the settings is triggered via the Maintenance panel. That is only triggerable with a valid secure nonce, from an ajax request. There is no way that can be triggered otherwise, that needs to be triggered from that menu, via that button, and then pass a security check on the server side.

Since the behaviour initially works, then changes, the only explanation is a 3rd party code or a server side issue/configuration or database replication/restoration trigger somewhere. The plugin itself is not able to restore the default options automatically.

Try the full plugin wipe, and see if that changes anything.

Ok, I guess we are going to attempt a full plugin wipe at this point. But also I wanted to point out to you that two more affiliated websites are all affected by the same issue. This and this. Not sure if this is relevant to this problem, but just wanted to make you aware of it.

• This reply was modified 2 years, 7 months ago by reverberation.