rjsorto

Hi John. Got it; Then why don't add both as options so we have a choice between speed and reliability? Just a mix from the old look up with the new one. And, what about sorting and / or hidding options? you control all the returned data from the providers, and I don't think it will be that dificult.

Hi Brian. I've been following your answers trough many posts, and you have helped in so many, and we all thank you for it. Standard whois although it does not shows suggestions, shows more owned domains in the results. I'm not asking to removed it (if and option to hide them can't be implemented), maybe just to sort them from exact matches to the rest, a customer looking for a name is usually looking for that name and not for a lot of variations, if there was access to this specific code (I know it will never be), many people here would have twek it already. That defeats the purpose, owned domains should not show on results (unless, like in the previous versions of the lookup says is "unavailable"), you should not give a customer hopes just to tell them in the next step "Sorry, but actually, it wasn't available", otherwise is like they just add them directly to any cart and hope for the best. I believe that a company that has gotten this far in this application development, could easily add some more options for this modules.

Is there a way to show only exact matches for domain names or at least sort the domain names to get the exact matches first then the rest (closest first of course) in the suggested domains area? Also, The suggestions I get from the enom provider usually includes many .bar domain names in the suggested domains. The whmcs provider shows domains like whmcs.us as available, even shows sugestions of domains we already have registered and are active.

You should add a limit, lets say if the invoice reaches $20 the fee is waived.

Problem fixed (template), sorry i should had looked a little more. Thread here: http://forum.whmcs.com/showthread.php?t=20606&highlight=array

I'm getting this error since i updated to version 4 how can i fix it? (I have v 4.0.1)

Just remember that chorme is still developing, i do like the speed and all, and i bet it will be amazing when it reaches its 1.x version, but, it will still be that fast?

Im having the same problem WHMCS 3.6.1 Plesk for Linux 8.4.0