[David Cranley]

Hi Ernest,

We chatted with Kinsta about this because we could not find further info in their error logs. Here is what they said.

“When a POST request is used, unlike GET, there is data being exchanged between the server and the browser (eg: some parameters will be sent to that URL, a good example of a type of page that would use POST instead of GET is a contact form, where the message would be sent in the POST request). So it could also be due to the contents of the POST request, as the script (in this case /wp-json/ajax-search-pro/statistics/interaction/add) may have received data that it doesn’t know what to do with, and in this case, a generic 500 error would be displayed. I have tried to access the URL from where that request was generated (/publications/ according to the log entry), and I tried to search for “test search” and didn’t get any errors, so this could indeed have been due to a request with either incorrect or malformed data, which the target script wasn’t able to process.”

When we asked if there was any more detailed info available:

“Unfortunately not, I do not see anything in the error log related to this. Your WordPress’ installation’s debug.log is also not showing anything related to that specific request (you can confirm this in the /wp-content/debug.log and debug.log.1 files). So it does look like it was something malformed, maybe from a bot/automated request.” 

We’re sorry that there isn’t more that I can provide.

[David Cranley]

Thank you very much Ernest, that fixed it.

[David Cranley]

Thank you Ernest, but unfortunately, the problem remains the same. Does this mean it is not possible at this stage?

[David Cranley]

Hi Ernest,

Thank you for this. It seems like this function only works on desktop, and not on mobile, is that correct? I did test on mobile in incognito and on several devices. If we can find a solution that works on both that’d be preferred.

[David Cranley]

Thank you for letting me know, I’ll keep an eye on the next updates.

[David Cranley]

Good morning Ernest,

Thank you for letting me know.

Do you now when (approximately) the next release milestone will be?

The project I am using this on is due for go-live soon, so I just want to plan accordingly.

[David Cranley]

Hi Ernest, I just wanted to thank you to fix this issue and add the autocomplete tab functionality in the latest release. It is truly refreshing how you take feedback to heart and use it to improve your already great product even further. Have a great day!

[David Cranley]

Thank you Ernest, adding the tab option will be great. With the upcoming release, do you mean the one scheduled for next week?

[David Cranley]

Thank you very much Ernest, we’ll keep an eye on the updates.

[David Cranley]

That did do the trick. Thank you very much!

[David Cranley]

That all makes perfect sense, thank you for spotting that. Yes, the values were indeed imported. We’ll take some time in a bit to manually update them, and will confirm it is then fixed.

[David Cranley]

Got it. Thank you. 🙂

[David Cranley]

Thank you for the quick reply. We’ve updated the SFTP access notes with the port, that may be it. Double-checked the other values, they are correct.

[David Cranley]

Hi Ernest,

Your recommendation to decrease the live search min characters to 0 indeed fixed that issue, that is great. Thank you. We didn’t expect that that setting would affect the filters as well.

Have not had the chance yet to test the PDF related code, but will revert back when we do.

[Author]

Posts