Jump to content

Registrar module for HEXONET


hexonet

Recommended Posts

  • 4 weeks later...
  • Replies 60
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

  • 4 weeks later...

Hi,

 

ispapi-domainchecker.php

 

every time I make a search I get this message

There was an error in your request

 

More Choices

 

Domain Name Status More Info

X hejmeddigharvidetgodt.com Unavailable WWW WHOIS

X hejmeddigharvidetgodt.net Unavailable WWW WHOIS

X hejmeddigharvidetgodt.org Unavailable WWW WHOIS

 

and the WHOIS shows only

 

WHOIS Results for hejmeddigharvidetgodt.com

 

Close Window

 

Best regards,

Link to comment
Share on other sites

  • 3 weeks later...
  • 2 weeks later...
  • 1 month later...

Hi Hexonet

 

I registered an account in Hexonet today. But I think the implementation process is confusing.

 

1. I have found Hexonet through WHMCS´ registrar module, then have googled it

2. I went to hexonet.net and have opened an account for the RegistrarOC

3. I have got an email to access the cp.hexonet.net

4. I have been to the Control Panel and figured out how to configure (and I am not sure if it was correct) and paid $15 to make a test.

5. Then I went to the WHMCS setup/registrars, choosen Hexonet, wrote the login and password

6. I thought it was so easy! Then I have simulated a real transaction (I need to buy a domain anyway)

7. It was not possible to register via WHMCS

