[Web Drive Module]

Hey there
 
I'm in the process of building a module for Web Drive, the most used domain reseller platform in New Zealand. I've got a few questions about the programming conventions.


 
The Web Drive API is XML-RPC (not documented properly either  ) so it's a bit different than the existing modules.
 
Now for the commands/webdrive_something files, it looks like almost all the other modules take a $vars array and call the API without any type casting or other logic. As the Web Drive API is using XML-RPC which is more strongly typed than PHP I need to do stuff like xmlrpc_set_type($date, 'datetime'); Is that the right place to do that sort of stuff? Or should I be doing that in the main Webdrive module class?
 
Another thing is that the API requires different authentication for each method, either the api key and password, or the api key, password and sub account name. I have decided to not use a magic method in commands/webdrive_all, and instead write each method which specifies the auth type when calling $this->api->submit(). Is this the best way, or again is this better in the main Webdrive module class?

[Several Questions]

Welcome to the community, 

 

1) You can only use one module however you might be able to use more than one if you have like .com (Logicboxes) and then .com (Nother registrar).

 

2) You can set nameservers on the domain package. eg: .COM (ns1.domain.com & ns2.domain.com) .NET (ns3.domain.com & ns4.domain.com)

 

3) There isn't yet however you could do a promotion code for yearly plans.

 

Xero (Not yet)

WebDrive (Not yet)

TPPWholesale and Ghandi (Not yet and Not yet)

Comodo SSLs (You can via GoGetSSL or TheSSLStore)

FreshDesk (Not yet, you can ask them direct)

CoinJar (Not yet, but you could try BitPay)

Swipe (Not yet, but you could try Stripe)

PayPal Express Checkout (Not yet but Blesta supports PayPal and PayPal Pro)

 

Hope this helps. Feel free to open a feature request for items you need and maybe if enough votes are got, the guys might add them to their list, but the guys will know more about this to help you.

 

Thanks for the answers

1. I thought as much regarding the multiple registrars. One radio for NZ and the other for gTLDs could work.  I might see if I could develop a page where you can add each domain and select which registrar would be used for each like boxbilling has.
2. Ok, that seems fine
3. That would probably be alright as well

Regarding all those modules/plugins I mentioned, I would be developing them myself (won't get all of them done before I start). I do similar stuff as an OpenCart dev. I'll have a look at the SSL stores mentioned.

[Several Questions]

I'm looking at using Blesta for my hosting company I'm launching soon. I have a few questions:

1. Is it possible to set up multiple registrars and choose which registrar each tld will be registered with?
2. Also can different nameservers be set by default for each registrar when doing the above?
3. Is there any way to give a free domain with the purchase of an annual hosting plan?

If I choose to use Blesta I will be integrating several services/products

• Xero (accounting)
• Webdrive (NZ domains)
• TPPWholesale or Ghandi? (gTLD domains)
• Comodo? (SSL certs)
• Freshdesk (Tickets, forums, chat, knowledgebase)
• Coinjar (bitcoin payments)
• Swipe HQ (NZ recurring credit card payments)
• Paypal express checkout (think that's the one, recurring payments via API)

[Coinbase - Bitcoin Merchant]

It sounds like coinbase is a hosted bitcoin wallet. It's like keeping your money in the bank, except that bitcoins are not insured, and hackers have breached and stolen a lot of bitcoins in the past.

 

I'd be cautious, and suggest that you don't store too many coins in an online wallet. 

 

I'd agree that it's not a good idea to keep most of your bitcoins on an online wallet (blockchain.info is an exception because it works differently), but just wanted to note that coinbase is often used to immediately exchange bitcoins received for USD just like Bitpay.