Akeeba Ticket System

Monday, 08 September 2014 05:31 CDT

user83594

I notice that the search for related result, start when the user write into the topic input after at least 6 character and after 2 second from the last call or after a space character.

If a mid speed user write the word "performance" in the topic input, after the first 6 characters "perfor" a research start and for example give no result (this is probably if the word is not complete).
If the user complete the whole word in less then 2 second no new research will made leaving the user with no proposed result.

You can see this behavior if you try the above use case on your site under the "Akeeba Ticket System" category.

An idea could be to start the research "500 ms after the user stops to write" or "500 ms after the user stops to write or write a space".
What you think?

I attach an update of instantreplay.js with an implementation of "500 ms after the user stops to write" if you want to try how it works.
(Include changes we are discussing in the ticket "#20859: Multiple "update_clicks" Ajax call")

Monday, 08 September 2014 07:28 CDT

tampe125

Hello Demis,

if you want to modify the javascript file to fulfill your needs, you can easily do that using a FOF unique feature: media overrides.
In this way you can tweak the delay time without hacking extension files, preserving your changes between updates.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Monday, 08 September 2014 07:59 CDT

user83594

Thank you, I know that i can override the js, but the problem is that if you write the word "performance" (in less than 2 second), using the keyboard (not a ctrl-v), the current implementation don't show related result where there are.

This is not an hacking of the extension files. With current implementation and values there are 2 way to get the results:
- write "performanc", wait 2 second and then type "e".
- write "performance" plus a space.

Now, if you try with word "performance" you get this ticket in the related result because in the ticket is present the word "perfor", but if you add a space you can see more results.
You can get the behavior described (no results) using the word "category".

Any value of delay, with exception of very small delays, can cause this issue.
Wait some time after the user stop to type remove the issue and avoid many call that will be done in the case of very small delay in the current implementation.

Mine was a proposal, any other solution that works is welcome.

Monday, 08 September 2014 08:55 CDT

nicholas

Hello Demis,

You have hit a restriction. InstantReply results will only appear after 2 seconds of keyboard inactivity and only if your search term is more than 6 characters long and contains at least one space. This is by design after very careful observation on what was happening on our site since June 2011 when we introduced this feature for the first time. We will not change the way it works as we have observed that any other approach results in a flood of requests with adverse impact to the performance of the site.

However, I can't convince you to not make this change. After all, your use case seems to be very different to ours. Don't worry, there is a solution! You are free to override our Javascript if you want. In fact, you can do so without your changes being overwritten after an update.

Assuming your site's template files are stored in <site root>/templates/mytemplate, create the folder
templates/mytemplate/media/com_ats/js
and copy the file
media/com_ats/js/instantreply.js
to
templates/mytemplate/media/com_ats/js/instantreply.js
This is called a "media override". It doesn't work with all components, just ours (and those from 3PDs who liked and copied this feature, of course). Now you can modify this file any way you please. It will be used instead of the one in the main media directory and won't be overwritten on updates.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Monday, 08 September 2014 09:17 CDT

user83594

Hi,
Thank you for the answer, i'll close the ticket.

Demis

Support