Feature Requests
Share ideas, discuss and vote on requests from other users in community
 
This object is in archive! 

Asynchronous Domain Registration

Anonymous shared this idea 7 years ago
Under Consideration

I'm using a registrar that uses an Asynchronous system, so whenever I

send a Register, Renew or any other request, a successful answer

actually means "we have received your request and you'll get an email

with the right answer".

the problem is, that WHMCS sees that successful message as an end to the

process, which sends confirmation emails (i.e "domain successfully

registered"), which isn't exactly true in an asynchronous case.

it'd be good to have a way to send an email saying "the request was sent

(to the registrar), and you'll get a reply when successfully

processed".

yes, I know the email template can be changed as such, but then for a

real synchronous registrar the email would be wrong, since the

successful message does indicate a successful (finished) process.

Comments (4)

photo
1

I find it hard to believe no one works with an asynchronous registrar.

WHMCS must have some sort of support for this...

photo
1

mtk wrote:

I find it hard to believe no one works with an asynchronous registrar.

WHMCS must have some sort of support for this...

I work at http://www.ascio.com and we have asynchronous orders with polling and HTTP-GET Callback. That makes realtime monitors possible although WHMCS doesn't really use it yet. Still I will try to implement it, so that the status switches without reload.

Here is our plugin:

https://github.com/rendermani/ascio-whmcs-plugin

(The hooks.php sets the domain pending. The Polling/Callbacks make it active in case there is no error.)

The WHMCS plugin is open-source.

photo
1

Manuel, I have downloaded your modules and changed a little bit, I have a problem though, when I try to set contacttype (I have to do this for .dk domains) it is not set.

How do I extend your module to work with contacts?

Regards,

Scott

photo
1

Well I actually figured it out, I was using a wrong field name.