Vincent Vega Posted January 9, 2008 Share Posted January 9, 2008 I was testing the system when something strange came up.. (detail: I'm just using the standard templates; portal and boxes) [Admin] On the DOMAIN PRICING page I filled the extensions with a . (dot) in front of the extension according the manual. [user] When ordering a domain name the list of available domain names is not as is suppose to be. The first name is the name literally checked; for example: baz00ka.com Al the other domainnames also checked are in the wrong format: baz00kanet baz00kaorg So without a dot between it. Another thing came up. When the admin does not put a dot before the extension on the DOMAIN PRICING page instantly got the function to change the period for that domain Is this a bug or is this a strange setting? (And the domain whois doesnt seem to work?) Link to comment Share on other sites More sharing options...
Brett Posted January 9, 2008 Share Posted January 9, 2008 Would you post the URL to your installation? (or PM me) I have a few ideas... Link to comment Share on other sites More sharing options...
Si Posted January 9, 2008 Share Posted January 9, 2008 I just came to the forum to post about a bug that has occurred twice to 2 customers of mine this afternoon. Bear in mind I've been running WHMCS for months now and this hasn't occurred before and so I can't comment on the above post about missing dots. As far as I'm concerned, on my setup, everything works, BUT there is a possibility that if customers input the domain TLD incorrectly, there doesn't appear to be a check to advise them. ie, customer opts to change the nameservers of a domain they already own. They enter the domain name mydomain in the first box and in the TLD section, (despite there being a 'dot' in between the 2 boxes), they enter .com (note the dot) instead of just com. The order process continues and only fails when the system attempts to set the domain up on the server and reports back that mydomain..com is invalid. (obviously). Shouldn't the system have picked this up during the order process? Si Link to comment Share on other sites More sharing options...
Vincent Vega Posted January 9, 2008 Author Share Posted January 9, 2008 Brett, you have a message! Si, the problem you mention is something else.. Link to comment Share on other sites More sharing options...
Brett Posted January 9, 2008 Share Posted January 9, 2008 I responded with the fix! Link to comment Share on other sites More sharing options...
weyandch Posted January 9, 2008 Share Posted January 9, 2008 We've had the same issue, been fixed as i activated "additional whois checks" on common tld's.. What's your fix been @Brett? Link to comment Share on other sites More sharing options...
Brett Posted January 9, 2008 Share Posted January 9, 2008 Oops, I guess I could have posted that here as well. If you go to your WHMCS admin section. Under configuration -> domain pricing, change the domain names to include the . in front on the name. So change nl and be to .nl and .be Link to comment Share on other sites More sharing options...
Vincent Vega Posted January 9, 2008 Author Share Posted January 9, 2008 @Brett: That doesn't solve it. Domains still apear without the dot in the 'Confirm Order' page + I'm still wondering why it act different without a dot @weyandch: Where can I find that option? Link to comment Share on other sites More sharing options...
weyandch Posted January 9, 2008 Share Posted January 9, 2008 Configuration -> General Config -> Domains -> Bulk Check Link to comment Share on other sites More sharing options...
Vincent Vega Posted January 9, 2008 Author Share Posted January 9, 2008 You mean selecting more TLD's? Well, that option is already in use but still the dot problem Link to comment Share on other sites More sharing options...
Brett Posted January 9, 2008 Share Posted January 9, 2008 Do you have multiple entries for the TLD's? Link to comment Share on other sites More sharing options...
WHMCS CEO Matt Posted January 14, 2008 WHMCS CEO Share Posted January 14, 2008 Thanks for the report regarding "." being allowed in the domain field. This has now been corrected for the next version. Matt Link to comment Share on other sites More sharing options...
Recommended Posts