8. Then I have researched in WHMCS and in your own wiki ISPAPI Registrar Module (https://wiki.hexonet.net/wiki/Downloads)

9. There I have found out I must download Ispapi_whmcs-0.9.3 and followed the instruction in the readme.txt. I did!

10. Now I am stucked in the follow error when tried to register a .dk TLD:

 

"An Error Occured

Missing required attribute; OWNERCONTACT MUST HAVE VATID FOR ORGANIZATION"

 

11. What to do?

 

 

Sorry about what I have said before" I think the implementation process is confusing.". And please, dont think it´s bad, but please see it as a suggestion to write something step by step focused to WHMCS (if there is one, I couldn´t find easilly).

 

Your fabulous work done by Hexonet must not be ofuscated by a such thing. Again, it´s positive what I have witten!

 

Can you please help me? I would appreciate it!

 

Best regards,

 

Fabio W. Neves de Brito

gefuso [.] com

Link to comment
Share on other sites

Hi Hexonet!

 

I did not understand how I can display additional domain fileds in WHMCS order form. I have istalled ISPAPI but in order form I can't see any additional fields. For example, with italian TLD (.it) The system display in order form only "VAT ID" field (already displayed with hexonet WHMCS standard register module) but don't display the other mandatory fields requested by italian NIC . Then I can't register this TLD by ISPAPI.

Could you help me?

Thanks in advance

Link to comment
Share on other sites

Did you use our additionaldomainfields.php?

It defines the fields for .it as follows:

 

## .IT DOMAIN REQUIREMENTS ##

 

$additionaldomainfields[".it"] = array();

 

if ( $ispapi_use_it_trustee_service ) {

 

$additionaldomainfields[".it"][] = array(

"Name" => "Local Presence",

"Type" => "dropdown",

"Options" => ",Registrant is domiciled in the EU (PIN required),Use Local Presence Service",

"Default" => "",

"Required" => "true",

 

"Ispapi-Name" => "X-IT-ACCEPT-TRUSTEE-TAC",

"Ispapi-Options" => ",,1"

);

 

$additionaldomainfields[".it"][] = array(

"Name" => "PIN",

"Type" => "text",

"Size" => "30",

"Default" => "",

"Required" => false,

 

"Ispapi-Name" => "X-IT-PIN",

);

}

else {

 

$additionaldomainfields[".it"][] = array(

"Name" => "Local Presence",

"Type" => "dropdown",

"Options" => ",Registrant is domiciled in the EU (PIN required)",

"Default" => "",

"Required" => "true",

);

 

$additionaldomainfields[".it"][] = array(

"Name" => "PIN",

"Type" => "text",

"Size" => "30",

"Default" => "",

"Required" => true,

 

"Ispapi-Name" => "X-IT-PIN",

);

}

 

$additionaldomainfields[".it"][] = array(

"Name" => "Section 3 - Declarations and assumptions of liability",

"Type" => "dropdown",

"Options" => ",Accepted",

"Default" => "",

"Required" => "true",

 

"Ispapi-Name" => "X-IT-ACCEPT-LIABILITY-TAC",

"Ispapi-Options" => ",1"

);

 

$additionaldomainfields[".it"][] = array(

"Name" => "Section 5 - Consent to the processing of personal data for registration",

"Type" => "dropdown",

"Options" => ",Accepted",

"Default" => "",

"Required" => "true",

 

"Ispapi-Name" => "X-IT-ACCEPT-REGISTRATION-TAC",

"Ispapi-Options" => ",1"

);

 

$additionaldomainfields[".it"][] = array(

"Name" => "Section 6 - Consent to the processing of personal data for diffusion and accessibility via the internet",

"Type" => "dropdown",

"Options" => ",Accepted",

"Default" => "",

"Required" => "true",

 

"Ispapi-Name" => "X-IT-ACCEPT-DIFFUSION-AND-ACCESSIBILITY-TAC",

"Ispapi-Options" => ",1"

);

 

$additionaldomainfields[".it"][] = array(

"Name" => "Section 7 - Explicit acceptance of the following points",

"Type" => "dropdown",

"Options" => ",Accepted",

"Default" => "",

"Required" => "true",

 

"Ispapi-Name" => "X-IT-ACCEPT-EXPLICIT-TAC",

"Ispapi-Options" => ",1"

);

 

 

$additionaldomainfields[".it"][] = array(

"Name" => "Registrant is Admin-C",

"Type" => "dropdown",

"Options" => "Accepted",

"Default" => "Accepted",

"Required" => "true",

"Ispapi-Eval" => 'unset($command["ADMINCONTACT0"]); $command["ADMINCONTACT0COPY"] = "OWNERCONTACT0";'

);

Link to comment
Share on other sites

ISPAPI.php includes the additionaldomainfields.php, as it uses user-configurable mappings from WHMCS additional parameters to our API. This is our solution to permit changes to additional parameters, without updating the module itself.

 

To have the additional parameters show up in the order flow, you need to insert or include the additionaldomainfields.php into your WHMCS-wide file. E.g., as the README.TXT proposes:

...

additionaldomainfields.php:

===========================

You can use in the registrar module's additionaldomainfields.php by adding the following command to includes/additionaldomainfields.php:

 

include dirname(__FILE__).DIRECTORY_SEPARATOR

."..".DIRECTORY_SEPARATOR

."modules".DIRECTORY_SEPARATOR

."registrars".DIRECTORY_SEPARATOR

."ispapi".DIRECTORY_SEPARATOR

."additionaldomainfields.php";

Link to comment
Share on other sites

Hi Hexonet,

 

I've another question.

 

I am testing .it domains registration by ISPAPI.

 

I get the following error from register:

 

"Data management policy violation; Registrant: registrant with the entity type = 1 and admin are different"

 

I get this error only if leave blank company name field in WHMCS order form using.

 

The registration process is ok if I put a name in company name field.

 

Have you tested ISPAPI in this condition?

 

Thanks in advance

Link to comment
Share on other sites

Hi forcontacteu,

 

it should work when using this in additionaldomainfields.php:

 

$additionaldomainfields[".it"][] = array(

"Name" => "Registrant is Admin-C",

"Type" => "dropdown",

"Options" => "Accepted",

"Default" => "Accepted",

"Required" => "true",

"Ispapi-Eval" => 'unset($command["ADMINCONTACT0"]); $command["ADMINCONTACT0COPY"] = "OWNERCONTACT0";'

);

Link to comment
Share on other sites

  • 1 month later...
  • 2 weeks later...

It would be great if the EPP code could be displayed right from WHMCS and the contact management side could be improved by using profiles and checkboxes to re-use previously entered information, but maybe this is a WHMCS limitation.

 

And also, it would be great if we could use one additionaldomainfields.php per language.

 

Regarding the importer, I wish we could select which user to import the domains to.

Edited by interfasys
Link to comment
Share on other sites

  • 1 month later...

Hi,

 

just released a new version of our ISPAPI module: 0.9.4:

 

- support for full WHOIS privacy service - http://www.WHOISTRUSTEE.com

- bugfix for additionaldomainfields.php

- support included for .ca, fix for .it

- options for automatic local presence service: .fr

- support for API HTTP proxy, used for secure high performance setups

- basic auto-setup of DNS zone for new registrations

 

Our new whois privacy service is fully compliant to section 3.4 (Retention of Registered Name Holder and Registration Data) of the ICANN RAA from May 21, 2009; our RDE dumps include the original registrant and contact information.

 

Best,

-jens

ispapi_whmcs-0.9.4.zip

Link to comment
Share on other sites

  • 3 months later...

Hi,

 

just released a new version of our ISPAPI module: 0.9.5

 

- new improved ispapisync.php script

- successful transfers now complete automatically (incoming and outgoing)

- automated registrar transfer to usertransfer fallback

- support for .fr trustee service (additionaldomainfields.php)

- support for .jobs

- code cleanups

 

Also released an updated SSL cert module, which supports WHMCS >= 4.5

 

Best,

-jens

ispapi_whmcs-0.9.5.zip

ispapissl_whmcs-0.9.5.zip

Link to comment
Share on other sites

  • 2 months later...
  • 3 weeks later...
  • 3 months later...

Hi,

 

just released a new version of our ISPAPI module: 0.9.6

 

- full support for WHMCS 5

- WHOIS Privacy / ID Protection can now be toggled in Admin area

- new WHOIS Privacy / ID Protection management in Client area

- corrections to make new WHMCS 5 bulk updates work correctly

- field name changes for WHOIS contact information to new standard

- code cleanups

 

The README file is now available in PDF format:

http://www.hexonet.net/files/whmcs/ispapi/README.pdf

 

Full module can be downloaded here:

http://www.hexonet.net/files/whmcs/ispapi/ispapi_whmcs-0.9.6.zip

 

Best,

-jens

Link to comment
Share on other sites

  • 10 months later...

New version available: 1.0.0

 

- full support for WHMCS 5.1

- supports WHMCS handling of IDNs, uses IDNA2008 if supported by tld

- supports new _Sync method to sync expiration/next due dates

- supports new _TransferSync method to finish transfers

- old sync method (ispapisync.php) got deprecated

- explicit domain deletions via _RequestDelete in admin panel

- new module logging via logModuleCall

- fix for authorization failed error on transfer request

 

 

The README file is now available in PDF format:

https://www.hexonet.net/files/whmcs/ispapi/README.pdf

 

Full module can be downloaded here:

https://www.hexonet.net/files/whmcs/ispapi/ispapi_whmcs-1.0.0.zip

 

Best,

-jens

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated