Home › Forums › Product Support Forums › Ajax Search Pro for WordPress Support › How does a user accept an autocomplete suggetion?
This topic contains 7 replies, has 2 voices, and was last updated by Ernest Marcinko 4 years, 3 months ago.
- AuthorPosts
- June 11, 2020 at 3:21 pm #27804
Although autocomplete suggestions are enabled, there does not seem to be any way for a user to accept them — is this by design?
Also, as a search term gets longer the display of the autocomplete suggestion seems somehow to get out of step — this might be a theme/css issue but I’d apreciate knowing is this is a known problem in some circumstances.
June 12, 2020 at 10:00 am #27818Hi,
The feature was designed when google suggestions did not use a drop-down feature to select from multiple suggestions. Hitting the right arrow key will complete the suggestion. This is due to a rework some time later this year.
I tried a few longer phrases, but it seemed all right on my end: https://i.imgur.com/aUnlEh6.png
Best,
I’m not sure if the issue is resolved, or if it was temporary. Let me know if it’s something else.
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
June 12, 2020 at 10:05 am #27820Type in Research and then the right arrow key to accept the suggestion. Because the suggestion isn’t aligned with the initial text Research turns into Researchch which isn’t found.
- This reply was modified 4 years, 3 months ago by ColeValleyGirl05.
June 12, 2020 at 10:10 am #27822May I ask, what are the sources set for the autocomplete suggestions?
Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
June 12, 2020 at 10:13 am #27823See attachment
Attachments:
You must be logged in to view attached files.June 12, 2020 at 10:26 am #27825Thanks, that is perfectly fine.
The issue is with the response from the server. There are two empty lines added before each ajax request (including the search and all other WordPress core requests). It is hard to tell where the cause is, usually it’s either a 3rd party code that hooks into page outputs (like a cache), or somewhere somehow a file was copied incorrectly. I don’t know if it’s worth looking to find the cause and fix, it could take hours.
The search query already has an auto-fix within the script for this, to remove empty lines and characters. Somehow we forgot to add that to the autocomplete part, it never came up until now.There is a new release scheduled for the next couple of days, I will implement a fix for it, and hopefully that should bypass the empty lines issue, resolving the problem.
Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
June 12, 2020 at 10:29 am #27826Thanks for the excellent support. Search is a vital part of navigating our site; its predecessor had an abysmal search facility that deterred people from using the site at all.
June 12, 2020 at 10:30 am #27827You cannot access this content. Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
- AuthorPosts
You must be logged in to reply to this topic.