Rhyzio

Hello mathewparet, This is not caused by the nameserver issue as claimed by the other member. While your nameserver configuration will likely confuse some of your customers, you are correct and it will function. The cause of the error was almost certainly a miscellaneous error from the registrar, which LogicBoxes or WHMCS cannot intemperate. Most likely the domain you are attempting to register is on a reserved list. As such it would still show-up as available in most WHOIS searches, but when you attempt to register it, you get the error in question.

I just thought I'd post that: {$_LANG["Readable Field Name"]} Does work for translating the Options, but then it sends the translated option through instead of the SYSTEMREQUIRED name. If | was activated for additiondomainfields then this would no longer be a problem.

IMO: This is what we need to get the additionaldomainfields working correctly (multilingual): 1) REQUIREDFIELDNAME|Readable Field Name 2) $_LANG["Readable Field Name"] 3) Support for "Name", "Options", and "Default" Any feedback from Admins?

With other fields (lets say Configurable Option Groups) I could use "SYSTEMREQUIREDOPTION|Readable Option". With additionaldomainfields I cannot. All I can get to work is SYSTEMREQUIREDOPTION, which looks terrible unless the Registrar designed their API for the language my WHMCS happens to be in.

Hey Neocorps, try this: (you can change "p.currency = 1" as needed) function getDomains() { $query = mysql_query("SELECT dp.extension'tld', p.msetupfee, p.qsetupfee FROM tblpricing p INNER JOIN tbldomainpricing dp ON dp.id = p.relid WHERE p.type='domainregister' AND p.currency = 1 ORDER BY dp.order ASC"); $dataArray=array(); while($row = @mysql_fetch_array($query, MYSQL_ASSOC)) $dataArray[$row['tld']]=$row; return $dataArray; } $mydata = getDomains();

Did you figure this out? If anyone knows how to get the Date and Time stamp to work, I'd appreciate you posting it. I can't seem to get the Date & Time to work in FF, IE, or Safari. As the previous poster stated you cannot use the spacebar and if you type it in manually you get odd looking dates. Thanks

I've found .cm: .cm|netcom.cm|Not Registered .co.cm|netcom.cm|Not Registered .com.cm|netcom.cm|Not Registered .net.cm|netcom.cm|Not Registered This works for .pe but you have to register your IP with http://www.red.pe .pe|red.pe/api/pe.php?BuscarDominio=|HTTPREQUEST-LIBRE .nom.pe|red.pe/api/pe.php?BuscarDominio=|HTTPREQUEST-LIBRE .net.pe|red.pe/api/pe.php?BuscarDominio=|HTTPREQUEST-LIBRE .com.pe|red.pe/api/pe.php?BuscarDominio=|HTTPREQUEST-LIBRE .org.pe|red.pe/api/pe.php?BuscarDominio=|HTTPREQUEST-LIBRE .ag needs to be corrected to .ag|whois.nic.ag|NOT FOUND .com.ag|whois.nic.ag|NOT FOUND .org.ag|whois.nic.ag|NOT FOUND .net.ag|whois.nic.ag|NOT FOUND .nom.ag|whois.nic.ag|NOT FOUND I'm still looking for .ht, .ms, and relieable .cn and .hk. If anyone has them, please post.

I noted a problem once we upgraded to 4.3.1, our .co.za domains checker stopped working. If you have this problem remove the http:// from the whois server URL: eg: change .co.za|http://whois.co.za/cgi-bin/whois.sh?Domain=|HTTPREQUEST-Match: No Matches to .co.za|whois.co.za/cgi-bin/whois.sh?Domain=|HTTPREQUEST-Match: No Matches This seems to affect all whois searches to URLs for HTTPREQUEST

Does this work in 4.3.1? I can't seem to get it working.

Okay so the following whois shipped with WHMCS are correct (but don't seem to work all the time). .cn, .hk I'm still looking for the following, if anyone finds them please post them: .ms, .cm, .ua, .fi, and a whois workaround for .gr I've added the following: .hu|whois.nic.hu|Nincs találat / No match .co.hu|whois.nic.hu|Nincs találat / No match .hn|whois2.afilias-grs.net|NOT FOUND .net.hn|whois2.afilias-grs.net|NOT FOUND .com.hn|whois2.afilias-grs.net|NOT FOUND .org.hn|whois2.afilias-grs.net|NOT FOUND .mn|whois2.afilias-grs.net|NOT FOUND .pe|kero.yachay.pe|El dominio no está registrado .nom.pe|kero.yachay.pe|El dominio no está registrado .net.pe|kero.yachay.pe|El dominio no está registrado .com.pe|kero.yachay.pe|El dominio no está registrado .org.pe|kero.yachay.pe|El dominio no está registrado .mu|whois.nic.mu|Not Registered .org.mu|whois.nic.mu|Not Registered .com.mu|whois.nic.mu|Not Registered .net.mu|whois.nic.mu|Not Registered

This seems to work .mn|whois2.afilias-grs.net|NOT FOUND

Hello Grzesiu, I think this not caused by the ispapi-domainchecker.php file. It is not happening on my site.

In response to my previous post, there is a wiki that you can get to if you can navigate the Hexonet platform (I find it confusing): GO to TOOLS => Support Center => Support Wiki. And the server info is at: http://hexonet.net/price-list.php?location=world (No HST/GST) http://hexonet.net/price-list.php?location=europe (With HST) Scroll to the bottom. Sorry about my privious posting but I do find the Hexonet interface far less easy to navigate than others I've used. Rhyzio

Hi Jens @ Hexonet, Thanks that solved it; Arabic, Chinese, Japanese, Hebrew, Telugu ... all seem to be 100%. I recommend this mod/company to anyone lurking for IDN support. Jens, since Hexonet seems to be actively working towards better WHMCS integration, can I suggest a couple things (in the spirit of constructive critisim): 1) Modify this module to allow for the customer to sign up for your trustee service if they don't qualify for the domain. Right now I have to manually sign them up after the fact. This would need to be an addon with a domain so I don't know if it's even possible, but if it is ... si vous plez. 2) Related to the above, add a method for users (my company, not our customer), to add an address in the backend so we can offer our own local admin in a country, provided we have one. 3) A module to auto setup SSL, like the Enom module. 4) A module to support auto setup of your VPS & DS. Also, much better info on your VPS & DS. I can't find the cost / specs ratio anywhere on your site, either logged in to logged out. 5) More info on your site, I realise that your established customers may already know what you're selling, but it seems like you're trying to recruit a few new customers, and I find your minimalist approach to documentation frustrating. That being said; I do recommend this company to anyone looking. I do deal with companies that are a lot less responsive, and have less documentation (although I'd rather not). Thanks, Scott, Rhyzio

Thanks for the quick response tsiedsma, I regards to your post from July 14: "...moving forward with an HTTP AP..." Do you know when that will take effect? Will it affect the email issue (the RS account needing to email customers)?